Tech Support Forums - TechIMO.com - View Single Post

alligator_al · July 24th, 2002, 02:15 PM

I came to the same conclusion as bjfontai. The culprit seems to be the Global Logger Session, and is documented at:

http://msdn.microsoft.com/library/de...about_2lny.asp

and the relevant registry key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WMI
Start REG_DWORD 0 = Off

It doesn't mention anything about colossal file sizes though. I suppose it must be logging the wrong things in some cases (even my keyboard entry was slower when it was logging)

This does the trick better than the temporary 'tracelog -x' fix.
Just out of interest, I also had a 'security' group under WMI in the registry, which looks suspect. I run Norton AV and Sygate personal firewall. I wonder if there's a conflict there?

(always remember to backup your registry first, kids ;-)

July 24th, 2002, 02:15 PM	#32 (permalink)
alligator_al Member Join Date: Jul 2002 Location: London, England Posts: 100	I came to the same conclusion as bjfontai. The culprit seems to be the Global Logger Session, and is documented at: http://msdn.microsoft.com/library/de...about_2lny.asp and the relevant registry key is: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WMI Start REG_DWORD 0 = Off It doesn't mention anything about colossal file sizes though. I suppose it must be logging the wrong things in some cases (even my keyboard entry was slower when it was logging) This does the trick better than the temporary 'tracelog -x' fix. Just out of interest, I also had a 'security' group under WMI in the registry, which looks suspect. I run Norton AV and Sygate personal firewall. I wonder if there's a conflict there? (always remember to backup your registry first, kids ;-)