The command line that starts TCC will typically include the program name with drive and path, followed by any options. For example:

 

"c:\program files\jpsoft\tcmd28\tcc.exe" @c:\jpsoft\tcmd.ini

 

Although the startup command line is usually very simple, you can add several options. You can do this manually in the Windows RUN dialog, in a Windows shortcut file (.LNK), at the TCC prompt or in a batch file (with or without using the internal START command). Each of these methods will start a new instance of the selected command processor, which will run in a new window, except when TCC is started from TCC (either at the command prompt or within a batch file) without the START command.

 

When you use a pipe in a command, either at the command prompt or in a batch file, TCC starts another instance of itself, using the same command line parameters (except as required for the pipe).

 

The complete syntax for the TCC startup command line is (all on one line):

 

d:\path\tcc.exe [d:\path] [[/]@d:\path\inifile] [//directive=value...] [/A /H /I[IPSX]/L: /LA /LD /LF /LH /N/Q /S /T:bf /U /V /X ] [/C | /K] [command]

 

Do not include the square brackets shown in the command line above. They are there to indicate that the items within the brackets are optional. Some options are available only in specific products; see below for details.

 

If you include any of the options below, you should use them in the order that they are described. If you do not do so, you may find that they do not operate properly.

 

The command line must start with the path and name of the executable program file (TCC.EXE):

 

d:\path\tcc.exe

 

The additional items below may be included on the command line:

 

d:\path

 

If included, this second copy d:\path of TCC path must be identical to d:\path in the command line segment above. It sets the drive and directory where the program is stored, called the COMSPEC path. This option is included for compatibility with other character mode command processors, but is not needed in normal use. TCC can find its own directory without a COMSPEC path.

 

 

This option sets the path and name of the .INI file. You don't need this option if

 

 

This option is most useful if you want to start the program with a specific and unique .INI file.

 

To start TCC without any .INI file, you can use the /I or /II options, or create an empty file and specify it as your .INI file.

 

To get around a Windows limitation that causes the displayed command line of a shortcut to be truncated when a parameter begins with @, you can use the alternative syntax

 

/@d:\path\inifile

 

TCC will skip the leading slash.

 

 

This option tells TCC to treat the text appearing between the // and the next space or tab as a directive. The directive should be in the same format as a line in the .INI file, but may not contain spaces, tabs, or comments. This option may be repeated. It is a convenient way to place a few simple directives on the startup line without having to modify or create a new .INI file.

 

Directives on the command line override any corresponding directive in the .INI file.

 

 

 

Warning: It may cause the system to operate incorrectly if you use this option without other software to handle Ctrl-C and Ctrl-Break. This option should be avoided by most users.

 

 

HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun

 

and / or

                                                                                                                                                           

 HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun

 

See also the AutoRun configuration option.

 

 

 

 

 

 

 

 

 

 

In most cases you should set default colors with the corresponding Output Colors configuration option. If you use both, the /T switch overrides the configuration options.

 

 

OPTION //UnicodeOutput=yes | no

may be used at any time to switch between Unicode and ASCII output.

 

 

OPTION //UTF8Output=yes | no

may be used at any time to switch between UTF-8 and ASCII output.

 

 

 

/C command   or

/K command   or

command

 

 

 

 

All other startup options must be placed before command, because TCC will treat characters after command as parameters for command and not as additional startup options.

 

If command is preceded by /C, TCC will execute command and then exit, returning to the parent program or the desktop without displaying a prompt.

 

The /K switch has no effect. Using it is the same as placing command (with neither /C nor /K) at the end of the startup command line. It is included only for compatibility with CMD.

 

Example 1

 

Assume that you execute the command line below:

 

c:\TCMD\TCC.exe c:\TCMD\start.btm

 

The events below will take place in the order shown:

 

TCStartPath=c:\start

and one of the files

c:\start\tcstart.btm

c:\start\tcstart.bat

c:\start\tcstart.cmd

c:\start\tcstart.exe

c:\start\tcstart.com

exists, that file is executed by TCC.

 

Example 2

 

The command line below, when executed by TCC, CMD, the RUN dialog, or a shortcut, will start TCC, select local aliases, execute any TCSTART file you have created, execute the file PROCESS.BTM, and exit. No prompt will be displayed by this session:

 

c:\tcmd28\tcc.exe /la /c c:\tcmd28\process.btm