Jump to content

Repacking driver.cab


RyanVM

Recommended Posts

OK, I tried searching for the answer, but IBB is pretty much useless in its search functionality. What are the settings used for makecab when recompressing driver.cab (after combining it with the other driver cabs) that allows for faster decompression? Is it just lowering CompressionMemory?

Link to comment
Share on other sites


Here's the link to a specific thread about CABARC.EXE (CabARC) It's part of a discution on longhorn but it's the correct tool to use for making CAB's for XP install discs.

Here's the command line for it:

cabarc -r -p -m LZX:21 N mmssetup.cab *.*

I've used it several times when I was building both unattended XP install discs and testing MCE 2005. It's part of an offical Microsoft SDK that you can download free from their site (sorry cant remember where). It's offical name is "Cabinet Software Development Kit" the commands I've put in are very well documented but I've found I can shave a few meg off any standard MS cab by using this higher compression optimisation.

Link to comment
Share on other sites

This is driving me nuts, because I think it was GreenMachine who posted on this before, but I can't find his post.

Why don't you take a look at Jdeboeck's batch files? They are able to remove drivers and other stuff and then recompress everything!

http://jdeboeck.msfnhosting.com

That's what I use :P. It suffers from the slow decompression time that I'm referring to. IIRC, you can adjust the settings so that the cab ends up at around 100MB (instead of ~80MB), but decompresses way faster. Heck, nLite even has the option to do the one or the other.

I think I'm gonna PM nuhi to get him in this thread :P

Link to comment
Share on other sites

Here's the link to a specific thread about CABARC.EXE (CabARC) It's part of a discution on longhorn but it's the correct tool to use for making CAB's for XP install discs.

Here's the command line for it:

cabarc -r -p -m LZX:21 N mmssetup.cab *.*

I've used it several times when I was building both unattended XP install discs and testing MCE 2005. It's part of an offical Microsoft SDK that you can download free from their site (sorry cant remember where). It's offical name is "Cabinet Software Development Kit" the commands I've put in are very well documented but I've found I can shave a few meg off any standard MS cab by using this higher compression optimisation.

LZX:21 is what's giving you the higher compression. Those options are available with makecab as well, using the command switches /D CompressionType=LZX and /D CompressionMemory=21.

Link to comment
Share on other sites

either that, or you're looking for this:
makecab /D CompressionType=LZX /D CompressionMemory=21

This is for individual files, I suppose.

And it's completely irrelevant. In fact, I already said those settings weren't what I needed.

LZX:21 is what's giving you the higher compression. Those options are available with makecab as well, using the command switches /D CompressionType=LZX and /D CompressionMemory=21.
nuhi gave me exactly what I was looking for.
Link to comment
Share on other sites

The point of that number isn't to increase compression, but to speedup decompression. Using the default value, it can take a long time to decompress files from there (setup will just "hang" from time to time).

FolderSizeThreshold=5000000 made a HUGE difference.

Link to comment
Share on other sites

I just found this document :http://home.hiwaay.net/~pittman/archive/makecab.doc, which explains makecab/ddf files in detail.

This is what it says about FolderSizeThreshold:

Folders are compression/encryption boundaries.  The state of the compressor and cryptosystem are reset at folder boundaries.  To access a file in a folder, the folder must be decrypted and decompressed starting from the front of the folder and continuing through to the desired file.  Thus, smaller folder thresholds are appropriate for a layout where a small number of files needs to be randomly accessed quickly from a cabinet.  On the other hand, larger folder thresholds permit the compressor to examine more data, and so generally yield better compression results.  For a layout where the files will be accessed sequentially and most of the files will be accessed, a larger folder threshold is best.

--

Pyron

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...