As I recall, <stop> will render whatever has been gotten so far, if it's possible to render it. That may explain why the (partial) page displays in this way. Does starting a big file dowload result in slow speeds or does it come whizzing in all the way? Most webpages are of relatively small size, so thinking about it, it would have to be connected at 2k or something ridiculous to have the effect you are seeing.

Download & install FireFox to see if it's browser specific and to show that the data transfer during the download is as fast as expected.. HTH James :-)

----- Original Message ----- From: "Eve Golden" <[EMAIL PROTECTED]>


OK, I can describe it a little better now, thanks to all of you. I am definitely connected to the Net. Things upload quickly and well. The browser is very, very, very slow in downloading. It's like it gets partway there and then stops. Sometimes it will eventually give a hiccup and finish. Sometimes it just sits there. If I click on Stop, whatever chunk of the page has been lost in the ether will appear -- complete or not, depending on how far the downloading has gotten. Eudora has no trouble even when all this is going on.

--

Reply via email to