Search options (Page 27 of 159)

A better way would be to add this to the .ini:

[i]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles	= 6
exc_1_tagFile1	= "%DPSROOT%\D\C\I\atapi.reg"
exc_1_tagFile2	= "%DPSROOT%\D\C\I\CriticalDeviceDatabase.reg"
exc_1_tagFile3	= "%DPSROOT%\D\C\I\PCIIde.reg"
exc_1_tagFile4	= "%SystemRoot%\system32\drivers\atapi.sys"
exc_1_tagFile5	= "%SystemRoot%\system32\drivers\pciide.sys"
exc_1_tagFile6	= "%SystemRoot%\system32\drivers\pciidex.sys"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\C\I\ich9core.inf"
exc_1_-infFiles	= 0
exc_1_commands = 3
exc_1_command1  = "regedit /s %DPSROOT%\D\C\I\atapi.reg" 
exc_1_command2  = "regedit /s %DPSROOT%\D\C\I\CriticalDeviceDatabase.reg" 
exc_1_command3  = "regedit /s %DPSROOT%\D\C\I\PCIIde.reg" 

Well, it seems to be a lot of work for little gain.  The Intel drivers in DriverPack Chipset are already newer than what you're using.
As long as you use an XP SP3 source then you'll already have current versions of those M$ sys files.
My advice would be to just use DriverPacks as normal on an up-to-date XP source and call it good.

This has been added to my own build for the next release (12.01?).

Sounds like a competing product...I wish them luck.
Links above go to a Chinese forum.  I updated the first post.

I don't know where they're getting their drivers from but it sure as h*ll isn't from Intel!  That's an early Alpha build and only meant for OEM engineers.  Knuckleheads!

I'm not sure why it's failing like that.  Maybe because you're trying to execute it from a command prompt.
Why not just double-click it?

Well that's disappointing!
When you get it up and running, can you post your entire HWID list?

SAD2 will run from a network source no problems.

Can you please be more specific on what happened?
Was the BSOD on the "host" system or on the "target" system?
Let me guess:
You integrated ALL the DriverPacks into a Win7 image using a batch script. (what DriverPacks and what versions were integrated, and what batch script?  Was the integration successful?  Was the install successful?)
If the Win7 install onto the target system was successful, you then used SAD2 to update the drivers on the target system even though you already integrated them into the source.  And you got the BSOD before/after running SAD2?
Or was the BSOD on the "host" system during the driver integration into an offline image?

Sorry if I'm confused on what you did.

We need more details if we're to help with any kind of accuracy.

Sounds like a very similar install method to our SAD2 script here: http://forum.driverpacks.net/viewtopic.php?id=5336
Maybe you could contribute/post your code there so we could use it to improve our script also (unless yours is a "trade secret").

Your problem was reported with an earlier DriverPack Chipset but I thought we fixed that.  I myself don't have hardware that supports that dual-hybrid-video...yet.  (I'm building a wish-list for a system upgrade that will incorporate that hybrid graphics on z68 chipset).

If you could tell us which specific driver folders cause the problem (or better yet, the driver files themselves), then we can quickly isolate the problem and issue a fix.

BTW, WTH are you doing posting this on Christmas day!?  Go away and be with your family!

Ah, Nvidia.  I was afraid of that.
I'll look into it when I have a chance.

Indeed!  The problem is with the compiled .iso file and NOT the install method.
You'll probably need to start from scratch and build your .iso in stages (test in VM at each stage), then troubleshoot when you find the stage which breaks your build.
Remember to document your steps to each stage so that we can potentially duplicate your steps and help troubleshoot more effectively.