|
Compression Engines in InstallAware
As of InstallAware X2, two compression engines are provided with the product. This change has been introduced to optimize the InstallAware engine runtime size.
InstallAware X8 introduced a third compression engine, used in the higher compression grades (heuristic optimized and binary optimized) with a 1.5 GB dictionary size. When using these higher compression grades, the compression engine packaged with built setups is managed internally by InstallAware, and the following discussion does not apply.
As of InstallAware X17, native (de)compression engines for and platforms have also been introduced, in addition to an upgrade of the existing engines to support dictionary sizes of 2 GB, 3 GB, and 4 GB; new binary compression technology is also now supported. These engines are again managed internally, and the discussion below again would not apply.
Engine Locations
The full compression engine is installed inside your main InstallAware folder, under the name , as in previous versions of InstallAware.
The size optimized compression engine is installed inside the subfolder of your main InstallAware folder, under the name . This is new since InstallAware X2.
Switching Engines
Setups are built using the size optimized compression engine by default (the DLL file found at ).
You may rename or backup this file and replace it with the full compression engine instead.
You would need to do this only if you invoke any of the following commands in your setup script:
Or if you invoke any of the following commands in your setup script, but only on archive types other than 7ZIP archives:You do not need to use the full compression engine if you use only the following commands on only 7ZIP archives:
Default InstallAware setups, templates, wizard created projects, and application runtime installers are fully satisfied with the size optimized compression engine.