At first I thought that it was a program called BootVis, and removed it.
But then I set several realtime sensors for disk free space, memory
available, and others, that constantly monitor the machine resources and
performance. The program that does it Norton System Doctor.
Now, again, in a session of three or four hours the free disk space
decreases until it blows the alarm.
Question: is it possible that the monitoring is writing such the data to the
file Trace.log, and letting it accumulate without purging the older?
TIA,
haim
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
Inflated TRACE.LOG problem, how to fix.
http://www.tweakxp.com/tweak1302.aspx
--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx
---------------------------------------------------------------------------------
I had the same problem. You should have shut down tracking before removing
the program. Install the program again. deactivate everything. Reboot to
make certain that it is not tracking. Then, shut down and delete the program
--
Regards:
Richard Urban
aka Crusty (-: Old B@stard :-)
"Haim Guivon" <ar...@lookup.net> wrote in message
news:OokEYi4t...@TK2MSFTNGP11.phx.gbl...
> Yes, it is from BootVis.
>
> I had the same problem. You should have shut down tracking before removing
> the program. Install the program again. deactivate everything. Reboot to
> make certain that it is not tracking. Then, shut down and delete the program
>
Haha! I know what you meant, but at first read when I saw
> Then, shut down and delete the program
I thought, how the heck is he gonna delete anything if the PC is shut down?
:)
Steve
Now, after reading about the issue, I actually don't want to turn event
tracing OFF, as you suggest. Instead, I'd like to go on tracing events with
the help of Norton System Doctor, but I'd like to set a time to flush the
buffers. Now, my Registry entries as follows:
...........................................................................
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\GlobalLogger]
"Start"=dword:00000001
"EnableKernelFlags"=hex:07,23,00,00,16,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,17,23,00,00
"BufferSize"=dword:00000040
"MinimumBuffers"=dword:0000001e
"MaximumBuffers"=dword:00000078
"ClockType"=dword:00000001
.............................................................................
If I set a smaller value for MaximumBuffers, it will stop tracing (so it
says) when the buffers are full, and this I don't want to happen.
What I'd like to do is to add a new Value as follows (according to MS
instructions it should be present in the default Key, but it is not):
"FlushTimer"=DWORD (Time delay in seconds before dirty buffers are scheduled
to be flushed).*
Now my quest, please:
What should be the exact syntax for the data string, if I want to set it to,
say, 3,000 seconds?
I'd highly appreciate an answer,
TIA,
haim
=====================================================================
"Dave Patrick" <ma...@Nospam.DSPatrick.com> wrote in message
news:%23hSico4...@TK2MSFTNGP11.phx.gbl...
> You might try setting the Reg_Dword 'Start' to zero
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/perfmon/base/global_logger_session.asp
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Haim Guivon" wrote:
> | The file \system32\logfiles\WMI\trace.log grows bigger until it eats up
> all
> | the free disk space (almost 4 GB)
......
TIA,
haim
Thanks,
haim
============================================================
"Carey Frisch [MVP]" <cnfr...@nospamgmail.com> wrote in message
news:uX2ikr4t...@TK2MSFTNGP14.phx.gbl...
> To define trace log buffers
> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/nt_smlogcfg_tracebuffer.mspx
>
> Inflated TRACE.LOG problem, how to fix.
> http://www.tweakxp.com/tweak1302.aspx
>
> --
> Carey Frisch
> Microsoft MVP
> Windows XP - Shell/User
>
> Be Smart! Protect Your PC!
> http://www.microsoft.com/athome/security/protect/default.aspx
>
> ---------------------------------------------------------------------------------
>
> "Haim Guivon" wrote:
>
> | The file \system32\logfiles\WMI\trace.log grows bigger until it eats up
> all
> | the free disk space (almost 4 GB)
> |
IOU, and also to Carey and Kelly for all the wise advises. I have a good
idea now of how the thing works.
BTW, I think that Norton System Doctor uses MS global_logger, and when
enabled it changes the Start Dword to 1. But when one removes NSD, the Dword
stays ON (1), and this was the cause of the continuous growth of the log
file. Well, I think....
Thanx to all of you,
haim
========================================================
"Dave Patrick" <ma...@Nospam.DSPatrick.com> wrote in message
news:%23hSico4...@TK2MSFTNGP11.phx.gbl...