WAD If pathext option is enabled, tcstart does no longer works

[Alpengreis]

Hello

If the pathext option is enabled (in options dialog), tcstart does no longer works.
I have tcstart.btm as usually in path where tcmd.exe and tcc.exe is. Even with explicite path in for tcstart/tcexit is doesn't works.

And wihout pathext enabled for example the external more command does no more works.

 

[Alpengreis]

I could solve that with adding .BTM to the System PATHEXT variable ... however: that wasn't necessary before v31.

 

[rconn]

Nothing changed w/PATHEXT or TCSTART in v31.

What is in your PATHEXT var?

 

[rconn]

I could solve that with adding .BTM to the System PATHEXT variable ... however: that wasn't necessary before v31.

If you set the PathExt option, and your PATHEXT var does not contain .BTM, then TCC will not find and execute BTMs. This is exactly what it is supposed to do, and has not changed for years.

 

[Alpengreis]

Thank you, Rex!

Then I was wrong (confused about now enabled pathext option, see below ...)

The following is my PATHEXT now and with that it works ...

PATHEXT=.COM;.EXE;.BTM;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.REX;.REXX;.PL;.PY;.RB;.TCL;.LUA