home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!darwin.sura.net!zaphod.mps.ohio-state.edu!uwm.edu!csd4.csd.uwm.edu!renegade
- From: renegade@csd4.csd.uwm.edu (Jun Hamaoka)
- Newsgroups: comp.compression
- Subject: Re: bug in PKLite 1.15??
- Date: 11 Nov 1992 21:29:18 GMT
- Organization: Computing Services Division, University of Wisconsin - Milwaukee
- Lines: 19
- Message-ID: <1drtveINNo0k@uwm.edu>
- References: <92315.194932GILLA@QUCDN.QueensU.CA> <1992Nov11.053329.21043@uwasa.fi>
- NNTP-Posting-Host: 129.89.7.4
-
- In article <1992Nov11.053329.21043@uwasa.fi> ts@uwasa.fi (Timo Salmi) writes:
- >In article <92315.194932GILLA@QUCDN.QueensU.CA> "Arnold G. Gill" <GILLA@QUCDN.QueensU.CA> writes:
- >> I just picked up version 1.15 of PKLite and converted all of my
- >>compressed .COM files to the newer version. (Don't ask why, it's just a
- >>thing that I do.) Anyway, it seems that none of the programs out there
- >>that check for executable compressions are able to detect version 1.15 of
- >>PKLite of .COM files, including the CHK4LITE that PKWare includes in the
- >>PKLite distribution!
- >
-
- This is a bug that is known to PKWARE. Apparently there was a last minute
- change that shifted the appearance of the PKLITE "header" by a few bytes,
- causing CHK4LITE to be unable to recognize it properly.
-
- Note that the PKLITE program itself WILL recognize it properly, it is only
- the CHK4LITE program that is affected. So this is not exactly a fatal
- flaw.
-
-
-