cm_executedos in TC 9 beta 14 does not work

[holst@wmd.de]

starter menu and direct call lead to "insufficient memory"

[Stefan2]

Hi and welcome holst

Which TC8b14? 32- or 64-bit?

Which Windows? Win10? 32- or 64-bit?


What happens if you execute 'cmd' command on your windows?





 

[Ovg]

2holst@wmd.de

Can't confirm. Working fine here. TC 9.0 β14 x86/x64, Windows 7 SP1 x64

[holst@wmd.de]

Hi and welcome holst

Which TC8b14? 32- or 64-bit?

Which Windows? Win10? 32- or 64-bit?


What happens if you execute 'cmd' command on your windows?

 

TC 9 beta 14 both 32bit and 64bit on Win7 64bit fully patched

Calling cmd directly works fine.

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")

Normally I use it from the starter menu. Titel: "cm&d" Command: cm_executedos

Did not happen with TC 9 beta 13. I'm using the cmd this way very often.

Starting TC without wincmd.ini and using "cm_executedos" in commandline leads also to: "not enough memory" (this time in english due to the missing wincmd.ini.

Hint: UAC on the system is disabled by company policy (no kidding).

[TieFighter]

Not Confirmed for Windows 7 X64 and TC 09.00 X32 or X64

[sqa_wizard]

holst@wmd.de: Just a hit in the dark: Do you have a file named "noclose.pif" at you TC directory or even at your windows directory?

Note: I don't mean the "noclose.exe", this is normal.
The "noclose.pif" is a deprecated file which may point to the wrong cmd file.

[petermad]

Not Confirmed for Windows 7 sp1 x64 and TC9b14 x86 and x64

[holst@wmd.de]

holst@wmd.de: Just a hit in the dark: Do you have a file named "noclose.pif" at you TC directory or even at your windows directory?

Note: I don't mean the "noclose.exe", this is normal.
The "noclose.pif" is a deprecated file which may point to the wrong cmd file.

@sqa_wizard: Thanks for the hint

Only "noclose.exe" in

c:\totalcmd\NOCLOSE.EXE
c:\totalcmd\NOCLOSE64.EXE

No "noclose.pif".

Deinstalled beta14 installed beta9 and afterwards beta13 und beta14.
Same problem with all 3 beta's, so it must be a configuration problem on my machine.

Enabling UAC on the machine does not change behaviour.
Disabling Antivirus on the machine does not change behaviour.

Have to dig deeper

@ghisler

Deinstallation is running without problems. After dialogue "Programm erfolgreich entfernt" and clicking on "OK" I get:

---------------------------
Error
---------------------------
Runtime error 216 at $0000000000410533

$0000000000410533

$00000000323136A0
---------------------------
OK
---------------------------

[petermad]

2holst@wmd.de

it must be a configuration problem on my machine.

Have you tried with a clean wincmd.ini file?

[holst@wmd.de]

2holst@wmd.de

it must be a configuration problem on my machine.

Have you tried with a clean wincmd.ini file?

Yep, see: Posted: Tue Sep 20, 2016 1:27 am

[sqa_wizard]

Another one:
If you use cmd directly you got the command window.
Just enter SET and get a list of system variables.

What is the value of "ComSpec" ?

[ghisler(Author)]

Are you able to run NOCLOSE.EXE or NOCLOSE64.EXE ? That's what TC has been using for a while instead of noclose.pif.

They both run the program defined in %COMSPEC% envrionment variable, which usually points to cmd.exe.

[holst@wmd.de]

Are you able to run NOCLOSE.EXE or NOCLOSE64.EXE ? That's what TC has been using for a while instead of noclose.pif.

They both run the program defined in %COMSPEC% envrionment variable, which usually points to cmd.exe.

Value of comspec:

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

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.

I checked the system drive and %PATH% for the existence of noclos*.exe.
There are only the two in the tc directory.

Following the whole output of set, minimally redacted (computername/domainname). Just for being as complete as possible.

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Holst\AppData\Roaming
APR_ICONV_PATH=C:\Program Files (x86)\Subversion\iconv
BPADir=C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power Tools\Best Practices Analyzer\
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME="changed"
COMSPEC=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Holst
LOCALAPPDATA=C:\Users\Holst\AppData\Local
LOGONSERVER=\"changed"
MOZ_PLUGIN_PATH=C:\Program Files\Tracker Software\PDF Viewer\Win32\
NewEnvironment1=C:\Program Files (x86)\IRISPowerscan\
NewEnvironment2=C:\IRISPowerscan
NUMBER_OF_PROCESSORS=8
OPENSSL_CONF=C:\Program Files\PostgreSQL\psqlODBC\etc\openssl.cnf
OS=Windows_NT
Path=C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;c:\Program Files (x86)\ctags\;c:\Program Files\sysinternals\;C:\Program Files (x86)\Kensington\TrackballWorks;C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\Subversion\bin;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Git\cmd;C:\Program Files (x86)\nodejs\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Anaconda3\Library\bin;C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power Tools\Best Practices Analyzer\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Users\Holst\AppData\Roaming\npm
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 94 Stepping 3, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=5e03
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\
PUBLIC=C:\Users\Public
PYTHONPATH=C:\Anaconda3;C:\Anaconda3\DLLs;C:\Anaconda3\LIB
RanorexPath=C:\Program Files (x86)\Ranorex 6.0\
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\Holst\AppData\Local\Temp
TMP=C:\Users\Holst\AppData\Local\Temp
USERDNSDOMAIN="changed"
USERDOMAIN="changed"
USERDOMAIN_ROAMINGPROFILE="changed"
USERNAME=Holst
USERPROFILE=C:\Users\Holst
VSTO_SUPPRESSDISPLAYALERTS=0
windir=C:\Windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log

[ghisler(Author)]

How about running them from the TC command line at the bottom? It uses CreateProcess instead of ShellExecuteEx, because CreateProcess supports longer command lines up to 32767 character instead of just 8191 characters.

[petermad]

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.