Ben Hunter

Hello Ben,

With what method do I rebuild my image after changing the sysprep.inf?  LTI?  ZTI?  By hand?

Thanks

Everytime Intel releases a new mass storage chipset I receive the same call/email from from most of my

I've followed these steps for the LTI process and I can't get it to work.  After LTI runs and the machine reboots for the text setup I get BSOD when it gets to "starting windows".  I

I've checked the drive during the LTI process and the driver set does get copied down from the driver library, but the folder name that gets created does match what we're specifying in the sysprep. (IASTOR is what I have in sysrep v.s. drivers\HDC\iaahc 6.1.0.1002 gets created).

How do I rectify this situation?  It seems like the driver injection/detection is working as expected for the LTI portion, but the unattend.txt/sysprep.inf files are not correct.

Any help would be much appreciated!

-Aaron

Hi Ben,

tried the steps above but Win XP image still goes into BSOD....

I'm able to deploy the Win XP OS, drivers, applications and finally, capture an image of the build but when I try to deploy it, it comes up with BSOD. Any thoughts?

thanks for your help!

Ben,  

you say to recreate the base or gold image which is fine.  an I correct in saying that when i bring this new image down to a machine that has the SATA drivers, it wont blue screen and give me the 7B error.  My questions is this, Id like to do a gold image on this machine with the sata drivers and it starts to work but upon the 1st reboot of the bdd, it gives me the stop 7B error.  any suggestions for me ?  

Ben Ive followed the instructions you give abot adding the sata drivers to sysprep and have created and wim that im trying to deploy to a machine with sata.  it loads pe, says its applying the image and upon re-boot, it gives me the bsod, 7b error.  any suggestions for me ?  Thanks In advance.

Jared

Ben,

followed your method to add the sata drivers to the base image, and i still receive the bsod 7b error when I apply this new image to the new machine witht he sata drive.  any suggestions for me?

Hi Ben,

I'm using the latest intel matrix driver for a Precision 490.  The driver came out in June and I got it from the Dell 490 download site.  I'm using these pnp IDs in my sysprepmassstorage section... I am running sysprep from the 490.  XP will not load.  Keeps rebooting.  Any ideas?  Of course I turn off AHCI in BIOS and it boots just fine.  Thank you!

BuildMassStorageSection=Yes

[SysprepMassStorage]

PCI\VEN_8086&DEV_2653&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_27C1&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_27C5&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_2681&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_2821&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_2829&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_2922&CC_0106=c:\drivers\pr490-sata\iaahci.inf

PCI\VEN_8086&DEV_27C3&CC_0104=c:\drivers\pr490-sata\iastor.inf

PCI\VEN_8086&DEV_2682&CC_0104=c:\drivers\pr490-sata\iastor.inf

PCI\VEN_8086&DEV_27C6&CC_0104=c:\drivers\pr490-sata\iastor.inf

PCI\VEN_8086&DEV_2822&CC_0104=c:\drivers\pr490-sata\iastor.inf

PCI\VEN_8086&DEV_282A&CC_0104=c:\drivers\pr490-sata\iastor.inf

Well, It is working now.  I put in the id for PCI\VEN_8086&DEV_2652&CC_0106 and PCI\VEN_8086&DEV_2652&CC_0104.  My inf files do not list those ids.  Re-ran sysprep and this time sysprep did take 20 minutes.   Thank you for the blog.

Well, It is working now.  I put in the id for PCI\VEN_8086&DEV_2652&CC_0106 and PCI\VEN_8086&DEV_2652&CC_0104.  My inf files do not list those ids.  Re-ran sysprep and this time sysprep did take 20 minutes.   Thank you for the blog.

I think what you guys are missing is the Textmode folder.

I came across the same problem myself, and I remember reading about the problem on the OEM website.  The situation is this: if you have an AHCI or RAID setup on the boot drive, you NEED to have the driver included into the text-mode portion of setup otherwise you'll get a STOP 7B error a few seconds after "Starting Windows" appears on the status bar.

I personally tried manually pressing F6 and having a driver floppy made up with the EXACT SAME drivers as was included with the above advice, but the result ends up with an error message stating "The specified driver disk does not contain any relevent drivers" (or words to that effect).  After this, I realized that integrating the drivers was the only option.  After some experimentation with the OEM help, I found a way to fix it.

The way to fix this is to do the following:

Under the <Build ID>\$OEM$ folder, you should create a folder called Textmode.  This folder is used for the equivalent of an "F6 Floppy" for extra SATA, RAID, or SCSI drivers.  The default path/share will look similar to this:

\\<server>\Distribution$\Control\<Build ID>\$OEM$\Textmode

(substitute the name of your server/dist-system for <server> and build name for <Build ID>)

Next, you have to edit the UNATTEND.TXT file in the <Build ID> folder and add the following:

Under [MassStorageDrivers], add all of the required drive controller friendly names, as described in [SCSI] section in the TXTSETUP.OEM file for your driver pack.  For instance, in the Intel Matrix Storage v7.5 file, it'll look like this:

[scsi]

iaAHCI_ICH9R = "Intel(R) ICH9 SATA AHCIController (Desktop ICH9R)"

iaStor_ICH8M = "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"

iaAHCI_ICH8M = "Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)"

iaStor_ICH8R = "Intel(R) ICH8R/ICH9R SATA RAID Controller"

iaAHCI_ICH8R = "Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)"

iaStor_ESB2 = "Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"

iaAHCI_ESB2 = "Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"

iaStor_ICH7MDH = "Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)"

iaStor_ICH7DH = "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"

iaAHCI_ICH7R = "Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"

iaAHCI_ICH7M = "Intel(R) 82801GBM SATA AHCI Controller (Mobile  ICH7M/DH)"

iaAHCI_ICH6M = "Intel(R) 82801FBM SATA AHCI Controller (Mobile  ICH6M)"

After you copy out the friendly names, you have to modify the lines and strip out the short names, and add = "OEM" to the end of each as follows:

[MassStorageDrivers]

"Intel(R) ICH9 SATA AHCIController (Desktop ICH9R)" = "OEM"

etc....

Finally, you have to add a list of all of the files in your Textmode folder under the [OEMBootFiles] section so that it looks like so:

[OEMBootFiles]

; This section is used to specify custom HALs, and also maps to the Mass Storage Device section

iaahci.cat

iaahci.inf

iastor.cat

iastor.inf

iastor.sys

txtsetup.oem

As far as Ben's advice goes, it is needed for Sysprepping an image, but it doesn't seem to work for the text-mode portion of setup.  Additional (secondary) drive controllers that are NOT required by a system drive can have drivers added using BDD's built in support and don't need these extra instructions.  Also, as I experienced with some experimentation, if you plan on making fairly barebones installation images and want to do some customization before Sysprep, DON'T FORGET to add LAN drivers into BDD's interface for deployment to systems because Windows needs them immediately after installation to complete the automated setup parts.

Hope that helps!

Hi,

I'm a little confused about this:

.\Distribution\Control\<BUILDID>\$OEM$\$1\Drivers\IASTOR

The path on the physical hard disk is:

c:\sysprep\i386\$OEM$\$1\MSD\HPXW4400\

Does this look right?

The sysprep.inf file is in c:\sysprep

I ask this because I'm getting registry permission errors when I try to reseal. My entry in the sysprep.inf file reflects this location too

[Sysprep]

BuildMassStorageSection = Yes

[SysprepMassStorage]

PCI\VEN_8086&DEV_2652&CC_0106="C:\MSD\HPXW4400\IAAHCI.INF"

PCI\VEN_8086&DEV_2653&CC_0106="C:\MSD\HPXW4400\IAAHCI.INF"

PCI\VEN_8086&DEV_27C1&CC_0106="C:\MSD\HPXW4400\IAAHCI.INF"

PCI\VEN_8086&DEV_27C5&CC_0106="C:\MSD\HPXW4400\IAAHCI.INF"

PCI\VEN_8086&DEV_2681&CC_0106="C:\MSD\HPXW4400\IAAHCI.INF"

PCI\VEN_8086&DEV_2682&CC_0104="C:\MSD\HPXW4400\IASTOR.INF"

PCI\VEN_8086&DEV_27C3&CC_0104="C:\MSD\HPXW4400\IASTOR.INF"

PCI\VEN_8086&DEV_2652&CC_0104="C:\MSD\HPXW4400\IASTOR.INF"

Cheers,

Neil.

Ben,

   We've followed this to the letter and also implemented http://support.microsoft.com/kb/931760

Any further tips on how to identify the issue? the reference build on the same machine is AOK, but the sysprepped one just dies every time.... any suggestions on how to troubleshoot this?

Thanks

