Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!ukc!icdoc!tgould!iwm From: iwm@ic.ac.uk (Ian Moor) Newsgroups: comp.sys.amiga Subject: Split archives (was Problems with comp.binaries.amiga) Message-ID: Date: 3 Jul 89 19:40:00 GMT References: <7318@cs.Buffalo.EDU> <5160046@hplsla.HP.COM> <1706@ucqais.uc.edu> <865@corpane.UUCP> <674@tolsun.tut.fi> Sender: news@doc.ic.ac.uk Organization: Dept. of Computing, Imperial College Lines: 19 In-reply-to: nix@tolsun.oulu.fi's message of 1 Jul 89 13:20:44 GMT Posting-Front-End: GNU Emacs 18.45.10 of Tue Jan 12 1988 on amvax5 (berkeley-unix) I have a problem with long binaries that are split up before posting. The difficulty is getting them together in the right order! The reason for this is the convoluted route I use to transfer files: Unix : Unshar | Kermit Mac | MCopy MS-Dos | DOS-2-DOS Amiga : uudecode & zoo Why such a long route ? The MSDOS machine is far away in a cold terminal room and using kermit on it is so slooow, but it can read mac discs. Anyway, kermit, mcopy , dos-2-dos and msdos all have their ideas about legal file names and what to do if two names clash. Thus long_name_indeed.zu2 might become longxnam.ex0 (or similar). It would be nice if there was some kind of sequencing in the uuencoded file perhaps as a comment line or an extra command for uudecode to check.