CAB compress Windows 7 Drivers (Page 1 of 2)

Well I'd like to fit all the current driverpacks on a DVD-R, currently the 64-bit drivers are a little over 5GB.  This is to be used on random computers that are missing drivers here and there.  I'm not interested in running dpinst.exe to update everything, as I've had problems in the past with it using incorrect video drivers that I couldn't roll back, and eventually just had to reinstall the OS.

I will see if I can run a recursive makecab, hopefully that will work.  Otherwise I guess I can just go dual layer.

Here is my first try at a script.  It works well except for a couple issues.

First, it only appends an _ on the extension instead of replacing the 3rd character.  I don't know if this will affect the drivers' installation.

Second, there are about 350 files that it is compressing twice, and appending two _'s on the extension.  Not sure why this is happening...

@ECHO OFF
SETLOCAL ENABLEEXTENSIONS
SETLOCAL ENABLEDELAYEDEXPANSION

CD /D "%~dp0"

FOR /R %%X IN (*.dll, *.sys, *.cfg, *.cpl, *.din, *.icm, *.forms, *.oem, *.pop, *.pnf, *.resources, *.rtf, *.rom, *.tvp, *.rfx, *.tip, *.vp, *.htm, *.html, *.reg, *.txt, *.cap, *.dat, *.xml, *.drv, *.lib, *.js, *.lrc, *.man, *.mof, *.mui, *.nvi, *.chm, *.hlp, *.blb, *.eng, *.dan, *.deu, *.nld, *.dut, *.esp, *.fra, *.ger, *.ita, *.jpn, *.kor, *.por, *.spa, *.swe) DO MAKECAB "%%X" "%%X_"& DEL /F /Q "%%X"

ENDLOCAL

The space saved is substantial.  The original directory size was 5.11 GB, and after compression it has shrunk to 3.7 GB, which is actually much better than I anticipated.

Wow this is an excellent idea, this should save me some space in my driverpack

Would be cool if it worked with the driverstore

Last edited by ricktendo64 (2013-11-01 15:44:23)

My Windows 7 integration instructional videos

Nibus, any driver uses machine language, and help files use what's there.

the crux to SIZE is, the HWID really only needs one set..  of all these languages

There were (in the past) WDM files. them are not needed (all in wdm can be safely deleted)

language for help, is not needed (and that alone will save big space)

default language in windooz in amerikaneez ingleez, and you will most likely NOT see EN folder
(you do know that even British English have to get american ingleez out of our language choices?)

the point is, I figure 3.8Gb from your driver collection are not needed at all.

That was the help I can offer you.

Now I need your help

Can you upload for me to download your collection, so I can filter this for drivers you dont even need at all

say where to, i will DL them next thursday
fellow geek

Last edited by Jaak (2013-11-01 17:34:04)

Note to Jeff,
remember when we had to create HWID finder from scratch? The early SED filter I originally used, the russinicof and de microsoft scripting guy tool found less..
Very early on we found HWID that early windows filter (win orig setup) missed, and that got us help from warmsnow (a DriverPacks guru back then)
And so on, and so on.

Our work had kinda eliminated all error driver writers left in by scripting around it, or by culling (pruning) out known conflicting duplicates.

a month later, a new driver for realtek came out, and it had all but two new HWIDS, and a known 7526 conflicts with its OWN legacy drivers.
The problem with driver writers was that they did NOT delete the HWID it was no longer suitable for.

The great job we did was that we had finally figured this out and once we knew what what worked in old and not in new, people like Jeff and Mr Smartepants could script around it.
Finding the culprit duplicates and generics way back when was one step. (I think I can honestly  say I was a great help in that)
Developing software to help filter out them conflicts was not  something I could do.

You know, I came on board by asking a question.
years ater, late 2009 I saw that ideas we'd discussed really got going, and I had a tough time in real life (steelplant issues, health issues)

in 2010 I got in a seriuos accident, and was immobile left side for months. it took 10 month revalidation, and I am still partially invalid.

But my brain started to work again.

And to return the drivers to the original extracted state you could use 7z.exe

for /f %X in ('dir/b *.*_') do 7z e %X & del /f /q %X

My Windows 7 integration instructional videos

Very interesting, thank you very much for this information.  I actually just downloaded all the Windows 7 x64 DriverPacks from the torrents here:  http://driverpacks.net/driverpacks/latest  and then exracted them all to the same directory.  Turned out to be a little over 5GB.

Maybe even more savings can be had when deleting unneeded files as well as compressing.

Fantastic!  I'll give that one a shot on the entire disc. 

I apologize I was unable to test over the weekend, I was out of town.  However I have a few new computer builds I can test these drivers on today or tomorrow, so I will get them all CAB'd up today and on a DVDR for testing.

Thank you all for your help and input!

you could just name the pack(s) with a valid NT5 name and run BASE on it in SAD mode

then you can see how much space is saved and test that the existing method is also valid for NT6.

and not have to write any code ...   Quick and easy

I'm trying to carve out some time for updating BASE SAD and Finisher soon. if it works with the test above then i can code it fast and easy to just do nt6 packs. i can also add and remove extensions from the list, or add exceptions for specific files / folders.
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!.

Rats... I was trying to make it easy for ya, sorry.

Don't bury yourself in code, keep it simple we just need proof of concept .

I can do this very easy if it works.

Does it work???

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

It didn't work on the 660 because the official drivers don't have support for the 660.
Check out each subforum for beta packs that have newer driver releases.
The beta driverpacks are larger as they contain more drivers.

Please revisit my original advise.

instead of INCLUDE, do EXCLUDE. (not equal to)

and exclude these...  "_",  "AX", "VP", "CAB", "CAT", "CMD", "INF", "INI", "EXE"

The best news is it looks like it works just fine !

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