Code: Select all
start /b cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R=PATH
Moderators: white, Hacker, petermad, Stefan2
Code: Select all
start /b cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R=PATH
Code: Select all
start /b cmd /c TOTALCMD64.EXE /O /R="PATH"
Code: Select all
start /b cmd /c TOTALCMD64.EXE /O /L="PATH1" /R="PATH2"
There is no start.exe. START is an internal command of CMD.
It is just unnerving that I could not pass a parameter in quotes without resorting to the method above, i.e. by removing the quotes in an other path. It works, but why ? It does not seems logical. The initial syntax should have worked. In any case, thank you, Ovg, for your practical proposal.
Just my ignorance. Once I have composed a working line from directives, which I picked up, and while it is working, I do not change it . Indeed, the same line works without the "start /b" header.
I am quite ignorant in this area, but I do believe that start does not interfere in terms of parsing of the subsequent expression by cmd (as pointed out by Dalai). If I remove "start /b" everything behaves similarly. However, to my utmost surprise, your method of using doubly nested paths is working !
Code: Select all
cmd /c ""C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH""
Code: Select all
"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O "/R=PATH"
Code: Select all
"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"
Roman, unfortunately neither case is working. I have just checked. Moreover, the second case was the one, I have reported as not working right in the first message.Hacker wrote: ↑2019-02-21, 19:56 UTCCode: Select all
"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O "/R=PATH"
Code: Select all
"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"
Code: Select all
start [/wait] "" "command with spaces.exe"
Code: Select all
start [/wait] "useless title" "command with spaces.exe"
Code: Select all
cmd /c ""C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH""
Code: Select all
"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"
Try to autostart some program minimized using entry in registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
Code: Select all
start "" /min C:\WINDOWS\system32\taskmgr.exe
How does CMD itself help with that? The START command can do that (start /min), but CMD without START can't and doesn't. Apart from that, I'd rather use something like NirCmd or Cmdow, or use an LNK file with minimized flag in the start menu.
I guess, if there is one. In any case, I have tested the previous examples also without the start command. I have found no difference with the shortened version, i.e. starting with cmd. It seems, that the use of start cannot be held responsible.
Dalai, thank you for educating me on this point. I had a feeling that one need a kind of 'executing directive'. However, it is superfluous and indeed, your version is working. Still, sometimes, it is nice to use command keys, e.g. with cmd, and good to know a method to pass the parameters, even if they contain spaces.
I know, I am just saying it works fine here, so there must be a problem elsewhere (not with the syntax itself).Moreover, the second case was the one, I have reported as not working right in the first message.
Can you perhaps create a video of what is happening?Roman, unfortunately neither case is working. I have just checked.
Code: Select all
cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"
Code: Select all
'C:\Program' is not recognized as an internal or external command, operable program or batch file