Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!wuarchive!psuvax1!rutgers!ub!acsu.buffalo.edu
From: cloos@acsu.buffalo.edu (James H. Cloos)
Newsgroups: comp.sys.handhelds
Subject: Re: ASC utility, posting, accessability
Keywords: hp48
Message-ID: <56157@eerie.acsu.Buffalo.EDU>
Date: 25 Jan 91 19:02:22 GMT
References: <3289@gmuvax2.gmu.edu>
Sender: news@acsu.Buffalo.EDU
Organization: State University of New York @ Buffalo
Lines: 24
Nntp-Posting-Host: lictor.acsu.buffalo.edu

In article <3289@gmuvax2.gmu.edu> peraino@gmuvax2.gmu.edu (Bob Peraino) writes:
[stuff del'ed]
>...    What would be more universal would be true uuencode/uudecode running
>on the '48. How big and bad can that be, considering it's functionally
>the same as ASC? This would make "encoded" postings more easily accessible;
>you can decode on the '48, but if you don't have the '48 version, you could
>decode on your UNIX system....
[stuff del'ed]
>peraino@gmuvax.gmu.edu

What rfc is it that explains the uuencoding scheme?  I really don't
think that it would be exceptionally difficult to do it, though it
will be larger that ASC\-> given that the crc (there IS one, isn't
there?) will have to be written in, rather than using the builtin
Kermit crc algorithm.

I'd be willing to try my hand at converting uudecode to the 48, though
it may take a while; it would surely make a good programming exercise.

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