Archives of the TeradataForum

Message Posted: Tue, 22 Jul 2014 @ 10:59:44 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

You might try DrWatson, it's a postmortem debugger that comes with Windows. You can start it from the Windows command line or include it in your 'autoexec.bat'. It has a small foot print and just sits in the background.

Although it might not always work, the idea is that when a problem triggers it, it will collect information about the state of the machine when the problem occurred.

If it's triggered (and that can be a big 'if'), the information will be written to a log file. Although the contents can be pretty arcane, you might get an idea of what's causing your problem.

There have been different versions: 'drwatson.exe', 'drwtsn.exe' or 'drwtsn32.exe'. I think that 'drwtsn32.exe' is the version for Windows XP. It would be best to do some searches for the version you need and how to use it.

When you start DrWatson, it will ask for some configuration information. Here's what I have:

- Log File Path: c:\

- Number of Instructions: 32

- Number of Errors to Save: 32

- Uncheck all options except you want to check these:

Dump Symbol Table
Dump All Thread Contexts
Visual Notification

Although I've found DrWatson to be really useful, I wouldn't make it a practice to always load it. Since it's rather dated, I would be concerned with how well it plays with newer programs - especially anti-virus stuff.

	<Prev	Next>		<<First	<Prev	Next>	Last>>