BSOD WinPE 2.0 & Win XP SP2 & Winnt32.exe

[ti1765]

Folks,

We've been working on this issue for several weeks and still stuck let me explain

- Doing scripted install using WinPE 2.0 on HP Hardware, this didn't work initially until we added the Mass storage drivers section to Unattend.txt, scripted install

completed fine. Got around the uber bug using the fixboot.reg and also the bootsect /nt52 c: /force

- I'm running sysprep of this install and noticed that when adding the

[sysprep]

BuildMassStorageSection=Yes

in sysprep.ini it does not include all mass storage drivers that I want to have added, to support other hardware using this image. When I do caputre of the image using ImageX, all seems fine

- If I try to deploy this image to other hardware right after the image is applied and workstation reboots the first time in Windows I get nice BSOD, don't get chance

to see the error message, but if boot Windows in Safe mode, it get stuck at mups.sys (That's where it reboots), is't during the load of that sys file or the next one

no idea.

- If I do scripted install on other Hardware that does not have mass storage device drivers, then it does seem to work fine, scripted as well as imaged install (using wim file)

If I try to use or older procedure which was combination of Dos boot diskett together wtih GHOST I do not have any issues, even applying images created on HW withouth Mass storage drivers, but setup sysprep to include these drivers, I'm able to apply that Ghost file to anoter device which has mass storage drivers. We try

to move away from this Dos/Ghost approach and use WinPE togeher wtih ImageX. Even in this approach I did not have to add the mass storage drivers separatly

Questions:

on the BSOD, does anybody know of switch I can apply to do some extensive logging so I have idea where it's failing, we have foreseen the hal detect approach, from looking on the web, using option to change the hal based on the result of the type and also check on #processors.

Anybody has good experience using WinPE2.0 & WinXP SP2 & Winnt32.exe we noticed from testing that Winnt32.exe might have different behaviour then Winnt16.exe

ANy suggestions, or ideas are welcome.