What I have yet to try is install Windows XP SP3 ontop of the existing installation OR make a new image just for this model, which is what I would least like todo, mainly because I have just got down to just 2 images that is deployed across our entire range of PC's(30'ish models). I have only seen this 2-3 times out of the 30 or so times I've experienced this error. When the PC is resumed from hibernation, the cable network adapter may or may not show as disconnected, even tho it has connectivity with the rest of the world. I have also experienced that on the first login, the PC can hang when I reach the desktop which then needs a hard reboot using the powerbutton to fix. When I then terminate that process and lets it continue the shutdown, there is a 50% chance that it actually also will lock up at "Closing all network connections." (the dialogs are translated from the Norwegian XP we use). It wont shut down(as in power off), it will sit as if idle for around 5 to 10 mins, before popping up with 1 of 2 dialogs, either "Connections Tray" or "PersistWndName" is not responding. The main problem arises if I take the PC to hibernation, wake it up then try to shut it down. The automatic installation works fine, I can log in and work on it just fine. I am deploying the same image to the Dell Latitude 2100 as I use on Dell Latitude E5400, E5500, E6400 and E6500, which is a patched XP Pro SP2 Norwegian image with SATA AHCI and RAID support and ACPI_MP for processor. So far this has been going great, untill I met the Dell Latitude 2100. I am responsible for the sysprepped images at my office, for our standard computers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |