Another XP Search question
 

Never solved this one.

Say I'm searching for *.xor on all drives.

It takes a while, and when it's done it waits a 10-15 seconds and
starts searching again.

If I press "stop" it restarts the search a few seconds later. It won't
accept "stop". Ruddy rapist.

Indexing disabled.

Is there a reg fix to make it search just the once ?

I'm aware that programs and services are running in the background and
probably writing new files, so it might detect the media (the HD) has
changed content.
TIA
[]'s

--
Don't be evil - Google 2004
We have a new policy - Google 2012
Nineteen Eighty-Four was a work of FICTION !!!! - Orwell

Another XP Search question
 

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.]

Another XP Search question
 

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.

You can also use Process Monitor from Sysinternals,
to study all the ReadFile, WriteFile, CreateFile events.
CreateFile, for example, includes stat() and isn't necessarily
the creation of a file. Just checking the size of a
file might cause a CreateFile event while opening the
path. If there is repetitive activity on the computer,
you can likely catch it.

Process Monitor logs to RAM... unless you configure it
to write to the file system, in which case there could
be some "pollution" in the results. But by default it
uses RAM for this, and should not aggravate things
while you are collecting a trace. In the File menu,
removing the tick mark, stops the tracing and you can
then study the results in peace.

Paul

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).

Another XP Search question
 

On Fri, 15 Mar 2019 15:08:34 -0300, Shadow wrote:

Never solved this one.

Say I'm searching for *.xor on all drives.

It takes a while, and when it's done it waits a 10-15 seconds and
starts searching again.

If I press "stop" it restarts the search a few seconds later. It won't
accept "stop". Ruddy rapist.

Indexing disabled.

Is there a reg fix to make it search just the once ?

I'm aware that programs and services are running in the background and
probably writing new files, so it might detect the media (the HD) has
changed content.
TIA

I have never had that problem. It searches once and stops. Period.
Dont matter if I am searching for dog, *.mp3, or anything else.

I do wish there was a more user friendly search program that I could
download though. I never was very fond of the built in one. I liked the
one in Windows 98 much better.

Another XP Search question
 

Average Person wrote:
On Fri, 15 Mar 2019 15:08:34 -0300, Shadow wrote:

Never solved this one.

Say I'm searching for *.xor on all drives.

It takes a while, and when it's done it waits a 10-15 seconds and
starts searching again.

If I press "stop" it restarts the search a few seconds later. It won't
accept "stop". Ruddy rapist.

Indexing disabled.

Is there a reg fix to make it search just the once ?

I'm aware that programs and services are running in the background and
probably writing new files, so it might detect the media (the HD) has
changed content.
TIA

I have never had that problem. It searches once and stops. Period.
Dont matter if I am searching for dog, *.mp3, or anything else.

I do wish there was a more user friendly search program that I could
download though. I never was very fond of the built in one. I liked the
one in Windows 98 much better.

User friendly = Agent Ransack.

Another XP Search question
 

In message , Bill in Co
writes:
Average Person wrote:
On Fri, 15 Mar 2019 15:08:34 -0300, Shadow wrote:

Never solved this one.

Say I'm searching for *.xor on all drives.

It takes a while, and when it's done it waits a 10-15 seconds and
starts searching again.

If I press "stop" it restarts the search a few seconds later. It won't
accept "stop". Ruddy rapist.

Indexing disabled.

Is there a reg fix to make it search just the once ?

I'm aware that programs and services are running in the background and
probably writing new files, so it might detect the media (the HD) has
changed content.
TIA

I have never had that problem. It searches once and stops. Period.
Dont matter if I am searching for dog, *.mp3, or anything else.

I do wish there was a more user friendly search program that I could
download though. I never was very fond of the built in one. I liked the
one in Windows 98 much better.

User friendly = Agent Ransack.


And even more so if you're just looking for filenames, Everything.
(Which can apparently search content too - I just don't know how it
compares with AR on user-friendliness. But it's certainly user-friendly
for its default function.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

I remember a lot of questions on a vocalist forum about the problems singing
"There is a balm in Gilead" without making it sound like a security alert. -
Linda Fox in UMRA, 2010-11-19

Another XP Search question
 

On Tue, 19 Mar 2019 18:17:23 -0500, Average Person
wrote:

On Fri, 15 Mar 2019 15:08:34 -0300, Shadow wrote:

Never solved this one.

Say I'm searching for *.xor on all drives.

It takes a while, and when it's done it waits a 10-15 seconds and
starts searching again.

If I press "stop" it restarts the search a few seconds later. It won't
accept "stop". Ruddy rapist.

Indexing disabled.

Is there a reg fix to make it search just the once ?

I'm aware that programs and services are running in the background and
probably writing new files, so it might detect the media (the HD) has
changed content.
TIA

I have never had that problem. It searches once and stops. Period.
Dont matter if I am searching for dog, *.mp3, or anything else.

I remember mine did too. I must have messed with something in
the registry.
When I changed a DVD, the title didn't change in "my
computer". Annoying. I "fixed" that, and now it updates.
Can't remember what it was I changed, but might have something
to do with the search updating automatically.

PS I have indexing and USN disabled. Though something insists
on turning journaling on once or twice a week ....

Batch
fsutil usn queryjournal c:
.......
fsutil usn queryjournal z:

sleep 3

If it's on I run another batch and delete and disable it.


I do wish there was a more user friendly search program that I could
download though. I never was very fond of the built in one. I liked the
one in Windows 98 much better.

Yes, that used to work ...

I currently use "Index Your Files". It has the advantage of
allowing me to search inside any file, but the disadvantage of
building an index.

Almost half a million files. Search for "dog" inside "*.exe"
files. 1236 files contain the string "dog". Took 2 minutes 45 seconds.
Didn't use USN. Clicking on any file on the list takes me instantly to
the place(s) that contains "dog".
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012
Nineteen Eighty-Four was a work of FICTION !!!! - Orwell