UseEverythingInstance and Everything options [SOLVED]

[petermad]

2cmd4ever

drop the Everything portable files in a folder, Run Everything.exe once. Do nothing and close it.

If I do that I get an new ini file of 20k bytes with 740 lines.

I have copied the lines you refer to earlier from my test TC instance - they are:

Code: Select all

hide_empty_search_results=0
auto_include_fixed_volumes=0 (1)
rename_select_filepart_only=0
date_descending_first=0
size_descending_first=0
index_folder_size=1 (0)
sort=run count
sort_ascending=0
ntfs_volume_includes=0,0,0 (1,1,1)
folders="C:\\Windows" ()
folder_monitor_changes=1
folder_buffer_size_list=65536
folder_rescan_if_full_list=0
folder_update_types=2
folder_update_days=0
folder_update_ats=3
folder_update_intervals=6
folder_update_interval_types=1

So even less tweaked than yours.

Do you only have those 18 lines in your everything.ini ?

[cmd4ever]

2cmd4ever
I can fully confirm what petermad said in his last response.
Something is wrong with you're Everything configuration.
Install the service and run it not as admin as suggested.

"Install the service and run it not as admin as suggested."
it's not a suggestion, it appears to be a mandatory TC condition. Unfortunately it doesn't suit my needs.

Also what's wrong with my configuration? As far as I know, the only two parameters that differs from a virgin portable everything.ini are:
=-> my value, =() default value
ntfs_volume_includes=0 (1)
folders="C:\\Windows" ()

My long time pairing of Servant Salamander and Everything works like a breeze as two independent and complementary tools with no additional
constraints. When I bought TC and saw there was some sort of integration with Everything. I thought it as an unexpected additional value.
So I gave it a shot. I lose so much of Everything value by doing so, that I rather keep them separate.

Thanks everyone for trying to be helpful.

My take away:
TC is not able to communicate with an -Instance if it was not running prior to TC.
No community interest (except for 2AntonyD, thank you pal for your support) in fixing the incoherent TC behavior in the GUI when it comes to deal with EV: and [ ]Everything check boxes (both in options and ALT-F7)

Don't worry my dear Everything. You still worth every free pennies I paid for you as a standalone tool.

My TC paid licenses still got some appeal. And dear TC community, I suspect we will talk again, because when I adopt a tool. Unlike most of the users (I was even told here, why can I not be just like most users) who use it blindly with the bare minimum tweaks. I get deep in every single of their options and features to understand what they do and how they could help me to squeeze the maximum out of them. If the Everything integration was a glimpse how TC works, then I'm bound to find more interesting things to talk about in the bug report.

[tuska]

The question remaining. Why TC can't use my instance when launched by TC itself.

Starting point

does Total EXACTLY know how to call this utility

Yes, calling everything is done like this:
1. Find a window where the class is named "EVERYTHING_TASKBAR_NOTIFICATION",
   or when UseEverythingInstance is set, look for a class named "EVERYTHING_TASKBAR_NOTIFICATION_(instance name)"
2. Send WM_USER messages to that window with specific requests, and wait for the reply.

Settings - 2 Everything 1.4 instances

Code: Select all

TWO Everything instances available!
Neither Everything 1.4 nor TC 11.57 was launched as an administrator.

Everything Service: "Everything" running -> Unnamed instance ==  my main instance ---- Task Manager > Processes: 1.7 MB
Everything Service: "Everything (TC)" running -> Named instance (my second instance) - Task Manager > Processes: 1.4 MB

Button in TC with command: C:\Everything\Everything_1.4\everything.exe
Button in TC with command: C:\Everything\Everything_1.4\TC\everything.exe -instance "TC" -startup

C:\Everything\Everything_1.4\Everything.ini
C:\Everything\Everything_1.4\TC\Everything-TC.ini

Options > Everything      - 1.4.1.1032 -> Indexes > Folders: C:\totalcmd\Tests\
Options > Everything (TC) - 1.4.1.1032 -> Indexes > Folders: C:\Testfolder\

wincmd.ini - [Configuration]
Everything=C:\Everything\Everything_1.4\TC\everything.exe -instance TC
UseEverythingInstance=TC

