PWBAt the end of installation, SETUP creates system-configuration files. These are listed in Table 2.1, along with SETUP's default directories:
Table 2.1 SETUP Configuration Files
| Operating System | Configuration Files | Default Directory |
| DOS or OS/2 real mode | NEW-VARS.BAT, NEW-CONF.SYS | C:\MASM\BIN |
| TOOLS.PRE | C:\MASM\INIT | |
| OS/2 protected mode | NEW-VARS.CMD | C:\MASM\BINP |
| TOOLS.PRE | C:\MASM\INIT |
If you add the contents of these files to your AUTOEXEC.BAT (or STARTUP.CMD), CONFIG.SYS, and TOOLS.INI files, your system will be correctly configured for MASM each time you start your computer. You can also run NEW-VARS.BAT or NEW-VARS.CMD to set environment variables before you run MASM.
The NEW-VARS.BAT and NEW-VARS.CMD files contain commands that set environment variables. Insert these commands in the AUTOEXEC.BAT or STARTUP.CMD file. All changes to environment variables are prefixed to the current settings. Table 2.2 explains these variables.
Table 2.2 Environment Variables
| Variable | Description |
| ASMEX | Location of assembly-language example files |
| HELPFILES | Location of help (.HLP) files |
| INCLUDE | Location of include (.INC) files |
| INIT | Location of initialization (.INI) files |
| MASM, ML | List of command-line options requested |
| PATH | Path to search for executable files |
| QH | Location of QuickHelp help (.HLP) files |
| TMP | Location of PWB/LINK temporary files |
The online reference system searches for help files in a specific sequence. Therefore, do not modify the HELPFILES variable unless you are familiar with the search sequence. Changing this path might make the online reference system inaccessible.
If the host operating mode is OS/2 real mode or DOS, check the values of files and buffers in CONFIG.SYS. The values in NEW-CONF.SYS are minimums; the CONFIG.SYS values should be at least as large.
Under OS/2, be sure the LIBPATH variable includes the directory of the help system's dynamic-link library MSHELP.DLL. OS/2 users who want to use CodeView must also include the statement IOPL=YES.
To use the extended memory features of CodeView under DOS, you must use the HIMEM.SYS driver supplied with this product. Add DEVICE=HIMEM.SYS to CONFIG.SYS. Be sure to specify HIMEM's full path. See the section later in this chapter called “Configuring Extended Memory for CodeView” for additional information.
The TOOLS.PRE file contains additional PWB configuration settings. Add the contents of TOOLS.PRE to your existing TOOLS.INI file. If you don't already have a TOOLS.INI file, rename TOOLS.PRE to TOOLS.INI.
PWB looks for TOOLS.INI in the directory containing PWB. If you move TOOLS.INI to another directory, specify its path in the INIT environment variable in your AUTOEXEC.BAT or STARTUP.CMD file.
The TOOLS.INI file controls many configuration options for MASM 6.0 utilities. These options let you customize the following:
PWB
CodeView debugger
Microsoft Advisor online reference system
NMAKE utility
You can modify the TOOLS.INI settings with the PWB editor or any word processor. These are some of the options you can change:
Screen colors and the number of lines displayed by PWB
Macros for PWB
Key assignments for PWB
Default key settings for PWB
Location of help files used by the online reference system
Options for NMAKE
TOOLS.INI is described in the online reference system. See Chapter 14 of the Programmer's Guide for more information about customizing PWB.