L.D. wrote:
>>Ran into near problems again today. Red boxes started sprouting! Check
on memory shows 13!!!! in bright red! Now what???
ALT E to shell out, Arachne cleans itself out of memory, enter EXIT to
return to Arachne and voila! memory is 108.
Arachne is capable of clearing everything from memory. Arachne is often
bogged down and crashed because memory is full.
Why can't Arachne clean memory out on its own?
Why should a user, if lucky enough to know the trick, have to *force*
Arachne to clear memory?
Doesn't Arachne poll periodically to see how much memory is left
available to it?
If not, why not? Arachne can count, can tell time, can check to see
how much memory is available, can do all the many things required to
keep memory from becoming clogged.
So why doesn't Arachne do just that?<<
=-=-=-=-=-=-=-=-=-=-=-=-
I think the main question should be, "What is Arachne keeping in memory that
isn't needed and why?"
Roger Turk
Tucson, Arizona USA
