Sysprep / Imaging problem

[Brian O'Neill]

I've been getting this problem with trying to create one XP image for
different hardware platforms. An example is a HP VL400 and Compaq EVO d51s.
I've started with teh lowest common denominator and we have a VL400 image.
I update this, sysprep it with just the reseal option selected and use PQ
image centre to store the image on a network share.

When I put this image on a D51s, I get a message on first boot up (shortly
after the 'moving' Windows XP graphic appears) saying 'A problem has been
detected and windows has been shutdown to prevent damage to your computer.'
It goes on about recommending the disbaling of AV, doing a chkdsk etc. At
the bottom of this BSoD, I have 'STOP 00000024: (0X001901FE, 0X80F47008,
0XC0000102, 0X00000000). The PC will not now boot into XP.

I've been researching this and I've confirmed that when XP is installed,
both are using the same HAL (Under file version...original
name...halacpi.dll). I've seen recommendations for similar issues to 'just
install drivers for all H/W types' - without any instructions for how this
might be done. I tried to manually include drivers for the D51s IDE
controller into the sysprep.ini after sysprep -bmsd option (putting .inf,
..sys and .cat in seemingly reasonable locations) and when the reseal was
happening, it looked like it found them (unsigned driver message that never
appeared before I tried to manually include these drivers.

I checked and all power mgt stuff is now enabled in the BIOS on the D51s and
it still fails.

One final confusing thing is that we have a base image that will work on
both hardware platforms. When I update this and reseal it, it only works on
the H/W it was created on.

Can anybody offer a solution or way to do this?

 

[Bill Curtis [MSFT]]

You have some sort of filter driver sandwiched in with NTFS.SYS (hence, the
stop 0x24). I would check and make sure that you have removed any
CDBurning software/Antivirus/3rd Party backup software and try it again.

- Bill Curtis [MSFT]
“This posting is provided "AS IS" with no warranties, and confers no
rights.”

 

[newbie]

I am also facing similar problem... i am interseted to
know how the base image was made compatible? I tried that
option also but it was unsuccessful attempt.
If you have solution for this can you elaborate:
"I've seen recommendations for similar issues to 'just
install drivers for all H/W types' - without any
instructions for how this
might be done. I tried to manually include drivers for
the D51s IDE
controller into the sysprep.ini after sysprep -bmsd option
(putting .inf,
...sys and .cat in seemingly reasonable locations)"


thanks
newbie

 

[George Ellis]

We support the 510 and 420 (the 400 follow-on). Don't load any of the
HP/Compaq software before imaging and start with your own copy of the OS
(not that you are).

Tip 2 - When the system builds the partition on your source, do not use
quick format for NTFS so that it will check the drive.

This will cover HP and Compaq Mass Storage:
[SysprepMassStorage]
;Intel IDE controllers from MS
PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2441=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_244A=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_244B=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_248A=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_248B=C:\pnp\ich3ide.inf
PCI\VEN_8086&DEV_24C1=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_24CB=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_24CA=%systemroot%\inf\mshdc.inf
;PCI\VEN_8086&DEV_24D1=C:\pnp\ich5ide.inf
;PCI\VEN_8086&DEV_24DB=C:\pnp\ich5ide.inf

Note that the last two (commented out) are required for the 530. For the
530, you will need a new image as it requires the APIC ACPI HAL.

[Unattended]
UpdateUPHAL=ACPIAPIC_UP,%systemroot%\inf\hal.inf

But, this will not work on any of the notebooks using ICH3-M.

But yes, a stop 24 is out of NTFS.DLL and means your NTFS partition is
having issues.