Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!ucbvax!LLL-MFE.ARPA!JMCCAULEY%PPC.MFENET
From: JMCCAULEY%PPC.MFENET@LLL-MFE.ARPA
Newsgroups: net.micro.atari16
Subject: uudecode suggestion (include CRC)
Message-ID: <8609140006.AA10982@ucbvax.Berkeley.EDU>
Date: Sat, 13-Sep-86 19:53:00 EDT
Article-I.D.: ucbvax.8609140006.AA10982
Posted: Sat Sep 13 19:53:00 1986
Date-Received: Sun, 14-Sep-86 07:29:05 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 25




One thing that might help with uudecode problems is to have the following
included in every uuencoded file (before the begin line of course!) or
posted in another message:

1) Size in bytes
2) CRC and/or linear checksum of binary (uuencode has no checksums!)
3) systems tested on (color/mono, tos-in-rom/tos-in-ram)

This way we can determine if uudecode worked correctly.
Some problems may not lie entirely with uudecode. I think uEMACS 3.4
did not work on mono systems (3.7 does with hres50).

Btw, this is assuming there *are* CRC programs already written. I haven't
seen one and have no C-compiler (yet). Perhaps a good topic to discuss
on this mailinglist is what public-domain crc checkers are out there and
how interchangeable they are.

        Hope this helps,
        
        Scott McCauley
        jmccauley%ppc.MFENET@lll-mfe.ARPA
        jsm@borax.lcs.mit.edu