Best Practice for TCMD11 Windows7 64

Jun 16, 2010
6
0
#1
Could someone explain what the best way is to configure Take Command in Windows 7.

I understand from the installer that the program should be installed installed in the x86 program files. But where is the tcmd.ini file installed?
And where should the TCstart.btm be runned from?

I have a lot of .ini and btm files that are being changed when TCMD starts. So placing them in the "program files" isn't an option.
Correct me if I'm wrong but as I understand it, the Windows fileprotection revert them back to the original files when TCMD is stopped.

Arjan
 

dim

Dimitry Andric
May 31, 2008
205
1
Netherlands
#2
On 2010-06-17 14:39, AFeddema wrote:

> Could someone explain what the best way is to configure Take Command in Windows 7.
>
> I understand from the installer that the program should be installed installed in the x86 program files. But where is the tcmd.ini file installed?
> And where should the TCstart.btm be runned from?
If you install the x64 version of Take Command, install in "C:\Program
Files", e.g. the x64 program files dir. If you install the x86 version,
install it into "C:\Program Files (x86)".

The installer does not install a .ini file, but Take Command will
automatically create one under %LOCALAPPDATA%\JPSoft, usually this is
"C:\Users\%USERNAME%\AppData\Local" under Vista or Windows 7.

You can put TCStart.btm and TCExit.btm anywhere you like, this is an
option which you can find in the TCC OPTION dialog under the Startup
tab. The most logical place is IMHO again the %LOCALAPPDATA%\JPSoft
directory, I also put my alias/function definitions there, and any
optional history logging goes there too.



> I have a lot of .ini and btm files that are being changed when TCMD starts. So placing them in the "program files" isn't an option.
> Correct me if I'm wrong but as I understand it, the Windows fileprotection revert them back to the original files when TCMD is stopped.
I guess you are running into the "virtual program files" feature that MS
created to make older apps run on Vista and higher with UAC. As far as
I know, these files should be saved anyway, but somewhere under your
profile directory instead of the program files directory.
 
#3
Regardless of where you install TCMD, you can specify the directory in
which your .INI file is located (and even provide an alternate name) in the
shortcut which starts TCMD. If that directory is not a restricted one, you
should have no problems with modifying them without the OS reverting them.
I have always installed all JP Software products in subdirectories of
x:\JPSOFT, where x is not always C. This makes it easy to have concurrent
installations of different versions, and sharing as much as possible. It
also makes it easier to have a PLUGINS subdirectory of the installation
directory, whose contents can be more easily updated.
--
HTH, Steve