Hey Ben,

        I set ExtendOEMPartition=0 and bingo-bango away it went.

Thanks man.

Hi Ben!

Thanks for a good blog.

I also have the stop (7b) error in OSD/sysprep. I think I have done everything correct but is still getting the loop with blue screen and reboot. I have the latest drivers (iaahc 7.6.0.1011. I have tried with other versions as well.

The Light Touch Reference computer is working just fine on the SATA computer models I have. It is no problem to capture a SATA computer to create an image. It is only problem to deploy.

I have also tried everything you suggested but no luck. Any suggestions are appreciated.

Thanks,

Fredrik

try to slipstream sp2!

no more "stop 7b", no more "iaStore.sys is corrupt"

i think, the problem ist the 128gb limit...

test-environment:

(asus a7s notebook, ICH8R, hdd: 200gb

dos7.1 @32gb drive c)

w2k (sp4) - intel driver v6.21

w2k (sp4) - intel driver v7.0 (last support for w2k)

wxp (sp0) - intel driver v6.21

wxp (sp0) - intel driver v7.0

wxp (sp0) - intel driver v7.5

wxp (sp2) - intel drivers v7.5 (works)

Hi!

I got a problem.

I got an old notebook drive with XP installed on it and a program that I need to get to pronto. For added fun, the program is bios-oriented, which means cloning the drive to Virtual PC is out of the question. Tech support tells me that as long as I use a (newer) notebook from same manufacturer I'll be fine (with their help). So, I imaged an old hard disk onto new machine.

Here is the kicker. Newer notebook has nVidia 430 SATA controller. Thus, when I boot I get 0x0000007b.

Checked HAL and it matches, therefore it's SATA.

Question: How do I install nVidia SATA driver on a cold OS (copy files, edit registry and so on)?

Thanks.

Hi Ben,

Thank you for the great blogs!  Does SCCM 2007 allow you to inject mass storage drivers into XP images, or just Vista images?

Also, I am getting an error stating that the "clonetag registry value does not exist" message when trying to capture an image with my extra MS drivers included in sysprep.inf.

Q. What additional files are needed to deploy Windows XP SP2 with BDD 2007? A. In addition to the Windows

A primary problem with the Intel storage drivers is that there are different versions which support different PnP ID's.  With my situation, I have to include the v7.5 PNP ID's into my sysprep file along with the 7.5 driver, and ALSO include one ID from the 7.0 driver and the 7.0 driver itself.  XP puts one driver into system32\drivers, and the other into LastKnownGood.  Windows then loads the correct driver for my two different hardware types (I use one WIM image to support (currently) about 15 different hardware types).

So for all of you that are seeing a BSOD after putting the drivers in, make sure that the driver you are using supports the PNP ID that your SATA controller is using.

Regards,

CJ

Friday, August 24, 2007 7:58 PM by thomas - berlin

you mentioned slipstreaming your cd... I like this idea,  How can I create a slipstreamed Windows XP CD to include the mass storage drivers.  which I can then import into bdd 2007.  I used nlite to do this the cd worked fine.  but when I imported this cd into bdd created an ISO with all my apps the image would not deploy.  have you got any instructions of how to update the orinal xp sp2 cd.  

Hello,

Im having problems with x60 and x61s.  If I create the BDD image on the x60 it deploys fine to the x60 machines but I get "Stop 7b" on the x61s. If I create the build on the x61 the opposite happens.  I believe sysprep, unattend and textmode are all correct and the files are correct since it deploys fine to the same model it was built on.  Any ideas?

Cheers,

JF

is there a log or anything created during sysprep that i can view to see if all the drivers were correctly integrated into the image?

Hey Ben,

Does this still work with Microsoft Deployment RC1 now that task sequences take over for builds? Also, would this still work for 2003 Servers?

Hi Ben

If you integrate the MSD drivers into the build media (i386 - unattended installation)

1. ? Do I need to specify the driver path in sysprep.inf (before creating the image)

2. ? If "all" possible msd drivers are present in the xp image, will Sccm2007 driver injection work ?

3. ? If Yes, where will Sccm place the drivers. (\inf or ?)

Br erik

All of this is very confusing.  I am trying to create an image that will deploy to a dell D630 laptop with an ICH8M Sata drive.  I tried the above solution but get a 0x000000ed error when it reboots after loading the image "Unmountable Boot Volume".  I have tried rebooting the machine with Winpe afterward to see any logs that might be available and the "C" drive is unreadable.  Any suggestions?

Hi Ben-

I'm following this guide. I have a question about this part:

[OEMBootFiles]

; This section is used to specify custom HALs, and also maps to the Mass Storage Device section

iaahci.cat

iaahci.inf

iastor.cat

iastor.inf

iastor.sys

txtsetup.oem

---

What happens if I want to add more than one type of TEXTMODE driver? Most of the files are named the same "txtsetup.oem" -- what do you do in that scenario?

Great help this blog to deal with problems with the mass storage issues.

Thanks a lot BEN

I kept on getting BSODs on the D630s even after I edited the MassStorage section described in this post.  I finally figure out that this laptop was configure to use Flash Cache Module since it originally came with Vista and we were installing XP.  Disabling this feature in the BIOS resolved this BSOD without having to reimage the machine.

G'day Ben,

I'm having some issues getting the lovely iastor driver to work (fantastic product isn't it?)

