The [TRMW] section of the DP4 configuration file contains a large number of possible entries which can be used to configure the behaviour of the DP4 terminal manager. Unless otherwise noted, any entry for the TRMW] section may also be specified in a program specific section. For example you could force a program called MYPROG.EXE to use special values for entries in the [TRMW] section by supplying corresponding entries in the [MYPROG] section. Such entries always take precedence over values specified in the [TRMW] section itself.
Some entries in the [TRMW] section are read when an application starts, and cannot be changed afterwards. Others may be changed by calling the
trm_set_progname() function, which can be used to over-ride the section used for accessing the [TRMW] entries. When a QAB program is first loaded it always calls this function, and sets the program name to the name of the QAB program. When trm_set_progname() is called the terminal manager rereads these variables, and may change the appearance, size or position of the application window as a result. Other variables are only read when they are needed and so always use the current program name. Entries marked below with an asterisk (*) are those which are either reread when QAB programs are loaded or when a C application calls the trm_set_progname() function, or which are only read as required and hence automatically use the current program name.
Many entries in the [TRMW] section are also used by the DFPRINT program. However in this case the values can, from 4.621, be overridden in the [DFPRINT] section as well as on a per-application basis.
Entries:
From 4.621 there are some additional entries that can be used as part of the skinning facilities. See Configuration file entries for bitmaps for details.
From Release 4.621(8) you can map the device names used for printing directly (i.e. not via DFPRINT) to other ports. For example if a program needs to print to a bluetooth device on a virtual COM port such as COM5, then create a print device for it using a device that you do not need, LPT3 perhaps, and add LPT3=COM5: to DP4.INI, either in the [trmw] section (if you are absolutely certain this will not cause problems for DP4 programs printing to another device), or in a [progname] section. This avoids the need for using the MODE command to redirect an LPT device to a COM port.
On Windows CE you must include the trailing : on the device name: DP4 will not add it for you, and the device will not be opened correctly without it.