<QP>
thanks for responding PA Bear. I just noticed something
that might give you a clue as to what was causing the
hourglass syndrome. The 'freezing' is NOT one that is
absolutely fatal. After about three minutes, IE resurrects
itself and starts responding normally. (I had previously
been too quick to end the process by way of task manager,
thinking it was an irrecoverable error.) Now, I always
keep task manager in the foreground. Whenever the
hourglass syndrome appears and IE freezes momentarily,
task manager shows TWO identical processes that are 'not
responding'.
</QP>
That sounds like adware. E.g. a popup. In XPsp2 you can get
a beep when they are allowed or you can suppress them.
If the site it is trying to find is down or too busy it could be slow
finding that out.
BTW which tab are you looking at to know it is two processes?
If you're seeing "Not responding" you would be looking at the
Applications tab where you would only be aware of tasks.
The Processes tab would show you whether or not there were
really more than one iexplore.exe PID.
What you might do is find out where the request is going.
One rough possibility would be to keep netstat running in a loop
netstat -anosp tcp 5
(Press Ctrl-c to end the loop.)
A more reliable monitor would require more effort on your part
both setting it up and analysing the captured data.
If nothing better you could try the NTx Port Reporter tool
<title>KB837243 - Availability and description of the Port Reporter tool</title>
Good luck
Robert Aldwinckle
---
<QP>
responding whilst attempting to connect to
www.google.com,
task manager will show TWO identical connections to
www.google.com that are both 'not responding'.
Subsequently, when IE comes back alive, task manager will
automatically show ONE instance of
www.google.com that
is 'running'. Any clues PA Bear. thanks.
</QP>
....