Dr Watts

[Mike Gasson]

I've noticed that the Dr Watson logfile on my laptop is over 2gb. Should
it be that big and can I delete it? The laptop is working just fine
(AFAICS).
Thanks.

 

[Wesley Vogel]

If you have a lot of program errors, drwtsn32.log will get huge.

Either delete the drwtsn32.log or open it and delete the contents.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Mike Gasson]

If you have a lot of program errors, drwtsn32.log will get huge.

Either delete the drwtsn32.log or open it and delete the contents.

I've deleted it as it was taking forever to open the file. I haven't
been getting a lot of program errors though.
Thanks Wes.

 

[Wesley Vogel]

Mike,

At some time you had been getting application crashes or drwtsn32.log would
not have been 2GB.

I only have a 10GB hard drive. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Mike Gasson]

Mike,

At some time you had been getting application crashes or drwtsn32.log would
not have been 2GB.

Hi Wes. I'm not sure about this. Does the event viewer tie up with the
drwtsn32.log? I noticed the event viewer entries ran from some time in
May when I got this laptop. Deleting the log didn't remove the event
viewer entries.
Also, does deleting the log mean I no longer have a Dr Watson logfile?
I was assuming that it would be recreated.

I only have a 10GB hard drive. ;-)

So you need to plug any leaks then. :-(

 

[Wesley Vogel]

Hi Mike,

Yes Drwtsn32.log ties in with the Event Viewer...

[[When Dr. Watson detects a program error, extensive diagnostic
information is logged in the Drwtsn32.log file. Dr. Watson also records an
entry in the Event Viewer Application Log containing the program name, date,
time, exception number, exception name, program counter, and function name
at the current program counter, as well as the complete diagnostic
information that was logged for that error.]]

But deleting entries in or deleting the Drwtsn32.log does not remove
anything from the Event Viewer and clearing events in the Event Viewer does
not affect the Drwtsn32.log.

Drwtsn32.log will be recreated if needed. Hopefully it'll never be needed.

I spend a lot of time plugging hard drive leaks. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Mike Gasson]

Hi Mike,

Yes Drwtsn32.log ties in with the Event Viewer...

[[When Dr. Watson detects a program error, extensive diagnostic
information is logged in the Drwtsn32.log file. Dr. Watson also records an
entry in the Event Viewer Application Log containing the program name, date,
time, exception number, exception name, program counter, and function name
at the current program counter, as well as the complete diagnostic
information that was logged for that error.]]

But deleting entries in or deleting the Drwtsn32.log does not remove
anything from the Event Viewer and clearing events in the Event Viewer does
not affect the Drwtsn32.log.

Drwtsn32.log will be recreated if needed. Hopefully it'll never be needed.

I spend a lot of time plugging hard drive leaks. ;-)

Thanks very much for the explanation Wes, it makes a lot more sense now!
Before I found the logfile I was down to 750meg on my C: drive so I'm
glad of your assistance here!

 

[Wesley Vogel]

Mike,

750meg, oooh!

Keep having fun.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi Mike,

Yes Drwtsn32.log ties in with the Event Viewer...

[[When Dr. Watson detects a program error, extensive diagnostic
information is logged in the Drwtsn32.log file. Dr. Watson also records
an entry in the Event Viewer Application Log containing the program
name, date, time, exception number, exception name, program counter, and
function name at the current program counter, as well as the complete
diagnostic information that was logged for that error.]]

But deleting entries in or deleting the Drwtsn32.log does not remove
anything from the Event Viewer and clearing events in the Event Viewer
does not affect the Drwtsn32.log.

Drwtsn32.log will be recreated if needed. Hopefully it'll never be
needed.

I spend a lot of time plugging hard drive leaks. ;-)

Thanks very much for the explanation Wes, it makes a lot more sense now!
Before I found the logfile I was down to 750meg on my C: drive so I'm
glad of your assistance here!

 

[Mike Gasson]

Mike,

750meg, oooh!

Keep having fun.

Send me a self-addressed plain brown envelope and I'll see what I can
do. ;-)