Thanks for the suggestion Billy - alas no go - details follow for the
edification of all
Billy said:
My guess would be that the indexing program has been corrupted, and it
needs
to rebuild the indexing files. Here is the procedure that I would use to
do
that.
Hmmm... I thought a corrupt index might be possible... but the program?
Anyway, adjusting slightly for differences seen over the description
(Vista:
double-click service or otherwise get its properties... service type is no
longer a direct drop down in the list)
I did this -
<snip> = Disable Windows Search service, reboot, reset Windows Search to
automatic, reboot
No change... and it should be noted that before trying this I had
completely
rebuilt the indexes (Indexing Options, Advanced). IMO disabling and
re-enabling the Search service should not affect the status of the indexes
themselves - and later examination after the final restart showed that the
count of indexed items was >50,000 in a time too short to have indexed
that
many files, so I the hypothesis is not falsified.
I think there is a bug in Windows Search or a bug in Windows Indexing -
though having said that, as I noted, someone said that a "game" search
worked
for them (I would be interested to hear of other experiences - I find it
difficult to see how an otherwise functional indexing/search system could
fail like this without a bug - so I now begin to doubt the positive
report).
For further info, it seems (although I can find no information on this in
Help) that Indexing does not index Removable media.
Not indexing removable media is I think a very poor decision, which if it
is
true. is exacerbated by the fact that there is no warning or advice when
adding specific locations to be indexed that the new locations will be
ignored! [I'll raise a new topic on this]
[I use Steganos encrypted safes for certain data - the media isn't
actually
ever "removed" it just appears like that]
Indexes for R/W media could be stored on the media - and if something has
disappeared surely it's a microsecond to check the file name the index
throws
up against a directory?
Almost everything I try in Vista is at least very slightly not-quite
right -
and the aggravation is increasingly disproportionate.