Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!samsung!sdd.hp.com!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!umbc3!gmuvax2!peraino
From: peraino@gmuvax2.gmu.edu (Bob Peraino)
Newsgroups: comp.sys.handhelds
Subject: RE: ASC versus uuencode
Keywords: hp48
Message-ID: <3475@gmuvax2.gmu.edu>
Date: 14 Feb 91 20:10:26 GMT
Organization: George Mason Univ., Fairfax, Va.
Lines: 20


>I feel compeled to mention one point that I left out of my immediatly
>previous post on this subject:  ASC includes a CRC, uuencode does not.  On
>a machine such as the 48, where incorrect binaries can cause a MEM LOST,
.
.
>  ASC will tell you the string is invalid if there is any
>coruption; uudecode will not, and could cause problems.
 
     uudecode may not have a checksum, but then, why do you really need
one, anyway? I don't know about you, but I KERMIT the stuff to my
48, and KERMIT does checksumming anyway, so it can't get from there
to here with an error anyway. I suppose, somewhere along the net,
something could get hosed, but aren't all those connections checksumming
as well? If I'm wrong about this, then indeed, the checksums are important.

>James H. Cloos, Jr.             Phone:  +1 716 673-1250
>cloos@ACSU.Buffalo.EDU          Snail:  PersonalZipCode:  14048-0772, USA

peraino@gmuvax.gmu.edu