Example 1:
- Total Commander is running -> ‘Everything’
- The two Everything instances, “Everything” and “Everything (TC)”, are running -> 2 icons in the system tray
- wincmd.ini [Configuration] UseEverything=1
- Search query in TC: ev: start
- Search result: C:\Testfolder\ -> Everything (TC) -> OK!

Example 2:
- Close the “Everything (TC)” instance, so that only the unnamed “Everything” instance remains open
- wincmd.ini [Configuration] UseEverything=1
- Restart TC with the command: cm_exit 9
- Total Commander has started -> ☐ ‘Everything’ <-- Everything is UNCHECKED because the “Everything (TC)” instance is closed
- Search query in TC: ev: start (click the “Start search” button)...
- The “Everything (TC)” instance was started in the background due to this search query in TC,
  based on this setting:
  wincmd.ini [Configuration] Everything=C:\Everything\Everything_1.4\TC\everything.exe -instance TC
  and the Everything option was checked -> ‘Everything’
- Search result: C:\Testfolder\ -> Everything (TC) -> OK!

Example 3:
- Close both Everything instances, “Everything” and “Everything (TC)”, meaning there are now NO Everything instances open
- Restart TC with the command: cm_exit 9
- wincmd.ini [Configuration] UseEverything=1
- Total Commander has started -> ☐ ‘Everything’ <-- Everything is UNCHECKED because the “Everything (TC)” instance is closed
- Search query in TC: ev: start (click the “Start search” button)...
- The “Everything (TC)” instance was started in the background due to this search query in TC,
  based on this setting:
  wincmd.ini [Configuration] Everything=C:\Everything\Everything_1.4\TC\everything.exe -instance TC
  and the Everything option was checked -> ‘Everything’
- Search result: C:\Testfolder\ -> Everything (TC) -> OK!

I'm again happy with the test results!
Those results were exactly what I expected!

In other words, if a parameterization is set up for a specific Everything [sub]instance in Total Commander,
and a search query is then performed in Total Commander using the TC parameters ed: or ev:,
only files and/or folders from folders or drives indexed in Everything appear in the TC search results.

It should work the same way in Everything 1.5 - though I haven't tested it.

In Everything 1.5, the option “Run indexing process as administrator (recommended)”
is suggested during installation if a portable version is being used:
Run indexing process as administrator

Typing the command `root: ...` directly into Everything shows which drives or folders are indexed in Everything.

I hope that answers your question, because my tests have shown that the expected results can be achieved,
and unfortunately I can't offer any further insight on this topic.

EDIT:
Added: Everything 1.5 - Run indexing process as administrator

[OT]My next task: Uninstall all instances of Everything 1.4 and revert to the latest 1.5 version.[/OT]

[cmd4ever]

2cmd4ever

drop the Everything portable files in a folder, Run Everything.exe once. Do nothing and close it.

If I do that I get an new ini file of 20k bytes with 740 lines.

I have copied the lines you refer to earlier from my test TC instance - they are:

Code: Select all

hide_empty_search_results=0
auto_include_fixed_volumes=0 (1)
rename_select_filepart_only=0
date_descending_first=0
size_descending_first=0
index_folder_size=1 (0)
sort=run count
sort_ascending=0
ntfs_volume_includes=0,0,0 (1,1,1)
folders="C:\\Windows" ()
folder_monitor_changes=1
folder_buffer_size_list=65536
folder_rescan_if_full_list=0
folder_update_types=2
folder_update_days=0
folder_update_ats=3
folder_update_intervals=6
folder_update_interval_types=1

So even less tweaked than yours.

Do you only have those 18 lines in your everything.ini ?

Yes 20k file and yes. Do you know what I meant by DIFF? I ran a differential line analysis between my ini file and the virgin ini file.
The line I gave were the only lines different from the virgin file (apart from windows positions). If you only compare my 18 lines with your 18 lines test ini file then how can you be sure you do not have other tweaks in your test files?

The real test is like I said. You have to run a differential analysis from the 20k virgin and your test file. Do you want me to suggest tools for that?

Also I'm not sure how to read your 18. eg: ntfs_volume_includes=0,0,0 (1,1,1). Is your custom ini is set to 0's or 1's?

[cmd4ever]

The tests I refer to here viewtopic.php?p=483715#p483715 was made with Everything NOT installed as service (as I usually do), and with Everything running as administrator (1.4) and running indexing process as administrator (1,5a)

