Part of the power of TCC is its flexibility, in allowing you to alter its configuration to match your style of computing. TCC's configuration is controlled through a file of initialization information.
See Locating the .INI files below to find out how TCC locates its TCMD.INI file.
You can create, add to, and modify the TCMD.INI file with the configuration dialog, available via the OPTION command, or (if in a Take Command tab window), the Configure TCC entry in the Options menu.
Most of the changes you make in the OPTION command take effect immediately. A few (e.g., those associated with the startup screen size) only take effect when you start a new TCC session. See the online help for each individual dialog page if you are not sure when a change will take effect.
The dialogs handle most of the configuration options. The Advanced directives and the Key Mapping directives do not have corresponding fields in the configuration dialogs, and must be entered manually.
TCC reads its TCMD.INI file (see Locating the .INI file) when it starts, and configures itself accordingly. The .INI file is not reread when you change it manually. For manual changes to take effect, you must restart TCC.
Each item that you can include in the .INI file has a default value. You only need to include entries in the file for settings that you want to change from their default values.
The password fields in TCMD.INI (for example, the Internet password settings) are encrypted by the OPTION command.
See Directives for information on the types and format of TCMD.INI directives.
Some settings in the .INI file are initialized when you install TCC; others are modified as you use and when you exit TCC.
You can optionally include environment variables in the TCMD.INI [4NT] and [TCMD] sections; they will be expanded when TCMD.INI is loaded. If you want to delay expansion until command execution time (for example, with ColorDir) you will need to double the %'s.
1) When starting TCC (a "primary shell"):
|If there is an @d:\path\inifile option on the startup command line, TCC will use the path and file name specified there.|
|Otherwise, the default .INI file name in the table below is used, and the search starts in the directory where the TCC program file is stored. If the .INI file is not found, TCC will look in the %LOCALAPPDATA% directory.|
If no .INI file is found, all options are set to their default values. A new .INI file will be created, using the default location and name, as explained above.
2) When starting TCC (a "secondary" shell) from another TCC shell:
TCC retrieves the primary shell's .INI file data, processes the [Secondary] section of the original .INI file if necessary, and then processes any @d:\path\inifile option on the secondary shell command line.
See Command Line Options for more details about the startup command line.
The TCMD.INI file has a number of sections. Each section is identified by the section name in square brackets on a line by itself. Take Command stores the user-defined options in [TakeCommand]; TCC stores its user-defined options in [4NT].
The [Primary] and [Secondary] sections include directives that are used only in TCC primary and secondary shells, respectively. You don't need to set up these sections unless you want different directives for primary and secondary shells.
Directives in the [Primary] section are used for the first or primary shell. The values are passed automatically to all secondary shells, unless overridden by a directive with the same name in the [Secondary] section.
Directives in the [Secondary] section are used in secondary shells only, and override any corresponding primary shell settings.
Note that the terms Primary and Secondary Shells are now mostly obsolete in Windows. The interaction between Primary and Secondary TCC shells is limited to some minor inheritance (due to the design of Windows).