Windows XP image goes to BSOD 0x0000007B on every model with IDE hard drive.
I have 4 different computer models, all equepted with IDE-hard drive. 3 of them uses Intel Ultra Ata Storage Drives and one is based on Nvidia chipset. I want to make 1 single image of XP, which would apply to all different models. Problem is, that I don't find any suitable drivers to import into mass storage box at Task Sequence. I asked this earlier from a different perspective. I'm thinking, how hard it could be to get this generic .wim image working? Funny thing is, that neither of these computer require pressing F6 and importing drivers. Also, if I install Windows XP from source files using TS, it will work, but not from .WIM.
December 26th, 2010 4:34pm

first of all how are you creating the initial WIM file ? are you doing it on a virtual platform or on real hardware, the former is advised as it will make it hardware agnostic, to add your storage drivers you can apply driver packages with WMI detection for different hardware like in this post My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2010 3:51am

My guess is HAL issues.. try an add this script i wrote to your TS. Michael http://kongkuba1.spaces.live.com
December 27th, 2010 4:02am

first of all how are you creating the initial WIM file ? are you doing it on a virtual platform or on real hardware, the former is advised as it will make it hardware agnostic, to add your storage drivers you can apply driver packages with WMI detection for different hardware like in this post My step by step SCCM Guides I'm on Twitter > ncbrady I'm using model based TS, so this won´t be needed. Last image was created from physical laptop, but I believe storage controllers may vary between the models.
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2010 6:36am

If the problem was storage drivers, the you would not be able to do an installation from source files. Installing from source would how ever set the corrct HAL.. Michaelhttp://kongkuba1.spaces.live.com
December 27th, 2010 7:25am

If the problem was storage drivers, the you would not be able to do an installation from source files. Installing from source would how ever set the corrct HAL.. Michael http://kongkuba1.spaces.live.com So do you mean that your script is answer to my situation? I have not yet started to use MDT2010. Will this .vbs work, if I just add is as command line task to TS?
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2010 7:19pm

If the problem was storage drivers, the you would not be able to do an installation from source files. Installing from source would how ever set the corrct HAL.. Michael http://kongkuba1.spaces.live.com So do you mean that your script is answer to my situation? I have not yet started to use MDT2010. Will this .vbs work, if I just add is as command line task to TS?
December 27th, 2010 7:19pm

If the problem was storage drivers, the you would not be able to do an installation from source files. Installing from source would how ever set the corrct HAL.. Michael http://kongkuba1.spaces.live.com So do you mean that your script is answer to my situation? I have not yet started to use MDT2010. Will this .vbs work, if I just add is as command line task to TS?
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2010 7:19pm

Yes just add the scripts the script to the script folder and call it before "restart computer" in your Postinstall phase. This is however the config manager forum, and to use it with sccm you need to integrate MDT into sccm and cretate a toolkit package Michaelhttp://kongkuba1.spaces.live.com
December 28th, 2010 3:22am

I might solved the problem by adding line BuiltMassStorageList (or something like that) to sysprep after I found this guide: http://www.vernalex.com/guides/sysprep/mass.shtml Now after capturing Win XP without any drivers installed on one model, it does install and run succsessfully on another model. Still on Nvidia based computer it goes to bsod, but now different error code: 0x0000007E (not ..7B).
Free Windows Admin Tool Kit Click here and download it now
January 3rd, 2011 10:53am

I might solved the problem by adding line BuiltMassStorageList (or something like that) to sysprep after I found this guide: http://www.vernalex.com/guides/sysprep/mass.shtml Now after capturing Win XP without any drivers installed on one model, it does install and run succsessfully on another model. Still on Nvidia based computer it goes to bsod, but now different error code: 0x0000007E (not ..7B).
January 3rd, 2011 10:53am

I finally realized what my problem was - I read this article and everything is now clear... almost :) http://www.vernalex.com/guides/sysprep/mass.shtml In this site I found best explanation of mass storage devices and how to use sysprep to get around with mass drivers. Still 1 question - what if I merge.. [Sysprep] BuildMassStorageSection=yes with this: [SysprepMassStorage] *pnp0a00=c:\windows\inf\machine.inf *pnp0a01=c:\windows\inf\machine.inf *pnp0a04=c:\windows\inf\machine.inf *pnp0a03=c:\windows\inf\machine.inf pci\cc_0604=c:\windows\inf\machine.inf +++ list continues for long [Sysprep] BuildMassStorageSection=yes [SysprepMassStorage] [Sysprep] BuildMassStorageSection=yes [SysprepMassStorage]
Free Windows Admin Tool Kit Click here and download it now
January 4th, 2011 2:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics