Quote:
Originally Posted by Trooper1
I've also been struggling to make this work and everything seems to indicate that sysprep -bmsd modifies the registry with the driver info. I've even tried merging the registry entries from a working system but continue to get a BSOD. Seems like there is no way to deploy an AHCI built image to a SATA disk.
|
I never use the two step sysprep method that employes the "sysprep.exe -bsmd" step. It's essentially garbage.
To be frank. you can do ACHI driver injection into your reference image with out it. But it requires that you set this switch:
Code:
[SysPrep]
BuildMassStorageSection=No
and that you then populate the "[SysprepMassStorage]" section by your self.
Seems to me every time you want to something as needle-tip specific as this, you gotta do it by hand.
The -bmsd switch will populate your sysprep.inf with ONLY those drivers that come standard in the WinXP Source disk you installed with. It wont add in the new drivers you really want.
Useless eh?
Short and skinny, you gotta roll up your sleeves and dig through your drivers own personal .inf files. You gotta find stuff that looks like this (this is taken from my own Intel Matrix Drivers):
Code:
PCI\VEN_8086&DEV_2652&CC_0106=<whatever>
PCI\VEN_8086&DEV_2653&CC_0106=<whatever>
PCI\VEN_8086&DEV_2652&CC_0104=<whatever>
That stuff wont be just hanging around on it's own. If memory serves, you'll find device descriptions or something on the right hand side of that equal sign.
The only thing you care about are the explicit device ID's (thats the PCI\Ven_<blah>&Dev_<blah>&CC_<blah>). Once you isolate all the device id's defined by the drivers INF file, you then drop those into sysprep.inf and replace the right hand junk with your explicit path to the original driver.inf file that originally defined them.
I'm on vacation in Oklahoma right now or I'd through up a comparison between the driver INF guts vs. the handcrafted sysprep.inf entries. If you still have trouble give a shout back and I'll do it.
But yeah. With these damned ACHI drivers, you gotta really get personal with the driver's .inf file. And it's messy in there. Really, freakishly messy. But the stuff you're looking for always looks the same.
