Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

@execstr not working in 31.01.14

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

Code:
[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

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

in my TCStart.btm. It causes Take Command to immediately close.
 
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.
 
It's also @execstr for me. The following code in my tcstartup.btm causes the window to immediately close before the prompt is displayed.

Code:
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/
 
Last edited:
Used in a BTM, @EXECSTR crashes TCC (have DMP files). At the command line it hangs TCC (using no CPU).
 

Similar threads

Back
Top