I successfully managed to get and older version working before with another machine, but the new machine that we are trying to create an image for requires a newer file.

Basically i've followed the steps that you have given both in this blog and the other one, as well as trying a few other solutions but i seem to be getting stuck on the same BSOD (7b).

Last time i had to create the folder in .\Distribution\Extra Files\i386\System32\Drivers and after changing the sif file it all worked happily.

I tried that again this time, but it wouldn't work. So i then went through the steps above, that didn't work, and the same with the other post.

Any ideas?

Cheers,

Phil

G'day Ben,

Yeah the drivers were added into out-of-box-drivers, enabled and added to the build model, then the entire image master image was recaptured to incorporate the newly added drivers.

The latest attempt that i'm trying to do has my sysprep.inf file looking somewhat like this:

[Sysprep]

  BuildMassStorageSection = Yes

[SysprepMassStorage]

PCI\VEN_8086&DEV_2652&CC_0106=%systemdrive%\UDS\Control\755\Drivers\IASTOR\iaahci.inf

PCI\VEN_8086&DEV_2653&CC_0106=%systemdrive%\UDS\Control\755\Drivers\IASTOR\iaahci.inf

Is that a correct approach?

Cheers,

Phil

I forgot to mention that in addition to disabling the flash cache module in the BIOS, the SATA Operation section was set to use AHCI instead of SATA.  I tried everything in this post and still got BSODs.  When I disabled these features in the BIOS, the BSODs went away without reimaging.

Hey Ben-

Sorry, I was trying everything on this post to get this to work with my Perc drivers. That was suggested by some of the other posters.

I pinged you offline...if you could offer any advice with this that would be awesome!

Thanks!

Hi Ben,

Thanks for this great article.

I'm trying to use your solution to add several mass storage drivers.

But I run into creating the sysprep image.

When I run my sysprep I use the following command: c:\sysprep\sysprep -quiet -mini -reseal -shutdown

In my Sysprep file I have added the location to the drivers:

[Sysprep]

   BuildMassStorageSection = Yes

[SysprepMassStorage]

PCI\VEN_8086&DEV_2652&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_2653&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_27C1&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_27C5&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_2681&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_2821&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_2829&CC_0106="C:\drivers\TextMode\iaahci.inf"

PCI\VEN_8086&DEV_282A&CC_0104="C:\drivers\TextMode\iastor.inf"

PCI\VEN_8086&DEV_2822&CC_0104="C:\drivers\TextMode\iastor.inf"

PCI\VEN_8086&DEV_27C6&CC_0104="C:\drivers\TextMode\iastor.inf"

PCI\VEN_8086&DEV_2682&CC_0104="C:\drivers\TextMode\iastor.inf"

PCI\VEN_8086&DEV_27C3&CC_0104="C:\drivers\TextMode\iastor.inf"

PCI\VEN_8086&DEV_2652&CC_0104="C:\drivers\TextMode\iastor.inf"

PCI\VEN_9005&DEV_809F="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8090="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8091="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8092="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8093="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8094="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_809E="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_808F="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8080="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8097="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_809D="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_809C="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8095="C:\drivers\TextMode\A320RAID.INF"

PCI\VEN_9005&DEV_8096="C:\drivers\TextMode\A320RAID.INF"

Only when I run the sysprep with these extra lines the machine doesn't seem to sysprep properly. It won't shutdown at the end. But just restarts the explorer.exe.

What could cause this?

Hi Ben,

I feel ashamed :)

