pinkpanther56
Technical User
Hi all
We are using WDS to deploy XP clients but have just come across an odd issue.
We have 50 PC's with Intel D945GCCR mainboards and these all build perfectly, one of them recently failed and had a slightly newer mainboard installed D945GCNL. This board has slightly different drivers so we added them to the image but each time i build the box after copying the files from the network it reboots to start the Windows install and errors saying (File corrupt or missing \system32\hal.dll). To get around this i have to disable the “Core Multiplexing Technology” option in the BIOS and boot the PC, this install then completes with all of the correct drivers i can then enable CMT and the system seems fine.
We have an XP SP2 and SP3 image and they both do the same, the images are flat file images so essentially just a network copy of the windows CD they are not hardware specific RiPrep images and work on a range of our clients but this is the only PC that shows this issue.
We have tried a different hard disk, memory and CPU from an identical system and it’s the same so we’re pretty sure it’s the slightly different mainboard.
Has anyone come across this issue?
Cheers.
We are using WDS to deploy XP clients but have just come across an odd issue.
We have 50 PC's with Intel D945GCCR mainboards and these all build perfectly, one of them recently failed and had a slightly newer mainboard installed D945GCNL. This board has slightly different drivers so we added them to the image but each time i build the box after copying the files from the network it reboots to start the Windows install and errors saying (File corrupt or missing \system32\hal.dll). To get around this i have to disable the “Core Multiplexing Technology” option in the BIOS and boot the PC, this install then completes with all of the correct drivers i can then enable CMT and the system seems fine.
We have an XP SP2 and SP3 image and they both do the same, the images are flat file images so essentially just a network copy of the windows CD they are not hardware specific RiPrep images and work on a range of our clients but this is the only PC that shows this issue.
We have tried a different hard disk, memory and CPU from an identical system and it’s the same so we’re pretty sure it’s the slightly different mainboard.
Has anyone come across this issue?
Cheers.