You will typically start CMDebug from a Windows shortcut, located:
•on the desktop, or
•in the Programs section of the Start menu (including its Startup subdirectory).
You may also start it from the Start / Run dialog.
The installation software will optionally create both a CMDebug folder or group (in the Programs section of the Start menu) and a desktop object (shortcut) which starts CMDebug. Usually these are sufficient, but if you prefer, you can create multiple desktop objects or items to start CMDebug with different startup commands or options, or to run different applications in the tab windows.
When you configure a CMDebug item, place the full path and name for the file in the Command Line field, and put any startup options that you want passed to CMDebug. For example:
|Command Line:||C:\Program Files\JPSoft\CMDebug 25\CMDEBUG.EXE|
You do not need to use the Change Icon button, because CMDEBUG.EXE already contains icons.
Each Windows program has a command line which can be used to pass information to the program when it starts. The command line is entered in the Command Line field for each shortcut or each item in a Program Manager group (or each item defined under another Windows shell), and consists of the name of the program to execute, followed by any startup options.
The CMDebug startup command line does not need to contain any information. However, you may add information to the startup command line that will affect the way CMDebug operates.
CMDebug Startup Options
The CMDebug command line includes the program name with drive and path, followed by any options. For example:
There are several CMDebug startup options. The complete syntax for the CMDebug startup command line is (all on one line):
d:\path\cmdebug.exe [[/]@d:\path\inifile] [//directive=value...] [/D d:\path] [/N /X] [/C command] [/T [d:\path\]program]
(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.)
The command line must start with the full CMDebug path and executable name (CMDEBUG.EXE):
If you are creating & debugging TCC-RT batch files, there are some additional options for the CMDebug command line.
The additional items below may be included on the command line):
This option sets the path and name of the .INI file. You don't need this option if:
|1)||your .INI file is named TCMD.INI, and|
|2)||it is in one of the following directories:|
|2.1)||the same directory as CMDebug|
2.2) the "%programdata%\JP Software\CMDebug 21" directory
|2.3)||the %localappdata% directory|
This option is most useful if you want to start the program with a specific and unique .INI file.
To start CMDebug without any .INI file, you can 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
CMDebug will skip the leading forward slash.
This option tells CMDebug to treat the text appearing between the // and the next space or tab as an initialization directive. The directive should be in the same format as a line in TCMD.INI, 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.
|/A||This option causes the output of internal commands to a pipe or redirected to a file to be in ASCII when CMDebug starts. This is the default value, and isn't necessary unless you want to override a Unicode Output configuration option.|
|/C||If the specified batch file doesn't exist, create it without prompting.|
|/D||Disable execution of AutoRun commands from Registry. If /D is not specified when CMDebug starts, it will look for and execute the following registry variables:|
and / or
|/I||Don't load the .INI file, execute TCSTART or TCEXIT, or load plugins. You can optionally specify any combination of individual arguments:|
|/II||Don't load the .INI file.|
|/IL||Don't load the default library functions.|
|/IP||Don't load plugins.|
|/IS||Don't execute TCSTART.|
|/IX||Don't execute TCEXIT.|
For example, /IILPSX will disable everything.
|/L:||Forces the use of local lists as the default for aliases, functions, directory history and command history, overriding any configuration options. This method allows you to use global lists as the default, but start a specific session with local aliases, functions and histories. See the topics ALIAS and FUNCTION for more details.|
|You can optionally specify individual arguments:|
|/LA||Forces the use of local aliases.|
|/LD||Forces the use of a local directory history.|
|/LF||Forces the use of local functions.|
|/LH||Forces the use of a local command history list.|
|/S||Disable ^C and ^Break.|
|/T:bf||This option sets the foreground and background colors in the CMDebug command window. Both b and f are hexadecimal digits. b specifies the background color and f specifies the foreground color. This option is included only for compatibility with CMD. See the CMD color codes in Colors, Color Names & Codes.|
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.
|/U||This option causes the output of internal commands to a pipe or redirected to a file to be in Unicode when TCC starts. The command :|
OPTION //UnicodeOutput=yes | no
may be used at any time to switch between Unicode and ASCII output.
|/U8||This option causes the output of internal commands to a pipe or redirected to a file to be in UTF-8 when TCC starts. The command :|
OPTION //UTF8Output=yes | no
may be used at any time to switch between UTF-8 and ASCII output.
|/V||Tells CMDebug to handle the CMD syntax !varname! as a delayed expansion of %varname. Since CMD, unlike TCC or TCC-RT, doesn't support delayed expansion of variable references in the %varname% format, it introduced a special !varname! notation. Using /V simply tells TCC to handle that syntax as an alternative to %varname% or %varname or %[varname].|
|/X||This option forces CMDebug to alter the operation of the MD (MKDIR) command to automatically create all necessary intermediate directories when it creates a new subdirectory. Its effect is the same as adding a /S option to all MD (MKDIR) commands. This option is included for compatibility with CMD, where it also enables other options. However, in CMDebug those options are already enabled by default.|