home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!uwm.edu!spool.mu.edu!umn.edu!msus1.msus.edu!eeyore.stcloud.msus.edu!skriefal
- Newsgroups: comp.compression
- Subject: Re: Another PKZIP 2.04C bug...
- Message-ID: <1993Jan10.233813.2041@msus1.msus.edu>
- From: skriefal@eeyore.stcloud.msus.edu (Scott Kriefall)
- Date: 10 Jan 93 23:38:13 -0600
- References: <16B5212D7A.NETOPRWA@ncsuvm.cc.ncsu.edu> <rdippold.726727344@cancun>
- Organization: St. Cloud State Univ., MN
- Nntp-Posting-Host: eeyore.stcloud.msus.edu
- Lines: 16
-
- > Were you running it from a batch file or other program (sounds like
- > it...)? This is something we've noted: random CRC errors and "Enter
- > Disk #x of archive" messages. If you then try to unzip the same file
- > right from the command line, it works. This might help you track it.
-
- I had the same type of error ("Enter Disk 3 of archive") earlier
- today while trying to unzip an archive created with PKZip 1.1.
- Unforunately, I didn't keep the .zip I was trying to dearchive, so I
- am unable to check it. This was from the *command line* - PKUNZIP
- was not being called from a batch file or or any other program.
-
- I'm _very_ seriously considering going back to PKZip 1.1 and PKUnzip
- 1.93a - at least until these bugs are fixed.
-
- skriefal@eeyore.stcloud.msus.edu
-
-