Still looking for a debug method for IE while it loads

[Steve Howard]

Hello,

I've been posting many times how to figure what IE is loading or
trying to load as it starts up.

I could best describe this by as IE loads it would show the
path and module it was trying to load. I just want to see
all modules external to IE (and internal if poked in IE code)
as they load. In this way I might determine what modules, if any,
are causing IE from comming up.

In this case IE returns no messages nor shows any windows or
output of any kind. That is why a debug method I'm describing
would allow the identification of failing components.

Thanks,

Steve Howard

 

[Al]

how about using a utility that lets you see running processes? You can look
before and after starting IE - with a glorified Task Manager, from
download.com

or how about a Windows' fault or error log, aren't they there from ME onward?

 

[Steve Howard]

how about using a utility that lets you see running processes? You can look
before and after starting IE - with a glorified Task Manager, from
download.com

or how about a Windows' fault or error log, aren't they there from ME onward?

Thanks,

That's a good idea and I will pursue this track along with
other suggestions.

Appreciation,

Steve

 

[Al]

Steve, I happened to run across one today, at prcview.com

You can invoke a system debugger, which I suppose you supply. I assume you
want to do something like breakpoints.

My IE6 showed a heap of associated modules

over 60, I'd say

 

[Bill]

Steve, I happened to run across one today, at prcview.com

You can invoke a system debugger, which I suppose you supply. I assume you
want to do something like breakpoints.

My IE6 showed a heap of associated modules

over 60, I'd say

You can also go to
C:\WINDOWS\APPLOG

and look for the files IEXPLORE.LGx
where x= hard drive letter.

Open these in a text-editor (as READ ONLY!!)

This will list, in order, the modules IEXPLORE.EXE loads.
BTW, this data is used by Windows Defrag to order your files for consecutive
loading.

 

[Steve Howard]

You can also go to
C:\WINDOWS\APPLOG

and look for the files IEXPLORE.LGx
where x= hard drive letter.

Open these in a text-editor (as READ ONLY!!)

This will list, in order, the modules IEXPLORE.EXE loads.
BTW, this data is used by Windows Defrag to order your files for consecutive
loading.

An excellent idea. I will try this tomorrow. If I find the
offending module I will let you know.

Thanks,

Steve

 

[Steve Howard]

You can also go to
C:\WINDOWS\APPLOG

and look for the files IEXPLORE.LGx
where x= hard drive letter.

Open these in a text-editor (as READ ONLY!!)

This will list, in order, the modules IEXPLORE.EXE loads.
BTW, this data is used by Windows Defrag to order your files for consecutive
loading.

I can not find APPLOG in Windows XP Pro. Have any idea where
this log would be found in Windows XP Pro?

Thanks again,

Steve

 

[Steve Howard]

Steve, I happened to run across one today, at prcview.com

You can invoke a system debugger, which I suppose you supply. I assume you
want to do something like breakpoints.

My IE6 showed a heap of associated modules

over 60, I'd say

IE starts then stops - no windows, no messages. What I really need is
something that will show me what IE is trying to load. As IE is stopped
I'm not sure a process viewer is going to help. I'll have to look at the
Prcview options as they many have a logging option which perhaps my show
enough history I can gleem why IE is not loading.

Thanks,

Steve