On Thu, 31 Aug 2000 23:58:07 -0400, L.D. Best wrote:
> Excuse me ...
> On Tue, 29 Aug 2000 16:57:13 -0500, Samuel W. Heywood wrote:
>> You can't UUDECODE one of his oversized attachments, the one having 56,349
>> bytes. You can't UUDECODE it because it is BASE64 encoded. Take a look
>> at it with a file viewer and see for yourself. In order to decode it you
>> will need MIME64.EXE, or a similar program. You want to get it? Then
>> you just ask for it, and I'll sock it to you. MIME64.EXE, 23,436 bytes.
> Don't think so. In fact, if he has Arachne I know not so.
> Sam, I think you maybe lost a file or two when you upgraded. Arachne
> handles BASE64/MIME encoding and decoding just fine.
Yes, I am perfectly aware that Arachne can handle BASE64/MIME decoding just
fine. I am beginning to think the "attachment problem" might have something
to do with a switcheroo of which is what between different versions and
setups. It doesn't matter which is what and what name you give to which, as
long as you know how to distiguish the difference and understand what to do
with which. A problem arises when you are attempting to communicate with
others, or even with yourself, in your email transmissions. The sender tells
the receiver that a file is UUENCODED and it arrives at the receiver's end as
BASE64 encoded, and vice-versa. Arachne doesn't know what to do with it
because she is receiving conflicting instructions from both ends.
> No need for an
> "independent source" piece of software unless files are missing from the
> Arachne 1.66 installation package... and then you'd be better off
> copying over missing files from earlier version of Arachne.
If the problem is about what I think it is, then you need some
independent source software because we can't switch things around in CORE
to get things sorted out the way it is supposed to be. In this case we
need to resort to independent source software because we do not know of any
method to manually select one or the other of the decoding routines built
into CORE.
I am inclined to think that the problem might be along the lines as I have
described, but I have not yet conducted any thorough tests of this
hypothesis, and neither have I been able to succinctly formulate the concept
due to its seeming complexity.
Anyway, I have discovered a way to work around the problem and I have found
a way to decode my attachments by use of independent source software.
> Arache simply does not contain any specific exe or com files which
> indicate by name that they would encode/decode using Base64[MIME]. But
> it gets done nonetheless without any need for bringing in outside files.
Yes, you are right. Normally this is the case, but what if Arachne has
become confused as to the type of encoding used?
Sam Heywood
-- This mail sent by Arachne, www graphical browser for DOS
-- Visit the Arachne DOS Browser Home Page, http://home.arachne.cz
