mjhmjh2

I'm guessing no one really knows the answer to this one - are there any corporate type forums where I might be able to post on the offchance? I'm going to try and strip out all but the specific driver file from the oem disc and see what happens. Will opst progress if anyone is interested. Matthew

Have you got an ide disc you can build the system on? If so, go ahead and build the system then add the sata drivers there. If you don't get an error you should be able ghost/image the system to the sata drive and then run from there. OK it's a workaround but should be able to get you going. Matthew

Hi there, I have created a syspreped image that suits all of our hardware by including all the drivers in the [OemPnPDriversPath] section of sysprep. I've also been placing entries in the [sysprepMassStorage] for the storage controllers so it moves between the hardware without fuss. Up until now all of the storage controllers have been available in a base XP system so I've used the -bmsd line to populate then removed the ones I don't need. Unfortunately our latest machine in has a SATA controller from intel, the drivers aren't built into windows. I have the driver disc and doing a fresh install using the f6 options works fine, but I want to add this machine into my multi-hardware build. Reading through the various manuals that come with sysprep it would appear to be a simple option of adding the section into [sysprepmassstorage] having placed the drivers locally on the machine. However everytime I reboot after putting the image on I get a blue screen mass storage controller error. Is anyone able to give me some pointers or assist please? I have posted below some code and attached the two driver inf files and txtsetup.oem in a zip file. I'm sure there is probably something I've obviously done wrong! Thanks Matthew txtsetup_iaachi_iastor.zip =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This is from the sysprep.inf file, the top few entries are the new ones I've put in (I put them all in to try and be safe, but the controller in question when build with a factory image reports itself as a ven_8086&dev_27c5 (thats an intel 82801BGM).. The new entries for this controller family are in upper case, old working ones lower. [sysprepMassStorage] PCI\VEN_8086&DEV_27C3=c:\drivers\stor\iastor.inf PCI\VEN_8086&DEV_2652=c:\drivers\stor\iastor.inf PCI\VEN_8086&DEV_24DF=c:\drivers\stor\iastor.inf PCI\VEN_8086&DEV_25B0=c:\drivers\stor\iastor.inf PCI\VEN_8086&DEV_2652&CC_0104=c:\drivers\stor\iastor.inf PCI\VEN_8086&DEV_27C1=c:\drivers\stor\iaahci.inf PCI\VEN_8086&DEV_27C5=c:\drivers\stor\iaahci.inf PCI\VEN_8086&DEV_2653=c:\drivers\stor\iaahci.inf PCI\VEN_8086&DEV_2652&CC_0106=c:\drivers\stor\iaahci.inf pci\ven_8086&dev_2651&cc_0101=c:\winxp\inf\mshdc.inf pci\ven_8086&dev_266f=c:\winxp\inf\mshdc.inf pci\ven_8086&dev_244b=c:\winxp\inf\mshdc.inf pci\ven_8086&dev_2653&cc_0101=c:\winxp\inf\mshdc.inf pci\ven_8086&dev_24ca=c:\winxp\inf\mshdc.inf =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-