From MACRIDES@SCI.WFEB.EDU Mon Jan 25 19:23:15 1993
Received: from PO1.indiana.edu by sunflower.bio.indiana.edu
	(4.1/9.7jsm) id AA02671; Mon, 25 Jan 93 19:23:14 EST
Received: from sci.wfeb.edu by PO1.Indiana.EDU; id AA27938
	(5.65c+jsm/2.5.1jsm); Mon, 25 Jan 1993 19:24:55 -0500
Received: from SCI.WFEB.EDU by SCI.WFEB.EDU (PMDF #2704 ) id
 <01GTY1VRB9SG000FGO@SCI.WFEB.EDU>; Mon, 25 Jan 1993 19:18:19 EST
Date: 25 Jan 1993 19:18:19 -0500 (EST)
From: Foteos Macrides <MACRIDES@SCI.WFEB.EDU>
Subject: vms_fileutils.uue in /incoming
To: gilbertd@indiana.edu
Message-Id: <01GTY1VRB9SI000FGO@SCI.WFEB.EDU>
X-Vms-To: IN%"gilbertd@indiana.edu"
X-Vms-Cc: MACRIDES
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Status: R

Don,
	I put  vms_fileutils.uue  in your incoming directory, with executables
and HELP library modules for the latest (as of 24-Jan-1993) versions of MFTU,
UNZIP, ZIP, TAR, LZDCMP and LZCOMP for VMS systems.  The  vms_fileutils.uue
header describes where to get the sources via email or ftp, and how to break
out and install its files.

	They should replace old versions of the following in your util/vms
directory:

     lzcomp.exe,
     lzdcmp.exe,
     everything in util/vms/tar/, and
     everything in util/vms/zip/        (should save you some disk space 8-).

It might be helpful if you also put a pointer to vms_fileutils.uue in
molbio/vms.  Also, be sure gopher is set up to see it as Type=0 (*not*
Type=6), so it can be seen via the VMS gopher client.

     Note that the uuencoded ZIP archive was made with the current version of
ZIP, which preserves VMS file structures, and can't be broken out on Unix
boxes (cuz they can't read the RMS file attribute block).  If you want
anything that's in the archive out individually, let me know and I'll put
it/them in incoming.  A "temporary" ZIP, that is not in the proper format, but
will work on VMS systems, is created on uudecoding and can be used to break
out the ZIP archive, which will generate another ZIP.EXE that *will* be in the
optimum format.

	The recent port of the Unix gopher client to VMS works great, so I
suspect your server/archive will be getting a lot more action via gopher from
VMSers.  The above may seem complicated, but it *is* the most efficient way to
ensure that the files will have the right formats when fetched via the VMS
gopher client (and if the file utilities are right, everything that's fetched
and broken out with them will be too).

				Fote

=========================================================================
 Foteos Macrides           Worcester Foundation for Experimental Biology
 MACRIDES@SCI.WFEB.EDU     222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================