The following appears to me to qualify as a candidate for BUG report.
You've got the bug, you've got confirmation, and you've got workaround
plus bonus detail re: TEMP and ARACHNETEMP.
That's a QUALITY bug.
Please ship it to the bug department as Michael requested. <G>
Edenyard wrote:
>
> On Sat, 27 Jan 2001 03:41:40 -0500, Samuel W. Heywood wrote:
>
> > Under options, local settings, there is a box you may check to enable
> > the caching of local objects. The default setting is on. I disabled
> > this bug by unchecking it and now my version 1.70 is a lot more stable
> > than it ever was before.
> > (....)
> > happen also if I clicked on the INDEX button. Has anyone else suffered
> > with this problem? Try disabling the "Cache local objects" bug. It
> > worked for me.
> >
>
> Yes, Sam! I spent hours trying to understand this one when V1.69
> first hit me and I never succeeded. That's one reason why I never
> persisted with 1.69. When I found it, I wrote to the list, asking if
> anyone else had come across it; no-one responded at all!!
>
> As you discovered, 1.70 does it, too. However, I found that setting
> ARACHNETEMP variable in AUTOEXEC.BAT overcomes the problem. If you only
> have TEMP set, Arachne seems to create ARACHNE.TMP as a branch from the
> directory that TEMP refers to; if, however, you have ARACHNETEMP set,
> Arachne uses that directory specified by that without trying to create
> another branch from it. Also, if you set up ARACHNETEMP, you can also
> re-enable the 'Cache local objects' switch and mail will once again work
> as intended. We never had this problem in 1.66, did we? I still don't
> understand what's happening. Let's hope the experts chip in soon!
>
> All the best,
>
> Ron.
--
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
