Hi Folks,
Clarence Verge wrote:
> I just don't like to part with WORKING Arachnes. <G>
Neither do I. :)
> I don't mind trying the new ones out, and to be true, the only reason
> I haven't fully switched to A1.66 is I haven't 'ported my customized
> stuff upstream yet. I've tested the 'porter and it works 100% for me
> when overlaying a test install on a ramdisk, BUT it's a one-way process.
> Well, I suppose I could re-install I guess.:(
> I have to find the time to fully examine A1.66 so I know what I will be
> changing. I know that's an old version, but I've been a bit busy. <G>
For me, this (1.66) was the last stable version of Arachne.
Versions 1.67 and upwards have found ways to crash or fail at simple
tasks (dgi) regularly.
I still test-run A1.69, did again this morning, but it crashed and
locked, told me to re-boot. Fortunately, I had made the ISP link with
A1.66 and then copied PPP.LOG over to A1.69, so I could just close
(Alt+X) A1.69 and re-invoke A1.66 with -r , and I was back on the air.
And I know that it is not lack of memory anymore. Thanks to everyone for
that.
Regards,
Ron
Ron Clarke http://homepages.valylink.net.au/~ausreg/music.html
-- This mail was written by user of Arachne, the Versatile Internet Client
