Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (Page 18 of 22)

i saw this and i put exactly what i saw i did not think that the systemdrive needs to be changed sorry so i put in the script:

@echo off
START D:\sources/$oem$/$1/D/SAD3\DP_Install_Tool.cmd

OR

@echo off
START %CDROM%\D\SAD3\DP_Install_Tool.cmd

I tried both options in the iso but they did not work

the last attempt i did was with :

@echo off
START %CDROM%\sources\$OEM$\$1\SAD3\DP_Install_Tool.cmd /s
DEL %0

But did not work also, but when i run the the setupcomplete.cmd manual from the disc it setup`s the drivers normal
Any Help ???

Last edited by symbios24 (2014-07-03 19:25:30)

Looks like my question got lost in the shuffle.
   bump --> http://forum.driverpacks.net/viewtopic. … 740#p57740

Release folder path:    ..\x64\All\M\ARECA\
Bigfoot:                      ..\x64\M\All\Areca\

Does SAD3 support this or other changes to folder tree?
  Can it cause some drivers to not be deleted when deleting other OS support?
    Pondering potential pitfalls perplexing pack person.

Also looking for a copy of SAD2 v101203 for potential win2k support.
Is "SAD1" a part of DPs_BASE?

Thank you.

Last edited by TechDud (2014-07-04 15:49:48)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

my setupcomplete.cmd file path is "sources\$OEM$\$$\Setup\Scripts"

and my SAD3 path is "sources\$OEM$\$1\SAD3"

my contents of the setupcomplete.cmd is

@echo off
START %CDROM%\sources\$OEM$\$1\SAD3\DP_Install_Tool.cmd /s
DEL %0

i tried by adding the extra D folder

@echo off
START %systemdrive%\D\SAD3\DP_Install_Tool.cmd

its not working.

Last edited by symbios24 (2014-07-04 21:35:59)

Hi again!  How are DriverPack.ini files supported by SAD3 in NT6?
Looking to be able to process exceptions via DPs_Fnshr, if practical (not for chipset/MS though, if i have that correct).

Last edited by TechDud (2014-07-05 07:49:12)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

I lit the fuse to my BBQ, that's about it.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

DriverPack Solution can only be used with the driverpacks which are included with it. It won't be able to use the driverpacks from driverpacks.net because they don't have markers(folders named 6x86, AllXP, NTx64 and etc) which help DriverPacks pick the compatible drivers.

SAD shouldn't be used with driverpacks from DriverPack Solution because SAD installs drivers via DPInst which is notoriously bad at doing its job of finding and installing drivers. Since driverpacks from DriverPack Solution are not meant to be installed via DPInst, they contain drivers which can't be installed via DPInst(and theretofore SAD).

There's another application: Snappy Driver Installer. It can be used with any driverpacks because it doesn't rely on markers to find compatible drivers and doesn't have any drawbacks which the other applications have. In fact Snappy Driver Installer can do anything SAD/DriverPacks can do and it can do it better.
Here's the thread: http://forum.driverpacks.net/viewtopic.php?id=10794

Hello i have a custom made winxp disc with the old driverpacks program how can i add the sad3?? i just replace the old DP_Install_Tool.cmd with the new one? and also after the setup of drivers finish it deletes the files used will if i replace the old tool with the new one it will do the same or i need to do something more that replacing files?
in final words how do a i add it to a winxp cd that already has it but it`s a very old version(2009)
and a last one which one should i use sad2 or sad3?
thanks

Last edited by symbios24 (2014-10-05 21:35:15)

i want to put a newer version of driverpacks program since the one included is too old and it`s not working with newer driverpacks as some of the require sad3,but i dont want to go from the beggining create the windows disc again so i`m asking how can i replace the driverpacks program in the windows disc(iso) with a newer one? just replace the folder or do something more?? In General words if i want to put winxp sad3 with the driverpacks in a winxp disc in the readme file of sad3 it says:

How to add ISO's:
%WinXP-Disc%\$oem$\$1\ (entire contents of SAD3 folder with all DriverPacks goes here %systemdrive%\)
%WinXP-Disc%\$oem$\$1\DP_Install_Tool.cmd
Call the Dp_Install_Tool.cmd from winnt.sif file which will go in %WinXP-Disc\I386\WINNT.SIF

what is the call thing i don't understand what i have to put in the winnt.sif file??

i searched in the disc that has the old driverpacks program in the winnt.sif file it has this:

[GUIRunOnce]
command9="%SystemDrive%\DPsFnshr.exe"
wucdcreator="wscript.exe %systemroot%\RunOnceEx.js"

so what i put for the sad3 in this file??

Last edited by symbios24 (2014-10-07 02:16:12)

Thank you for your help can i put the silent switch /S in the end also? and where i put the driverpacks?? inside the OEM\NT5\x86 folder or i leave them in the main folder of sad eg. "OEM"

you mean you want the page that i get the driverpacks here?

if i give you the names will be easier

this are the new driverpacks

DP_Bluetooth_MS-Misc_wnt5_x86-32_1408061.7z
DP_Chipset_wnt5_x86-32_1308271.7z
DP_CPU_wnt5_x86-32_904.7z
DP_Graphics_A_wnt5_x86-32_1401181.7z
DP_Graphics_B_wnt5_x86-32_1408051.7z
DP_Graphics_C_wnt5_x86-32_1403071.7z
DP_Graphics_PhysX_wnt5_x86-32_1408051.7z
DP_LAN_wnt5_x86-32_1408061.7z
DP_MassStorage_wnt5_x86-32_1308271.7z
DP_Misc_wnt5_x86-32_1308272.7z
DP_Modem_wnt5_x86-32_1403111.7z
DP_Phone-Mobile_wnt5_x86-32_1406041.7z
DP_SmartCard_wnt5_x86-32_1403281.7z
DP_Sound_A_wnt5_x86-32_1406011.7z
DP_Sound_B_wnt5_x86-32_1406021.7z
DP_Sound_C_wnt5_x86-32_1406011.7z
DP_WebCam_wnt5_x86-32_1405281.7z
DP_WLAN_wnt5_x86-32_1408061.7z
DP_Graphics_ATi-TV_wnt5_x86-32_1310291.7z
DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z

and the old driverpacks i had before for xp are those that already available in the latest,in the driverpacks download page

Did you make any changes to your XP install disc after you added DriverPacks?

Did you fail to make a copy of the disc from immediately before you added DriverPacks?

if the answer to either of these questions is yes then it is unlikely that your mass storage drivers can be updated.
the other drivers may be updated simply by replacing them with newer versions (woo hoo)

it's that simple for all but mass storage

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.