cm_executedos in TC 9 beta 14 does not work

[sqa_wizard]

holst@wmd.de: One more: Do you have a file like cmd.bat or cmd.cmd in your path (just try to run them from TC commandline)

[holst@wmd.de]

2ghisler(Author)

How about running them from the TC command line at the bottom?

It sems that holst@wmd.de already did that:

Calling "cm_executedos" in the commandline of TC leads to a dialogue box.

Header: Total Commander
Text: Nicht genug Speicher (german for "not enough memory")

noclose.exe and noclose64.exe exists and run without problems.
Running them from TC via double click or in tc commandline opens
a command prompt window.

@ghisler: As quoted above, did not work in tc commandline. Switched to using cmd instead of cm_executedos as a workaround. No need to dive deeper in this issue as it's obviously a configuration problem on my side.

[ghisler(Author)]

That's not what I meant!

I asked whether running noclose.exe from the command line worked or not. You already said that cm_executedos didn't work from the command line.

[petermad]

noclose.exe and noclose64.exe exists and run without problems.
Running them from TC via double click or in tc commandline opens
a command prompt window.

[holst@wmd.de]

That's not what I meant!

I asked whether running noclose.exe from the command line worked or not. You already said that cm_executedos didn't work from the command line.

1. cmd.exe
Opening cmd.exe from windows startmenu.
Switching via cd to c:\totalcmd
Executing noclose.exe and noclose64.exe
After hitting "enter" nothing happens, except a newline in the cmd window
What should happen?

2. executing "noclose.exe" and "noclose64.exe" from the tc commandline
This opens a windows commandline window in the correct directory (c:\totalcmd). c:\totalcmd is not in %PATH%.

No "cmd.bat" or "cmd.cmd" on the whole system, not in %PATH% and not in any other location on the local partitions.

[lloogg]

got the same problem.

environment:
windows 7 SP1 64 bit
9.0a 64bit
ComSpec: c:\windows\system32\cmd.exe
no cmd.cmd or cmd.bat
noclose64.exe from TC commandline works right.

guess some configuration from c driver cause this problem, because another computer(same env) doesn't have this problem.

And uninstall, ccleaner register, install 8.52a 64 bit still the same which doesn't in the same computer about one month back.

maybe reinstall the system is the final solution.

[ghisler(Author)]

What does
set comspec

show? It sounds like the 32-bit version of the command processsor referenced by this option is not found.

[holst@wmd.de]

What does
set comspec

show? It sounds like the 32-bit version of the command processsor referenced by this option is not found.

For me, it's:

c:\>set comspec
COMSPEC=C:\Windows\System32\cmd.exe

[nsp]

What does
set comspec

show? It sounds like the 32-bit version of the command processsor referenced by this option is not found.

For me, it's:

c:\>set comspec
COMSPEC=C:\Windows\System32\cmd.exe

to be sure that you have COMSPEC variable well defined inside TC process, in the command field of a test button:
1) just put %COMSPEC%
2) cmd /k "echo %COMSPEC%"

Test each version. If you have an error or not COMSPEC pointing to your shell, probably a wdx plugin like autostart or the process from wich you launched TC did an unexpected modification...

[lloogg]

What does
set comspec

show? It sounds like the 32-bit version of the command processsor referenced by this option is not found.

For me, it's:

c:\>set comspec
COMSPEC=C:\Windows\System32\cmd.exe

me too.
c:\>set comspec
ComSpec=C:\Windows\system32\cmd.exe

[lloogg]

What does
set comspec

show? It sounds like the 32-bit version of the command processsor referenced by this option is not found.

For me, it's:

c:\>set comspec
COMSPEC=C:\Windows\System32\cmd.exe

to be sure that you have COMSPEC variable well defined inside TC process, in the command field of a test button:
1) just put %COMSPEC%
2) cmd /k "echo %COMSPEC%"

Test each version. If you have an error or not COMSPEC pointing to your shell, probably a wdx plugin like autostart or the process from wich you launched TC did an unexpected modification...

mine works right now.
like before, uninstall, cclean registry, install and suddenly it works!

[holst@wmd.de]

I don't waste any more time on this, using a workaround for calling cmd directly and in the long run using powershell.

By the way: is there something similar to cm_executedos for powershell?

[ghisler(Author)]

COMSPEC=C:\Windows\System32\cmd.exe

32-bit and 64-bit programs see different system32 folders:

32-bit sees SysWow64
64-bit sees SysNative

Make sure that both contain cmd.exe.