2024-03-20 12:37 21,340,808,618 tcc.exception.log That's an interesting file. It starts like this. [2024/03/20 12:20:46.183] D:\TakeCommand32\TCConsole\ntinit.cpp:412 wmain() SEH Exception: 0x00007FFCFFAFBCB7 - ACCESS_VIOLATION [2024/03/20 12:36:04.302]...

I have customized some keystrokes in TCC. I don't know how to do that in TCMD.

If Everything is running as it should, service plus unelevated client, then EVERYTHING /E only starts a new (possibly elevated) instance of Everything.exe long enough for it to communicate with the already-running one. There should be no problem with that.

I do have this. 2024-03-20 12:37:56 21,340,808,618 C:\ProgramData\JP Software\Take Command 32\tcc.exception.log That is likely to be thousands of crashes! I wish I could open it to see what was going on; it's too big for anything I have

I have none of them. But for one of the dumps I have analyzing the exception identifies TCMD and does not mention any DLL. BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_tcmd+372a4 FAILURE_EXCEPTION_CODE: c0000005 FAILURE_IMAGE_NAME: tcmd.exe BUCKET_ID_IMAGE_STR: tcmd.exe...

Does Everything start automatically at login (the service and the client)? If so, maybe a logoff/logon will help. If not, the proper way to start the client is (unelevated) [path]\everything.exe /startup ... EVERYTHING /E will also start it if necessary, but do that unelevated. TaskMgr should...

Too big for my Exchange server. You can get them from my OneDrive public folder. In WinDbg, one of them doesn't make it to the point where I can analyze the exception.

It might even crash twice. I get, for example, 2024-04-20 17:57 321,186,020 tcmd.exe.11636.dmp 2024-04-20 17:57 321,181,676 tcmd.exe(1).11636.dmp

When I start TCMD (show Command Input configured) it starts looking like this (not docked). If I click or hover over its tab (?) it drops down, partially covering the TCC tab's client area. If I then click in the TCC tab client area, the Command Input window rolls up and shortly thereafter...

TMP9: doesn't seem special. A command much like the example in the help (Save to STDOUT) does nothing. Have you ever seen "Save to STDOUT) do something? v:\> dir /b | tcedit | grep btm v:\>

OK, I get it now. That's too much for the user to remember. I have this (so far). No doubt, there will be more changes. :: PATHEDIT.BTM setlocal if "%1" == "/?" goto syntax if "%1" == "/A" (shift & goto append) if "%1" == "/P" (shift & goto prepend) set before=%temp\pathedit_before.tmp...

I don't follow that. How does anything get into CLIP:?

Too hard!

Thanks, @samintz. You're right about that. And thanks @Joe Caverly and @Rodolfo. If I ever used _CMDSPEC it had to be a couple decades ago. I wrote a BTM to make editing PATH easier ... split it into parts in a tmpfile, edit the file, put it back together again, set it. Is there something...

I'm using %@left[-7,%comspec] but that seems kludgy. I looked for an internal variable and didn't find one.