es.exe not working, gives IPC window not found error
es.exe not working, gives IPC window not found error
es is not working for me:
es
Error 8: Everything IPC window not found. Please make sure Everything is running.
I'm using 1.5.0.1391a and es version 1.1.0.30.
I've tried admin and non-admin runs on all combinations.
es
Error 8: Everything IPC window not found. Please make sure Everything is running.
I'm using 1.5.0.1391a and es version 1.1.0.30.
I've tried admin and non-admin runs on all combinations.
Re: es.exe not working, gives IPC window not found error
Please try the -instance <instance-name> command line option with es:
-or-
Disable the 1.5a alpha instance in Everything:
es -instance 1.5a-or-
Disable the 1.5a alpha instance in Everything:
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
alpha - Select: alpha_instance
- Set the value to: false
- Click OK.
Re: es.exe not working, gives IPC window not found error
Ok, it works with es -instance 1.5a
Does disabling alpha have any pitfalls/interactions with other things?
Does disabling alpha have any pitfalls/interactions with other things?
Re: es.exe not working, gives IPC window not found error
Everything 1.5 alpha will interfere with Everything 1.4.
You cannot run both at the same time.
You will only run into pitfalls/interaction issues if you have Everything 1.4 installed.
You cannot run both at the same time.
You will only run into pitfalls/interaction issues if you have Everything 1.4 installed.
Re: es.exe not working, gives IPC window not found error
I only have 1.5a "installed"
But I have a related question as I was going to install 1.4.
I want to run two instances of everything. Either two independent installs or the same but with two interfaces.
There reason is that I have one computer but essentially two terminals(I use one at a desk then one at a piano).
I've setup the piano so I can do "piano things" to avoid having to go back an forth. I'd like to use everything on both sides so I can easily find files. Ideally what I'd like is a "2nd window" which I can "pin" to the monitor I want it on.
One issue is that I use everything in the tray and that doesn't show up on the other monitor so no easy access to it. There is also issues with running it with and without administrator access. Simply running it while it is already running does nothing. E.g., I have an elevated link that runs it if it is not running but if it is running won't do anything.
I probably could make a script that opens the window and then switches it to the other monitor but I'm wondering if there is a simpler solution(as that is not the optimal way since usually I have to duplicate everything).
Maybe a command line option that can get it to open it's window and a monitor if running or run and open it's window on a specified monitor?
I thought about using es.exe and set a terminal to the other monitor but I'd like to have the full gui since it is much easier to use.
There are the options about creating a new window which I have both unchecked. I typically only need one window being used at any time. (although this might be a problem if I start using two windows)
E.g., I use sumatrapdf for a similar thing to view pdfs and I keep them separated by using two distinct instances. This keeps everything nicely separated.
But I have a related question as I was going to install 1.4.
I want to run two instances of everything. Either two independent installs or the same but with two interfaces.
There reason is that I have one computer but essentially two terminals(I use one at a desk then one at a piano).
I've setup the piano so I can do "piano things" to avoid having to go back an forth. I'd like to use everything on both sides so I can easily find files. Ideally what I'd like is a "2nd window" which I can "pin" to the monitor I want it on.
One issue is that I use everything in the tray and that doesn't show up on the other monitor so no easy access to it. There is also issues with running it with and without administrator access. Simply running it while it is already running does nothing. E.g., I have an elevated link that runs it if it is not running but if it is running won't do anything.
I probably could make a script that opens the window and then switches it to the other monitor but I'm wondering if there is a simpler solution(as that is not the optimal way since usually I have to duplicate everything).
Maybe a command line option that can get it to open it's window and a monitor if running or run and open it's window on a specified monitor?
I thought about using es.exe and set a terminal to the other monitor but I'd like to have the full gui since it is much easier to use.
There are the options about creating a new window which I have both unchecked. I typically only need one window being used at any time. (although this might be a problem if I start using two windows)
E.g., I use sumatrapdf for a similar thing to view pdfs and I keep them separated by using two distinct instances. This keeps everything nicely separated.
Re: es.exe not working, gives IPC window not found error
Ok. -service-pipe-name "\\\\.\\PIPE\\Everything Service" wasn't working(everything wouldn't start) but I specified it through the options(using "\\\\.\\PIPE\\Everything Service") and I can get multiple instances running using -instance.
In any case, the issue is this: Can I share the same database between instances? They are creating two databases which is duplicate and it's based on the instance name. I could potentially symlnk or hard link to it but I'm not sure if that would cause corruption?
In fact, I'd like to use the same ini files too. I want it to be as much as just a "window" into the same database as possible. (although if they have to be separate than it's not that big a deal)
Thanks.
In any case, the issue is this: Can I share the same database between instances? They are creating two databases which is duplicate and it's based on the instance name. I could potentially symlnk or hard link to it but I'm not sure if that would cause corruption?
In fact, I'd like to use the same ini files too. I want it to be as much as just a "window" into the same database as possible. (although if they have to be separate than it's not that big a deal)
Thanks.
Re: es.exe not working, gives IPC window not found error
Everything 1.5 only needs one service for all instances.Ok. -service-pipe-name "\\\\.\\PIPE\\Everything Service" wasn't working(everything wouldn't start) but I specified it through the options(using "\\\\.\\PIPE\\Everything Service") and I can get multiple instances running using -instance.
The Service name is still hard coded as "\\\\.\\PIPE\\Everything 1.5a Service"
(unless you specify -service-pipe-name)
No.In any case, the issue is this: Can I share the same database between instances?
Everything loads the db into memory on startup and saves the db to disk on exit.They are creating two databases which is duplicate and it's based on the instance name. I could potentially symlnk or hard link to it but I'm not sure if that would cause corruption?
Both instances will overwrite each other.
Please try the -config "c:\shared-Everything.ini" command line option.In fact, I'd like to use the same ini files too. I want it to be as much as just a "window" into the same database as possible. (although if they have to be separate than it's not that big a deal)
Re: es.exe not working, gives IPC window not found error
That exists, i use two .lnk files, one on my tv and one on my monitor, to have everything open where i need it.Stretto wrote: Sun Jul 13, 2025 10:55 pm I probably could make a script that opens the window and then switches it to the other monitor but I'm wondering if there is a simpler solution(as that is not the optimal way since usually I have to duplicate everything).
Maybe a command line option that can get it to open it's window and a monitor if running or run and open it's window on a specified monitor?
"C:\Program Files\Everything 1.5a\Everything64.exe" -x 2009 -y 1272 -width 1109 -height 619
"C:\Program Files\Everything 1.5a\Everything64.exe" -x 134 -y 94 -width 1664 -height 1056
Downside is if you click on the tray icon it opens last position, if i'm clicking on my primary monitor task tray i generally want it to open there. And any change you make on the column sizes will be reflected on both displays, but other than that, works good.
Re: es.exe not working, gives IPC window not found error
Please try setting your tray_show_command_line:
Please also see: -columns
You can get your current columns from Help -> Troubleshooting information.
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
tray - Select: tray_show_command_line
- Set the value to:
-x 134 -y 94 -width 1664 -height 1056 - Click OK.
Please also see: -columns
You can get your current columns from Help -> Troubleshooting information.
Re: es.exe not working, gives IPC window not found error
Wow you have really thought of everything, tried both settings, worked perfectly.
Re: es.exe not working, gives IPC window not found error
void wrote: Tue Jul 15, 2025 1:02 amEverything 1.5 only needs one service for all instances.Ok. -service-pipe-name "\\\\.\\PIPE\\Everything Service" wasn't working(everything wouldn't start) but I specified it through the options(using "\\\\.\\PIPE\\Everything Service") and I can get multiple instances running using -instance.
The Service name is still hard coded as "\\\\.\\PIPE\\Everything 1.5a Service"
(unless you specify -service-pipe-name)
No.In any case, the issue is this: Can I share the same database between instances?
Everything loads the db into memory on startup and saves the db to disk on exit.They are creating two databases which is duplicate and it's based on the instance name. I could potentially symlnk or hard link to it but I'm not sure if that would cause corruption?
Both instances will overwrite each other.
Please try the -config "c:\shared-Everything.ini" command line option.In fact, I'd like to use the same ini files too. I want it to be as much as just a "window" into the same database as possible. (although if they have to be separate than it's not that big a deal)