Inter-op with v1.4

[vefatica]

I'm having trouble getting the 1.5a EVERYTHING64.EXE to work with tools which work with v1.4. My EVERYTHING64.EXE (distributed with JPSoft's TCC shell version 31) is version 1.5.0.1356a. Here's the setup; there are no running instances of older versions of EVERYTHING.EXE.

The service and the client are running.

Code: Select all

v:\> ver
TCC 30.00.22 x64
Microsoft Windows 10 Pro for Workstations
10.0.19045.3448 (2009, 22H2)

v:\> sc start "everything (1.5a)" | grep STATE
        STATE              : 4  RUNNING

v:\> start d:\tc31\everything64.exe -startup & echo %_startpid
1096

Here's TCC's v30 (older) built-in search command (no output).

Code: Select all

v:\> which everything
everything is an internal command

v:\> everything *

v:\>

Here's a 64-bit version of ES.EXE (built from the distributed source).

Code: Select all

v:\> u:\es.exe *
Error 8: Everything IPC window not found. Please make sure Everything is running.

And here's a plugin (mine) ES command (no output).

Code: Select all

v:\> plugin /l d:\tc30\Plugins\es\es.dll

v:\> which es
es is a plugin command (ES)

v:\> es *
Everything_Query error: 2

v:\>

In TCC version 31 (beta) the internal EVERYTHING command works and ES.EXE and my plugin ES don't (as above). When the service and client are version 1.4, ES.EXE and my plugin work and the internal EVERYTHING command does not.

Should older tools should inter-op with the version 1.5a service and client?

Thanks.

- Vince

[void]

The Everything 1.5 alpha runs in a "1.5a" instance.

To disable this "1.5a" instance:

• Please make sure Everything 1.4 is not installed.
• 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.
• Restart Everything (File -> Exit)

[vefatica]

Thanks, void. Now I remember going through this before. That setting keeps getting lost, possibly because with each TCC install, Everything (1.5a) is re-installed. In fact, a build of ES.EXE distributed with TCC also fails as I described without that option. I'll tell the author. Thanks again.