Search options (Page 1 of 6)

I don't think that OverFlow is done writing the Service Pack 3 compatability.  You may need to use a nightly build to even attempt it.

Here is another tutorial for making 3rd party driverpacks that you might find easier to follow:
http://forum.driverpacks.net/viewtopic.php?id=279

Jaak, Bâshrat the Sneaky?  Can one of you can direct abdou to the SaveHWID.exe so that he can get the Hardware ID for his device?

http://www.driverpacks.net/DriverPacks/ … .php?pag=m

I don't see your particular device on the supported list.  That might be why it isn't detected.

You need to put the zipped up driverpacks inside the "DriverPacks" folder that is next to the DPs_Base (check the image in step 3 for a reference).  That will make them markable.

If you downloaded 3rd party packs, you need to put those packs in the "3rd party DriverPacks" folder next to the DPs_Base (again, step 3 shows you).

The first one is a Wireless network card driver for some Novatel Express, the second one is a 3rd party pack.

I would expect unsigned (or mistakenly corrupted) drivers in the 3rd party packs, but I didn't expect one in the WLAN pack...

Someone from the DriverPacks team will have to verify if these drivers are correct or just corrupted.

I, personally, slipstream SP2 via nLite first.

Then I use Boooggy's WMP 11 Slipstreamer to add in Windows Media Player 11 and a few hotfixes for it.

Next I use nLite to patch windows with the available/compatible hotfixes.  Alternatively, I have used RVM Integrator for the patches in the RVM Update Pack.  I find that RyanVM isn't always as up-to-date as I need, so I built up the library of hotfixes on my own.

Next step is the RVM Addon packs.  Again, I use nLite to add them in but it's probably smarter to use the RVM Integrator.

Then I use DriverPacks.  Method 2, Quick Stream Cache enabled.

Finally I use nLite one last time to create a bootable ISO (which I burn after testing).  Although I have used Nero once...

One thing that I always have to do before burning is that I have to extract the contents of the bin and the finisher archive manually to $OEM$\$1.  I don't know if the DriverPacks base is supposed to do that at all, but it never has for me.  I then have to add in a record for RunOnceGUI/RunOnceEx for a cleanup command file that goes in after DriverPacks runs and deletes all of the files I had to add to $OEM$.  This cleanup command file is just a personal preference - not necessary.  However you may experience some missing file errors if you don't handle the larger issue at hand.

So to answer question 1, the short answer is "no".  You can't assume that all of the files are there.  You probably need to extract the finisher archive to the system in some way.  Some people extract it at windows install runtime, others extract it into the preinstall folders (like I do).  Which leads you to question 2, "no" again.  You can make a bootable CD but it won't work without those finisher files.

I'm going to qualify my answers for your first two questions by saying that I haven't kept up with the DriverPacks base version.  If a new one was released they might have made an answer to that "problem".

As for your third question, I do like to test out my disk on a virtual machine first, but in some cases it ends up taking WAY too long (I usually add in the Windows Post Install just before DriverPacks).  So while it's nice, in some cases it can be impractical.

McAfee isn't doing as hot as it used to.  It's sub-Norton at the moment (just barely - there's almost no difference).

NOD32 > Kaspersky > Avast > Norton > McAfee > Trend Micro > OneCare > AVG

You have to use the OEMPreinstall folders on the CD source - not your current systemroot or systemdrive.

The way the "$OEM$\$$\" folder works, is it copies all of the files inside that folder to the systemroot when you install windows.  This solves the issue of not being able to find certain files when you unpack everything from the DPsFnshr.7z in there.  "$OEM$" lies next to "I386" on your install CD.  You also have to set OEMPreinstall correctly in your winnt.sif file for it to copy the files over.

Oh I see.  I thought he was talking about updating an install CD.  To update a system that's already got the drivers on it - yeah...  That'd be tough.

Have you considered a problem with source file?  Sometimes if your source file is corrupted in some way (if there are hickups in the download stream) you can't cab compress.

Try re-downloading the chipset and/or mass storage driver packs.  The first issue you reported mentioned the chipset driver packs (Could not copy Intel Chipset drivers' .inf files), and the new issue you've just mentioned says mass storage (\D\M\3).

Uh.  Yeah...

You're making the process a lot harder than you should.  All you need to do is run the DriverPacks base again.  DriverPacks base will recognize the old DriverPacks and automatically remove/replace them for you.  At least, the current base does that.  Not sure if you're running an outdated base or not.

Well if you have OEMPreInstall set to true in your winnt.sif file, you can unpack them in your $OEM$ folder.

http://unattended.msfn.org/unattended.xp/view/web/18/

WinXPDisk\$OEM$\$1\

Just unzip the finisher 7z to that.  Then you can call a cleanup.cmd file after finisher

@ECHO OFF
TITLE Windows XP Installation Cleanup

echo Cleaning up temporary files...
DEL /Q %systemdrive%\devcon.exe
DEL /Q %systemdrive%\DPsFnshr.exe
DEL /Q %systemdrive%\DSPdsblr.exe
DEL /Q %systemdrive%\makePNF.exe
DEL /Q %systemdrive%\mute.exe
DEL /Q %systemdrive%\pmtimer.exe
echo Temporary Files Deleted...

exit