Yes, which is why we include both .sys files in each folder. If their utility is removing files or consolidating the folders, they broke it.

xp_user wrote:

I then create a installation USB using the program WinSetupFromUSB

I'm wondering if that utility is modifying the source files at all.  I'm at a loss to explain why you're getting that error.

Did you modify your source after DriverPacks were installed?
Can you check to see if iaStor.sy_ is present in %source%\i386\iaStor.sy_

Please post your DPs_BASE.log so we can see how you're installing the DriverPacks.

By default the DriverPacks are extracted to %systemdrive%\D\ and that location can not be changed easily.
The folder is deleted upon completion of the install, unless you enable the "KTD" option (Keep The Drivers) which is NOT recommended for 99% of users.

Welcome to DriverPacks.  Enjoy.

There's nothing in the .inf that would prevent an XP install.
In fact, here's a quote from the .inf:

; - This version supports Windows XP and later operating systems.

I'll see about adding this in for you.

You can't.  DriverPacks BASE only works with NT5-based OS like Win2000, XP or Win 2003.
Win7 requires DISM and there are several tools to help you with that.  Check out the stickies in this section.
http://forum.driverpacks.net/viewforum.php?id=47

This should be fixed in the 12.06 Graphics DriverPacks.  Please test.

This is implemented in DriverPack Graphics B 12.06.
We'll have to keep an eye out for this on any future updates.

Please test the new Graphics DriverPacks and let us know if this problem still exists.

Included in DriverPack Graphics B 12.06

Marking as solved with DriverPack Graphics C 12.06

Implemented in DriverPack Graphics B 12.06

389

(5 replies, posted in DriverPack Graphics)

The Intel drivers were updated in the new Graphics DriverPacks.  Please test and let us know if this problem still exists.
I don't know what to suggest, this is an unusual setup.

390

(11 replies, posted in DriverPack Graphics)

Please try the new 12.06 Graphics DriverPacks and let me know if this problem still exists.

Of course there's a better way! smile
Try our SAD2 utility.  We wrote it specifically for use with our DriverPacks for exactly your scenario.
Welcome to DriverPacks.

The only drivers you should be integrating into any PE disc are Mass Storage and MAYBE network (LAN, WLAN) or chipset.
So can you tell us what drivers in dpms are corrupted?  I tested in UBCD4win (PEbuilder) and had no errors.
In your screenshot you're trying to integrate audio/sound drivers into PE.  No wonder they failed!

DriverPack LAN 12.06 released.

No response...
dpms 12.06 released.
http://driverpacks.net/driverpacks/wind … rage/12.06

Glad it worked for you.  But just to clarify, KB939315 doesn't apply to w2k3r2, only the original w2k3.
http://social.technet.microsoft.com/For … c8818b88aa

Yes of course.  I can't test because I don't have your hardware.  Your hardware is the one with the problem that we're trying to fix/test.

The driver in AM7 is the newer version of the one most compatible with your system.  The driver in AM8 supports your controller ONLY for XP, not Win2k3.  If you want to test to see if it works with w2k3, then open M\AM8\ahcix86.inf
and change:

[ATI.NTx86.5.2]
%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4392&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4393&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1022&DEV_7802&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1022&DEV_7803&CC_0104

to read:

[ATI.NTx86.5.2]
%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4391&CC_0106
%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4392&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4393&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4394&CC_0106
%NapaDesc%=Napa_Inst,PCI\VEN_1022&DEV_7801&CC_0106
%NapaDesc%=Napa_Inst,PCI\VEN_1022&DEV_7802&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1022&DEV_7803&CC_0104
%NapaDesc%=Napa_Inst,PCI\VEN_1022&DEV_7804&CC_0106

Then try to "force load" the driver into your running system and see if it works.

AM7: DriverVer=07/01/2009, 3.1.1540.151 (older, more compatible)
AM8: DriverVer=11/17/2011, 3.3.1540.26 (newer, untested)

Just because a driver is newer, does NOT make it better.  Let us know how your testing goes.

Do NOT restart until the first 3 steps below are finished.
1) Install the full Intel chipset drivers from here: http://downloadcenter.intel.com/Detail_ … p;lang=eng
2) Install the full Intel RST drivers from here: http://downloadcenter.intel.com/Detail_ … p;lang=eng
3) Follow the instructions here: http://support.microsoft.com/kb/922976
3.1) This will change the registry settings to allow boot to AHCI/RAID once the BIOS change is completed.
4) Restart and enter BIOS.
5) Change drive controller BIOS setting from IDE (legacy) to AHCI or RAID (your choice).
6) Restart and enter OS.
7) Run HWID tool to extract full HWID list and repost here.

...no response means no support...

...no response means no support...