1,676

(3 replies, posted in Software)

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

Third Party DriverPacks always use the filename DP_*title*_wnt5_x86-32_YYMM.7z and always have the folder structure \D\3\*\*
Mass storage drivers don't play well as Third Party DriverPacks.  You should consider making your own (or altering) dpms.

1,678

(3 replies, posted in Software)

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.

1,679

(7 replies, posted in Feedback and Support - DriverPacks Base)

Can you also post your HWID list?

1,680

(5 replies, posted in Universal Imaging)

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

1,681

(5 replies, posted in Universal Imaging)

Check the FAQ first.
http://forum.driverpacks.net/viewtopic.php?id=4422

1,682

(5 replies, posted in DriverPack Graphics)

Well that is very strange. neutral

1,683

(5 replies, posted in DriverPack Graphics)

Do you also integrate the modem Third Party DriverPack?  That file is in the modem pack in \D\3\M\P and \D\3\M\Z4

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?

1,685

(11 replies, posted in Installation Platforms)

I've found that if you use any ROE installers that it's best not to call the DriverPacks Finisher from GUIRunOnce because the two stages will run concurrently and interfere with each other.  If you already use ROE to install items, call DriverPacks Finisher from your ROE .cmd file.

1,686

(11 replies, posted in Installation Platforms)

donald7777 wrote:

driver-packs finisher launches during the t-13 time of xp install and works great.

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?

1,687

(5 replies, posted in DriverPack Graphics)

I don't use any of OnePiece's projects.  Everytime I tried, I had problems so I don't use them anymore.
You're adding way too many things to determine if it's a DriverPacks problem or not.
Start with the updatepack and DriverPacks just to see if the DriverPacks are working on their own.  Then add the addons one at a time to figure out what breaks.
I'm not sure why you're switching from RVMI to nlite to RVMI back to nlite in multiple sessions.  Just use RVMI for everything except Rick's MCE addon (requires nlite).

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

Wim Leers wrote:

And finally, we need to look into ways to generate more income, to be able to continue running this project. A first and obvious step, is to cease the ability to download/update the Windows 2000/XP/2003 DriverPacks from within the DriverPacks BASE for free. In the first phase, the downloads will stop working, thereby increasing our number of visitors.

...Topic closed

http://tppc-support.nl/driverpacks/Nightlies/icon_lock.gif

1,689

(85 replies, posted in Vista / 7 DriverPack Chipset)

Fragbert wrote:

It would be nice to know if you ran the chipset inf installer on a live windows 7 system if the installer itself would use any INF's from "ALL" even though they are not supposed to be for Windows 7.

Hmmm, I should add that to my "to do" list since I have an ICH9R chip and I'm working on the new SAD2 utility.  I could do a test install on a spare drive with a base Win7, then "update" the driver and check the file versions.

1,690

(85 replies, posted in Vista / 7 DriverPack Chipset)

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.

1,691

(85 replies, posted in Vista / 7 DriverPack Chipset)

v9.2.0.1016 isn't final.  It's pre-release.  So who knows what folder layout Intel will go with once final.  v9.1.2.1008 is still the current final from the official Intel downloads page.
But it wouldn't surprise me that they would segregate the drivers like that.

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.

Can you post your full HWID list using the utility linked in my signature?
Try removing the D\M\SS1 folder and the [SS1] section from the .ini and retest.

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]

Just download the latest release and strip out what you don't need.
For each folder you remove, also remove it's corresponding .ini entries.

1,696

(25 replies, posted in Software)

Adler wrote:

where i can find WINDOWS 7 tool , and for free plz , link me

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

1,697

(6 replies, posted in Vista-Tool)

A more advanced version of our S.A.D utility is in development here (2nd post): http://forum.driverpacks.net/viewtopic.php?id=4954
I am continuing to improve it's functionality but it's about 95% ready right now.  Works with all Windows versions (32 & 64 bit).
I'll try to create a new thread with better instructions over the holidays.

1,698

(7 replies, posted in News)

Merry Christmas everyone, and Happy Holidays.
New Years resolution: Take time to go out of your way to do something extra-ordinarily nice for at least one stranger each day.

OverFlow wrote:

Mr_Smartepants wrote a script to make XP a preactivated copy (Like an OEM restore CD).

Yup.  It's linked in my signature.  Though to be honest I've never tried it in a sysprep environment.  As long as it's called before/during the mini-setup it should be fine.
Please report any problems in the thread over at siginet's forums.

1,700

(5 replies, posted in DriverPack Mass Storage)

Can you post the HWIDs of the system that's failing?  Use the tool linked in my signature.  And please post your DPs_BASE.log.