Per.Letni@f15.n231.z2.fidonet.org (Per Letni) (03/16/91)
* Original: AREA.... PASCAL * Original: FROM.... Per Letni * Original: TO...... All * Forwarded by...... Maximus-CBCS v1.02 at 2:231/15.0 This program is designed to work only with version 0.91 of LZEXE, a uti that can compress EXE files substantially while leaving them executable compressions LZEXE achieves are usually in the range of 30 to 40 percen although they are often higher than that. Programs compressed with LZE decompress themselves when they are run. The decompression time is neg LZEXE was written by Fabrice Bellard, of Grabels, France and is still u development. It is a free program, but Mr. Bellard retains the copyrig memory size for compressed files. The compressed files now take about amount of memory to load as they did before compression. For this reas previous shell program LZEFIX, which ran Microsoft's EXEMOD header util to reduce the excessive load sizes created by version 0.90, should not with version 0.91. It isn't needed. In fact it could cause problems (including having to reboot your system) if you try to use it with this version of LZEXE. Accordingly, LZESHELL makes no adjustment to the hea user input, depending on what it finds out about the file you have aske to compress. LZESHELL translates the prompts into English (the transla of course, and a new program he has written called UPACKEXE v1.00. UPA unpacks EXE files that have been compressed with Microsoft's EXEPACK ut Unpacking such files allows LZEXE to do an even better compression job. does, it tells you so and asks whether it should continue the compressi quit so you can run UPACKEXE first. In that situation, you would norma up running two programs manually. When you use LZESHELL, however, you don't have to quit if you want to use UPACKEXE. LZESHELL translates th prompt into English, and if your response is that you want to unpack th before compressing it, it immediately runs UPACKEXE. Then it runs LZEX to complete the compression. In other words, you don't go back to DOS both programs have been run. The effect is to make these two fine util to *.OLD. This can create a problem when you run UPACKEXE then run LZE The *.OLD backup file saved by UPACKEXE will be replaced by the *.OLD f saved by LZEXE -- you end up losing the EXEPACKed *.OLD file. LZESHELL eliminates this problem by immediately renaming the *.OLD file produced UPACKEXE to *.OPK. This leaves you with two backup files -- one for th original EXEPACKed file (*.OPK) and one for the unpacked file (*.OLD). third file will be your compressed EXE file. If the compressed file wo you can remove both backup files from your disk. Otherwise, you can er the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl the compressed EXE file and rename one of the backups to *.EXE (probabl EXEPACKed one, *.OPK, since it's the original and it's smaller). LZESHELL also generates English prompts for another situation that LZ v.0.91 detects, namely the use of overlays by the EXE file. Here you a v.0.91 detects, namely the use of overlays by the EXE file. Here you a v.0.91 detects, namely the use of overlays by the EXE file. Here you a v.0.91 detects, namely the use of overlays by the EXE file. Here you a v.0.91 detects, namely the use of overlays by the EXE file. Here you a v.0.91 detects, namely the use of overlays by the EXE file. Here you a given the choice of aborting the compression or continuing it (taking t chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects chance that the compressed file won't work). UPACKEXE v1.00 detects "internal" overlays (I'm not sure what those are), but in that situatio "internal" overlays (I'm not sure what those are), but in that situatio "internal" overlays (I'm not sure what those are), but in that situatio "internal" overlays (I'm not sure what those are), but in that situatio "internal" overlays (I'm not sure what those are), but in that situatio "internal" overlays (I'm not sure what those are), but in that situatio "internal" overlays (I'm not sure what those are), but in that situatio -- uucp: uunet!m2xenix!puddle!2!231!15!Per.Letni Internet: Per.Letni@f15.n231.z2.fidonet.org