mr_smartepants was nice enough to answer you, but it should be known that this website is NOT a "help me find this driver" website.

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.

Driverpacks does not currently support Windows 64-bit.  Sorry. sad

Here is another tutorial for making 3rd party driverpacks that you might find easier to follow:

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?

Do not use nLite to add a driver after you've slipstreamed DriverPacks.  It can really mess up the install disk, because DriverPacks is designed to replace the official windows driver setup (the one that nLite uses).

If you find the driver, you can make your very own 3rd party pack.

However, if you only need this for one machine, I don't think you need to go to all of that trouble.  Might as well just install it yourself later.

If you want the device to be added to the official DriverPacks, get the Hardware ID and make a request for it in the Mass Storage Discussion area: … .php?pag=m

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

Uh...  DriverPacks is about slipstreaming drivers into a windows XP install disk...  I think you came here expecting that DriverPacks was about installing drivers for anything you're missing.

That topic discusses installing driverpacks into an existing installation of Windows XP.

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).


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

RIS installs are not officially supported by DriverPacks.  However, one issue that MANY people have with RIS installations is that they don't setup the network share to be exactly like a CD. … 405#p15405

Another thing that you might consider is that in many RIS situations you have to slipstream drivers for CPU and Network cards on your bootdisk (since you have to have a boot disk to even initiate the RIS to begin with).

People have done it, but the I386 folder locations have thrown them for a loop so be careful.  As I understand it, you have to basically treat the RIS image location just like a CD.  That is, you have to put the OEM folder that gets added as part of the slipstream process next to the i386 directory in the RIS.

You should be able to do a forum search for RIS and find some more helpful topics.

I did a quick search and found out you had already asked about RIS...

You should avoid creating new threads for the same thing.

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.

OverFlow wrote:

@tiger stop misleading people

My bad.  tongue  It's just something that happens with me, and I've seen others with the same problem.

If it works without doing what I said then you're gold - but if it does complain of missing files we may need to do something to the base...

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.

I think you just repeated everything I said tongue

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

AVG Antivirus doesn't catch anything.  Rather, it catches so few that I've decided it's a gateway virus.  It lulls the user into a false sense of security and lets all the really bad viruses in.

If you want a good free antivirus - go with Avast Antivirus.  Their home edition is free, all you have to do is request a home key from their website and they give it to you.  You have to renew that free home key every year, but it's at least a good antivirus.

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.

I still don't think you're doing the obvious thing yet...  OverFlow and I both said before that you need to put the contents of DPsFnshr.7z on your system root.

OverFlow wrote:

the contents of the bin folder and the contents of teh 7zip file must be in %systemdrive%\

and they are seemingly not according to your script results - make sure everything from DPsFnshr.7z is in %SystemRoot%

The easiest way to do this is to use OEMPreinstall Folders.  Here is a website that will help you: … e148b3d6c/

On your source disk make a folder called "$OEM$" and a subfolder called "$$".  Then unpack everything into that.  Make sure that you set the following value in your winnt.sif

OverFlow wrote:

trying to update an existing system image would be a VERY tough job.

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.

KB883667 was included in SP1 and SP2, wasn't it?  Actually, I think that KB883667 caused video driver issues and they had to release another hotfix to fix the hotfix.  That was supposedly all handled in SP1, though.

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...

2. Removed %SystemRoot%\DriverPacks directory.

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.

Uh.  Yeah...

2. Removed %SystemRoot%\DriverPacks directory.

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.

Good work.  Thanks for your input!  A lot of people have been having this same problem with RIS.

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


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

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...


You should slipstream Windows Media Player 11 before putting the addons in.  Like... Run nLite to strip everything out, and bring it up to SP2 if you have it - then slipstream WMP11... Then do the RVM addons (like IE7)...  Then you should do DriverPacks and finish it off with the ISO.


The system cannont find the file specified.

That line conscerns me.  You may need to extract the contents of "DPsFnshr.7z" to the root directory via $OEM$ folders and then run a cleanup file delete those extra files after DPsFnshr is complete.

That is, sometimes it isn't enough just to put the base in the disk source, you need to put the finisher in the right place on the disk too.