More Diagnostics and Bugs

the zipfile format was detected. Pro‐ cessing may have completed successfully anyway; some bro‐ ken zipfiles created by other archivers have simple work‐ arounds. 4 zip was unable to allocate memory for one or more buffers during program initialization. 5 a severe error in the zipfile format was detected. Pro‐ cessing probably failed immediately. 6 entry too large to be processed (such as input files larger than 2 GB when not using Zip64 or trying to read an existing archive that is too large) or entry too large to be split with zipsplit 7 invalid comment format 8 zip ‐T failed or out of memory 9 the user aborted zip prematurely with control‐C (or simi‐ lar) 10 zip encountered an error while using a temp file 11 read or seek error 12 zip has nothing to do 13 missing or empty zip file 14 error writing to a file 15 zip was unable to create a file to write to 16 bad command line parameters 18 zip could not open a specified file to read 19 zip was compiled with options not supported on this system VMS interprets standard Unix (or PC) return values as other, scarier‐ looking things, so zip instead maps them into VMS‐style status codes. In general, zip sets VMS Facility = 1955 (0x07A3), Code = 2* Unix_sta‐ tus, and an appropriate Severity (as specified in ziperr.h). More de‐ tails are included in the VMS‐specific documentation. See [.vms]NOTES.TXT and [.vms]vms_msg_gen.c. BUGS zip 3.0 is not compatible with PKUNZIP 1.10. Use zip 1.1 to produce zip files which can be extracted by PKUNZIP 1.10. zip files produced by zip 3.0 must not be updated by zip 1.1 or PKZIP 1.10, if they contain encrypted members or if they have been produced in a pipe or on a non‐seekable device. The old versions of zip or PKZIP would create an archive with an incorrect format. The old versions can list the contents of the zip file but cannot extract it anyway (because of the new compression algorithm). If you do not use encryption and use regular disk files, you do not have to care about this problem. Under VMS, not all of the odd file formats are treated properly. Only stream‐LF format zip files are expected to work with zip. Others can be converted using Rahul Dhesi’s BILF program. This version of zip handles some of the conversion internally. When using Kermit to transfer zip files from VMS to MSDOS, type "set file type block" on VMS. When trans‐ ferring from MSDOS to VMS, type "set file type fixed" on VMS. In both cases, type "set file type binary" on MSDOS. Under some older VMS versions, zip may hang for file specifications that use DECnet syntax foo::*.*. On OS/2, zip cannot match some names, such as those including an excla‐ mation mark or a hash sign. This is a bug in OS/2

This section details additional diagnostic exit codes from zip, covering issues like temporary file errors, read/seek errors, missing zip files, and write errors. It explains how zip maps Unix return values to VMS-style status codes on VMS systems. It also lists known bugs in zip 3.0, including incompatibility with PKUNZIP 1.10 when updating zip files with encryption or created via pipes. Specific issues on VMS regarding file formats and DECnet syntax are also highlighted, along with OS/2's inability to match certain filenames.