S
squishy
I am running Vista Ultimate 32 bit edition, and noticed that I did not have
as much hard drive space as I thought I should.
Upon further investigation, I found 2 HUGE files.
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\SystemIndex.Crwl344.gthr
which is 20,511,977,472 bytes
and
C:\Users\All
Users\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\SystemIndex.Crwl344.gthr
which is also 20,511,977,472 bytes.
What is a "gthr" file? Why is it so damned big? Why is it duplicated on my
drive? How can I eliminate it - or at least reduce it's size?
It seems like it has to do with the indexer/search function (which I have
found to be woefully inadequate). But, Google has a desktop search that is
not even close to this space hog's footprint. So why does Bill want such a
huge chuck out of my hard drive?
And why is the indexing so inefficient? Sometimes my Vista PC seems to hang
up (3GB RAM, 2.0Ghz AMD 64 bit proc) and I find it is the IndexSearcher
hosing my PC. All user files should be indexed immediately after any write
process AND the file is released by whatever wrote to it. NOD32 does
something like this when scanning files for viruses and it works great -
real-time protection.
How about a little real-time scanning (but with a lower priority than what I
am doing please).
squishy
as much hard drive space as I thought I should.
Upon further investigation, I found 2 HUGE files.
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\SystemIndex.Crwl344.gthr
which is 20,511,977,472 bytes
and
C:\Users\All
Users\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\SystemIndex.Crwl344.gthr
which is also 20,511,977,472 bytes.
What is a "gthr" file? Why is it so damned big? Why is it duplicated on my
drive? How can I eliminate it - or at least reduce it's size?
It seems like it has to do with the indexer/search function (which I have
found to be woefully inadequate). But, Google has a desktop search that is
not even close to this space hog's footprint. So why does Bill want such a
huge chuck out of my hard drive?
And why is the indexing so inefficient? Sometimes my Vista PC seems to hang
up (3GB RAM, 2.0Ghz AMD 64 bit proc) and I find it is the IndexSearcher
hosing my PC. All user files should be indexed immediately after any write
process AND the file is released by whatever wrote to it. NOD32 does
something like this when scanning files for viruses and it works great -
real-time protection.
How about a little real-time scanning (but with a lower priority than what I
am doing please).
squishy