Ron & All,
I received both the 1.64 attachment & the 1.66 attachment.
My version 1.64 unencoded both automatically.
Both MIME file headers were in the same format, and precisely the same
with the exception of the attached file code name [changes by date time,
apparently, just like Arachne mail files].
Both encoded files were precisely the same size, with precisely the same
number of lines, and decoded to zip files precisely the same size.
Both zip files unzipped perfectly, to files of matching size.
Now -- Who was having the problem???
What some may not have realized/noticed is that InSight changed with
version 1.66 ... did the person having problems perhaps only "install"
the files which appeared to have changed, like core.exe ??
It could be that InSight 3.51 is *required* by Arachne 1.66 for things
to work correctly?
Ron's setup uses the new InSight 3.51 with Arachne 1.66 as it should.
l.d.
--
Learn about B'FOR
Join B'FOR - B'mothers For Open Records
<a href="http://www.b-for.org">B'FOR web site</a>
[Associate members of triad also welcome; membership confidential.]
Every member counts! We need numbers to produce valid statistics.
-- Arachne V1.64, NON-COMMERCIAL copy, http://arachne.cz/
