It's getting so bad I avoid all PDFs.
Typically what happens is, the first page seems to
load fine, I page down on the scrollbar, and it locks up.
I go to Task Manager, everything looks fine till I
drag another window across the Netscape window.
Then TM shows 100% CPU. The Netscape screen shows
"trails" of the window I'm dagging, and they stay
that way. No screen refresh, all Netscape functions
locked.
The modem is accepting data at very fast rates.
(I assume that means it's being highly compressed.)
The file may unlock after what seems like unbelivably
HUGE file sizes such as 30M and over half an hour.
I can't believe that PDFs are routinely this large.
(Are they?)
Possibly the new PDFs are too big for 56k modems?
Task Manager shows Netscape at around 10% CPU and
PDF at around 90%. Some of the memory values bounce
around but are not climbing. End PDF and everything unlocks,
Netscape drops to around 1% and an unloaded blank screen.
Everything fine. ...often 10+ minutes killed, cuz if I
broke down & clicked on a PDF, I REALLY want it. .
Possibly related?
It used to be that Web pages' text showed up almost
imediately, then the images slowly filled in.
Worked well.
But for the last year??? the pages stay blank
for a long time, then blink; the whole thing is there.
Frustrating dead time. Is that a setting? Cache?
Or new hip-baby HTML code?
(It seems like PDFs used to work that way too,
only slower cuz they are bigger.)
Any ideas?
Thanks,
--Doug
|
