I have not found a fix. I have tried many different inf files and I have completely formatted and reloaded the computer at least 4 times trying to get around this problem. I also imaged a brand new D610 before it has ever been booted for the first time and looked at what Dell has in their sysprep folder. You may want to try this, you will find it interesting to say the least. Dell has included several fixes that load during sysprep. Until Dell tells us what to do I suppose we just wait the extra 5 minutes per computer?
What I have discovered is that if I leave out the Intel Wireless NIC Drivers, my sysprep install will complete. I still get the hang ... for about 5 minutes. If I have the Intel Wireless NIC drivers included, then the hang turns into a permanent "freeze" and the WiFi LED is illuminated. I have downloaded the latest drivers from Dell (and can even install them manually with no problems). It has made no difference.
I have found that removing the files USBPORT.INF and USBPORT.PNF from the C:\windows\inf folder my workstation images (syspreped image) will load with out hanging.
There is an obvious problem with this approach though and that is that the USB core devices are represented as question marks in the device manager. Also when I try and put this INF file back in the system in order to activate the USB devices, it will lock up the laptop.
The point here is that while this is not a solution to the problem, it is sort of telling as to what the problem might be. This is a MS provided INF file. I will be opening a call with them soon on this issue.
Upgrading the BIOS to A03 solved my issues with the WiFi light illuminating and the entire system freezing up. As it happens to be, the readme that accompanies the A03 BIOS update states that changes were made to accomodate "non standard operating system configurations" ... ie - a custom sysprep'ed image that didn't come from Dell.
It looks like the problem on my end is definitely the wireless card drivers. If you leave these out of the image and then add them back after image load it is fine.
If you will ghost a D610 that is brand new before you ever bot it and look at what all Dell has done with their sysprep you may find yourself surprised. Browse through the sysprep folder on that factory image. There is a usbfix that is loaded there but I can't figure out exactly what it does. They are loading several "fixes" during mini-setup.
gr67
2 Posts
0
May 24th, 2005 13:00
Tommy_Hlfgr
14 Posts
0
May 24th, 2005 13:00
CommCtr
2 Posts
0
May 26th, 2005 18:00
Ditto to the problem.
What I have discovered is that if I leave out the Intel Wireless NIC Drivers, my sysprep install will complete. I still get the hang ... for about 5 minutes. If I have the Intel Wireless NIC drivers included, then the hang turns into a permanent "freeze" and the WiFi LED is illuminated. I have downloaded the latest drivers from Dell (and can even install them manually with no problems). It has made no difference.
defiant998
1 Message
0
June 8th, 2005 17:00
I have found that removing the files USBPORT.INF and USBPORT.PNF from the C:\windows\inf folder my workstation images (syspreped image) will load with out hanging.
There is an obvious problem with this approach though and that is that the USB core devices are represented as question marks in the device manager. Also when I try and put this INF file back in the system in order to activate the USB devices, it will lock up the laptop.
The point here is that while this is not a solution to the problem, it is sort of telling as to what the problem might be. This is a MS provided INF file. I will be opening a call with them soon on this issue.
Could someone verify this result??
CommCtr
2 Posts
0
June 8th, 2005 18:00
gr67
2 Posts
0
June 8th, 2005 18:00
Tommy_Hlfgr
14 Posts
0
June 8th, 2005 22:00
MarkT1891
12 Posts
0
July 5th, 2005 11:00
I had a similar problem with the D410. I too thought it related to the Wifi drivers as the light illuminated and then mini setup stopped.
After looking at setupapi.log I discovered that the issue related to the video driver install. The following fix from MS addresses the issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;883667
The problem is due to the .inf file in the video driver not containing information for child devices (like monitors).
Mark.