Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site lsuc.UUCP
Path: utzoo!lsuc!jimomura
From: jimomura@lsuc.UUCP (Jim Omura)
Newsgroups: net.micro.atari16
Subject: Re: Uudecode wierdidities, ue 3.7 (from Turner*Imagen),etc.
Message-ID: <1326@lsuc.UUCP>
Date: Wed, 3-Sep-86 23:14:27 EDT
Article-I.D.: lsuc.1326
Posted: Wed Sep  3 23:14:27 1986
Date-Received: Wed, 3-Sep-86 23:56:49 EDT
References: <517@elmgate.UUCP> <5661@topaz.RUTGERS.EDU>
Reply-To: jimomura@lsuc.UUCP (Jim Omura)
Organization: Barrister & Solicitor, Toronto
Lines: 26
Keywords: uudecode emacs ST kermit errors
Summary: This is why sources should be posted.

In article <5661@topaz.RUTGERS.EDU> paone@topaz.RUTGERS.EDU (Phil Paone) writes:
>
>     I also was unable to do anything. I didn't get the TOS error 35,
>but when I ran a crash utility, I saw that I had a bus error. 
>     I catted all files together after removing the signitures. Then 
>I uudecoded it without error, then I used xmodem to transfer it to my
>ST and VOLIA, it didn't work.
>
>
>Phil Paone



     This really emphasizes the importance of posting real source code
instead of Uuencoded files.  Often a slightly broken source can be repaired
without reposting the whole code.  Uuecoded files are generally scrap when
they are busted.  It makes me wonder how much Net time is going to be wasted
because of the bad MicroEMACS sending.  If it's re-sent, how much confusion
is going to result?

Cheers! -- Jim O.
-- 
James Omura, Barrister & Solicitor, Toronto
ihnp4!utzoo!lsuc!jimomura
Byte Information eXchange: jimomura
(416) 652-3880