home *** CD-ROM | disk | FTP | other *** search
- This is the README file for the 2 August 1994 public release of the
- Info-ZIP group's portable UnZip zipfile-extraction program (and related
- utilities).
-
- unzip511.zip portable UnZip, version 5.11, source code distribution
- unzip511.tar.Z same as above, but compress'd tar format
-
- __________________________________________________________________________
-
- BEFORE YOU ASK: UnZip, its companion utility Zip, and related utilities
- and support files can be found in many places; read the file "Where" for
- further details. To contact the authors with suggestions, bug reports,
- or fixes, continue reading this file (README) and, if this is part of a
- source distribution, the file "ZipPorts". Also in source distributions:
- read "BUGS" for a list of known bugs, non-bugs and possible future bugs,
- and see "Contents" for a commented listing of all the distributed files.
-
- ALSO NOTE: Info-ZIP's mailing addresses CHANGED between UnZip 5.0p1 and
- 5.1 releases (and since Zip 2.0.1)! The old BITNET address doesn't even
- exist anymore. See below.
- __________________________________________________________________________
-
-
- GENERAL INFO
- ------------
- UnZip is an extraction utility for archives compressed in .zip format (also
- called "zipfiles"). Although highly compatible with PKWARE's PKZIP and
- PKUNZIP utilities for MS-DOS (in addition to Info-ZIP's own Zip program),
- our primary objectives have been portability and non-MSDOS functionality.
-
- This version of UnZip has been ported to a wide array of hardware--from
- micros to supercomputers--and operating systems: Unix (many flavors),
- VMS, OS/2, MSDOS (+ Windows), NT, TOPS-20 (partly), AmigaDOS, Atari TOS,
- Macintosh and Human68k. UnZip features not found in PKUNZIP include source
- code; default extraction of directory trees (with a switch to defeat this,
- rather than the reverse); VMS, Macintosh and OS/2 extended file attributes;
- and, of course, the ability to run under most of your favorite operating
- systems. Plus, it's free. :-)
-
- For source distributions, see the main Contents file for a list of what's
- included, and read INSTALL for instructions on compiling (including OS-
- specific comments). The individual operating systems' Contents files (for
- example, vms/Contents) may list important compilation info in addition to
- explaining what files are what, so be sure to read them. Some of the ports
- have their own, special README files, so be sure to look for those, too.
-
- See unzip.1 or unzip.doc for usage (or the corresponding UnZipSFX, ZipInfo
- and fUnZip docs). For VMS, unzip_def.rnh or unzip_cli.help may be compiled
- into unzip.hlp and installed as a normal VMS help entry; see vms/descrip.mms.
-
-
- CHANGES AND NEW FEATURES
- ------------------------
- The biggest new feature in the 5.11 release is the addition of UnZipSFX,
- an executable stub which may be prepended to any new-style zipfile to
- create a self-extracting archive. This has been tested under Unix, VMS,
- MS-DOS, OS/2, etc., and it works pretty well, although the size of the
- compiled stub may be rather large on some OSes (e.g., a few hundred kilo-
- bytes on Crays :-) ), and the resulting archives are NOT portable *across*
- different operating systems. We mainly wanted this for our own use in
- distributing UnZip...
-
- Also new/changed in 5.11: rewrote unshrink() completely from scratch,
- allowing for a "clean," unencumbered version on 32-bit and better systems
- (see COPYING for details); moved virtually all strings to far memory in
- MS-DOS, once again allowing use of the small memory model (at least for
- Microsoft compilers); added numerous customization options (see INSTALL
- for details) and extended the -v option to print a diagnostic screen of
- local customizations if no zipfile name is given (i.e., "unzip -v"); added
- a -C option for case-insensitive filename matching (oft asked-for on MS-DOS
- and OS/2, especially in the BBS and offline-mail-reader communities); added
- more "intelligence" for dealing with bad zipfiles (and, in some cases, con-
- catenated multi-part archives--doesn't always work, but better than before);
- changed the former -U behavior to be the default, with a new -L option to
- provide what was the default behavior (auto-convert filenames from uppercase
- OSes to lowercase); added a new ZipInfo -T option to print times in a deci-
- mal format (yymmdd.hhmmss) suitable for piping into sort(1); and improved/
- expanded the documentation a great deal (particularly man pages/*.doc files
- and INSTALL file). We even managed some extra performance tuning (albeit
- rather minor).
-
- Since 5.1 was never posted to comp.sources.misc, here's a quick summary of
- the features which were new in version 5.1: wildcard zipfiles; ability to
- extract to a directory other than the current one; auto-conversion of text
- files; disabling of ANSI sequences in comments and filenames (to protect
- against "ANSI bombs"); incorporation of ZipInfo into UnZip; full Amiga,
- Atari, Mac, NT and Human68K support (and partial TOPS-20 support); and per-
- formance tweaks resulting in 35-70% faster extraction, depending on the
- compression method.
-
-
- DISTRIBUTION
- ------------
- If you have a question regarding redistribution of Info-ZIP software,
- either as-is, as packaging for a commercial product, or as an integral
- part of a commercial product, read the Frequently Asked Questions (FAQ)
- section of the included COPYING file.
-
- Insofar as C compilers are rare on some platforms and the authors only
- have direct access to Unix, VMS, OS/2, MS-DOS, Mac, Amiga and Atari
- systems, others may wish to provide ready-to-run executables for new
- systems. In general there is no problem with this; we require only that
- such distributions include this README file, the Where file, the COPYING
- file (contains copyright/redistribution information), and the appropriate
- documentation files (unzip.doc and/or unzip.1 for UnZip, etc.). If the
- local system provides a way to make self-extracting archives in which both
- the executables and text files may be stored together, that is best (in
- particular, use UnZipSFX if at all possible, even if it's a few kilobytes
- bigger than the alternatives); otherwise we suggest a bare UnZip executable
- and a separate zipfile containing the remaining text and binary files. If
- another archiving method is in common use on the target system (for example,
- Zoo or LHa), that may also be used.
-
-
- BUGS AND NEW PORTS: CONTACTING INFO-ZIP
- ----------------------------------------
- All bug reports and patches (context diffs only, please!) should go to
- zip-bugs@wkuvx1.wku.edu, which is the e-mail address for the Info-ZIP
- authors. "Dumb questions" which aren't adequately answered in the docu-
- mentation should also be directed here rather than to a global forum such
- as Usenet. (Kindly make certain that your questions *isn't* answered by
- the documentation, however--a great deal of effort has gone into making
- it clear and complete.) Suggestions for new features can be sent to
- info-zip@wkuvx1.wku.edu, a mailing list for the Info-ZIP beta testers,
- for discussion (the authors hang out here as well, of course), although
- we don't promise to act on all suggestions. If it is something which is
- manifestly useful, sending the required patches to zip-bugs directly (as
- per the instructions in the ZipPorts file) is likely to produce a quicker
- response than asking us to do it--the authors are always somewhat short
- on time. (Please do NOT send patches or encoded zipfiles to the info-zip
- address.)
-
- If you are considering a port, not only should you read the ZipPorts file,
- but also please check in with zip-bugs BEFORE getting started, since the
- code is constantly being updated behind the scenes. For example, an Acorn/
- Archimedes port is already almost complete, as is an OS/2 dynamic link lib-
- rary (DLL) version; VMOS, VM/CMS, Netware, QDOS and NT DLL ports are claimed
- to be under construction, although we have yet to see any up-to-date patches.
- We will arrange to send you the latest sources. The alternative is the pos-
- sibility that your hard work will be tucked away in a sub-archive and mostly
- ignored, or completely ignored if someone else has already done the port
- (and you'd be surprised how often this has happened). IBM mainframe ports
- (VM/CMS and/or MVS) would be particularly welcome. (It can't be *that* hard,
- folks...the VMS filesystem is similar in many ways.)
-
-
- BETA TESTING: JOINING INFO-ZIP
- -------------------------------
- If you'd like to keep up to date with our UnZip (and companion Zip utility)
- development, join the ranks of beta testers, add your own thoughts and con-
- tributions, etc., send a two-line mail message containing the commands HELP
- and LIST (on separate lines in the body of the message, not on the subject
- line) to mxserver@wkuvx1.wku.edu. You'll receive two messages listing the
- various Info-ZIP mailing-list formats which are available (and also various
- unrelated lists) and instructions on how to subscribe to one or more of them
- (courtesy of Hunter Goatley). As of mid-1994, subscribing to the announce-
- ments list requires a command of the form
-
- SUBSCRIBE Info-ZIP-announce "Joe Isuzu"
-
- The discussion list is called either Info-ZIP or Info-ZIP-digest, depending
- on one's preference for delivery.
-
-
- -- Greg Roelofs (Cave Newt), UnZip maintainer/container/explainer and
- developer guy, with inspiration from David Kirschbaum
-