Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!uunet!mcsun!unido!laura!tommy!klute
From: klute@tommy.informatik.uni-dortmund.de (Rainer Klute)
Newsgroups: comp.sys.atari.st
Subject: Re: uudecoding multi-part files?
Message-ID: <3225@laura.UUCP>
Date: 2 May 91 09:42:20 GMT
Article-I.D.: laura.3225
References: <56360001@hpcvia.CV.HP.COM> <91120.232749REEVES@SLACVM.SLAC.STANFORD.EDU>
Sender: news@laura.UUCP
Organization: University of Dortmund, Germany
Lines: 30

In article <91120.232749REEVES@SLACVM.SLAC.STANFORD.EDU>,
REEVES@SLACVM.SLAC.STANFORD.EDU (Terry Reeves) writes:
|> In article <56360001@hpcvia.CV.HP.COM>, alten@hpcvia.CV.HP.COM
|> (John_Altendorf)
|> says:
|> >
|> >Can anyone please explain the requirements for file names in order to
|> >uudecode a multi-part file?  I seem to recall something like the file
|> >names must be sequentially named file.uaa, file.uab file.uac etc. 
|> Also
|> >it seemed that the ----end---- line of the file had to have some
|> notation
|> >in it.  Please clarify my misunderstandings.
|> 
|> The files do not need to sequentially named, at least not with the DUMAS
|> UUX
|> utilities that I use. If you look at the files, there is a line at the
|> bottom
|> pointing to the next file. However, the sequential naming is still
|> useful. You
|> won't be as easily confused as to what the file is.

With Dumas uud you do not even need any file naming at all. It is
sufficient to concatenate the files and pipe the result through uud.

-- 
  Dipl.-Inform. Rainer Klute      klute@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB             klute@unido.uucp, klute@unido.bitnet
  Postfach 500500         |)|/    Tel.: +49 231 755-4663
D-4600 Dortmund 50        |\|\    Fax : +49 231 755-2386