Starting CMDebug

<< Click to Display Table of Contents >>

Navigation:  CMDebug IDE / Batch Debugger >

Starting CMDebug

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 21\CMDEBUG.EXE
Working directory:C:\

 

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:

 

"c:\program files\jpsoft\cmdebug21\cmdebug.exe"

 

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):

 

 d:\path\cmdebug.exe

 

TCC-RT Syntax

 

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):

 

@d:\path\inifile OR
/@d:\path\inifile

 

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

 

 /@d:\path\inifile

 

CMDebug will skip the leading forward slash.

 

Options:

 

//directive=value

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.

 

/CIf the specified batch file doesn't exist, create it without prompting.

 

/NDon't load TCMD.INI (useful when trying to isolate configuration problems).

 

/XRetrieve and store the CMDebug window layout in a file (TCMD.XML) instead of the Windows Registry. This is for systems where the administrator has locked registry write access (even to HKEY_CURRENT_USER).  The TCMD.XML file must be in the same directory as TCMD.INI.