Hi Beebo,
Not sure if you got the email I responded to but I'll post here what we can
try next.
We can still troubleshoot what your issue is it will just be a little more
difficult. We can handle this a couple different ways. Two I just ran into
but I have never used myself so I don't know first hand how easy they are.
We can save those for later if the other two don't work. The first method
requires some registry editing but it will save you from having to do (as
many) debugger commands yourself.
1.. Open the Registry by clicking Start -> Run and type "regedit" without
quotes in the Run dialog box.
2.. In the Registry editor navigate in the left pane to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
3.. In the right pane right click the key called Debugger and edit so it
says "NTSD -p %ld -e %ld -g" without quotes instead of "drwtsn32 -p %ld -e
%ld -g"
4.. Once modified click Ok and ensure the entry has been modified
correctly.
5.. Minimize the editor and proceed to crash Explorer as you have.
6.. You should get a DOS looking window that is a debugger instead of the
online crash tool.
7.. You should be able to type in the debugger (without quotes but with
the '.' ) ".dump c:\explorerdump.dmp"
8.. Close the debugger window.
9.. You can do this more than once if you want. Just change the name of
the file created each time.
10.. Send me the files created and I'll look at them in a debugger and see
if I can find something that indicates what is going wrong.
Let me know if you need something explained more. If you don't feel
comfortable editing the registry let me know that too and I'll send you some
files that will do the editing for you.
Joshua Smith
VIDOCA and OpenGL Test Labs
Microsoft
-----
Get Secure!
www.microsoft.com/security
This email is provided "AS IS" with no warranties, and confers no rights