Is it possible to run version 1.4 and 1.5 side by side?

[wunderbar]

I'm interested in exploring the API for Everything, and it makes sense to familiarize myself with the 1.5 world that is on the way.

But I have to day I'm very happy with 1.4, from a "just your average user" point of view. So, I really don't want to give up 1.4

I did a search on Kagi which indicated that there were a lot of weird problems that could happen, particularly with integrations against other third party tools, such as Total Commander. However, my setup is rather generic, and I'm not using Total Commander.

I did not see any links pointing back here to explain what the "side by side" story is. So, please forgive my inadequate search-fu.

[void]

Everything 1.5 alpha doesn't interfere with Everything 1.4.

The Everything 1.5 alpha runs in a 1.5a instance.
You can run Everything 1.4 and Everything 1.5a at the same time.



Everything 1.5 SDK
ES (command line interface) source code
alpha_instance

[wunderbar]

I did not see any links pointing back here to explain what the "side by side" story is. So, please forgive my inadequate search-fu.

I did find this thread: viewtopic.php?t=17050 , titled "Everything Service" which discusses the fact that 1.4 and 1.5 use distinct an incompatible executables for the service, but also that they use distinct names for each service.

This seems to imply that I can run Everything 1.4 and 1.5 side by side. But some time has passed since that thread was active, so maybe things have changed since then?

Also: after the release of version 1.5, will the name for the service remain as "Everything 1.5a" service name? Or will default installs return to a service name of simply "Everything". (I can sense the potential for confusing no matter which choice is made with this matter.)

[wunderbar]

Everything 1.5 alpha doesn't interfere with Everything 1.4.

The Everything 1.5 alpha runs in a 1.5a instance.
You can run Everything 1.4 and Everything 1.5a at the same time.

Thank you! You are too fast for me!

[void]

This seems to imply that I can run Everything 1.4 and 1.5 side by side. But some time has passed since that thread was active, so maybe things have changed since then?

Nothing has changed since.
You can still run Everything 1.4 and Everything 1.5 alpha side by side.

Everything 1.4 and Everything 1.5 alpha use a separate Everything Service.

Also: after the release of version 1.5, will the name for the service remain as "Everything 1.5a" service name? Or will default installs return to a service name of simply "Everything". (I can sense the potential for confusing no matter which choice is made with this matter.)

Once Everything 1.5 is in beta, the 1.5a instance will be removed.
You will not be able to run Everything 1.4 and Everything 1.5b side by side by default.
Same applies to the release version.

The Everything 1.5 Service will be renamed to

Everything Service

once in beta.
It is possible to use a custom instance in Everything 1.4 to install a service with a different name.
eg:

Everything-1.4.exe -instance "1.4"

will use a service named

Everything Service (1.4)

Everything 1.5 will only have one service, which manages all 1.5 instances.

[Herkules97]

You can run as many instances as you want. Maybe there are bugs associated with service-less running, for example my monolithic instance doesn't index almost any files' extra properties like size-on-disk for one specific HDD. Some have been indexed only when I run the file via the instance, others remain empty for those extra properties still.
Or maybe that bug comes from running it as admin when I first started the db..Or maybe the HDD itself broke indexing first time I added it and it'd fix if I removed, applied, then added it back in and applied. Whatever the case there may be bugs that does not exist with the service method.

I run one monolithic instance and one-device instances at the same time. Currently I have 22 instances running. The solo device instances index files almost flawlessly. If there are enough changes(Maybe 50K plus files/folders but even then I seldom come across this issue and it may be the fault of something else) one of them might break like the monolithic one does and restarting it to index extra properties is required. If the instances aren't up-to-date(besides in my monolithic case where it doesn't index extra properties for most files on one HDD yet I can still run files without the instance freezing), running any file from that instance will cause it to freeze and require force-exiting AFAIK. Maybe that could be fixed, I've not found it an issue worth asking about, I just restart the instances and let them process remaining files instead.

I assume you have ran what you want fine with the services.
But if someone else also indexes size on disk, date accessed, and without using the services and want to find when an instance has frozen reading those(presuming there will be new files post-freeze), I use this search:
"!size-on-disk:0b !size-on-disk:=>1b !folder: sort:date-accessed-descending online: !"\System Volume Information" max-threads:4 !"C:\Program Files\WindowsApps\Deleted" !"C:\Windows\servicing\Packages" !"C:\Windows\System32\config\systemprofile\AppData" !"C:\Windows\System32\LogFiles\WMI\RtBackup""
Skip the first and last quote marks.
The excluded paths being files that EBV can't touch either because it's not using the service, permissions don't cooperate with EBV or whatever it may be.