Remote debugging requires two computers. The host system must support the Microsoft C/C++ development system. The target system needs only enough resources to run the remote monitor and your program. You run the MS-DOS CodeView on the host system, and you run either the MS-DOS remote monitor or the Windows remote monitor, according to the type of program you are debugging.
You connect the host and target machines with a null-modem cable plugged into the serial ports on the two machines. A null modem is a serial cable that connects the transmitting line at each end to the receiving line at the opposite end. For CodeView, you can tie all control lines to a TRUE signal. Note that such a cable may not be suitable for use with other software. You cannot use an extension cable with “straight-through” connections.
Any good computer store can assemble a null-modem cable for you with the correct wiring and the appropriate connectors for your host and target machines.
CodeView's serial transport layers use interrupt-driven input and output, which is supported in MS-DOS only with the COM1 and COM2 ports. Therefore, your machines must be connected using the COM1 or COM2 ports. You can use different ports on the two machines.
If you plan to debug with two machines, you must have the correct files in the correct locations on the host and target. You can start a remote session with a TOOLS.INI file that configures CodeView for local debugging. However, it is recommended that you configure CodeView for remote debugging in TOOLS.INI.
For remote debugging, you must have the CodeView debugger CV.EXE and its associated DLLs on the host machine. The SETUP program copies all the required files when you install the development system.
You configure CodeView for remote debugging by setting entries in the TOOLS.INI configuration file. The settings for CodeView appear in the [CV] tagged section of TOOLS.INI. Your settings should specify the DLLs for remote debugging. Most of the entries are the same for local and remote debugging. The only differences are the Native and Transport entries.
The remote debugging configuration is described in the following table:
| Entry | Value | Description |
| Symbolhandler | SHD1.DLL | MS-DOS symbol handler. | |
| Eval | EED1lang.DLL | Expression evaluator. You must load at least one expression evaluator. Use EED1CAN.DLL for C or MASM. Use EED1CXX.DLL for C++, C, or MASM. | |
| Model | NMD1PCD.DLL | P-code execution model. To debug p-code, you must load the p-code nonnative execution model. Specify this entry only if you are debugging p-code. | |
| , | |||
| Transport | TLD1COM.DLL | The serial transport layer. (For local debugging, use TLD1LOC.DLL.) | |
| Native | EMD1D1.DLL EMD1W0.DLL | Execution model. The execution model that you use depends on the target. Use EMD1D1.DLL for MS-DOS targets or EMD1W0.DLL for Windows targets. | |
For more information on configuring CodeView, see “Configuring CodeView with TOOLS.INI”.
You must have your program's executable file on both the host and target machines. The program must have the same path on the host and target machines, including drive letter and all directories. The filenames must be identical. For Windows applications, you must also have your application's DLLs (if any). The DLLs that you want to debug must also have the same path on the host and target machines.
For remote debugging of an MS-DOS program, you need the MS-DOS remote monitor RCVCOM.EXE on the target machine along with your program's executable file. The program must have the same path on the host and target machines, including drive letter and all directories. The filenames must be identical.
You can set default parameters for the remote monitor in the [RCVCOM] section of a TOOLS.INI file on the target machine. For more information, see “Remote Monitor Settings in TOOLS.INI”.
For remote debugging of a Windows application, you need the Windows remote monitor RCVWCOM.EXE and its support DLLs on the target machine along with your application's executable files. The application and DLL files that you are debugging must have the same path on the host and target machines, including drive letter and all directories. The filenames must be identical.
The Windows remote monitor (RCVWCOM.EXE) and its support DLLs
(TOOLHELP.DLL and DMW0.DLL) must be in a directory listed in the PATH environment variable.
You can set default parameters for the remote monitor in the [RCVWCOM] section of a TOOLS.INI file on the target machine. For more information, see “Remote Monitor Settings in TOOLS.INI”.