Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sunybcs!bowen
From: bowen@cs.Buffalo.EDU (Devon Bowen)
Newsgroups: comp.sys.cbm
Subject: Re: UUENCODE / UUDECODE for C-64
Keywords: uudecode, uuencode, c64
Message-ID: <15206@eerie.acsu.Buffalo.EDU>
Date: 23 Dec 89 21:48:41 GMT
References: <21932@usc.edu> <6579@brspyr1.BRS.Com>
Sender: news@acsu.Buffalo.EDU
Reply-To: bowen@cs.Buffalo.EDU (Devon Bowen)
Organization: SUNY at Buffalo Computer Science
Lines: 19

In article <21932@usc.edu>, acliu@skat.usc.edu (Alex C. Liu) writes:
> Yes the program is well written, and runs in 64 and 128 mode.  It has
> some Quircks, though, It creates a STANDARD ASCII file, so when you
> upload the file, you must make sure your term program won't try to
> Convert what it thinks is a PETASCII code into standard ASCII.  (You
> will end up wrong info)  Also, the program ends a Line with a CR
> (CHR$(13)) which is not that smart on a Unix/amiga system that likes
> an LF (CHR$(10)) or on a CPM/MS-DOS system, that likes a CRLF.

I wrote it to match my upload program.

> Besides that the program works like a charm...

If you've got a few hours. I wrote that program cause I needed to upload
some screen dumps one weekend. Haven't used it since. The only reason I
even posted it was to demonstrate how uuencoding works. It's actually quite
horrible...

Devon