Bogus bugs (not our fault!):---------------------------By far THE BIGGEST source of bug reports to Info-ZIP/zip-bugs is theincorrect transfer of zipfiles (or of the UnZip executable itself).ALWAYS TRANSFER IN BINARY MODE! This includes ftp transfers and *both*ends of a Kermit connection ("set file type binary"). If your copyisn't exactly the same size as the original, you made a mistake.Another common source of errors such as "compression method 8 not sup-ported" is the existence of an old version of UnZip somewhere in yourpath. Make sure you're using the version you think you're using; givethe full path explicitly if necessary. Executing "unzip" without anyoptions will print a help screen, at the top of which is the UnZipversion number and release date; and executing "unzip -v" without anyzipfile or other options will give information about what compiler wasused, the target operating system, any special UnZip options, and thedate of compilation--only for version 5.11 and later, though! (Also,under Unix C shell and some Bourne shells, "which unzip" will printthe path of the unzip you're actually using. Under OS/2 and MS-DOS,whch21gr.zip [on Simtel mirror sites] will do the same thing; in addi-tion, "which -a unzip" will show *all* copies of "unzip" in your path.)Bugs (real and/or imagined):---------------------------- [OS/2 DLL] when trying to use the REXX function UzUnZipToStem to extract afile with `&' in its name, the DLL crashes (but UzUnZipToVar still works)[Daniel H, 961215]- UnZip has problems with archives bigger than 2GB; it may print "note: didn'tfind end-of-central-dir signature at end of central dir" (harmless) ormay not be able to seek to member files [James Lemley 970107, Iris Spaniol970206, ...]- fix overwrite behavior: hidden/system problems?; etc.- 32-bit DOS UnZip still unable to set volume labels?- 32-bit DOS UnZip under OS/2 doesn't extract all wildcard zipfiles?[DOS box: unzip386 (ver 5.12) x:\32bit\unix\emx09a\*.zip, Hobbes 3/95]- 32-bit DOS UnZip under OS/2 doesn't set timestamp when overwriting fileson HPFS partition? (go32 and pmode/w both; emx/rsx OK) [Eberhard Mattes950726]- USE_FWRITE still causes occasional CRC errors when extracting on Pyramid?[Kevin Fritz 931102]- still NT/W95 bug with "unzip -v d:*.zip" not matching properly? [Steve S940527]980427: bug no longer exists, Opendir() must have been corrected by someone- when ^Z received in no-echo mode, echo is not restored (works OK ifresume, however)- signal() handler disabled after first use with one of BSD/SysV?- MKS Korn shell: unzip assumes the MKS-style command-line environmentoptions are relevant to it, but this is not the case if unzip was calledby another program (e.g., from a .BAT file). A fix for this exists forBorland compilers but not for MSC, Watcom, djgpp, etc.- OS/2: for paths with one long component, the .LONGNAME EA may be saved forall components (waste of disk space): how to check??- VMS: for extracting to other directories, only the VMS-style "-d [.foo]"format is accepted; "-d foo" should also be allowed. Long filenames arenot automatically truncated to 39.39.- Novell Netware: Netware drives may clear the archive bit on extractedfiles under OS/2 and/or MS-DOS. UnZip always *tries* to set the archivebit, however. [pynq@uchicago, 940527]- DEC Ultrix: on long zipfiles, unzip will sometimes fail (bad CRC, not alwaysreproducible); this is apparently due either to a hardware bug (cache mem)or OS bug (page faults?) [Igor, Jean-loup, bottom of BUGS.long]- funzip/more/decryption/no-echo bug: race condition(?) causes terminal tobe "reset" to no-echo state- Macintosh (100200), Atari (020000) external file attributes not interpretedcorrectly (both unzip and zipinfo)- pkbug error: zipfile with incorrect csize and/or ucsize--check for end ofcompressed (csize) data in uncompression routines:unreduce.c: while (((outpos + outcnt) < ucsize) && (!zipeof)) {[James Birdsall, Mark, bottom of BUGS.long]- OS/2: directory EAs not restored if directory exists [Kai Uwe, KG27515@uark](subsequent note: no way to determine which EAs are newer ==> cannotrestore without user input)(update: as of UnZip 5.30, option -o forces restoring of directory EAs)- MS-DOS: Borland executables don't allow other than 80-column, 25/43/50-linescreen modes (Borland bug) [Michael Stillwell]