Clarence,
Send one file with 1.62 and receive it with 1.66. The problem as I see it is
that 1.66 is just changing the name of the file and not decoding it.
Roger Turk
Tucson, Arizona USA
>>On Mon, 28 Aug 2000 21:41:32 -0500, I wrote:
> Seriously, allowing for your expertise in these matters L.D., it looks like
> it could be wrong file type. Should be easy enough to check.
I just sent myself two copies of QS.zip.
I sent 1 with A1.66 and 1 with A1.62.
I specifically noted when I checked my OUTBOX that both files were
marked as encoded Base64. The intent was to re-check the encoding
type at the receiving end.
Two minutes later I picked them both up with A1.62.
Both of the files were specified as encoded base64 and when I saved
them to download they were the same freaking size - exactly one byte
bigger than they were when I sent them.
I did this same experiment last week and the file sent with A1.66
was about 50% oversize !!!! I kept getting files from Ron 50%
oversize. Sam got the test file 50% oversize.
Glenn got it the proper size ! (of course)
Someone is hallucinating here and I don't think it's me this time.
Maybe A1.66 only screws up on certain days - or at a certain time
of day ?? The day following the last test above, I did the same
experiment again with smaller files - but I picked them up with
Netscape at the office. NEITHER was oversize by even *ONE* byte.<<
