Avoid wrong message at start of Everything.exe

[jb]

When the user enables the checkbox `Everything` in the `Find Files` dialog
and TC is running as normal user (not as administrator)
and Everything.exe is not running at all (but is installed and configured correctly)
then TC pops up a wrong message box telling:

`Everthing` is a search tool ...
`Everthing` isn't installed! Do you want to download it now?

I think this happens because TC depends on a timeout for the start of Everything.exe and this timeout is currently too short.

[Horst.Epp]

When the user enables the checkbox `Everything` in the `Find Files` dialog
and TC is running as normal user (not as administrator)
and Everything.exe is not running at all (but is installed and configured correctly)
then TC pops up a wrong message box telling:

`Everthing` is a search tool ...
`Everthing` isn't installed! Do you want to download it now?

I think this happens because TC depends on a timeout for the start of Everything.exe and this timeout is currently too short.

Running Everything this way is wasting time.
Without running in the background there are unnecessary delays for updating the index.
Installing the serviice and running in the background provides the best results with almost no delays.

[tuska]

Original notifications

1. 'Everything' is a search tool and search index for the NTFS file
   system.
   
   'Everything' isnt installed! Do you want to download it now?
    ⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
2. 'Everything' ist ein Suchprogramm und Suchindex für das
   NTFS-Dateisystem.
   
   'Everything' ist nicht installiert! Möchten Sie es jetzt herunterladen?

Suggestion

1. 'Everything' is a search tool with a search index.
   
   Start 'Everything' to perform a search query with this
   parameter.
   
   'Everything' is not installed? Do you want to download it now?
    ⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺
2. 'Everything' ist ein Suchprogramm mit Suchindex.
   
   Starten Sie 'Everything' um eine Suchanfrage mit diesem
   Parameter durchzuführen.
   
   'Everything' ist nicht installiert? Möchten Sie es jetzt herunterladen?

A connection from TC to 'Everything' can only be established via the parameters ed: or ev: (... "search query with this parameter"...).
There is not only a search index for the NTFS file system (Folder indexing, etc.).

[Horst.Epp]

A connection from TC to 'Everything' can only be established via the parameters ed: or ev: (... "search query with this parameter"...).

A connection is also made if you search for files and have enabled Everything.

[tuska]

A connection from TC to 'Everything' can only be established via the parameters ed: or ev: (... "search query with this parameter"...).

A connection is also made if you search for files and have enabled Everything.

Yes, thank you, I had overlooked that.

If 'Everything' is checked - without prefix ed: or ev: - then the search criteria of TC (with the support of 'Everything') apply,
i.e. you still get the search result much faster than if 'Everything' is not checked.

But the message always appears only when you use ed: or ev: for a search query and Everything has NOT been started.
... [and e.g. Everything=C:\Everything\Everything64.exe -startup is not present in the "wincmd.ini" file in the [Configuration] section] ...

[jb]

Running Everything this way is wasting time.
...

There is only a delay for the first search operation with Everything. My general policy is to start things when I need them, not in advance.

[Horst.Epp]

Running Everything this way is wasting time.
...

There is only a delay for the first search operation with Everything. My general policy is to start things when I need them, not in advance.

The problem is, that the client is responsible for updating the index.
Not the service !
So on starting the client it has to make all necessary database updates
including properties or content indexing.

[jb]

The problem is, that the client is responsible for updating the index.
Not the service !

What is the client supposed to do for updating the index apart from starting Everything.exe?

So on starting the client it has to make all necessary database updates
including properties or content indexing.

Sure, this results in a delay for the first search operation with Everything, as I already mentioned above.
Are you assuming that I terminate Everthing after each search?

[NotNull]

What is the client supposed to do for updating the index apart from starting Everything.exe?

The heavy lifting.
The Everything Service is needed to access the Master File Table (MFT) and USN HJournal on NTFS volumes. These are the "address-book" and "change log" for files and folders. On Windows, these are only accessible using elevated rights.
So the Everything client asks the Everything Servive -- which has elevated rights -- "Go fetch USN journal" (for example). Service passes this on to the client, which processses that data and puts it in the database (or removes or ...).



But this is all sidetracking from the original issue:

nd Everything.exe is not running at all (but is installed and configured correctly)
then TC pops up a wrong message box telling:

`Everthing` is a search tool ...
`Everthing` isn't installed! Do you want to download it now?

I think this happens because TC depends on a timeout for the start of Everything.exe and this timeout is currently too short.

That could be prevented in TC by checking if database is fully loaded by calling Everything_IsDBLoaded or directly through EVERYTHING_IPC_IS_DB_LOADED.
(when re-indexing, it does not have the loaded state)


Might be useful too: EVERYTHING_IPC_IS_DB_BUSY.