Search options (Page 68 of 159)

Creating your own Mass Storage DriverPacks
Making your own DriverPacks for n00bs

First, in your situation (if space is that much of an issue) I would use the Chipset, Mass Storage, and LAN DriverPacks especially since Chipset is so critical to everything else working smoothly.  The rest (or all) could go in a separate SAD disc.  SAD won't work for everything, but it'll cover 90% or better of your workload.
Next, the two graphics HWIDs you posted...only one is in DriverPack Graphics B (folder \I4 specifically).  But VEN_8086&DEV_2582 is not.  Are you sure it's a graphics HWID?  Can you post your entire HWID list?
Last, Dell audio is notoriously difficult to support, since they include just about every controller under the sun and none of their drivers cover all.  Even the overlapping ones cause problems!
In your case the best option would be for you to create your own custom sound pack with all the drivers you'll need.

Sorry, I misunderstood you.
Yes, bigfoot is correct.  The "findhwids" tool is what you want.  I've used it extensively.

Well that is very strange.

Having the beep.wav play is a leftover from the original SAD code.  I never liked it, and since it's causing problems, I may remove it.

Having the files extract to the \D\ folder was standard procedure for the DriverPacks in the first place and been like that for years.  Although I could rework the code to extract to %systemdrive%\DriverPacks\D\ instead.  Would that help?

Impossible.  DriverPacks Finisher never runs during T-13 unless you manually added it to svcpack.inf and modified the presetup.cmd file.

So, assuming you got your terminology wrong, we'll proceed under the assumption that you scheduled DriverPacks Finisher to execute during ROE instead since you have the DPs_BASE.ini flag: finisherMethod    = "custom"
During Method-2, DPsFnshr.ini gets copied to %systemdrive% during extraction prior to T-39 providing that presetup.cmd is not altered.

So, what exactly did you select in DriverPacks BASE for the "custom" setting?
Did you modify presetup.cmd?
Did you modify ANY system files after integrating DriverPacks using DriverPacks BASE?

This is intentional.  It was also posted in the News and on the front page of the site.
http://forum.driverpacks.net/viewtopic.php?id=4850

...Topic closed

Wow I didn't even notice.  You're right.  These packs support both Vista & Win7 so including everything won't hurt unless there's an integration error.  But before releasing, I always do a test integration with DISM.  No errors, no problems.

Glad it worked out for you.  I agree that powerpacker needs better help files and guidance.  But it's a great tool, though a bit old.

What you need to do is build each source in parallel ie. XPHO (Home OEM), XPPO (Pro OEM), XPMO (MCE OEM), XPPV (Pro VLK), etc. adding SP3, updates, oemscan, and DriverPacks TO EACH FOLDER.
Once you make EACH folder source work perfectly (building/testing .iso in VM), then AND ONLY THEN, build your final PowerPacker .iso with each folder added one at a time, testing between each addition.
In PowerPacker, it doesn't give you the option to use a common "shared" OEM folder.  So you need to add the first folder with everything intact, then remove the OEM folder for each subsequent additional folder source (don't worry, they'll share the one OEM folder.)

Contents of "powpack.ini":

[InputOutput]
XPSource=C:\Tools\XP\Projects\XPPO
XPDestination=C:\PP

[Exclusions]

[Extra Files]
ExtraPackDest=
ExtraRootDest=

[Custom Options]
FileToRun=
RunParams=
PackNameOn=Y
Tri-Pack=N
PackName=XPPO
BootEntryOption=Windows XP Professional Edition OEM SP3

[Unattended]
Winnt.sif=C:\Tools\XP\Projects\XPPO\I386
$OEM$=C:\Tools\XP\Projects\XPPO\$OEM$
Unattend=X

[DriverPacks]
DPSource=C:\Tools\XP\AutoImage\DPs_BASE\DPs_Base.exe
DPSettings=
DriverPack=O

[WinXPVersion]
XPVersion=P
CMPNENTS=C:\Tools\XP\Projects\XPMO\CMPNENTS

[WinXPEdition]
XPEdition=O

[Win2k3Version]
2k3Version=

[Boot Entry]

Right here (2nd post): http://forum.driverpacks.net/viewtopic.php?id=4954