On Thu, 24 May 2001 14:15:02 -0500, L.D. Best wrote:

> 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 ...

l.d....eerrrm....you didn't give enough warning...I had a, ahh..accident
...<g g g>

----------snip-----------

> 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.

yes...we can sort of "customize" an install, with "the-best-of-the-best"
(pun definitely NOT intended...not even contemplated) for Seek...
(..and..if you believe that....well...there's this bridge...<g g g>)
--------snip----------

> 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??

I think we can just use the .CFGs and .ACFs from 1.70r3, the 1.66 core.exe
and etc should work okay with that.
...LATER.....
In fact, upon more thought....we'll just use the 1.70r3 install, with
the 1.66 core.exe substituted on that, plus substitute any of the
other "choice" pieces of the earlier installs.

--------------snip-------------

> 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].
-------------insert-----------

1.  We can "zip" up the empty directory structure for Arachne using:
.....X:\ARACHNE\xcopy *.zzz x:\arachne\dir\ /e /s
2.  We can zip up the contents of each major directory..and/or group
of directories.
3.  We send Seek the zipped up empty directory structure.
4.  We send Seek the individual zipped up packages..
....NOTE - something along these lines will probably work best for him.
BUT...he must understand that he MUST do this as an additional installation
on his current working computer box.  Totally as a separate installation, or
we might end up breaking his working install.
...Since Seek was running Winzz, he undoubtably has a box with enough RAM
and other resources to let him do multiple Arachne Installations..
--------end ins----------

l.d.,
I think we got a "possible" here..........<g g g>...we can break it up
into attachable size, and email it all to him in bits and pieces..

.........gregy

PS....once we get him set up with that, we MIGHT try emailing him some
of the .APMs, if we can come up with a working setup for him to install
them manually from his local drive (or install them automagically from
his local drive - something I haven't yet accomplished, and for which
I am still irritated).

--This mail composed/sent with Arachne...the SUPERDuper Internet
Client...<g g g>

Reply via email to