- Dec
- 236
- 2
Because I wasn't ready to move everything to version 16, I redefined my short cuts for version 16 to:
"C:\Program Files\JPSoft\TCMD16\tcmd.exe" @"C:\Documents and Settings\myusername\Local Settings\Application Data\JPSoft\16\TCMD.INI"
I also created directories that mirror those for version 15 and they are:
Startup-16
Log-16
Batches-16
So where the TCMD.INI for version 15 said "Startup" the version 16 version would have "Startup-16" and similar with the other directories. But things didn't seem work the way I expected, for example, the "TCSTART/TCEXIT Path" in the version 16 was "C:\JPSoft\Startup-16" but the TCSTART.btm that actually runs is the one in "C:\JPSoft\Startup", the one from the version 15 TCMD.INI.
Also, if I use the "Options" menu from TCMD-16, I can edit the version 16 TCMD.INI but if I type "option" at the command prompt, I am editting the version 15 TCMD.INI.
Does TCC.EXE ignore the fact TCMD is pointing to a different TCMD.INI?
Craig
"C:\Program Files\JPSoft\TCMD16\tcmd.exe" @"C:\Documents and Settings\myusername\Local Settings\Application Data\JPSoft\16\TCMD.INI"
I also created directories that mirror those for version 15 and they are:
Startup-16
Log-16
Batches-16
So where the TCMD.INI for version 15 said "Startup" the version 16 version would have "Startup-16" and similar with the other directories. But things didn't seem work the way I expected, for example, the "TCSTART/TCEXIT Path" in the version 16 was "C:\JPSoft\Startup-16" but the TCSTART.btm that actually runs is the one in "C:\JPSoft\Startup", the one from the version 15 TCMD.INI.
Also, if I use the "Options" menu from TCMD-16, I can edit the version 16 TCMD.INI but if I type "option" at the command prompt, I am editting the version 15 TCMD.INI.
Does TCC.EXE ignore the fact TCMD is pointing to a different TCMD.INI?
Craig
Last edited: