View Single Post
  #4  
Old March 19th 19, 09:15 PM posted to microsoft.public.windowsxp.general
Bill in Co[_3_]
external usenet poster
 
Posts: 303
Default Another XP Search question

Paul wrote:
James Davis wrote:
Sounds like Shady-Activity ;-D

Check your Indexing Options (in Control Panel).

Remove everything it wants to search; then stop/disable it (stops
forever). Then use a better finder like Search "Everything" or something
else.

[Advice applies to Windows 7; it may not apply to Windows XP.]


There is no particular reason that Everything.exe would
not do the same thing.

The WinXP search code is re-triggered by file system
activity. For example, for sure, if you empty the Recycle Bin,
that causes the built-in search to regenerate a result.

Everything.exe is triggered by the USN journal, so at least
the index updating code is going to trigger, if the file
system state changes. Any process which changes a file date
once a second, could cause a tiny piece of Everything.exe
code to run.

Only Agent Ransack would be quiet after a search runs.
But the actual searches with that, are expensive.

*******

If you "dump" the USN Journal as a text file (fsutil?), you can
go through the results and see what events have
happened recently.


But again, this is just for NTFS volumes, as I understand it. If you've got
any FAT32 partitions, this does not apply. But, as I understand it, you can
have Everything check for changes, but you have to specify that, explicitly,
or it won't happen (like on a scheduled basis of every xx hours).

None of this is an issue with Agent Ransack or FileLocator Pro, but
admitedly, you do have to wait for the results. :-) But at least with the
latter, you can exclude a lot of useless directories in the searches, which
greatly speeds things up, and, of course, there are no indexing issues to
deal with, particularly with FAT32 volumes (which might not get indexed
frequently enough to be accurate).


Ads