LZEXE  Crack (Updated 2022)
- Random access to the data
- Progressive compression: decompressing a portion of the data as soon as all the necessary data has been loaded from the previous portion.
- Small size in memory: the decompression part of the engine should be in charge of decompressing the entire file.
The internal data format is very simple and uses no hash table.
- The output format is based on the LZSS algorithm.
The old LZEXE Serial Key version was written in assembly, the new version written in C/Assembler.
It's the only program released under the GPL v2 in the world that has to reach the 16.816 GB limit of MSDOS disks.
Features:
- Free (I mean "free" as in Free Software, ie without any cost): this version is free (and the new version will be too).
- Full compliance with the GPL v2: You are free to share the LZEXE decompression part.
- Perfect compatibility with the former LZEXE version: no code was modified in LZEXE except the decompression engine which is completly rewritten.
- Compression ratio quite smaller than other known applications: 31,33% compared to the best known application 36% (compressed size / original size) with absolutely the same decompression engine.
- Compression time constant (time to compress a GB of data):
NEW VERSION: 20 seconds (Pentium 80 processor)
OLD VERSION: 2,3 minutes (ZX80 processor)
- Compression speed is compatible with the disassembly speed of LZSS (compared to the disassembly speed of the ZX80 processor, here are the decompression times of LZEXE and the decompression time of LZSS)
- Compression speed is compatible with the execution speed of the MZ80 processor (compared to the execution speed of the MZ80 processor, here are the decompression times of LZEXE and the decompression time of MZEXE)
- No memory limit : the memory limit is around 15MB for compact disks
- No configuration files : the user must configure the compression/decompression engines with nothing but some flags.
- No need to define the original file size (the application will determine automatically the right compression ration based on the size of the uncompressed file)
- No need to define the destination file size.
- Working on every 16 bits disk (I
LZEXE  (LifeTime) Activation Code
In decompressing LZEXE Serial Key application, the data which is inside the.EXE file are "moved" during the decoding process. In fact, the way is done consist of different steps. Each of these steps is controlled by different "bits" of the data. The order of operation is as following:
1. The loader puts his machine code inside the.EXE file. It is first one, the most executable part of the.EXE file. It makes sense to put it first because the loader could not be compressed because he already has a compressed code. This code is uncompressed before putting it inside the.EXE file.
2. The loader also puts the machine code of the LZEXE compression engine inside the.EXE file. This is the step which allows the decompression of the executable. It consist to put the compression engine data before the uncompressed machine code to simplify its decoding. This is not mandatory but I think that it is very appropriate.
3. When the compressed machine code is put in the.EXE file, the decompressor will be able to decompress the code as an UNICODE string for example. At the same time, the decompression engine load the machine code of the compression engine from the.EXE file and decompress it and replace the machine code of the compression engine.
This is in fact the last step of the decompression because the loader "catched" the data from the decompression engine and put them on the stack. The loader will execute them when the.EXE file is opened. As LZEXE applications are compressed for secure, it is mandatory that the stack is not initialized by the loader (LASM assembly language). It is quite easy to achieve using a "NOP" instruction of size one or two bytes.
4. When the.EXE file is opened, the loader also put several data in the stack: the version of the executable file. This is int32 (4 bytes) which allow the check if a different version is already present and enable me to allow the installer to use older version of the executable. But this is not mandatory and other possibilities will be considered too.
5. Then, it is required to set some flags in the registers for being compatible with the Microsoft "internal" APIs: eax, ecx, edx and esp, depending on what kind of executable file was opened (EXE, DR or COM).
6. In the end, the
b7e8fdf5c8

Items