I forgot to copy the drivers. That was the reason the Explorer restarted.

It all seems to work now

Thank you very much.

I have tried everything above with an ASUS P5K motherboard and i still get the error after booting from the cd image for windows xp; windows failed to start......windows failed to load because a critical system driver is missing or corrupt.

file: \windows\system32\drivers\jraid.sys

status: 0xc000035a

Hi Bob,

This is an excellent blog and I found it to be very useful.  The information posted by Joe Raby helped me to resolve an issue with an unattended build, so thanks to him also.

Many Thanks - Fred

Ben,

You mention that SCCM is able to intergrate the SATA drivers into the Image. Do you meen MS Deployment in combination with SCCM or is it also possible with only MS Deployment.

Thx in advance, Regards

Just to make things clearer for others who may struggle with this concept (as I did for a number of days)...and also to prevent more emails directly to Ben ;-)

A new master image must be created which incorporates the steps Ben lists at the start of this page.  You then capture your new master image and deploy this to the "problem" workstation...and everything will work!

I hope this helps to clarify the solution for those (like me) who hoped that they could just add the drivers to their deployable image, sysprep and then re-capture...unfortunately this wont work...

Best wishes

Carl

Ben,

We currently have a working BDD2007/SMS2003/OSD setup for all of our machines from Dell Optiplex GX100-745.

The problem i'm having is adding in the mass storage drivers for the 755 to my master image.

PE2005 is updated and working with 755 network/Mass storage I have added the $OEM$/Textmode below the build and if I do a Lite touch source installation of XP on the 755 then minisetup etc is working correctly and I end up with a fully working XP machine.

Previously I have had a blank SysprepMassStorage section and sysprep has built this section itself

Now I have

[Sysprep]

  BuildMassStorageSection = Yes

[SysprepMassStorage]

PCI\VEN_8086&DEV_2822&CC_0104="C:\DRIVERS\IASTOR\IASTOR.INF"

etc...

Since I manually added the 755 entries and tried to rebuild my master image on the GX100 it's now giving 7B error.

Is this due to me having manually added some entries? Do I now need to manually add all my mass storage drivers manually or am I missing something else?

Thanks,

Nick

Ben,

If manually adding mass storage entried into sysprep.inf do you then have to manually supply all mass storage entries for all of your PC's or does BuildMassStorageSection = Yes still take effect for the ones not manually listed?

I ask as we usually build our master images on a GX100 (the most basic machine we have) and since adding the entries for the new 755's we cant build any images on this machine as it gives a 7B error itself now.

Thanks,

Nick.

Ok,

Im about numb in the brain. I have Dell, d830, d620, d620, d420 d430, opti 745/755, panasonic cf30, cf52, and a couple older models. I want to inject mass storage drivers for all models that gave me the 7b errors (most newer models) How do i go about editing sysprep or unattend with the new id's and where do i seperate the files on the distribution share or the deployed hard driver or the HDD for the base image being created. Also, how do i stop a base build and capture to configure prior to BDD syspreping it. Seems its all captures in one big run if the 7b error doesnt come up in vm session.  Say I want a 755 and 745 but both need drivers for sata or a panasonic cf30 how do i go about this? I have many models and will need a "distribuion structure" for drivers for each particular model.  I GREATLY appreciate your help Ben and as well as others with their posts.  Once i have the 7b fix down any newer models that come in say a optiplex 765 (guessing) and it has different drivers do i have to "recreate" this base image? Or can I inject somewhere after the build?  Can i use multiple Iastor files in different folder structures and have bdd call on wmi from the hardware and pull only those mass storage drivers? Or will this "have" to be injected in the master or base image thats created from the source files all through the unattened and then sysprep and image creation. Do i deploy my base image to a vm then configure it to our standards then sysprep again and wim the image for deployment and add our scripts lastly.???

Yes Lots of questions but spent about a month on this project and stumbling everywhere.

Ben,

I'm having an issue with this working correctly also, I've added all my entries to the MassStorage section and tried to sysprep my workstation and the workstation either gets a registry error or sysprep finishes but doesn't shut down the workstation. I had an issue with sysprep being on the workstation I created the image on and the microsoft tech had me remove the .inf from the workstation before I ran sysprep. I did that because sysprep on the workstation was interferring with sysprep in the build and was preventing the script in the [GuiRunOnce] to run, Do you have any suggestions?

Thanks,

Sam

