About everyrthing.exe process

[yemanqitipo]

everything version: 1.4.1.1005 (x64)
I have two Machines. Both of them are windows 10.
When I double click everything.exe to run it, On one of my Machines there is only one everything.exe process, but the other there are two.
so what make that difference.

[void]

There should be two processes.

One for the Everything Service and one for the Everything Search client.

Please make sure Everything is installed correctly and running as a standard user:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Check Store settings and data in %APPDATA%\Everything.
• Uncheck Run as administrator.
• Check Everything Service. (Please make sure this is tick-checked and not square-checked)
• Click OK.
• Exit Everything (right click the Everything tray icon and click Exit).
• Restart Everything.

[ChrisGreaves]

There should be two processes.

Install_06.png (116.47 KiB) Viewed 2680 times

I voted myself the rawest recruit in my office, purged all copies of Everything (RevoUninstaller and Control Panel/Programs and features), downloaded and ran the Everything-1.4.1.1022.x64-Setup.exe.

The image above shows (top row) that under windows 7 there appears to be but the one process and (bottom row) after quitting and restarting Everything.exe, the Tools, Options, General settings appear to conform to your suggestion.

I think that I have misunderstood something somewhere.

I am running Everything from the desktop shortcut created by the Installer.

(signed) "Puzzled" of Bonavista

[therube]

See if you don't see the other "Everything" in the Services (tab).
(Most like using only few MB of RAM. [I have no idea what Task Manager may or may not show?])

One item is the Process, the second item is the Service.

[ChrisGreaves]

See if you don't see the other "Everything" in the Services (tab).

Install_07.png (45.45 KiB) Viewed 2669 times

TheRube, thank you for this prompt response.
So perhaps the "Two Everythings" rule applies to Win10 and Win 11, but under Win7 one should look for "Three Everythings".

I did do a novice/naive install accepting every installation default, so I have confidence that it did install correctly for novices like me.
I was puzzled as to why that default did not show Two copies; I am now unused to Win7!
Cheers, Chris

[therube]

What Windows (Windows Explorer) calls Applications is the same as what shows in Processes.
So two, Win7 or not (is the "norm").


But then, why not have more?
The more the merrier .

Everything Win7 6 Processes 5 Services.png (17.35 KiB) Viewed 2666 times

And there are times when a "program" may crash, so will no longer show under (WE) "Applications", yet the "program" has hung in memory, so will still show in (WE) as a "Process".

[ChrisGreaves]

There should be two processes.
One for the Everything Service and one for the Everything Search client.

Hello David. I think I understand this.
There is a program developed by you that maintains a watch on my Windows file system, and uses that incoming data to maintain a database of file data - names, date modified, size and so on. That's rather like an office clerk maintaining a bank of filing cabinets with hanging folders, manilla folders, documents.

There is a second program developed by you that specializes in obtaining data from this database and presenting it in a digestible format to humans like me.

The office parallel is that a "manager" like me can ask the office database clerk to hand me data related to a specific set of files such as "All my workbook files". I do this by asking the second program for "*.XLS", and the second program analyzes my request and communicates it to the first program which delivers the data for the second program to lay out in a readable fashion. This second program also handles my subsequent request to "sort in ascending sequence" or "eliminate workbooks older than a year".

The clerk that maintains the database/filing cabinets is what you call "the Everything Service" and the manager (me!) is "the Everything Client".

It would then follow that Everything Service can be thought of as an Engine which can be used to power many different applications. If I came up with an idea for an application that could make use of ultra-fast retrieval of file data, then the one Everything Service would be the engine for both your application and mine.
Indeed several applications could make use of the Everything Service engine without needing to be bothered about USN Journals, Drives, Folders etc.

Am I close to the truth?
Thanks, Chris

[void]

You may need to click Show processes from all users to see the Everything Service Everything.exe process:




I like your analogy.

It's worth mentioning though:
The Everything Service is really dumb and stateless.
The Everything Service doesn't update your Everything index directly.
The main Everything Search Client maintains your index.

The Everything Service can do the following two things:
1). Provide a copy of a full index of a specific volume to the Everything Search Client.
2). Provide a copy of the USN Journal on a specific volume to the Everything Search Client.

These are low level features.
This makes the Everything Service useless for other applications.

[ChrisGreaves]

But then, why not have more? The more the merrier .
(snip!)
And there are times when a "program" may crash, so will no longer show under (WE) "Applications", yet the "program" has hung in memory, so will still show in (WE) as a "Process".

Hello therube; apologies for my tardy reply.
I agree that there are times when we may well have more than two instances of Everything. After all, we are dealing with Windows, right? Anything will happen!
But specifically in the sense of a brand-new installation or a flushed-clean re-installation, I understood earlier comments to mean that I should see (Catch-22 alert!) two of Everything.
I learn a lot by feedback from taking what I think I have learned and re-phrasing it.
Now, off to disagree with David on the same issue (grin!)
Thanks again, Chris

[ChrisGreaves]

The Everything Service is really dumb and stateless.
(snip!)
This makes the Everything Service useless for other applications.

David, you know how much I hate disagreeing with you but:-
The Everything Service may appear really dumb and stateless to every one and every thing except The main Everything Search Client, but without the Service, surely the Client can not function?
The main Everything Search Client is the critical user interface with the Windows File System via The Everything Service, is it not?

It ought not to be beyond my imagination to devise a brand-new application that can make very good use of material that is made available by The Everything Service. And if I were to devise such an application, then wouldn't that make The Everything Service a general-purpose engine?

My background is that many years ago I wrote an Interesting Words engine; it can locate interesting words in any text in any language. Pretty smart engine! The showroom floor for the engine is a one-click indexer that produces an index in seconds (not minutes); but once you can collect Interesting Words from any chunk of text, you can write a better Precis writer than the MSWord version, locate where in a stream of paragraphs of text Headings should go, and at which level, and even generate the Heading text, Blaze trails through a forest of words, and so on. Multiple applications using the one engine.
Cheers, Chris

[void]

The Everything Service is really dumb

I meant this as the Everything Service is really simple.
The Everything Service doesn't try to be "smart".
The Everything Service avoids doing any processing on any data.

For example:
The Everything Search Client asks the Everything Service, Can I have an index of the C: drive? the Everything Service replies with: Sure, here's a copy of all the filenames on the C: drive.
The Everything Search Client asks the Everything Service, Can I have a list of changes on the C: drive since x? the Everything Service replies with: Sure, here's a copy of all the filename changes on the C: drive since x.

The Everything Service may appear really dumb and stateless to every one and every thing except The main Everything Search Client, but without the Service, surely the Client can not function?

The Everything Search Client will need the Everything Service to index and monitor your main C: drive.
Without the Everything Service this would not be possible with running the Everything Search Client as a standard user.

The main Everything Search Client is the critical user interface with the Windows File System via The Everything Service, is it not?

I'm not sure about calling it critical.
The Everything Search Client is the only user interface to the Everything Service.

It ought not to be beyond my imagination to devise a brand-new application that can make very good use of material that is made available by The Everything Service. And if I were to devise such an application, then wouldn't that make The Everything Service a general-purpose engine?

Maybe in the future.
For now, the Everything Service is designed to only be used by the Everything Search Client.