Custom Image on Latitude E6400

Are you trying to load a custom XP image from an incompatible or non Dell unit onto your new machine? Did this machine originally have Vista on it when you did?

 

In short, I think your network driver isn't compatible.

 

Most of the software drivers that were used in older network image transfers were optimized for the Win95/98 days and XP doesn't initially support this function unless you have a network license. You can force it to work, but it typically still uses these older drivers to run in the DOS mode ignoring the XP install UI. Most newer motherboards that use Vista will not run in the older format and drivers are incompatible causing system hangs. Because you are using a custom image that is optimized for one specific hardware configuration it isn't optimized for a Vista optimized hardware config, and is the crux of where I believe your issue arises.

 

This is a more recent example of the issue but it appears that you are trying to use a custom image from another machine that was optimized for a specific configuration and the configuration is in conflict with the hardware. I am assuming that the image is originally from a different configuration and its configuration is in conflict with the machine. You would find this same issue upon boot up if you did something as simple as swapped HDD rather than tried to upload an image. You might have to start fresh with this one.

 

When doing network installation of OS images I have always had images of motherboard configurations as the simplest difference can cause the information to become corrupted as the network drivers don't cover all bases and allow information to flow unimpeded from network image to destination. One of the easiest fixes was to have a modified boot disk with the information needed to allow a data transfer like this, so check your network driver as it may not have a 'boot' mode built in to the version of software you are using without having to force it.

Mine freezes while installing video driver:

 

[2008/11/03 05:02:36 632.259 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2a42&subsys_02331028&rev_07,pci\ven_8086&dev_2a42&subsys_02331028,pci\ven_8086&dev_2a42&cc_030000,pci\ven_8086&dev_2a42&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2a42&rev_07,pci\ven_8086&dev_2a42,pci\ven_8086&cc_030000,pci\ven_8086&cc_0300,pci\ven_8086,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#I022 Found "PCI\VEN_8086&DEV_2A42&SUBSYS_02331028" in C:\DRIVERS\CACHE\E6400\VIDEO\kit14865.inf; Device: "Mobile Intel(R) 4 Series Express Chipset Family"; Driver: "Mobile Intel(R) 4 Series Express Chipset Family"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "iCNT0".
#I023 Actual install section: [iCNT0]. Rank: 0x00000001. Effective driver date: 06/27/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [iCNT0] in "c:\drivers\cache\e6400\video\kit14865.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "PCI\VEN_8086&DEV_2A42&SUBSYS_02331028&REV_07\3&61AAA01&0&10".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [iCNT0.Interfaces] from "c:\drivers\cache\e6400\video\kit14865.inf".
#I054 Interfaces installed.
[2008/11/03 05:02:39 632.882 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2a42&subsys_02331028&rev_07,pci\ven_8086&dev_2a42&subsys_02331028,pci\ven_8086&dev_2a42&cc_030000,pci\ven_8086&dev_2a42&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2a42&rev_07,pci\ven_8086&dev_2a42,pci\ven_8086&cc_030000,pci\ven_8086&cc_0300,pci\ven_8086,pci\cc_030000,pci\cc_0300
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2a42&subsys_02331028&rev_07,pci\ven_8086&dev_2a42&subsys_02331028,pci\ven_8086&dev_2a42&cc_030000,pci\ven_8086&dev_2a42&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2a42&rev_07,pci\ven_8086&dev_2a42,pci\ven_8086&cc_030000,pci\ven_8086&cc_0300,pci\ven_8086,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I022 Found "PCI\VEN_8086&DEV_2A42&SUBSYS_02331028" in c:\windows\system32\drvstore\kit14865_8ccdc8096fb7d1a911e28f62720f0f0cf7e748ed\kit14865.inf; Device: "Mobile Intel(R) 4 Series Express Chipset Family"; Driver: "Mobile Intel(R) 4 Series Express Chipset Family"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "iCNT0".
#I023 Actual install section: [iCNT0]. Rank: 0x00000001. Effective driver date: 06/27/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [iCNT0] in "c:\windows\system32\drvstore\kit14865_8ccdc8096fb7d1a911e28f62720f0f0cf7e748ed\kit14865.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
[2008/11/03 05:02:40 632.1025]
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2a42&subsys_02331028&rev_07,pci\ven_8086&dev_2a42&subsys_02331028,pci\ven_8086&dev_2a42&cc_030000,pci\ven_8086&dev_2a42&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2a42&rev_07,pci\ven_8086&dev_2a42,pci\ven_8086&cc_030000,pci\ven_8086&cc_0300,pci\ven_8086,pci\cc_030000,pci\cc_0300
#I022 Found "PCI\VEN_8086&DEV_2A42&SUBSYS_02331028" in c:\windows\system32\drvstore\kit14865_8ccdc8096fb7d1a911e28f62720f0f0cf7e748ed\kit14865.inf; Device: "Mobile Intel(R) 4 Series Express Chipset Family"; Driver: "Mobile Intel(R) 4 Series Express Chipset Family"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "iCNT0".
#I023 Actual install section: [iCNT0]. Rank: 0x00000001. Effective driver date: 06/27/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [iCNT0] in "c:\windows\system32\drvstore\kit14865_8ccdc8096fb7d1a911e28f62720f0f0cf7e748ed\kit14865.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_8086&DEV_2A42&SUBSYS_02331028&REV_07\3&61AAA01&0&10".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [iCNT0.Interfaces] from "c:\windows\system32\drvstore\kit14865_8ccdc8096fb7d1a911e28f62720f0f0cf7e748ed\kit14865.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_8086&DEV_2A42&SUBSYS_02331028&REV_07\3&61AAA01&0&10".

We just received a few E6400's and also ran into the issue with the battery.  I applied our image (with injected drivers and modified oempnp driver path in the sysprep.inf file) and they froze exactly as you described.  I removed the batteries and tried again and they built without any other problems.  Once the imaging was complete I put the batteries back in and had no further issues.  I reached out to a few of our Dell reps who said no one has reported this to them yet.  If anyone else is experiencing this I suggest escalating to your Dell reps.  If enough of us are experiencing this issue perhaps a fix can be released.

 

Regards...Corey

 

corey.bergman@amerigas.com

such a simple fix...

Its almost mind numbing. Thanks for the info!

Sorry I haven't responded yet but I had a hard time finding my own posting.  It was moved on me and that was it.  I had opened a ticket with Microsoft and he pointed me to my original post.  Pretty funny.  But I made some progress with this issue on my own.  I received a E4300 the other day and before trying to put my image on it, I copied the drive using ghost.  I then booted it up and had a look.  I found that the C:\windows\inf\battery.inf was the same version but had a different time stamp on it.  I also noticed that c:\windows\system32\batt.dll had a similar time stamp.  So I tried overwriting the files on my base image with these current files.  Battery.inf went fine but windows protection restored the older batt.dll.  Since I am using SCCM, I put in a task to overwrite the batt.dll after the image is laid down but before it boots into mini-setup.  Gave it a try and Bingo, it worked!