Autorun defined for CDM.EXE makes the start of tcc.exe extremly slow

[MEBSware]

Dear Team,
we use an command combination at startup of cmd.exe to colour the screen red, when the environment is at highest level:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\Autorun REG_EXPAND_SZ AutoRun
(C:\WINDOWS\SYSTEM32\WHOAMI /groups /nh 2>NUL | C:\WINDOWS\SYSTEM32\FIND "S-1-16-12288" >NUL 2>&1) && (color 47 & PROMPT $E[33;1m$P$G$E[0;37;41m)) & VER >NUL
With cmd.exe there is no delay
With kind regards,
Bodo

 

[vefatica]

It may not be consequential but that command line has unbalanced parentheses in it.

 

[MEBSware]

Dear Vince,
you are wright, but with corrected line, behavior did not change:
(C:\WINDOWS\SYSTEM32\WHOAMI /groups /nh 2>NUL | C:\WINDOWS\SYSTEM32\FIND "S-1-16-12288" >NUL 2>&1) && (color 47 & PROMPT $E[33;1m$P$G$E[0;37;41m) & VER >NUL

 

[vefatica]

And, TCC will start another TCC to handle the pipe. That new TCC will execute Autorun. And so on.

Suggestions:

In TCMD.INI, [4NT] section,

AutoRun=No

In TCStart.btm,

if %_elevated == 1 (color 47  &  prompt $E[33;1m$P$G$E[0m)

 

[MEBSware]

Dear Vince,
thank you for the workaround.
The behavior of the TCC.EXE is not "conform" to CMD.EXE and other programms.
Usealy the exec externals programs directly, not by a loop of it self.
The pipes are handled by system not in TCC.
When TCC.EXE would do like this for every external command i can close my hope for using this tool.
Bodo

 

[vefatica]

Many who use TCSTART.BTM do this at/near the beginning:

IF %_PIPE%%_TRANSIENT%%_IDE% != 000 QUIT

 

[rconn]

The behavior of the TCC.EXE is not "conform" to CMD.EXE and other programms.
Usealy the exec externals programs directly, not by a loop of it self.
The pipes are handled by system not in TCC.
When TCC.EXE would do like this for every external command i can close my hope for using this tool.

Pipes are not handled by the system, they are handled by the command processor (TCC or CMD or PowerShell etc.).

If you are piping to an external command, TCC executes that command directly, not through another shell. If you are piping to an internal command, batch file, or alias, TCC has to call another copy of itself to execute the child pipe process.