Windows 10 and 7, UAC is standard setting.

Thank you and perfect. We are not running the same OS.
That could explain a lot. Windows 11 has a stronger memory/process isolation than 10. Which could explain some of the differences amongst our results.

I have a Windows 10 VM I can test with. I suspect I will end up with the same results as yours (unless there are other differences between your OS and TC configuration). Because I cannot run a leaner Everything.ini file than what I have to test with.

Protocol is so simple.
drop the Everything portable files in a folder. Run it, close it.
Change in the virgin Everything.ini those two parameters

folders="C:\\Windows"
and
ntfs_volume_includes=0

Rename rename it to everything-test.ini
In Wincmd.ini
Everything= exepath\Everything.exe -instance test -startup
UseEverythingInstance=test

Have fun.
On Windows 11, ALT-F7 will give c:\windows\ tree only if enter EV: AND if the Instance was already running prior to launch TC.

[AntonyD]

It seems, guys, that you have done quite enough for testing purposes - now all that's left is to wait for Mr. Ghisler's answers
to all the questions posed and the inconvenient situations that were revealed during the tests.
We've set the main goal for reflection with our tests and a post-analysis of their results.
Huge thanks to all the participants))

[petermad]

Yes 20k file and yes. Do you know what I meant by DIFF?

Sorry I didn't notice that what was you meant.

Here is the differencies for the TC -instance that I tested with for v 1.4 and a fresh ini file:

Code: Select all

auto_include_fixed_volumes=0
last_options_page=15
exclude_list_enabled=0
index_date_created=1
index_folder_size=1
ntfs_volume_includes=0,0,0
folders="C:\\Windows"
folder_monitor_changes=1
folder_buffer_size_list=65536
folder_rescan_if_full_list=0
folder_update_types=2
folder_update_days=0
folder_update_ats=3
folder_update_intervals=6
folder_update_interval_types=1

For the record - I am testing with Everything 1.4.1.1032 (x64) and 1.5.0.1409a (x64)

[cmd4ever]

Yes 20k file and yes. Do you know what I meant by DIFF?

Sorry I didn't notice that what was you meant.

Here is the differencies for the TC -instance that I tested with for v 1.4 and a fresh ini file:
For the record - I am testing with Everything 1.4.1.1032 (x64) and 1.5.0.1409a (x64)
(code)

hmmm. We basically have the same ini file. So the problem(s) do not come from Everything...
I'm puzzled because I also get the same results (problems) from both Win10 and Win11.

The remaining "unknown" variables resides
-in TC configurations itself: Relatively easy to narrow down (Everything=, UseEverythingInstance=, [ ]Everything checkboxes in both CTRL-F7 and Configurations/Operations)
-in TC code (blackbox to us normal users)
-in Windows privilege, service and security settings related to both TC and Everything

The Everything side is the most transparent and do not need to run as a service to receive IPC queries from other tools. It even provide a debugging console to see exactly who's doing what. Since "my" OS/TC settings and/OR TC Code prevent TC to communicate with Everything. I can't reverse engineering what is going on the TC side.

So at this point I also side with 2AntonyD

It seems, guys, that you have done quite enough for testing purposes - now all that's left is to wait for Mr. Ghisler's answers
to all the questions posed and the inconvenient situations that were revealed during the tests.
We've set the main goal for reflection with our tests and a post-analysis of their results.
Huge thanks to all the participants))

I even welcome the hobbyists comments even if they make unusable noise sometimes. Can't throw any stone myself. Cause I know I participate to that kind of noise as well.

Special thanks to AntonyD and PerterMad who kept their cool and provided relevant insides.

[tuska]

If I run TC with as admin, it opens Everything but does not use my Instance
(although the process was clearly launched with the - instance and -startup).

If I start a generic Everything instance prior to TC, TC will still launch Everything will all the parameters
but ALT-F7 does not use the Instance

With TC 32bit 11.57R5

TC do not appear to use the ini parameter UseEverythingInstance=TC
If everything is not running when TC is launched, it lauches it with -startup only without including the -instance TC parameter.
Regardless if the proper instance is already running or not.

I couldn't reproduce the UAC flood.

See image below. Two instances of Everything running.
Left launched by TC (ignoring the UseEverythingInstance=TC wincmd.ini line)
Right launched by my beloved Servant Salamander with the wanted commandline.
Image: https://i.imgur.com/bJyGGQ8.jpeg

