I watched very carefully today, and it seems that the code may have a
glitch in it somewhere, taking it to the "Loading Page from Disk" module
when it shouldn't be there.
I watched the page come down partially, then Arachne froze into "Loading
..." mode for a few seconds, then more page came down, and the "loading"
appeared again with accompaning freeze, the graphics came down, and once
again Arachne was "loading" ... and the only thing which appeared on the
screen during this entire process was the two blank lines in the bottom
2/3 of the page which would indicate it was a "4-frame page" with one
frame across top, one large frame in middle of bottom with one small
frame on both sides of bottom.
But throughout the process, Arachne kept hanging up in the "Loading Page
from Disk" mode. When it came time for the screen write, Arachne didn't
load the page from disk [or at least the messages didn't say so] ... it
was "Adjusting frames, tables ...." and then the screen finally wrote.
Since I have screen refresh set to 60 seconds, I don't think that aspect
would be causing Arachne to want to "load page from disk" when the page
isn't complete enough to load much of anything.
Why is this happening? don't ask *me* ... I'm just a user, not a
programmer. <G>
l.d.
P.S. I've lost my "smooth scroll" again for some reason. It's set that
way, I went in and set it again, saved & used new ... but no smooth
scroll even on short pages with emptied cache before loading.
--
-- Arachne V1.61, NON-COMMERCIAL copy, http://arachne.cz/
