Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!motcid!king From: king@motcid.UUCP (Steven King) Newsgroups: comp.sys.amiga Subject: Re: FTP Servers Message-ID: <5944@orchid3.UUCP> Date: 27 Dec 90 16:02:23 GMT References: <1033.27783F09@weyr.FIDONET.ORG> <1990Dec26.172922.17717@ericsson.se> Organization: Motorola Inc. - Cellular Infrastructure Div., Arlington Heights, IL 60004 Lines: 29 In article <1990Dec26.172922.17717@ericsson.se> etxtomp@eos.ericsson.se writes: >Having no access to ftp, I use bitftp@pucc.princeton.edu to do the ftp for >me, from ux1 and abcdf20, specifying BINARY. I get the file UUencoded by >email and UUdecode it (I have tried both on a SparcStation and on my Amiga). >The files are transferred from Sparc to MS-DOS diskettes using mtools, which >has binary transfer as default. From MS-DOS to Amiga I use DOS-2-DOS, which >also has binary transfer as default. > >All files are corrupted, but not totally screwed up. If I have UUdecoded >a Zoo archive and does zoo -l archive, it lists 2 or 3 files from the >archive before complaining about corrupt file. I use Bitftp all the time, and haven't found any problems so far. I suspect you're not stripping the headers off the messages before you uudecode them. Uudecode is a rather dumb program. There's almost no error checking done whatsoever. Bitftp splits large files into multiple segments. If you just cat the segments together and then uudecode the large file, UUDECODE WILL TREAT THE MAIL HEADERS AS DATA AND DECODE THEM! Naturally this will mess up the files. You've got to make sure you strip out everything that's NOT uuencoded text. Anything between the "begin" and "end" lines is fair game to be decoded. Good luck! -- ---------------------------------------------------+--------------------------- They're furry, they're funny | Steven King They're Babs and Buster Bunny... | Motorola Cellular (Unabashed "Tiny Toon Adventures" plug) | ...uunet!motcid!king