Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!gsbsun!valley
From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: PKLITE, what's the catch???
Message-ID: <1991Jun29.150110.19766@midway.uchicago.edu>
Date: 29 Jun 91 15:01:10 GMT
References: <1991Jun26.012138.13729@mlb.semi.harris.com> <11230005@hplsla.HP.COM> <1991Jun29.052850.2121@netcom.COM>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 24

mrs@netcom.COM (Morgan Schweers) writes about EXE compressors:

>    (As a side note:  AXE was the first, originally by SEA.  It didn't
>fly very well, and it's compression was abysmal.  It was also commercial
>(as befits SEA, of course.)  LZEXE came next, and was written by
>Fabrice Bellard of France.  It's not updated much anymore but it is
>the freest of all the packages.  PKLite is a good compressor, but
>really wins in the area of being able to decompress exactly the file
>you compressed.  It also wins because it's able to handle internal
>overlays better.  It, however, costs.  I haven't used DIET, or any of
>the others mentioned by frisk.)

Most of the responses I have gotten to my query about this (which is better???)
have said PKLITE and said so because of the ability to restore the original.
To me, that doesn't sound like much of a selling point; you should
maintain originals of any program you compress anyway, just as you
should maintain sources of any program you compile.
This leads me to ask, however, ...

Question: If not to the original, what does LZEXE recontruct to?
Something functionally similar or what?
--

	(Another fine mess brought to you by valley@gsbsun.uchicago.edu)