Click above to get retro games delivered to your door ever month!

 Compression overview
------------------------------------------------------------------------------
 Using Blinker to compress .EXE and .DLL files for the final link before
 distribution offers the benefit of minimising distribution costs, in the
 same way as traditional compression and archiving tools, but has the
 convenience and distinct advantage of not requiring an external
 decompression program at installation or run time. The fact that the
 program is compressed is completely transparent.

 In addition, network traffic is significantly reduced when .EXE and .DLL
 files are stored on a network server, since it is only the compressed image
 which is transferred across the network, rather than the complete
 uncompressed file.

 Another significant benefit is that compression is a very good form of
 encryption, thus programs compressed with Blinker are well encrypted
 against disassemblers and decompilers, protecting the hard work and
 innovation put into each of your programs.

 Blinker is able to transparently compress 16 bit Windows, DOS and DOS
 extended .EXE files and Windows and DOS extended .DLL files. In the case
 of real mode DOS or dual mode DOS extended programs the overlay files are
 not compressed, since the overheads would outweigh the benefits, as
 discussed in the section `Compressing DOS real mode programs' below.

 Decompression currently requires a maximum of approximately 100 Kb of extra
 memory above the normal requirements of a program. In the case of a DOS real
 mode program, this memory is not required once the program has started, so
 there is no loss. With Windows and DOS extended programs, however, segments
 are only loaded on demand, so this memory is not available to the rest of
 the program.

 For Windows and DOS extended programs, each segment is compressed separately
 to allow it to be loaded and discarded on demand at run time. The
 compression ratios achieved may therefore not be quite as good as those
 achieved by some archiving programs, as they are able to treat the whole
 .EXE as one block to compress. However, with separate archiving programs the
 benefit of transparent decompression at run time is lost.

 For maximum compression of Windows and DOS extended programs, the individual
 segments of a program file should be kept as large as possible, and the
 PACKCODE and PACKDATA options enabled if they are not already set. See the
 online help for details of these commands. The individual segment sizes can
 be examined in the .MAP file produced at link time by the MAP link script
 command.

 Compression of VB DOS programs using CHAIN is not currently supported
 because the runtime library attempts to read data from CHAINed files.