Hold onto your hats, folks ... I don't want any coffee on keyboards and
monitors either, so put down what you are eating and drinking...
I agree 100% with greggy! I worked my way through from 1.60 to 1.70r3
and the "stable version" I have kept for the kids to use is the same one
he prefers ...
On Thu, 24 May 2001 03:12:17 -0700, Gregory J. Feig wrote:
> NO..!!!...don't give him 1.69...that has the "Your Browser sent this
> Server a message this server did not understand" bug.
> 1.67 and 1.68 both had the "MemoryMonster" bug, baaaaddd...!!!
> About the best, most recent version is the 1.66...it is very stable,
> and has most of the bells and whistles...
For anyone looking to a stable, manageable, version of of Arachne, I
also would recommend 1.66 ... with one adendum: I would suggest
that the version of InSight which comes with 1.70r3 [and earlier?] be
substituted for the version which came in 1.66 originally. Doing that
seems to totally cure the 'lost chains' problem that was around for so
long.
Now, if I recall correctly, there was a change in mime.cfg structure
between 1.59 and the 1.60+ versions; if this is the case, that would
mean that Seek couldn't use the current mime.cfg file, but he should be
able to use the current Arachne.cfg file ... correct? Any bells and
whistles added between 1.59 & 1.66 could then be entered into
Arachne.cfg via Options??
*****
Seek ... I know you said you'd try the e-mail route; that may not work
for you, if your ISP has limits on the size of e-mail. Once 600K is
UUEncoded it takes up a LOT of space. And I don't think archive
versions are available that way either. :<
But you still have options ... once we figure out what you need, we can
put small files up for downloads "in pieces" or can attach files to
messages that won't run over a Mbyte in length. <G> Don't give up ...
we're very talented in this group [even though it doesn't show at
times].
l.d.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
