On Tue, 29 Aug 2000 10:29:32 -0400, Roger Turk wrote:
<snip>
> Sam,
> I just used Richard Marks' UU to encode DR.COM and *all lines* started with
> "M", as they should, and none had only a period on a line by itself. Here is
> the UUencoded file:
> section 1 of 1 of file DR.COM < uuencode 97 (v58) by R.E.M. >
> [Attached file: DR.COM]
> sum -r/size 59823/4669 section (from "begin" to "end")
> sum -r/size 26280/3370 entire input file
> Also, I could not find any option to use "all caps."
Roger:
The results of your transmission were indeed quite strange at my end.
When I clicked on the icon representing the attachment I got the
"Arachne Load Error" page with the smiley-faced guy.
I searched my C:\ARACHNE directory and all subdirectories thereof for
DR.* and I found DR.COM, 8564 bytes in my C:\ARACHNE directory. I should
have found DR.COM in my C:\ARACHNE\CACHE directory. Maybe a copy of
DR.COM had already been in my C:\ARACHNE directory before you had sent it.
Dunno.
BTW, there is an option to use "all caps". This is known as XXENCODE,
so I understand. The below is excerpted from Richard Marks'
documentation file, UTECH.TXT:
---------- quoted material begins --------
In my opinion, XX-encoding is superior to UU-encoding because it uses
more "normal" characters that are less likely to get corrupted. In fact
several of the special characters in the UU set do not get through an
EBCDIC to ASCII translation correctly. Conversely, an advantage of the
UU set is that it does not use lower case characters. Now-a-days both
upper and lower case are sent with no problems; maybe in the
communications dark ages, there was a problem with lower case.
This "UU" encode/decode pair can handle either XX or UU encoding. The
encode program defaults to creating a UU encoded file; but can be run
with a "-x" option to create an XX encoding.
The decode program defaults to autodetect. However the program can get
confused by comment lines preceding the actual encoded data. The decode
mode can be forced to UU or XX with the "-u" or "-x" parameter.
--------- quoted material ends -------------
I have just now completed doing some experiments with Richard Marks'
program in encoding and decoding of DR.COM by use of various options.
At this time I cannot repeat the unfavorable results I had experienced
in the past, such as a period on a line by itself. Now I don't know
why I had previously had problems with the program. Beats the hell out
of me!
When I use Richard Marks' program I find that not all lines start
with an M. I remember I once had a problem in attempting to send an
email to someone with DR.UUE being an attached file. The email
transmission would terminate upon encountering a certain character.
As I recall, it was a period on a line by iself. I changed the parameter
for my encoding choice and then the message and the attachment flew OK.
At this time I cannot reproduce such results. Therefore, I cannot prove
my point. Oh, stupid me!
All the best,
Sam Heywood
-- This mail sent by Arachne, www graphical browser for DOS
-- Visit the Arachne DOS Browser Home Page, http://home.arachne.cz
