Getting more friendly logs from Drwatson. 2

[Naguall]

There´s a tip in Drwaton´s "HELP", teaching how to copy some "symbols" from the XP instalation CD to a Folder in Windows Root Directory, in order to get more friendly logs from the debuger. I´ve searched the instalation CD for the "symbols" but didn´t find them. Can someone give a more detailed explanation of how doing it ?
Thanks for any kind of help !

 

[bcastner]

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

If you already have the SP1a SYMBOLS installated, on the Service Pack 2 CD ROM the SP2 SYMBOLS can be found here:
\SYMBOLS
- Contains the Symbol files for Windows XP SP2. These are used to debug and troubleshoot XP SP2.

 

[linney]

315263 - Reading the Small Memory Dump Files That Windows XP Can Create for Debugging

http://support.microsoft.com/default.aspx?scid=kb;en-us;315263&FR=1&PA=1&SD=HSCH

314084 - How to gather information after a memory dump in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;314084&FR=1&PA=1&SD=HSCH

315271 - How to Use Dumpchk.exe to Check a Memory Dump File

http://support.microsoft.com/default.aspx?scid=kb;en-us;315271&FR=1&PA=1&SD=HSCH

254649 - Overview of memory dump file options for Windows 2000, for Windows XP, and for Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;254649&FR=1&PA=1&SD=HSCH

Any errors logged in the Event Viewer can be expanded by double clicking on the error line.

Take any event error I.D. number and search for it on this site.

http://www.eventid.net/events.asp

If you want the highly technical cause of the crash look in the Documents and Settings/ All Users/ Application Data/ Microsoft/ Dr Watson/ Drwtsn32.log

Find the entry that is relevant by date and time to the crash you are investigating. The exact cause of the crash is indicated by "FAULT ->" on the left of page next to line of code causing crash. This, if your as cluey as me, wont tell you much but you can use it to see if it is the same fault all the time, and further up the log you can find what processes and modules are running.

 

[Naguall]

Thank you very much.The first url posted by bcastner was straight-to-the-point.linney´s tips also help me.
Bye !