Error in TCC/LE when succeed smoothly in native windows cmd.exe

Nov 8, 2015
I made a flle assiociation of .pml extension. So I have in shell\open\command key registry:

z:\tcc /h/c "reg add "HKCU\Software\Sysinternals\Process Monitor" /v MainWindow /t REG_BINARY /d 2c000000 /f&z:\Procmon.exe /quiet /openlog "%v""

then get into TCC/LE console and type:
App.pml <enter>

it failed an error:
TCC: (Sys) The system cannot find the path specified.
"z:\tcc /h/c reg add HKCU\Software\Sysinternals\Process Monitor /v MainWindow /t REG_BINARY /d 2c000000000 /f&z:\Procmon.exe"

while in windows cmd.exe prompt it flawlessly run it and smoothly launch the Procmon.exe with App.pml as parameter

How to solve this ?
That registry key is really for use by Explorer. To create file associations in TCC, I would suggest an environment variable:
set .pml=command....
This way also causes filename completion to pick up on .PML files.
doesn't matter.
The point is as I said,

Why it runs flawlessly in native windows while tcc/le fails ?
Using your command with appropriate paths, with CMD.EXE.


The default shell\open\command (shown below) works in bot CMD and TCC/LE.
V:\> reg query HKEY_CLASSES_ROOT\.pml

    (Default)    REG_SZ    ProcMon.Logfile.1


V:\> reg query HKEY_CLASSES_ROOT\ProcMon.Logfile.1\shell\open\command

    (Default)    REG_SZ    "G:\processmonitor\procmon.exe" /OpenLog "%1"
I was mistaken. I thought it worked because after being successful from CMD, procmon.exe resets the shell\open\command to the default.

With this command,

g:\tccle14\tcc.exe /c reg add "HKCU\Software\Sysinternals\Process Monitor" /v MainWindow /t REG_BINARY /d 2c000000 /f & g:\processmonitor\Procmon.exe /quiet /openlog "%v"

and trying only with TCC/LE, I see that the reg command succeeded and then I get a rather inexplicable error (below).


However, a small change fixed that ... change "%v" to "%l". I don't know why "%v" works in CMD and not in TCC

This one worls in TCC/LE.

g:\tccle14\tcc.exe /c reg add "HKCU\Software\Sysinternals\Process Monitor" /v MainWindow /t REG_BINARY /d 2c000000 /f & g:\processmonitor\Procmon.exe /quiet /openlog "%l"

But, as I said above, when it does work (once) procmon.exe resets that command back to the default.
I am figuring out.. sorry if I won't respond. It'd be slow and long time to get my solving and tell it back

Similar threads