Have to disagree with Sam, here.
I had problems with Arache sleeping and I had a problem with the page in
question. And the two are *not* the same. I supposedly got the page
into cache, so I checked to see if it was there. It was, and consisted
of two nested frame and nothing else... That would seem to imply that
something in the page code somewhere between the 2nd frame and the 3rd
one caused Arachne to think the d/l was over and start trying to load
the page. Since the page wasn't complete, Arachne couldn't find any
references it needed to load, and thus a never-ending circle of "now is
time to load" vs. "I don't have enough to load" and it's lock up time.
I haven't had any problems with sleeping since 1.5 s.r.c.
Sam is correct that lock-ups and such are things we argue about. <G>
l.d.
--
-- Arachne V1.61, NON-COMMERCIAL copy, http://arachne.cz/
