Thanks for your informative reply. I'll do some research on script debugging,
as I never have dealt with it. Meanwhile, if you have a suggestion for a
debugger, it would be appreciated. In any case, Happy New Year!

"Robert Aldwinckle" wrote:

> "Padrino" <Padrino@discussions.microsoft.com> wrote in message
> news:F6C718A6-9745-487C-9072-74F040158870@microsoft.com
> ....
> > Does anyone have any suggestions on how to determine what's happening on
> > the browser when it locks up?
>
> Have you tried running a script debugger to see what happens before it hangs?
> An inferior but still useful substitute would be to activate prompting for scripts,
> ActiveX, etc. just to see what the pattern there is. Running FileMon and
> RegMon to trace file system and registry accesses leading up to the hang
> and then comparing the equivalent traces of what happens when a transaction
> works would be useful too. Do you even know if the symptom is a hang
> or a loop? Activating maximal column statistics in Task Manager could help there
> and again, depending on how loose the loop is, the other tools could help
> clarify what it was doing then.
>
> Finally, are the IE6sp1 systems fully updated with the latest cumulative
> update for IE or is some lower level of maintenance present?
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>