Not supported "Everything 1.5a"

[3D designer]

Hello
Dear Sirs,
Total Commander is not supported "Everything 1.5a" in "Find Files" menu
Should I wait for "Everything 1.5" (full)?

[Horst.Epp]

Its supported if you make the necessary settings in TC and Everything.

wincmd.ini set the Everything lines to
; UseEverythingInstance=1.5a
Everything=C:\Tools\Everything\Everything64.exe

In Everything-1.5.ini set
alpha_instance=0

The Everything path in wincmd.ini must be set to your path of course

[AntonyD]

But by the way, it's damn interesting - why do we still have to write something somewhere?
Can't Total natively and by default use ANY exe for this program?
WHAT is so special about the exe of this version that nothing works by default?

[Horst.Epp]

But by the way, it's damn interesting - why do we still have to write something somewhere?
Can't Total natively and by default use ANY exe for this program?
WHAT is so special about the exe of this version that nothing works by default?

Should we take this post as a joke
If you want to use the much better Alpha version of Everything
you just have to change one line in a config file.
If that is to much work for someone he can stay with the Everything release version.

[tuska]

WHAT is so special about the exe of this version that nothing works by default?

Because it's the Everything 1.5 Alpha version.

• Everything 1.5 SDK
  This 1.5a instance will be removed when Everything 1.5 is ready for beta/release.
• Disable the Everything 1.5a instance
   
• 13. SETTINGS: For 'Everything' in Total Commander & 'Everything' -> from 'Everything' Version 1.5

---

Windows 11 Pro (x64) Version 22H2 (OS build 22621.900) | TC 10.52 x64/x86
'Everything' 1.5.0.1330a (x64) | Switching from Everything 1.4 to 1.5

[3D designer]

Its supported if you make the necessary settings in TC and Everything.

wincmd.ini set the Everything lines to
; UseEverythingInstance=1.5a
Everything=C:\Tools\Everything\Everything64.exe

In Everything-1.5.ini set
alpha_instance=0

The Everything path in wincmd.ini must be set to your path of course

Thank you dear Horst,
This is exactly what I want.

[AntonyD]

Should we take this post as a joke

definitely not.
Because it's very strange for me that for support of this release we really have to add something.
As for me, it's very easy for me to imagine a situation with an ordinary person who rarely updates something, but if he does, he does not expect that something can go wrong. And now he has updated TotalCmd - and no problem - everything works as he used to. He updated Everything and the utility works as he used to. And note that the utility is used very rarely;). Not all the time! as you for ex. And it was enough for him to try to use the utility from inside Total - as he stumbles upon problems??? And tell me - how many people know that you can go to this forum and read, look for the necessary information? And that on the forum of that utility you have to/can go and read, look for the necessary information?
Therefore, it is not really clear - why not embed the support for the new version of this utility seamlessly and by default in TotalCMD?
So no one has to put anything in anywhere.

[tuska]

Therefore, it is not really clear - why not embed the support for the new version of this utility seamlessly and by default in TotalCMD?

In my opinion, the main reason for this is that not all Total Commander users also use the tool 'Everything'.

Another reason might be the following:
There are currently 3 possible settings for establishing a connection between Total Commander and Everything 1.5 - some with different effects.

---

Windows 11 Pro (x64) Version 22H2 (OS build 22621.900)
TC 10.52 x64/x86 | 'Everything' 1.5.0.1330a (x64)
Search queries: Total Commander <=> 'Everything' | Troubleshooting

[AntonyD]

There are currently 3 possible settings for establishing a connection between Total Commander and Everything 1.5 - some with different effects.

And this further impairs the understanding of what and how should be done for the seamless and default connection of the utility to the Total.

[Sir_SiLvA]

And this further impairs the understanding of what and how should be done for the seamless and default connection of the utility to the Total.

No it does not, because a user who uses TC is supposed to be able to read the helpfile.
TC is not a tool for your average Joe but someone who is willing to do the work, in this case read the helpfile.

[tuska]

There are currently 3 possible settings for establishing a connection between Total Commander and Everything 1.5 - some with different effects.

And this further impairs the understanding of what and how should be done for the seamless and default connection of the utility to the Total.

I am not quite sure what you mean by your statement (I am not a native speaker).

I think the facts of how it currently works have been stated/linked.
In such a case (Everything 1.5) a user has to make at least ONE ENTRY in an .ini file ONCE (point 13.2.b.).

From Everything 1.5 Beta or Release something will change again.

I don't want to seem rude, but I'll end this topic for myself here.

Regards,
Karl

[Hacker]

AntonyD,

it's very strange for me that for support of this release we really have to add something
[...]
why not embed the support for the new version of this utility seamlessly and by default in TotalCMD?

Perhaps it's not really clear. It was a decision of the author of Everything to make the use of v1.5 alpha incompatible with the usual usage. As I understand, this was made so users could keep using v1.4 normally and also install v1.5 alpha for testing, not affecting their stable v1.4 installation. If you want to use v1.5 alpha seamlessly instead of v1.4, you have to ask the author of Everything to enable it. There is a workaround available both in TC and in Everything to use this incompatible v1.5 alpha, if one desires to do so. But when Everything becomes incompatible on purpose, the requests to the authors of all other tools to make them compatible, are misplaced.

Roman

[AntonyD]

It was a decision of the author of Everything to make the use of v1.5 alpha incompatible with the usual usage.

Ahhha!!!! A very important and timely clarification!

But when Everything becomes incompatible on purpose, the requests to the authors of all other tools to make them compatible, are misplaced.

Agree)))

[att]

Thank you for your help how to integrate "Everything 1.5a".
Just a little clarification: So the "-startup" parameter is not required anymore?
My Wincmd.ini looks like this :

Code: Select all

[Configuration]
Everything=c:\WINPROG\EVERYTHING\Everything 1.5a\Everything64.exe -startup

Should the "-startup" parameter be removed ?

[Horst.Epp]

Thank you for your help how to integrate "Everything 1.5a".
Just a little clarification: So the "-startup" parameter is not required anymore?
My Wincmd.ini looks like this :

Code: Select all

[Configuration]
Everything=c:\WINPROG\EVERYTHING\Everything 1.5a\Everything64.exe -startup

Should the "-startup" parameter be removed ?

The -startup is not necessary,
If your Everything installation is running as suggested:
- The Everything service is installed
- Everything starts with system startup
- Everything is NOT running as Administrator