I know that this doesn't probably belong in this thread. Please if not just address it to the right one.

Here is the problem. We are still on BDD2.5 and moving to Microsoft Deployment in the next few months. That being said we are now having a problem we never encountered before and not able to get any help anywhere. We are trying to creat an image for the new Dell T3400 and the GX755 and the BDD process starts installs the OS and on the first reboot always comes back with the following error: FILE \MININT\SYSTEM32\BIOSINFO.INF COULD NOT BE LOADED THE ERROR CODE IS 14 PRESS ANY KEY TO EXIT. No matter what we try we arent able to get past this error and we are running out of ideas.

Some of the changes we have done are as follows:

in the unattend\source\xppro\sp2\i386 we edited the txtsetup.sif and added the following lines

[HardwareIdsDatabase]

PCI\VEN_8086&DEV_2653 = "iaStor"

PCI\VEN_8086&DEV_27C5 = "iaStor"

PCI\VEN_8086&DEV_27C1 = "iaStor"

PCI\VEN_8086&DEV_27C6 = "iaStor"

PCI\VEN_8086&DEV_27C3 = "iaStor"

PCI\VEN_8086&DEV_2681 = "iaStor"

PCI\VEN_8086&DEV_2682 = "iaStor"

PCI\VEN_8086&DEV_2821 = "iaStor"

PCI\VEN_8086&DEV_2822 = "iaStor"

PCI\VEN_8086&DEV_2829 = "iaStor"

PCI\VEN_8086&DEV_282A = "iaStor"

PCI\VEN_8086&DEV_2922 = "iaStor"

[SCSI.Load]

iastor = iastor.sys,4

[SCSI]

iaStor = "Intel(R) ICH8R/ICH9R SATA RAID Controller"

iaStor = "Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)"

iaStor = "Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)"

iaStor = "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"

iaStor = "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"

iaStor = "Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"

iaStor = "Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)"

iaStor = "Intel(R) 82801GBM SATA AHCI Controller (Mobile  ICH7M/DH)"

iaStor = "Intel(R) 82801FBM SATA AHCI Controller (Mobile  ICH6M)"

iaStor = "Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"

iaStor = "Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"

iaStor = "Intel(R) ICH9 SATA AHCIController (Desktop ICH9R)"

[SourceDisksFiles]

iastor.sys = 1,,,,,,4_,4,1,,,1,4

we added the drivers in the textmode folder

also we edited the unattend.txt file to:

[MassStorageDrivers]

; Used when custom disk drivers must be specified

; Enter the description name =Retail or OEM

"Intel(R) ICH9 SATA AHCIController (Desktop ICH9R)"="OEM"

"Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"="OEM"

"Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)"="OEM"

"Intel(R) ICH8R/ICH9R SATA RAID Controller"="OEM"

"Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)"="OEM"

"Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"="OEM"

"Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"="OEM"

"Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)"="OEM"

"Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"="OEM"

"Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"="OEM"

"Intel(R) 82801GBM SATA AHCI Controller (Mobile  ICH7M/DH)"="OEM"

"Intel(R) 82801FBM SATA AHCI Controller (Mobile  ICH6M)"="OEM"

[OEMBootFiles]

; This section is used to specify custom HALs, and also maps to the Mass Storage Device ;section

iaahci.cat

iaahci.inf

iastor.cat

iastor.inf

iastor.sys

txtsetup.oem

our sysprep.inf is set to

[Sysprep]

  BuildMassStorageSection = yes

[SysprepMassStorage]

;PCI\VEN_8086&DEV_2652&CC_0104 = "c:\mstor\1\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C3&CC_0104 = "c:\mstor\1\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2682&CC_0104 = "c:\mstor\1\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C6&CC_0104 = "c:\mstor\1\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2822&CC_0104 = "c:\mstor\1\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2652&CC_0106 = "c:\mstor\1\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2653&CC_0106 = "c:\mstor\1\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C1&CC_0106 = "c:\mstor\1\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C5&CC_0106 = "c:\mstor\1\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2681&CC_0106 = "c:\mstor\1\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2821&CC_0106 = "c:\mstor\1\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_1000&DEV_0054&SUBSYS_1F041028 = "c:\mstor\2\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F061028 = "c:\mstor\2\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F071028 = "c:\mstor\2\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F081028 = "c:\mstor\2\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F091028 = "c:\mstor\2\symmpi.inf

