The Microsoft C/C++ SETUP program installs all the necessary CodeView files and correctly configures CodeView for your selected environment. Make sure that all of the CodeView executable files (.EXE and .DLL files) are in a directory listed in the PATH environment variable.
In addition, it is highly recommended that you merge the entries in the TOOLS.PRE file with your TOOLS.INI file. SETUP creates TOOLS.PRE in the INIT directory that you specify when you run SETUP. If you do not already have a TOOLS.INI file, rename TOOLS.PRE as TOOLS.INI.
This file contains the recommended settings to run CodeView for MS-DOS and CodeView for Windows. For more information on the entries in TOOLS.INI, see “Configuring CodeView with TOOLS.INI”.
CodeView version 4.0 introduces a new, flexible architecture for the debugger. CodeView is made up of a main executable program: CV.EXE (CodeView for MS-DOS) or CVW.EXE (CodeView for Windows) and a collection of dynamic-link libraries (DLLs). Each DLL implements an aspect of the debugging process.
The following table summarizes CodeView's component DLLs:
| TOOLS.INI Entry | Component | Required | Example |
| Eval | Expression evaluator | Required | C or C++ |
| Model | Additional nonnative execution model | Optional | P-code |
| Native | Native execution model | Required | MS-DOS or Windows |
| Symbolhandler | Symbol handler | Required | MS-DOS or Windows |
| Transport | Transport layer | Required | Local or remote |
This architecture allows for the implementation of such improbable debugging configurations as a Windows-hosted debugger that debugs interpreted Macintosh programs across a network. The existing CVW.EXE could be used with new transport, symbol handling, and execution model DLLs. Instead of creating completely different programs for each combination of host and target, all that is needed is the appropriate set of DLLs.