Search options (Page 85 of 159)

Updated to 1007b1

Implemented in DriverPack LAN 1007.
Thank you!

How in the h*ll did this one post get over 94 thousand views!  People must think this is important.
The driver in DriverPack LAN \NV3 is the same as the one in the first post EXCEPT that the file in the first post has driver-signing intact.
I'll restore the files from the first post back into NV3 but I've kept the modified .inf files tucked away in NV3.7z for safe keeping.

Implementing 15.4.1 in DriverPack LAN 1007

I typically only add mass storage to the boot.wim and then chipset, mass storage, LAN, & WLAN to the install.wim for this very reason.  Windows Update will typically download whatever else is needed for that system.  Another option is to create a script to run at first logon to purge the %windir%\system32\driverstore\* directory.
I haven't played with dpinst in Win7 but I'm certain we can tailor our SAD command script to work in both Vista/Win7.

I'll look into it.
I wouldn't say they're very popular.  I've never heard of that model and it's all the way at the bottom of Logitech's support page which indicates it's also very old.

I'm looking at it right now and that HWID is NOT "remarked", commented, or hidden in any way in CX_95952.inf.  CX_95952.inf in DriverPack Graphics C 1005 is signed by ATI and unaltered by us.  If it's remarked, then someone else did that.  CX_76825.inf is heavily altered by me and is from a different driver entirely.  That HWID is supposed to be blocked in CX_76825.inf.
I suggest you redownload DriverPack Graphics C 1005 and check for yourself.
It's refreshing to have a support "call" from someone who knows the material!  Instead of the usual "Hey dude your stuff is broke, fix it" posts.
So you'll understand how dpinst will do a recursive search for a HWID through each .inf and "rank" any possible matches.  An ideal match would be a total VEN_*&DEV_*&SUBSYS_*&REV_* match with a signed driver (if available).  Those are rare, so the next ideal match would be VEN_*&DEV_*&SUBSYS_* and then VEN_*&DEV_* (we term that "generic") with the last choice being VEN_* (a "Super-generic").
I haven't had the best of luck using SAD (which calls dpinst) on ATI hardware.  Their drivers just do not react very well to that environment.  The recommended install method is direct integration into the OS source.

Yeah, that's true.  The batch file can't delete a file in use.
The inst_upd.cmd file needs to have a line added to it (taskkill):

ping 127.0.0.1 /n 15
taskkill /f /im dps_base.exe
del /f /q DPs_BASE.exe
"%insert_variable_location_here%\DPs_BASE_1006.exe" x -y -aoa -o"%insert_variable_location_here%"
del /f /q DPs_BASE_1006.exe
ping 127.0.0.1 /n 5
DPs_BASE.exe
del %0

To be honest, I haven't tried it.
I'll give it a shot and see what happens though.

Sounds interesting.
Any info on what versions of Windows it works with?  Screenshots?
Thank you for your contribution!

910 was the previous working one.  Maybe it should stay.
I don't have any bluetooth devices (except my phone), so I can't test anything.