ggranger@nro.cs.athabascau.ca (Greg Granger) (04/30/91)
alten@hpcvia.CV.HP.COM (John_Altendorf) writes: > 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. > > > John Altendorf alten@hpcvia.cv.hp.com > Hewlett-Packard > Corvallis, Oregon I believe to uudecode one file into multi-parts, you have to use the -x (where x is the no. of lines that you want in the uue file). To UUE, say for instance, a 100K file called DUMMY.LZH, on the command line, type: -700 DUMMY.LZH. This will create a series of uuencoded files that are 700 lines long (except for the last file, which will be the remainder, but not necessarily 700 lines long). Greg Granger | INet: ersys!ggranger@nro.cs.athabascau.ca | | Fnet: Greg Granger (Node 532) Dark Knight (Node 595)| | Post: 5906-188 Street Edmonton, AB Canada T6M-2A9 | | Tele: +1 403 481-0803 OR +1 403 481-5110 | Greg Granger ersys!ggranger@nro.cs.athabascau.ca Edmonton Remote Systems: Serving Northern Alberta since 1982
alten@hpcvia.CV.HP.COM (John_Altendorf) (05/01/91)
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. John Altendorf alten@hpcvia.cv.hp.com Hewlett-Packard Corvallis, Oregon
REEVES@SLACVM.SLAC.STANFORD.EDU (Terry Reeves) (05/01/91)
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. Terry Disclaimer: The above opinions are my own, and are not related to the policies of SLAC, Stanford University, the DOE, or the U.S. government.
steve@thelake.mn.org (Steve Yelvington) (05/02/91)
[In article <91120.232749REEVES@SLACVM.SLAC.STANFORD.EDU>,
REEVES@SLACVM.SLAC.STANFORD.EDU (Terry Reeves) writes ... ]
> 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.
Is anybody interested in a GEM-based uuencoder/uudecoder? I just stitched
one together. It's not quite ready for release, but if there's interest
I'll post it (with sources, of course) when it's finished.
----
Steve Yelvington, Marine on St. Croix, Minnesota, USA / steve@thelake.mn.orgklute@tommy.informatik.uni-dortmund.de (Rainer Klute) (05/02/91)
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
alten@hpcvia.CV.HP.COM (John_Altendorf) (05/03/91)
/ hpcvia:comp.sys.atari.st / ggranger@ersys.CV.HP.COM / 8:17 am Apr 30, 1991 / alten@hpcvia.CV.HP.COM (John_Altendorf) writes: > 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. > > > John Altendorf alten@hpcvia.cv.hp.com > Hewlett-Packard > Corvallis, Oregon I believe to uudecode one file into multi-parts, you have to use the -x (where x is the no. of lines that you want in the uue file). To UUE, say for instance, a 100K file called DUMMY.LZH, on the command line, type: -700 DUMMY.LZH. This will create a series of uuencoded files that are 700 lines long (except for the last file, which will be the remainder, but not necessarily 700 lines long). Greg Granger | INet: ersys!ggranger@nro.cs.athabascau.ca | | Fnet: Greg Granger (Node 532) Dark Knight (Node 595)| | Post: 5906-188 Street Edmonton, AB Canada T6M-2A9 | | Tele: +1 403 481-0803 OR +1 403 481-5110 | Greg Granger ersys!ggranger@nro.cs.athabascau.ca Edmonton Remote Systems: Serving Northern Alberta since 1982 ----------
alten@hpcvia.CV.HP.COM (John_Altendorf) (05/03/91)
Thanks to each of you who have offered information both as responses here, and through unix mail. John Altendorf alten@hpcvia.cv.hp.com
ljdickey@watmath.waterloo.edu (L.J.Dickey) (05/05/91)
In article <56360002@hpcvia.CV.HP.COM> alten@hpcvia.CV.HP.COM (John_Altendorf) writes: > [...] >I believe to uudecode one file into multi-parts, you have to use the -x ******** ---- I think John means "uuencode" here. >(where x is the no. of lines that you want in the uue file). To UUE, say >for instance, a 100K file called DUMMY.LZH, on the command line, type: >-700 DUMMY.LZH. This will create a series of uuencoded files that are 700 >lines long (except for the last file, which will be the remainder, but not >necessarily 700 lines long). > >Greg Granger > >| INet: ersys!ggranger@nro.cs.athabascau.ca | >| Fnet: Greg Granger (Node 532) Dark Knight (Node 595)| >| Post: 5906-188 Street Edmonton, AB Canada T6M-2A9 | >| Tele: +1 403 481-0803 OR +1 403 481-5110 | > >Greg Granger ersys!ggranger@nro.cs.athabascau.ca >Edmonton Remote Systems: Serving Northern Alberta since 1982 >---------- -- Prof L.J. Dickey, Faculty of Mathematics, U of Waterloo, Canada N2L 3G1 Internet: ljdickey@watmath.UWaterloo.ca UUCP: ljdickey@watmath.UUCP ..!uunet!watmath!ljdickey BITNET/EARN: ljdickey@watdcs