I believe Josephur is correct. The
SFC command log file function is built on the same model used by Windows for generating Crash Dumps (mini-dumps), and most of the Event Viewer log files such as System log, Application log, and Security log also work the same way. Microsoft wants to give you results of the logs, but doesn't let you manipulate them (unless you use a non-Microsoft 3rd party app), nor the generation behavior such as how to produce the log, or where it can be stored on your C: drive, or other drive location. They are not overly concerned about filling up your hard drive with these, as computers used by power-users and businesses rarely cause the free space of almost any hard drive to be consumed by these rather large files. But, since they are only text files, thousands of entries in each log only take up a few KB, or MB. Unless, you are running your hard drive at 98% or 99% used space of capacity this would almost never happen. At least on a well-maintained computer. If you are running only 1%-2% free space on any windows computer of any version; it would have crashed usually long before you can try to fix a problem from log files sucking up any remaining space you might have.
You might google the forums and see if there are some freeware utilities out there that can help you. Like I said I think I've run across a few; don't remember their names. Also, this is the sort of thing that Microsoft encourages, which is having programmers find a niche for some not-often used tool not included with Windows to provide additional functionality, just because they wanted it for themselves and decided to share it, and in some cases expand on it and make some money.
<<BIGBEARJEDI>>