;PCI\VEN_8086&DEV_27C3&CC_0104 = "c:\mstor\4\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2682&CC_0104 = "c:\mstor\4\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C6&CC_0104 = "c:\mstor\4\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2822&CC_0104 = "c:\mstor\4\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_282A&CC_0104 = "c:\mstor\4\iastor.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2653&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C1&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_27C5&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2681&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2821&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2829&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_8086&DEV_2922&CC_0106 = "c:\mstor\4\iaahci.inf" , "Intel RAID Controller"

;PCI\VEN_1000&DEV_0054&SUBSYS_1F041028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F061028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F071028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F081028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0054&SUBSYS_1F091028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0058&SUBSYS_1F101028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_1000&DEV_0058&SUBSYS_021D1028 = "c:\mstor\5\symmpi.inf

;PCI\VEN_8086&DEV_24DF = "c:\mstor\6\aarich.inf"

;PCI\VEN_8086&DEV_25B0 = "c:\mstor\6\aarich.inf"

;PCI\VEN_8086&DEV_2652&SUBSYS_01801028 = "c:\mstor\6\aarich.inf"

;PCI\VEN_8086&DEV_2652&SUBSYS_01851028 = "c:\mstor\6\aarich.inf"

;PCI\VEN_8086&DEV_24DF = "c:\mstor\7\aarich.inf"

;PCI\VEN_8086&DEV_25B0 = "c:\mstor\7\aarich.inf"

;PCI\VEN_8086&DEV_2652&SUBSYS_01801028 = "c:\mstor\7\aarich.inf"

;PCI\VEN_8086&DEV_2652&SUBSYS_01851028 = "c:\mstor\7\aarich.inf"

we have rem'ed out the lines in the sysprep.inf file but it still was working when the weren't removed.

Does this look right or are we doing something wrong with the way we are injecting the drivers into the source?

Any help would be greatly appreciated.

Thanks,

Paulo

Ben,

Is it possible to do this on a machine that has already been sysprepped once?

Thanks

Jason

Hi ben,

I'm using bdd2007. I've made a .wim XP image from a desktop computer. Now im trying to deploy this to a virtual machine on vmware and i'm getting the 7B error. Is it possible in the deployment workbench to add the Mass storage driver to the out-of-the box drivers? Should this be working? And what does the sysprep.inf file do in the Distribution\Control\<Name> directory ? Can i add the driver names on the mass storage section? Can i inject drivers without editing the image? Thanks in advance

Thanks Ben,

Can this stage be run as many times as necessary?

Jason

Great. Thanks Ben!

And just to clarify, unless you use SCCM or SMS, this is the only want to add these drivers into the XP image...correct?

Ben,

Does Microsoft plan on changing this in a future release of MDT or is this going to be the set in stone method.

Thx,

Jason

Thanks ben, another problem here now :(

command: FORMAT.COM C:/FS:NTFS /V:OSDisk /Y /Q  FAILED with error = 1

ZTI ERROR - Non-zero return code by ZTIDiskpart, rc=1

Non-zero return code executing command "X:\Deploy\Tools\X86

\TsmBootstrap.exe" /enc:SAStart, rc = -2147467259

Any ideas?

Thanks in advance

David

Ben,

If i need to add other drivers, do i add a $2 folder, or just another folder under the $1.

MDT provides a quick and easy way of sysprepping and capturing a WIM for deployment. What happens if

Ben,

Have you tried using BDD 2007 to install XP on to a VMWare virtual machine running on an ESX server ? The problem I face is the virtual machine is using an LSI Logic scsi controller and VMWare also has its own SCSI drivers. Another virtual machine that I have converted from a physical machine is showing the IDE controller as an Intel 82371AB/EB IDE Controller. PE applies the image and copies teh XP setup files to the VM. The VM then restarts, goes through the text setup of XP and comes up with the 0x0000007B BSOD. Which driver do I need to add to sysprep/unattended text files?

Regards,

Mark

Mark, I had the same problem before. Set the VM scsi controller to Buslogic and the OS to windows XP. Download the vmscsi-1.2.0.4.flp and mount it to vmware. Press F6 during install and load the driver. Greetings

I'm having an issue where an Image captured on a VMware Server 1.04 machine gives the BSOD 0x00000007B when restored to the same VM or a Compaq Evo D300 box. The VM uses IDE and the the Compaq uses a standard Intel 845G chip which doesn't need any seperate XP drivers.

Still I keep getting the dreaded 7B BSOD.