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

you can use SAD with a custom driverpack, or you can make a custom install with DPINST.exe yourself
SAD is a script that uses / automates Microsoft DPINST. dpinst.exe is the engine that makes it possible.

It's pretty easy to learn and use even if you have entry level code skills

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

you can simply run SAD on each workstation that needs updated, but, you must have the driverpacks on the local machine.

since the entire set of packs is rather large a custom pack makes more sense. You could do it with the entire set if you like.

you could use a number of methods to automate the process at night from a server, that would depend on your specific setup as to how you would do it.

I will offer you this old adage "If it ain't broke, don't fix it" 
Translation: The machines are running fine, don't update the drivers. When they break, then update the drivers.
there is very rarely a benefit to updating a working machine, and the benefit is always negligible. Updating the drivers may in fact cause issues, perhaps even make them non-bootable.

Can you elaborate on why you wish to do this?

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

you simply put the drivers you want in the correct folder in SAD. The driver folders are separated by OS and type (x86 or x64) there are place holders to help you, it really could not be any easier. We compress our packs to save space but that is not neccessary, and would be an extra step you could skip.

so download sad put your windows 7 X64 drivers in

SAD\NT6\x64\D\your drivers here
SAD\NT6\x86\D\your\drivers\here
ETC...

NOTE : uncompressed drivers go in subfolder "\D\"  if the folder "D" exists then any DriverPacks are ignored.
It's an either or situation, DriverPacks OR extracted drivers.
(why bother to extract them if they are already extracted )

Add a \D\ folder and put your drivers in there, simple and easy.
the D\ folder will be searched recursively so you can put as many folders as you like.

run with admin privileges   "SAD\DP_Install_Tool.cmd /KR"

Or one of the other silent switches listed in the readme on the machines that you wish

from the included readme file...

if you are going to push this from logon script or similar keep in mind you must put the \SAD\.. folder on teh remote machine and run it locally on the remote machine.

We have made it as easy as possible to do what you want

best wishes for your success.

PS if you are dead set on making a DriverPack start another thread. (perhaps in graphics sub forum)

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

What do I need to do to get this to run in Win 8.1 x64? I see references to the script supporting Windows 8.1, but upon running, I get a "windows 8.1 Pro - which uses DriverPacks - not currently supported - please the exit program now" and prompt to exit

Edit; using the latest version available on the 1st page link SAD3-130627

Last edited by Fragbert (2014-03-27 07:03:18)

The WinSetupFromUSB crew has linked to your project, Mr_Smartepants!

Last edited by TechDud (2014-04-07 20:01:25)

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)

mr_smartepants im interested in using SAD3 for a winxp x64 install ive got all my drivers for a install just wondering as nt5 only has a x86 folder what should i do so i can add mine after desktop?? is the script ok to just add a x64 folder and will it then unpack and use what is needed

Last edited by darky35 (2014-04-13 05:33:32)

Hello,

When I put these files in $1 he deletes the DP_Install_Tool.cmd but the folders bin and nt6 stay in the root of my installation, can I also delete this folders after install or are they still needed for one of the two methods? I believe that the D folders must not be removed if I am correct.

Method 1 according to your readme file says that it will scan on removable drives, when I use it with the setupcomplete the files are placed in my root, will windows scan there also when adding new hardware?

My goal is to have an installation where when I add a new device windows will automagicly find the correct drivers, I think method 1 is the way to go or am I wrong and do I need to create a disk for it?

Thanks in advance!

1

Last edited by RyperX (2020-08-28 06:42:25)

You should consider using Snappy Driver Installer. It's able to install nested drivers in a single go.
http://forum.driverpacks.net/viewtopic.php?id=10794

I must warn you, though. Be careful with USB 3.0 drivers from Intel. You'll get BSOD if you try to install latest drivers on an old generation chipset. Snappy Driver Installer is able to distinguish different generations and pick the correct driver but drivers inside the driverpack must be put inside folders with names intel_2nd and intel_4th.

Intel USB 3.0 driverpack for Snappy Driver Installer.
http://www.mediafire.com/download/actdb … tel_FIX.7z
Do not use this driverpack with SAD for it cannot pick the correct driver.

By the way, SAD uses DPInst to do the actual work of picking and installing drivers. SAD can be configured to use Snappy Driver Installer in place of DPInst by changing only one line in DP_Install_Tool.cmd.

It shows the License dialog only the first time you run it. You can see that settings.cfg includes the -license switch from now on.
You can also run SDI with the -license switch to suppress the dialog.

Awesome to get good feedback on SDI since it's new to us here at DriverPacks.net.
It looks very comprehensive, looking forward to trying it myself.

RyperX is right... quit hijacking my thread man!

As you have discovered now this has to do with nested driver installation. USB depends on Chipset. Since you did not integrate your chipset drivers into your install WIM your OS is not ready to install the USB drivers. you can run SAD a second time or the best thing to do is to add DriverPack MassStorage and DriverPack Chipset to your setup and install WIM files, this keeps the size of the wim down and eliminates nested driver issues.

Best of luck

Jeff

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

Are Bigfoot's Vista-7-8 beta DP's fully compatible with SAD3?
It would seem that the tree structure has been grafted, à la Frankenstein there.  That could be instrumental.  Leuk!

Last edited by TechDud (2014-07-02 13:27:56)

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)