Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trace.log file growing in size 1

Status
Not open for further replies.

olderrocker

Technical User
Aug 19, 2003
38
GB
Hello

My son reported last night that his IBM desktop has a problem with the c:\windows\system32\log files\WMI\trace.log file swallowing up most of the C drivespace after a time. Error reports that the C-drive is full but after a reboot, the space is returned and the 'trace.log' size is reduced. He told me that this problem has existed since he got the machine.
Machine is running XPHome with 1G of RAM
I don't know much about the function or necessity of this file as I can't find it on my work laptop and I don't know if it can safely be removed, so any help greatly appreciated - thanks
 
draiGoch,

A star. A better choice than using bootvis.exe is shown in faq779-4518

I am curious if this is a case of pilot error, or whoever built the machine screwed up. Bootvis was essentially a driver tool to test the effects of different driver versions and is an unsupported utility for end users. This demonstrates one reason. The other is that when Intel introduced the P4 processor the timing results returned by Bootvis.exe had little to do with reality.



 
Problem now solved lads - thanks draigGoch for your expert reply and thanks bcaster for you valuable input
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top