Maybe that's the reason?

Left launched by TC:
The command line differs from that in Servant Salamander in that
the following is missing in TC: -instance TC

[cmd4ever]

Left launched by TC:
The command line differs from that in Servant Salamander in that
the following is missing in TC: -instance TC

You again, this is outdated and no longer the problem since. Although this is another unresolved debate. Why make Everything= UseEverythingInstance= redondant. One of the numerous unanswered questions in this 6 pages quest. I put full -instance namedinstance since I was told TC wants redundant parameters for sake debatable of user control.

[tuska]

You again, I'm little tired of typing the same thing over and over.

OK, you don't have to feel like I'm bothering you anymore.

[cmd4ever]

[DELETE]

[cmd4ever]

You again, I'm little tired of typing the same thing over and over.

OK, you don't have to feel like I'm bothering you anymore.

You were too quick to read. I noticed afteward that you were replying to an outdated post so I corrected it too late. I have being using proper commandline forms for Everything= for quite a while after THAT post you are refering too.

I keep hitting quote when I meant edit. The timer to delete post is too short for my old eyes.

[tuska]

Settings: 2 Everything 1.5a instances | TC: User, EV: User; ✅ Run indexing process as administrator

1. Total Commander 11.57 is used as a user.
2. TWO Everything instances available.
    
3. Everything 1.5.0.1409a (x64) is running as a standard user, AND the indexing process is running as an administrator,
   which means that in Task Manager, there is no “Everything” service listed under either ‘Processes’ or “Services.”
   
   Only the “Everything” process is displayed with the command line:
   “C:\Everything\Everything.exe” under “Apps”
   - OR -
   under the background process ‘Everything’ with the command line:
   “C:\Everything\Everything_PRIVATE\Everything.exe” -instance “PRIVATE” -startup
   
   In Everything 1.5, the option “Run indexing process as administrator (recommended)”
   is suggested during installation if a portable version is being used: Run indexing process as administrator
   
   If this option is selected while the program is running and this results in a change to the settings,
   then Everything 1.5 must be restarted, for example by entering the command /restart and pressing the <ENTER> key.
    
4. Everything Service (as mentioned above): Not available.
    
5. Instances: Multiple Instances
   1. Instance-1: Everything -> Unnamed instance == my main instance ---- Task Manager > Processes: 2 061,6 MB
      C:\Everything\Everything.exe ---> Start Everything on system startup
   2. Instance-2: Everything (PRIVATE) -> Named instance (my second instance) - Task Manager > Processes: 719,2 MB
      "C:\Everything\Everything_PRIVATE\Everything.exe" -instance "PRIVATE" -startup ---> Manual start
6. Buttons in Total Commander
   - Button with command: C:\Everything\Everything.exe
   - Button with command: C:\Everything\Everything_PRIVATE\Everything.exe -instance "PRIVATE" -startup --- manueller Start
    
7. Everything 1.5a - Configuration files
   C:\Everything\Everything.ini
   C:\Everything\Everything_PRIVATE\Everything-PRIVATE.ini
   C:\Everything\NO_ALPHA_INSTANCE Search queries in TC using 'Everything', 13.2.c.
    
8. Options > Everything 1.5.0.1409a (x64)
   - Unnamed Instance: Indexes > NTFS: System drive (C:), D:, G: - not i: (!)
   - Named Instance:   Indexes > NTFS: i: --> root: ... result: I:\ (== i:\)
    
9. wincmd.ini - section [Configuration]

   Code: Select all

   UseEverything=1
   UseEverythingInstance="PRIVATE"
   Everything=C:\Everything\Everything_PRIVATE\Everything.exe -instance "PRIVATE" -startup

⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺

Example 1 - TC, an unnamed EV 1.5 instance, and a named EV 1.5 instance have been started

Code: Select all

- Total Commander is running -> ✅ ‘Everything’

- The two Everything instances (2 icons in the system tray),
  - “Everything” -> Tooltip in Systray: "Everything 1.5.0.1409a (x64)" AND
  - “Everything (PRIVATE)” -> Tooltip in Systray: "Everything 1.5.0.1409a (x64) PRIVATE", are running

- wincmd.ini [Configuration] UseEverything=1

