w8sdz@WSMR-SIMTEL20.ARMY.MIL (Keith Petersen) (02/23/90)
[File: UUD19.DOC]
UUD19.DOC
by David Kirschbaum <kirsch@@ARSOCOMVAX.SOCOM.MIL>
UUD uudecodes uuencoded files to original binary form. It is
compatible with the Unix (and other) uuencode/uudecode utilities.
Usage:
UUD<RETURN>
Displays usage message, prompts for input file name.
UUD [d:][\path\]filename.uue
Produces a uudecoded file, with the filename taken from
within the uuencoded file (which might include a path).
Notes:
WARNING: UUD does NOT check for existing files, and will gleefully
write over them! Check first!
UUD will accept an input path\filename up to 80 chars long, and will
prompt if none is specified.
A uudecoded filename is taken from the uuencoded source file and is
written to the current directory (or to the path included in the file
header).
Input files may be any length.
Uuencoded file headers (mailing headers, etc.) need not be removed.
However, any spurious lines between the "begin" and "end" lines MUST
be removed.
Anything beyond the "end" line is ignored. If no "end" is found, the
output file is saved, but an error message is displayed.
Certain uuencoders append a "checksum" character to the end of each
uuencoded line. UUD ignores these.
Uuencoded files generated or moved through a Unix system may have LF
(ASCII 10) line endings instead of the DOS-convention CR/LF (ASCII
13/10) endings. UUD will handle those LF ends of line as well. You
MAY get a "end not found" message, but the uudecoded file will be
intact.
Certain systems and mailers will strip off trailing spaces on lines.
UUD attempts to replace them.