"tones" <firstname.lastname@example.org> wrote in message news:96A52558-D9FB-47D7-B77C-81BC42BFC277@microsoft.com...
> Thanks for your input. In compatibility mode, that page loads with even more
> red crosses in place of graphics. It was perhaps not a good example.
> This page is another example where this happens
> (it does seem to happen on pages with quite a lot of graphics):
That's mainly a symptom of poor connectivity.
Instead of doing a Refresh what you want to do then
is load a page over the one you want to finish loading
and then go back to it. So, for example, with about
for your Home page you could press Alt-Home and Alt-CursorLeft
instead of F5. Another thing you could try (but just for that case)
would be to set your cache-checking option to Never
(e.g. press Alt-T,O,Alt-S,N ). That would reduce the network
overhead to a minimum when you were trying to continue
loading a partially loaded page. OTOH you might find that
by using the Every time I visit the web page check
(e.g. after pressing Alt-T,O,Alt-S,E) the additional regular activity
might be enough to keep the loading going longer.
Finally, your type of network connection, e.g. dialup or LAN
can have a bearing on your network performance,
especially with IE8, since it now can automatically start using
more than the default 2 maximum HTTP connections per server
if the connection is determined to be fast.
FWIW no problems loading that page through my DSL PPPoE link.
A previous poster (last year) had a much more extreme example...
Oops. It was longer ago than that. ; )
Probably no longer available... Nslookup shows the host is unknown.
Too bad. It was a fun test. ; )
> I know this is not a general IE error - I'm sure it is happening because
> I've tinkered with something I shouldn't have and I expect the pages will
> load fine for everybody else. I was hoping installing IE8 might reset things
> and fix it.
> I realise this makes it difficult to pinpoint a fix, but I'm just hoping
> that someone might be able suggest something else to try.
> I remain puzzled as to why clicking on any encoding language allows the page
> to display properly.
That's probably just another way of getting the page to reload with less
overhead than doing a Refresh. You could use Fiddler2 to trace your
cases and see exactly what is happening in each.