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

Hi Guys,

I was thinking about how we could go about making the driver installs a bit quicker, and I have a rough idea that I'm not sure would work, so I'm just gonna throw it out there.

Currently (Correct me if I'm wrong) it appears that when you run the driver installer from a USB stick, it asks you if you want to discard drivers for other windows versions, then it copies the drivers across to C:\D\ and goes through each driver, one by one, checking if the device is present.

Even on a quick machine with an SSD, this still takes a good 5-10 mins, including the time it takes to copy the drivers from the usb stick to the HDD.

The question and suggestion I want to ask, is...

Why can't we cache all the device ID's that we have a driver for, to a file on the usb stick, then run a program to determine the device ID's on the PC, and only copy across the drivers that are required?

I understand why the drivers can't be installed direct from the usb. If it updates the usb controller driver, the usb stick will stop working and will mess up the install.

I know there are programs out there to determine the device ID's of the current hardware, so why can't those ID's simply be compared to a list, instead of going through all drivers, one by one?

Have I misunderstood something, or is there something I just don't get?

I'm doing testing in VMs right now...I'll upload this tonight if all goes well.
Here's what I have so far:

:: Changelog:
:: v130423 v3.0
:: Remerged codebases (briefly forked during simultaneous development).
:: Sound effect script removed from bin folder...SAD now creates it dynamically.  (SteveDun)
:: SAD now calls UAC Check for NT6 OS's dynamically (replaces the Elevate commands in bin folder) (SteveDun)
:: Now fully works when added to windows ISO's. (SteveDun)
:: Corrected error's in Cleaning Phase.  (SteveDun)
:: Modified code to support commandline switches using either slash '/' or dash '-' (example: script.cmd -s) (Erik Hansen)
:: Modified extraction code to minimize extraction windows. (Erik Hansen)
:: Added code to count extraction progress in title bar. (Erik Hansen)
:: Cleaned up displayed text to center in window. (Erik Hansen)

:: v130420 v3.0 (Erik Hansen)
:: Fixed bug in :Elevate section where commandline switches were not passed to utility when run as a normal user.
:: Fixed bug where utility would try to delete itself after complete.
:: Minor fixes to :Cleaningphase section and :Usage verbiage.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I actually started to code this up (in VBS - don't hate).

* Recursively walk the uncompressed DP directory structure (don't need it compressed if you're only copying select drivers)
* For each .inf, parse out the HWIDs and driver locations.
* Do a quicksort and delete the dupes.

What I ended up with was a tab-delimited file that looks like:

8086&154D&7B118086    x64\Server\L\Intel\1\Winx64\NDIS62    ixn62x64.inf    74
8086&1557    x64\Server\L\Intel\1\Win64\NDIS62    ixn6264.inf    61
8086&1A38    x64\Vista\L\Intel\4\NDIS61    qd160x64.inf    51
8086&1C00    x64\All\M\Intel\5    cougide.inf    40
8086&1C01    x64\Win7\M\Intel\5    couide2.inf    34
8086&1C02    x64\All\M\Intel\3    iaAHCIC.inf    95

Fields:

1 = HWID
2 = relative path
3 = inf file name
4 = line number in .inf

The last two fields are for debugging.

The whole thing takes roughly 20 seconds. This is with 5 packs on an SSD  - about 1 GB and 4,500 files.

I wrote a separate script that reads the entire index into an array. It then uses WMI to retrieve HWIDS and do a binary search of the array. That part takes all of a second per this log file.

4/23/2013 12:05:42 PM Loading Index
4/23/2013 12:05:42 PM Index loaded
4/23/2013 12:05:42 PM Get driver failed for 10EC&8168&84321043 Realtek PCIe GBE Family Controller
...
4/23/2013 12:05:42 PM Starting copy
4/23/2013 12:05:42 PM tools\Robocopy dpacks\x64\All\C\Intel\1 \dpacks-sel\x64\All\C\Intel\1 /s /r:0
4/23/2013 12:05:42 PM tools\Robocopy dpacks\x64\Win7\C\Intel\1 \dpacks-sel\x64\Win7\C\Intel\1 /s /r:0
...
4/23/2013 12:05:43 PM Copy done

I got stuck at this point as I didn't really understand how to use this with dpinst.

Maybe someone smarter than me *cough* could take this concept and actually make it work.

Ken@fri,
Thats why there is a option to delete or keep them in the script.  Of course if silent it will auto leave it but that might change with mr_smartepants new version to be released soon (I dont know).

(Battery)
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{72631E54-78A4-11D0-BCF7-00AA00B7B32A}\0000" && echo Laptop found!

or

(Portable Battery)
WMIC SystemEnclosure GET ChassisTypes
WMIC ComputerSystem GET PCSystemType

would work for lappys.    It looks for the battery value in the reg entry in the first example.  This would not work on image restore though just to let you know for that reg entry isnt included in images usually.  The second example gets its info from the SMBIOS tables off the motherboard which is the method I would prefer for some systems might not have the reg entry like from a image restore.

@ mr_smartepants this would be a good addon if ya will to only leave behind touchpad/HID if lappy present.

Last edited by SteveDun (2013-04-24 05:37:50)

Well now THAT is very encouraging!
To be honest, once a match is made, just moving the encapselating folder to a temp dir then pointing dpinst to that temp dir would be the easiest method.
Post the code you have in code boxes and one of us will run with it.

BTW, I don't hate VBS, it's just not my forte (like a left-handed hammer).

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I'm currently chasing a bug in the :Elevate section (and elsewhere).  The bug is in how the variable %0 is used.
When the SAD script is called from a command line, then %0 populates as a fully qualified path with name.ext (C:\SAD\DP_Install_Tool.cmd).  But when the SAD script is double-clicked, the :Elevate .vbs script fails because %0 only populates with the name.ext, not the path (DP_Install_Tool.cmd).
This can be solved by substituting %0 with %~dpnx0 (DrivePathName.eXtension) which has a more consistent behavior.
To illustrate this behavior, create a test.cmd file with the following code:

@ECHO off

ECHO Path with '0'    : %0
ECHO Path with 'dp0'  : %~dp0
ECHO Path with 'dpnx0': %~dpnx0
PAUSE

Run from command line:

When double-clicked:

I'm still busy testing M1 and M2 in both XP and Win7...but I'm close!

Jeff is right about the DriverPacks archive streams.  When I build the final DriverPacks, I use the tool here: http://forum.driverpacks.net/viewtopic.php?id=4789
I don't think the testing packs are built the same way (solid packs).

@DanInWV, please post your sample code so we can see what's going on.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

oVoice.SpeakStream oSpFileStream......it cant speak the tone if no or not the correct sound card driver installed. 

solution for mr_smartepants to add to his script to correct this error is no sound card driver is installed...

IF NOT EXIST "%temp%\tada.vbs" (
ECHO Set oVoice = CreateObject^("SAPI.SpVoice"^) > "%temp%\tada.vbs"
ECHO Set oSpFileStream = CreateObject^("SAPI.SpFileStream"^) >> "%temp%\tada.vbs"
ECHO oSpFileStream.Open "%windir%\Media\tada.wav" >> "%temp%\tada.vbs"
ECHO On Error Resume Next >> "%temp%\tada.vbs"                                       <---- The correction if error to continue
ECHO oVoice.SpeakStream oSpFileStream >> "%temp%\tada.vbs"
ECHO oSpFileStream.Close >> "%temp%\tada.vbs"
START /W %windir%\System32\wscript.exe "%temp%\tada.vbs"
DEL /F /Q "%temp%\tada.vbs"
) >nul

Tested with sound card driver enabled and disabled......no more error's. 

Last edited by SteveDun (2013-04-24 19:07:05)

No problem.

And anyway, the work done on the Driverpacks is SIMPLY FANTASTIC, AMAZING!

Thanx.

Last edited by Ken@fri (2013-04-24 18:46:54)

Cool, grabbing now.
You know, one of the great tools I use to do line-by-line code comparison is WinMerge.  http://winmerge.org/
It'll spot the difference between a space and a tab, as well as between a short-dash and long-dash which depending on the font used look the same.
Speaking of fonts, I prefer the free Adobe SourceCodePro.  http://sourceforge.net/projects/sourcecodepro.adobe/

I have two text editors of choice.  NotePad2 (with code folding) and SublimeText2.
http://xhmikosr.github.io/notepad2-mod/
http://www.sublimetext.com/2

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I added some code to pull the OS info from WMIC if the registry isn't loaded yet.  Using WMIC is slower, but more compatible.
The only problem IIRC is that in most cases, WMI isn't available during PE setup, so I'm not sure how useful that will be.
In my tests, pulling the info via WMI took 15 ms but the reg query only took 5 ms.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Hi!

I've made some tests with SAD3-130423 fixed by SteveDun.

Every time I use the switches (/S or -S  -no problem with /SR or -SR), at firstlogon, I have a message asking me to reboot my computer.

Any idea?

EDIT:

After fresh install on HP ProBook 4510s, the followings TouchPad drivers appear in Add/Modify programs CPL at the same time:

• Dell Touchpad (from ALPS ELECTRIC CO., LTD)

• ETDWare PS/2-X86 10.7.13.1_WHQL (from ELAN Microelectronic Corp.)

• Synaptics Pointing Device Drivers(from Synaptics Incorporated)

Last edited by Ken@fri (2013-04-27 04:33:28)

@mr_smartepants

Thanx.

I'll waitin' 4.