Search options (Page 40 of 159)

Go for it!  Nobody else is going to.

Please stay on topic.  That has nothing to do with the OP.

You didn't indicate what version of DriverPack LAN you used.  Moved thread out of the XP support forum.
This is a DriverPacks support forum.
If you didn't even try DriverPacks yet, then try our SAD2 utility. http://forum.driverpacks.net/viewtopic.php?id=5336
Download the NT6 DriverPacks (either x86 or x64 to match your system) and copy them to the respective folders for SAD2 (example: SAD2\NT6\x86\)

Why not just make a pack .ini and let DriverPacks Finisher do all the work?

Yes, basically it would be a "missing-file...finder"
Not all files required by the driver are referenced in the [sourcediskfiles] section but can also be referenced in the [*copyfiles*] sections.

Moved to the sysprep area.

Yes, exactly that.
I use my SAD2 utility to update all drivers post-install.  Otherwise the install.wim driverstore folder gets ballooned into oblivion for no reason.
boot.wim - dpms only
install.wim - two DriverPacks; DriverPack Chipset & Mass Storage only

That's my personal preference.

OK, I need to know what controller your drives are connected to.
When windows setup DOES see the drives, the controller is named in brackets; [jraid] is Jmicron controller, [iastor*] is Intel controller.
What does yours say?

From the jmicron release notes:

I'm interpreting that as the Jmicron drivers don't work in a server environment.  Can someone prove me wrong?

I still don't know what's causing your problem.  I can't replicate it here.
*Edit
I see it now.  I'll have to look into it later this week when I get back from vacation.
Did any previous versions of dpms work?  That would give me a head start...

Odd.  It might be how your image is deployed.
More testing is needed.

[IT1]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA XP"
ms_1_tag="iteatapi"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k3,w2k"

[IT1-2k]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA Win2000"
ms_1_tag="iteatapi"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k3,wxp"

[IT1-2k3]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA Win2003"
ms_1_tag="iteatapi"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="wxp,w2k"

Notice in the above extract from the dpms .ini that there is a OS discriminator built in.
ms_1_exc_skipIfOS=
This line means the inclusive section is "skipped" if the OS is (insert OS here).
IT1 is for XP.
The other two are similar.  H7 is for XP, H7S is for (S)erver.

*****
Edit:
Oops, Now I see what you mean.  There are no corresponding entries in the txtsetup.sif for XP.  I see it now.
I renamed your thread title to be more descriptive.
Thanks for reporting.

No, unfortunately the way DriverPacks BASE and DriverPacks Finisher are coded the D\3\ folder structure is hard-coded into both apps for KTD compatibility.  A rewrite of both would be required.