Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!rutgers!sri-spam!sri-unix!hplabs!ucbvax!UHUPVM1.BITNET!ACS19
From: ACS19@UHUPVM1.BITNET (Mike Vederman)
Newsgroups: net.micro.atari16
Subject: finally, i've figured uudecode ...
Message-ID: <8610072120.AA09863@ucbvax.Berkeley.EDU>
Date: Tue, 7-Oct-86 15:42:05 EDT
Article-I.D.: ucbvax.8610072120.AA09863
Posted: Tue Oct  7 15:42:05 1986
Date-Received: Wed, 8-Oct-86 08:22:23 EDT
Sender: broome@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 34

After many, many problems with BITNET, IBM machines and uudecode, I have
found the true answer to having all of my files uudecode.  Every single file
which has bombed in the past, now decodes perfectly.

The normal sequence that I do is to send the file over from the IBM machine
(actually we have an AS/9000N) to the AT&T 3B20 and uudecode on the 3B20.
Previously, the only two files which worked were UNITERM and uEmacs.

Now, however, I have found the solution, but I am uncertain as to the exact
cause.  Here is what I do.  First, while in Xedit, I set the logical record
length to 61, then I set the record format to fixed.  The following commands
do this:

set lrecl 61
set recfm f

now, when I send the file to the 3B20, I enter the command:

sf file uue to acs19 at uhnix1

to receive on the 3B20, I enter the command:

receive $job/pnch6 >file.uue

(since the 3B20 is hooked up as a punch machine (yuck).  What you do may be
different, but I know setting the logical record length and the record format
have made all of my files work.)
When I get to the 3B20, I do have to fix the file a little bit.  I go to the
last line and delete the blanks to end of line, after 'end'.  Then I go up one
line and make sure that there is only 1 (one) blank on the second to the last
line.  Then I save the file and uudecode it.  All the files I have tried thus
far have worked, and most of these have always bombed.

Mike