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.
1 2007-12-30 21:19:08
Re: I need Toshiba Satellite m55 series laptop driver (3 replies, posted in Feedback and Support - DriverPacks Base)
2 2007-12-27 18:27:41
Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr (8 replies, posted in Feedback and Support - DriverPacks Base)
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.
3 2007-12-23 12:07:56
Re: Windows XP 64-bit Integration? (8 replies, posted in Feedback and Support - DriverPacks Base)
Driverpacks does not currently support Windows 64-bit. Sorry. 
4 2007-12-20 07:27:23
Re: Fujitsu MHW2080BH ATA..not detected (9 replies, posted in Feedback and Support - DriverPacks Base)
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?
5 2007-12-19 20:25:39
Re: Fujitsu MHW2080BH ATA..not detected (9 replies, posted in Feedback and Support - DriverPacks Base)
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.
http://forum.driverpacks.net/viewtopic.php?id=5
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:
http://forum.driverpacks.net/viewforum.php?id=12
6 2007-12-19 17:07:32
Re: Fujitsu MHW2080BH ATA..not detected (9 replies, posted in Feedback and Support - DriverPacks Base)
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. 
7 2007-12-17 06:42:39
Re: Pleeez help this newbie ..... (2 replies, posted in DriverPack Graphics)
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.
http://forum.driverpacks.net/viewtopic.php?id=1756
That topic discusses installing driverpacks into an existing installation of Windows XP.
8 2007-12-14 09:42:40
Re: DriverPacks BASE tutorial (English) (32 replies, posted in Frequently Asked Questions)
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).
9 2007-12-14 09:38:10
Re: RIS input (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.
http://forum.driverpacks.net/viewtopic. … 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.
EDIT:
I did a quick search and found out you had already asked about RIS...
You should avoid creating new threads for the same thing.
10 2007-12-06 05:45:43
Re: setupapi.log errors (3 replies, posted in Feedback and Support - DriverPacks Base)
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.
11 2007-12-04 03:30:31
Re: desktop.ini (7 replies, posted in Feedback and Support - DriverPacks Base)
I think you just repeated everything I said 
12 2007-11-26 08:09:36
Re: [solved] False Positive (trojan horse) in MUTE.EXE (DPbase 7.05.2) (10 replies, posted in Feedback and Support - DriverPacks Base)
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
13 2007-11-26 05:57:56
Re: [solved] False Positive (trojan horse) in MUTE.EXE (DPbase 7.05.2) (10 replies, posted in Feedback and Support - DriverPacks Base)
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.
14 2007-11-25 20:17:51
Re: [Solved] SB.ini - AutoIt Error - Line 0 (File "I:\DPsFnshr.exe"); (33 replies, posted in Feedback and Support - DriverPacks Base)
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.
15 2007-11-25 15:41:52
Re: [Solved] SB.ini - AutoIt Error - Line 0 (File "I:\DPsFnshr.exe"); (33 replies, posted in Feedback and Support - DriverPacks Base)
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:
http://unattended.msfn.org/unattended.x … 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
[Unattended]
OemPreinstall=Yes16 2007-11-16 06:57:50
Re: Got stuck with KTD update. Help please. (5 replies, posted in DriverPack Mass Storage)
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.
17 2007-11-15 15:50:40
Re: [SOLVED] newdev.dll is missing (25 replies, posted in Feedback and Support - DriverPacks Base)
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.
18 2007-11-13 06:33:33
Re: Critical error: Could not copy Intel Chipset drivers' .inf files from (7 replies, posted in Feedback and Support - DriverPacks Base)
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).
19 2007-11-08 16:41:44
Re: Got stuck with KTD update. Help please. (5 replies, posted in DriverPack Mass Storage)
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.
20 2007-11-08 16:41:10
Re: How to update already installed driverpacks? (Disk image + sysprep...) (1 replies, posted in Feedback and Support - DriverPacks Base)
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.
21 2007-11-08 16:37:41
Re: Setup cannot copy the file: setupORG.exe (presetup.cmd) (43 replies, posted in Feedback and Support - DriverPacks Base)
Good work. Thanks for your input! A lot of people have been having this same problem with RIS.
22 2007-11-08 16:31:01
Re: [Solved] SB.ini - AutoIt Error - Line 0 (File "I:\DPsFnshr.exe"); (33 replies, posted in Feedback and Support - DriverPacks Base)
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...
exit23 2007-11-07 07:23:14
Re: [Solved] SB.ini - AutoIt Error - Line 0 (File "I:\DPsFnshr.exe"); (33 replies, posted in Feedback and Support - DriverPacks Base)
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.
Also:
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.
24 2007-11-02 01:36:34
Re: Wish to install also drivers defined in winnt.sif/oempnpdriverspath (4 replies, posted in Feedback and Support - DriverPacks Base)
Right. The whole point of driverpacks is to be a replacement for the standard driver installation for XP setup.
That said, you need to make your own custom "3rd party" driver pack for the drivers you want to install yourself.
Check out how to make a 3rd party pack yourself here.
25 2007-10-22 12:32:46
Re: Is there a more updated version of "DPs_fnsh.cmd" available? (4 replies, posted in Feedback and Support - DriverPacks Base)
Does the new base recognize and remove the old formats automatically? That might be why...