EMD1D1.DLL for debugging an MS-DOS program.After the CodeView components are in their locations and properly configured, you can begin a remote debugging session.
·To start a remote debugging session:
1.Transfer your program and its DLLs to the target machine.
You can copy the files to a floppy disk, transfer them across a network, or transfer them across the serial line using communications software or serial file-transfer software.
Make sure that the full path of the program on the target machine exactly matches the full path of the program on your host machine. The directory structures for your program's files on the host and target machines must also match exactly. If the paths of the files do not match, the remote monitor is unable to locate the program.
2.Start the remote monitor. If you are debugging a Windows application, double-click the Windows remote monitor icon or use the Run command from the Program Manager File menu. For an MS-DOS program, start the monitor from the command line.
The remote monitor starts and begins polling the communications port. It waits for the host debugger to initiate the debugging session.
3.Start CodeView on the host machine. How you start CodeView depends on your settings in TOOLS.INI.
If you have configured CodeView for remote debugging in TOOLS.INI, you can specify a program on the CodeView command line or use the Load command on the Run menu to load the program. You have already configured the transport layer and execution model.
If you have configured CodeView for local debugging, you can start a remote session as described in the following section, “Starting CodeView for a Different Configuration.”
CodeView starts, loads your program, and initiates communication with the remote monitor. You are now ready to debug.
Once the debugging session is started, you can use CodeView just as you would for a local debugging session. When you quit CodeView, the remote monitor quits (unless you specified /R when you started the monitor).
If your system has trouble maintaining the communications link between the host and target machines, reduce the bit rate.
Starting CodeView for a Different Configuration
If you have CodeView configured for local debugging in TOOLS.INI, start CodeView without specifying a program on the command line. This allows you to change CodeView's configuration before it loads your program. It is recommended that you configure CodeView for remote debugging.
·To start a remote session from a local configuration:
1.Transfer your program and its DLLs to the target machine.
2.Start the remote monitor on the target machine.
3.On the host machine's command line, start CodeView with the following syntax:
CV [[options]]
Do not specify the program's filename or arguments.
CodeView starts and displays the Load dialog box. Instead of specifying a program and its arguments, you must first reconfigure CodeView for remote debugging.
4.Choose Configure Remote. CodeView displays the Configure Remote dialog box. Load the remote transport layer and target execution model, as follows:
A.Choose the TLD1COM.DLL transport layer.
Select the communications port and bit rate for the session. Make sure that the bit rate is the same on the host and target machines.
B.Choose the execution model for the appropriate target:
EMD1D1.DLL for debugging an MS-DOS program.
EMD1W0.DLL for debugging a Windows application.
C.Choose OK.
CodeView returns to the Load dialog box.
5.Type the name of your program in the File to Debug text box, or select the name in the Files List box. Type your program's command-line arguments in the Arguments text box.
6.Choose OK.
CodeView starts and initiates the remote session.