TCMD 14 Ignores Argument

Jun 2, 2008
376
2
Newton, MA
When I launch TCMD 14 with a shortcut comtaining the command

"C:\Program Files\JPSoft\TCMD14x64\tcmd.exe" /@C:\Users\Jay\AppData\Local\JPSoft\tcmd14.ini

or if I issue that command from the command with (with or without the '/' before '@', the argument is ignored. The variable %_ininame says that the INI command is tcmd.ini, not tcmd14.ini.

Am I doing something wrong, or is this a bug. Is there a better way to keep my configurations for version 13 and 14 separate from each other?

Now I see that with version 13, launching TCC with that argument (but with 13 instead of 14) also fails to access the designated INI file. But an INI file in "C:\Program Files\JPSoft\TCMD13x64" is used. I must be forgetting how these arguments work.

-- Jay
 
When I launch TCMD 14 with a shortcut comtaining the command

"C:\Program Files\JPSoft\TCMD14x64\tcmd.exe" /@C:\Users\Jay\AppData\Local\JPSoft\tcmd14.ini

or if I issue that command from the command with (with or without the '/' before '@', the argument is ignored. The variable %_ininame says that the INI command is tcmd.ini, not tcmd14.ini.
Isn't %_ininame the ini file for the shell, not for TCMD?
 
May 20, 2008
11,400
99
Syracuse, NY, USA
When I launch TCMD 14 with a shortcut comtaining the command

"C:\Program Files\JPSoft\TCMD14x64\tcmd.exe" /@C:\Users\Jay\AppData\Local\JPSoft\tcmd14.ini

or if I issue that command from the command with (with or without the '/' before '@', the argument is ignored. The variable %_ininame says that the INI command is tcmd.ini, not tcmd14.ini.

Am I doing something wrong, or is this a bug. Is there a better way to keep my configurations for version 13 and 14 separate from each other?

Now I see that with version 13, launching TCC with that argument (but with 13 instead of 14) also fails to access the designated INI file. But an INI file in "C:\Program Files\JPSoft\TCMD13x64" is used. I must be forgetting how these arguments work.

-- Jay
You're telling TCMD to start with that INI file and it probably is doing do. But _ININAME gives the INI file used by TCC. You might do well to edit COMSPEC in the options for a particular TCMD and specify there the INI file you want the default TCC to use.
 
Jun 2, 2008
376
2
Newton, MA
You're telling TCMD to start with that INI file and it probably is doing do. But _ININAME gives the INI file used by TCC. You might do well to edit COMSPEC in the options for a particular TCMD and specify there the INI file you want the default TCC to use.

I had the same thought, but as I wrote in my original message, I tried running a TCC command (not TCMD) with the same argument and got the same result.

I just went into my TCMD14 configuration to try adding the argument to the COMSPEC and tab command line -- and I noticed something strange. Although %_ininame reports TCMD.INI, the top border of the TCMD option screen shows TCMD14.INI! Something doesn't seem right here. And checking the time stamps on the files, I see that TCMD14.INI is the one being changed.

Well, this may be the result of the change taking effect the minute I saved the configuration. A new TCC tab reports %_ininame with TCMD14.INI.

Now I went back and tried to make a similar change in TCMD13, and the INI file did not change for the current tab. Oh, that's probably because the current INI file location is in the program files directory, so I probably have to open TCMD in admin mode to make any changes. What's the chance that I'll remember all this when version 15 comes out!!!

-- Jay
 
May 20, 2008
3,515
4
Elkridge, MD, USA
The answer is simple.Do not install in the default locations. My installations are in F:\JPSOFT\Inn, where nn=05, 06, ..., 14 (I stands for "interpreter"). My .INI files are actually in F:\JPSOFT, which is also my startup directory, and named Vnn.INI. Each version has its own desktop shortcut; the most recent versions even have hotkeys. One of the nice things about WinXP hotkeys is that if the version is already running, but is not the foreground window, e.g., it is minimized, the hotkey brings it into the foreground, so I can immediately start typing.
 
May 20, 2008
11,400
99
Syracuse, NY, USA
I just went into my TCMD14 configuration to try adding the argument to the COMSPEC and tab command line -- and I noticed something strange. Although %_ininame reports TCMD.INI, the top border of the TCMD option screen shows TCMD14.INI! Something doesn't seem right here. And checking the time stamps on the files, I see that TCMD14.INI is the one being changed.

If, in TCMD, you go to Options\Configure (either TCMD or TCC) you're going to be configuring the INI file that TCMD was started with. TCMD does not keep track of the fact that your COMSPEC specifies a different INI file for TCC (COMSPEC may not point to TCC at all). If, inside TCMD, you want to get at the INI file used by a TCC, use TCC's OPTION command.
 
Similar threads
Thread starter Title Forum Replies Date
D Bug TCMD /X option Support 6
vefatica TCMD hides itself! Support 3
vefatica Tray min'd TCMD and ACTIVATE Support 6
C How to? starting TCC/TCMD v25 Support 2
CWBillow TCC and TCMD in Powershell Support 6
kb6ojs How to? "Specified Account Already Exists" error installing TCMD v27 Support 12
CWBillow TCMD Colors Support 8
Jay Sage Issues With TCMD File Explorer Support 0
C Last TCMD that supports win 7? Support 5
gentzel TCMD background color confusion Support 6
R Upgrade TCMD 19 to TCC 26 Support 1
Alpengreis Remaining TCMD background process (v26) ... Support 19
S Windows Server version not being detected correctly in TCMD 26RC2 Support 9
G TCMD crash when copy Support 3
Joe Caverly DrawVLine results different in TCMD tab and detached TCC Support 11
Alpengreis [TCMD v25.00.24] Small space problem with the DE translation in Prefs-GUI Support 1
Alpengreis [TCMD v25.00.24] Problem with copy and paste and the # char via mouse in TCC Support 6
Jay Sage TCMD Crashes with "tctoolbar /c /r file" Support 5
nikbackm TCMD 25 - Unregister older TCMD version Support 2
G Documentation on TCMD.INI Support 9
R New Clear Buffer in TCMD Home Menu Support 2
CWBillow Back up TCMD tabs Support 2
CWBillow Upgrade Windows 10's effect on TCMD and TCC Support 3
DrusTheAxe TCMD 24.02.49 x64 crashed due to DivideByZero :-( Support 4
A After update to 24.02.49, helpfile tcmd.chm hangs when opened Support 0
David McClelland TCMD 24 & Perl - perl thinks it's own executable is ...\TCMD24\TCC.EXE??? Support 3
dcantor How to? Can 32-bit TCC be run on a system with 64-bit TCMD and TCC installed? Support 6
W pdir returns diff results between tcc and tcmd - one is an error msg Support 5
vefatica What's TCMD's problem with ^e[0m? Support 13
CWBillow TCMD PowerShell Tab elevated Support 6
A How to? Copy+Paste in TCMD tabs with Ctrl-Shift-Ins? Support 5
vefatica TCMD output invisible on Win10 Support 22
J Moving from TCC v22 to TCMD v24 issues Support 3
RChrismon How to? Copy TCMD.INI to New Version Support 7
rps TCMD OPTIONS dialog Support 2
rps TCMD Tabs priority option setting Support 0
D Can we fix the scaling for TCmd? Support 14
CWBillow TCMD Tab Defs Support 4
A How to? TCMD Configuration Dialog: 'Smooth Scrolling' Option missing? Support 1
A Fixed [23.0.22]: TCMD crashes shortly after start, TCC keeps running in background Support 6
A TCMD - Dir Command puts out blank lines? Support 16
P Symantec Endpoint Protection trapped TCMD.EXE and said it contained WS.Reputation.1 (Virus?) Support 3
Emilio III TCMD Tab titles on Insider Windows Support 2
kb6ojs Want to start TCMD v20 with every Windows 10 bootup Support 3
D Tcmd 22.00.42 - annoying desktop refresh Support 47
CWBillow Context menu extensions for TCC/TCMD v18? Support 1
vefatica Pasting into TCMD via right-click menu? Support 2
M Please explain TCMD's ANSI x3.64 support Support 4
CWBillow Powershell tab in TCMD? Support 2
D Custom ini-file is not read, by tcmd.exe cli Support 6

Similar threads