@execstr not working in 31.01.14

[David Marcus]

I just updated to 31.01.14. %@execstr hangs, i.e., no output and the prompt does not appear:

[C:\]ver /r

TCC  31.01.14 x64   Windows 10 [Version 10.0.19045.3693]
TCC Build 14   Windows 10 Build 19045
Registered to DAVID-DESKTOP

[C:\]echo %@execstr[2,ver /r]

I normally have

iff "%@execstr[alias e >&> nul]" == "" then

in my TCStart.btm. It causes Take Command to immediately close.

 

[Fross]

My tcmd also closes before I get a prompt. Starting with a blank config works, but I'm going to have to dig through the config/startup file to determine what's causing it.

 

[Fross]

It's also @execstr for me. The following code in my tcstartup.btm causes the window to immediately close before the prompt is displayed.

rem ----------------------------------------------------------------------------------------------
rem -- Verify that CoreTemp is running.  If not execute it.
rem ----------------------------------------------------------------------------------------------
iff x%@ExecStr[*tasklist "Core Temp"]x==xx then
    Detach /Q "C:\Utils\CoreTemp\Core Temp.exe"
endiff
[/CODE/

 

[rconn]

@EXECSTR was not changed in build 14. I will test it here ...

 

[vefatica]

Used in a BTM, @EXECSTR crashes TCC (have DMP files). At the command line it hangs TCC (using no CPU).

 

[rconn]

@EXECSTR didn't change, but the RTL did. Bug in the new RTL; I have worked around it and uploaded a fix in 31.01.15.

 

[Fross]

Looks good here Rex. Thank you.

 

[Charles Dye]

I just tested, and I notice that @EXECSTR still has trouble with Unicode text when n < 0. I don't remember whether this one got fixed, and the issue has returned; or whether it was never addressed in the first place.