Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!um-math!hyc
From: hyc@math.lsa.umich.edu (Howard Chu)
Newsgroups: comp.sys.atari.st
Subject: UUencode (was Re: FTP)
Keywords: uudecode vs.uue
Message-ID: <581@stag.math.lsa.umich.edu>
Date: 27 Feb 89 00:41:27 GMT
References: <969@blake.acs.washington.edu>
Sender: usenet@math.lsa.umich.edu
Reply-To: hyc@math.lsa.umich.edu (Howard Chu)
Distribution: usa
Organization: University of Michigan Math Dept., Ann Arbor
Lines: 28
UUCP-Path: {mailrus,umix}!um-math!hyc

Standard Unix uuencode/uudecode does not know anything about the
include directives. That's part of your problem. If you concatenate
the multi-part encodings by hand and still get errors, one can only
presume you did something wrong - put them in the wrong order, left
in a line you should have deleted, or deleted a line you should have
left intact. A multi-part encoded file begins at the
	begin blahhh
and ends at the
	include blah2

You should delete all the "include" lines when concatenating by hand,
as well as all but the first "begin" line. Usually every encoded line
begins with 'M' - when you finish, there should be one "begin," one
"end," and a lot of lines starting with 'M', but nothing else. (There
may be a line beginning with a space, immediately preceding the end
line. This is generated by a [harmless] off-by-one error in the test
conditions of standard uuencode. Since it only results in 3 extra bytes,
I guess no one has ever bothered to fix it.)

The easier thing to do is to grab the sources for the ST uuencode/uudecode
programs and install the programs on your Unix machine. They run fine,
and then you never have to worry about those includes ever again.
--
  /
 /_ , ,_.                      Howard Chu
/ /(_/(__                University of Michigan
    /           Computing Center          College of LS&A
   '              Unix Project          Information Systems