Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: cloos@acsu.buffalo.edu (James H. Cloos)
Newsgroups: comp.sys.handhelds
Subject: Re: Why ASC over UUENCODE?
Message-ID: <59678@eerie.acsu.Buffalo.EDU>
Date: 14 Feb 91 00:20:24 GMT
References: <20148@shlump.nac.dec.com> <1991Feb13.101558.5056@lth.se>
Sender: news@acsu.Buffalo.EDU
Organization: State University of New York @ Buffalo
Lines: 16
Nntp-Posting-Host: lictor.acsu.buffalo.edu

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,
and not everyone is able to backup to a computer (I'm currently stuck w/
backing up to a ram card which I do not take out (though sometimes FREE and
set to R/O)).  ASC will tell you the string is invalid if there is any
coruption; uudecode will not, and could cause problems.

(I don't want to create another immense flame war (asbestos suits can be
expensive); I hope that we can get back to the more interesting posts!)

-JimC
--
James H. Cloos, Jr.		Phone:  +1 716 673-1250
cloos@ACSU.Buffalo.EDU		Snail:  PersonalZipCode:  14048-0772, USA
cloos@ub.UUCP			Quote:  "If you miss any humor, too bad!"