That looks good!

I'm curious! Having let Windows do that, what do assoc .btm and ftype %@assoc[.btm] show?

And the 2-click in Explorer still doesn't work?

I'm running out of ideas. What happens if you use the Run dialog (Win+R)? Try "C:\Program Files\JPSoft\TCMD32\tcc.exe" /c ... "C:\Program Files\JPSoft\TCMD32\tcc.exe" /c pause ... "C:\Program Files\JPSoft\TCMD32\tcc.exe" /c [path to test BTM]. And there seems to be a mixture of TCC v31 and...

In TCC's home directory there should be TCCBATCH.BTM. That will do it.

Now it's getting strange! Do you have TCSTART.BTM files? Could anything in them start (or not start) a non-transient TCC? You might try putting ECHO %_PID in the test BTM file and then, when you have dismissed the PAUSE and the window doesn't close, ECHO %_PID at the command line to see if...

Try these commands. They say what Explorer does when you 2-click on a BTM. v:\> assoc .btm .btm=TCC.Batch v:\> ftype tcc.batch tcc.batch="D:\tc31\tcc.exe" /c "%1" %* If you see the "/C" on the TCC command, the TCC running the BTM will be transient and will exit when the BTM terminates. If...

QUIT ends a BAT/BTM. EXIT terminates TCC. QUIT would terminate TCC if TCC was transient (started with "/C").

What's special about running TCC like that?

I didn't know this but the name of a subkey of "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths" need not be the name of an existing app. There is no VS22.EXE here but there is this AppPaths entry. v:\> regdir /v /d...

Can you reproduce it? Can you make it any simpler? This seems OK. v:\clio> type bat1.bat touch /q /c foo.txt d:\7zip\7z.exe a foo.7z foo.txt > nul del /q foo.txt d:\7zip\7z.exe e foo.7z > nul call bat2.bat "a b c" d v:\clio> type bat2.bat echo %%1 = %1 echo %%2 = %2 v:\clio> bat1.bat %1 =...

Interesting! I don't know what it all means but it will probably help Rex.

I can work around the problem reported here with some quotes. do x in *.dll (if "%@exec[strings %x | findstr cmd.exe]" == "0" echo **%x) Interrupting that command with Ctrl-C makes TCC crash. I get a dump file and no entries in tcc.exception.log. Analyzing the crash with WinDbg I see this...

This works in TCC v31. v:\> if %@exec[echo foo | findstr foo] == 0 echo yes foo yes in TCC v32 I get this. v:\> if %@exec[echo foo | findstr foo] == 0 echo yes FINDSTR: Cannot open == FINDSTR: Cannot open 0 FINDSTR: Cannot open echo FINDSTR: Cannot open yes TCC: Syntax error "@exec[echo"...

You could probably do the same with WinEventHooks (as opposed to scanning); ever use them? Theyr'e pretty easy and efficient. I only do any of this in a 4WT plugin which refuses to load if it doesn't think TCC is in WT. It seems like quite a chore to do it more generically (handling WT...