Please try running Everything 1.4 with the command line option -instance 705 :
This will start a new instance of Everything.
In Everything, from the Tools menu, click Options.
Click the General tab.
Check Everything Service.
This will install the Everything service with the service name "Everything (705)".
Now is this in order to be able to run 1.3 & 1.4 concurrently?
Or multiple instances of 1.3 & 1.4, so 1.3 & 1.4 & 1.4, or 1.4 & 1.4?
Any of the above.
And then how to effect it?
Use a unique name for -instance <name> for each version you wish to run concurrently.
Does the use of -instance automatically create a same named service?
(Don't think so.)
The service name should be: "Everything (<instance name>)".
Where <instance name> is the instance name.
So -instance 705 creates a service "705"?
(I don't think I saw that.)
Should be "Everything (705)".
Or do you need something like:
Everything -install-service-pipe-name 705 -exit
Everything -instance 705
(Seemed to bring up an empty Everything window.)
Or might you need -instance 705 -service-pipe-name 705 ?
The -install-service-pipe-name 705 will do nothing on its own, it needs to be used with -install-service.
However, I don't recommend doing this from the command line. Install the service from within Everything (Tools -> Options -> General -> Everything Service)
The pipe name will also include the instance name.
Strange the empty window showed, I would have expected the Access denied dialog, asking if you would like to run as admin / install the service / do not index ntfs volumes.
Once you've got it working, is it expected to see multiple instances of Everything.exe (service) in Task Manager? And are they uniquely identified (other then by PID)?
Or some other machinations?
Yes, There will be multiple services running. There will be a Everything.exe process for each service and instance.
Oh, I bet you need -svc-pipe-name?
Thats for the -svc command line option, I do not recommend using this.