I am trying to use OSD to deploy windows XP to various laptops. I have it working on all but 1 of them.It uses an Intel 82801GBM Sata Controller (ICH7M) and is applied in the task sequence. However, after the image is applied and the laptop is deployed I get a BlueScreen with error 7B displayed.When I check the SCCM logs I get the following message when the driver is applied:The task sequence execution engine successfully completed the action (Apply CF19C Storage Driver) in the group (Install Operating System) with exit code 0Action output: -and-play search path.TxtSetupOEM::init("C:\drivers\1\txtsetup.oem")Installing Mass Storage Driver for PCI\VEN_8086&DEV_27C5&CC_0106 from C:\drivers\1\iaAHCI.inf.Copying mass storage driver files to offline machine.C:\WINDOWS\system32\DRIVERS\iaStor.sys already exists, skipping file copy.Adding mass storage driver services to offline machine.Driver service has already been installed.Adding mass storage driver settings to offline machine.Skipping non HKLM rooted add registry operation.Adding mass storage driver to critical device database.Successfully applied driver package "PRP000B1".Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\PRP000B1reference count 1 for the source C:\_SMSTaskSequence\Packages\PRP000B1 before releasingDelete source directory C:\_SMSTaskSequence\Packages\PRP000B1Released the resolved source C:\_SMSTaskSequence\Packages\PRP000B1Unloading offline SOFTWARE registry hiveUnloading offline SYSTEM registry hiveExiting with return code 0x00000000.Any help on this issue would be very appreciated.Thanks

have you tried changing the SATA mode in bios ? what laptop model is it ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

I took a look before posting and there was nothing in the bios for Sata mode.I am trying to put the image onto a Panasonic CF19C (I already have it working on an panasonic CF19F and K).I just added a step into the task sequence to delete the IAStor.sys file before applying the mass storage driver, so I will see if that helps.

So, let me make sure I have this right. You have a Windows XP base image, that you are layering a mass storage driver on top of? Have you tried removing the iaStor driver from the base XP WIM? It seems apparent from the log file you provided, that it doesn't want to overwrite the existing file (not even considering the file version).I would recommend mounting your base image with ImageX, removing the file, and then trying it again.Also, I would ask you ... what type of system did you build your base image on? What storage controller did it have? I would personally recommend building your base XP WIM on a virtual machine, either VMware or Microsoft Virtual Server.Trevor SullivanSystems EngineerOfficeMax CorporationTrevor Sullivan Systems Engineer OfficeMax Corporation

I am actually just in the process of downloading the Microsoft AIK so I can get ImageX and modify the image. Once I have removed the IaStor.Sys file I will let you know if it works. The image was actually built on a Panasonic CF18 toughbook. For whatever reason, the CF19C is the onlytoughbook that wont take the image(both the CF19K and CF19F need a different storage driver layered on it and it seems to take it). Thanks for the quick reply and I will let you know how it goes as soon as I can.

I think this might help: http://technet.microsoft.com/en-us/library/bb680403.aspxMy Blog: http://www.petervanderwoude.nl/

The AIK is already installed on the ConfigMgr site server. Why not not run imagex from there? (The WAIK is a 1GB+ download). How did you build the reference image? It looks like you may have some type of conflict as Trevor eluded to?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

deleting the iaStor file from the WIM image did not resolve the issue. I now get the following message in the logs: ****************The task sequence execution engine successfully completed the action (Apply CF19C Storage Driver) in the group (Install Operating System) with exit code 0 Action output: r PCI\VEN_8086&DEV_27C5&CC_0106 from C:\drivers\5\iaAHCI.inf. Copying mass storage driver files to offline machine. Copying C:\drivers\5\iaStor.sys to C:\WINDOWS\system32\DRIVERS\iaStor.sys. Adding mass storage driver services to offline machine. Driver service has already been installed. Adding mass storage driver settings to offline machine. Skipping non HKLM rooted add registry operation. Adding mass storage driver to critical device database. Copying "C:\_SMSTaskSequence\Packages\PRP000B1\E6D04B1A-681C-4877-BD76-74F6F3AFF215" to "C:\drivers\6". Successfully applied driver package "PRP000B1". Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\PRP000B1 reference count 1 for the source C:\_SMSTaskSequence\Packages\PRP000B1 before releasing Delete source directory C:\_SMSTaskSequence\Packages\PRP000B1 Released the resolved source C:\_SMSTaskSequence\Packages\PRP000B1 Unloading offline SOFTWARE registry hive Unloading offline SYSTEM registry hive Exiting with return code 0x00000000. ****************The error on the bluescreen is actually 7E not 7B (my mistake). Could it be related to the "Driver service has already been installed" message?

Update: After removing the IaStor and changing the driver I am injecting the blue screen has switched to 7E (so initially it was 7B). I thikn tihs means I definetly have the correct driver, but something else might be going on. Any more ideas?

can you remove all drivers that are applied in the task sequence and see does the problem go away ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064

Seems like some trouble with the drivers you have on your image. I would try to sysprep the base XP over again, and then capture it with imagex. BUT, before you sysprep, put in Johan Arwidmarks package of drivers and edit the sysprep.inf in the folders c:\sysprep on the client, like Johan describes:http://www.deployvista.com/Home/tabid/36/EntryID/76/language/en-US/Default.aspx(Check to see if some of the drivers in the package needs updating)Wouldn't normally put drivers on the image, but since you have som driver issues, this can perhaps resolve them.

Eight, Curious, Did you ever work through this issue? If not, where are you now..