home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.compression
- Path: sparky!uunet!world!robjung
- From: robjung@world.std.com (Robert K Jung)
- Subject: Re: More severe bugs in PKZIP 2.04c.
- Message-ID: <C0JG3H.M2o@world.std.com>
- Organization: The World Public Access UNIX, Brookline, MA
- References: <3561@accucx.cc.ruu.nl> <C0JEvz.KM6@world.std.com>
- Date: Fri, 8 Jan 1993 13:57:17 GMT
- Lines: 24
-
- robjung@world.std.com (Robert K Jung) writes:
-
- >Using -3 -) on a vanilla DOS 5.0 (no config.sys, no autoexec.bat) on
- >a 486DX machine, I used PKZIP 2.04c to backup several Wing Commander
- >EXE files to diskettes. (PKZIP -& -3 -) b:test *.EXE). On compressing
- >the last file onto the first diskette, PKZIP displayed "done" indicating
- >that it had finished the compression phase and then prompted for
- >the insertion of a new diskette. Then PKZIP wrote about 60K of data on
- >that diskette.
-
- >I immediately typed "PKUNZIP b:test". PKUNZIP extracted all BUT the last
- >file reporting a file CRC error with a "file has bad table" error message.
-
- Apparently, a user reported a similar error to the PKWARE CompuServe forum.
- They were backing up a 1.7 MB ZIP file (zipped with 1.1) and got the
- "file has bad table" error. So I tried the same thing, creating a ZIP file
- slightly larger than one diskette. PKZIP 2.04 compressed it saving 1 percent
- onto two diskettes. This backup set produced the same "bad table" error
- message.
-
- *** PROCEED WITH CAUTION backing up ZIP files ***
-
- Regards,
- Robert K Jung
-