- Search query in TC: -> Search for: ev:parent:D:\Test exact:Test.txt -> click on button "Start search"
  Result:  [No files found] -> OK, UseEverythingInstance="PRIVATE" -> only drive I: is indexed in the named instance!

  Search query in TC: -> Search for: ev:parent:i:\Test exact:Test.txt -> click on button "Start search"
  Result: I:\Test\Test.txt -> OK, UseEverythingInstance="PRIVATE" -> Drive I: is indexed in the named instance!

- Search directly in Everything 1.5:
  - parent:D:\Test exact:Test.txt -> result: 0 items --> OK!  --> UseEverythingInstance="PRIVATE" (i: NOT indexed in named instance!)
  - parent:i:\Test exact:Test.txt -> result: I:\Test\Test.txt --> OK

  Example 1 - 4 tests were successfully completed (2x TC & 2x EV 1.5)!
⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺

Example 2 - Only the unnamed “Everything” 1.5 instance is open

1. Close the “Everything (PRIVATE)” instance 'completely' (menu "File" - "Exit").
   'Completely' means that the Everything icon must also be removed from the system tray as follows: Right-click the icon -> Exit,
   so that only the unnamed “Everything” instance remains open.
    
2. wincmd.ini [Configuration] UseEverything=1
    
3. Restart Total Commander with the command: cm_exit 9
    
4. Total Commander has started -> ☐ ‘Everything’
   Everything is UNCHECKED because the “Everything (PRIVATE)” instance is closed.
    
5. Search query in TC: -> Search for: ev:parent:D:\Test exact:Test.txt -> click on button "Start search"
   1. The “Everything (PRIVATE)” instance was started in the background due to this search query in Total Commander,
      based on this setting in wincmd.ini - section [Configuration]:
      Everything=C:\Everything\Everything_PRIVATE\Everything.exe -instance "PRIVATE" -startup
      and the Everything option was checked -> ‘Everything’
   2. Search result: [No files found] --> OK!
      Reason: UseEverythingInstance="PRIVATE" (i: NOT indexed in named instance!)
6. Search query in TC: -> Search for: ev:parent:i:\Test exact:Test.txt -> click on button "Start search"
   1. Result: I:\Test\Test.txt --> OK
      Reason: UseEverythingInstance="PRIVATE" -> Drive I: is indexed in the named instance!

  Example 2 - 2 tests were successfully completed!
⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺⸺

Example 3 - The “Everything” and “Everything (PRIVATE)” 1.5 instances have been closed

1. Close both Everything instances, “Everything” and “Everything (PRIVATE)”, meaning there are now NO Everything instances open
    
2. Restart Total Commander with the command: cm_exit 9
    
3. Total Commander has started -> ☐ ‘Everything’
   Everything is UNCHECKED because the “Everything (PRIVATE)” instance is closed.
    
4. Search query in TC: -> Search for: ev:parent:D:\Test exact:Test.txt -> click on button "Start search"
   1. The “Everything (PRIVATE)” instance was started in the background due to this search query in Total Commander,
      based on this setting in wincmd.ini - section [Configuration]:
      Everything=C:\Everything\Everything_PRIVATE\Everything.exe -instance "PRIVATE" -startup
      and the Everything option was checked -> ‘Everything’
   2. Search result: [No files found] --> OK!
      Reason: UseEverythingInstance="PRIVATE" (i: NOT indexed in named instance!)
5. Search query in TC: -> Search for: ev:parent:i:\Test exact:Test.txt -> click on button "Start search"
   1. Result: I:\Test\Test.txt --> OK
      Reason: UseEverythingInstance="PRIVATE" -> Drive I: is indexed in the named instance!

  Example 3 - 2 tests were successfully completed!

[tuska]

You again, I'm little tired of typing the same thing over and over.

OK, you don't have to feel like I'm bothering you anymore.

You were too quick to read. I noticed afteward that you were replying to an outdated post so I corrected it too late.
I have being using proper commandline forms for Everything= for quite a while after THAT post you are refering too.

I keep hitting quote when I meant edit. The timer to delete post is too short for my old eyes.

I think I read that correctly, but it's not a problem for me.
Based on my test results, I don't think I can help you with this issue anyway.

I will provide an example of "Admin" - "Admin" 1.5 at a later time, and that's it for me in this topic.