Visual C++ README.WRI Part 6-CodeView

The information in this article applies to:

• Microsoft Visual C++ for MS-DOS, version 1.0

SUMMARY

The text below presents information from Part 6 of the README.WRI file distributed with Microsoft Visual C++ version 1.0. Setup installs README.WRI into the MSVC\HELP directory.

MORE INFORMATION

System Requirements

CodeView for Windows (CVW) requires a VGA-compatible display adapter to debug on a single monitor system. A monochrome Hercules adapter can only be used as a secondary display adapter. A system based on the 80386 or later processor can be used for single screen debugging using CVW. An 80286-based system requires a secondary monitor to use CVW.

Running 32-bit MS-DOS extended tools from the MS-DOS Shell

You cannot run a 32-bit MS-DOS-extended tool from the MS-DOS shell in CodeView.

Running Two Debuggers Simultaneously

You cannot run more than one debugger at the same time. For example, you should not run an application under CVW and then start CodeView for MS-DOS or the Visual Workbench debugger.

Viewing Breakpoints on a Secondary Monochrome Display

If you set a breakpoint while running CodeView on a monochrome display, and the breakpoint doesn't appear to be highlighted, check that the brightness and contrast settings are properly adjusted.

Setting Breakpoints on a Windows Exit Procedure

You should not set a breakpoint on a Windows Exit Procedure (WEP). Doing so will cause system instability.

Stepping Over INT 2 In CodeView for MS-DOS Under DPMI

Stepping over an INT 2 (Non-Maskable Interrupt) using CodeView for MS-DOS running under a DPMI server (such as an MS-DOS box in Windows or 386^MAX) may cause the instruction pointer (IP) to end up in the middle of the instruction.

Opening Modules with the Same Name

If two or more modules in the same executable file (.exe) have the same name and extension then they must be compiled with different paths before they can be loaded separately. For example, the two TEST.C modules cannot be differentiated:

   cl /Od /Zi test.c
   cd testdir
   cl /Od /Zi test.c ..\test.obj

   cl /Od /Zi test.c testdir\test.c

Using CVW with Dr. Watson

Dr. Watson (DRWATSON.EXE) will pass exceptions to CVW if they occur while the application being debugged is running. However, Dr. Watson will not pass the exception to CVW if it occurs while you are stepping through an instruction that causes a fault. Instead of stepping through an instruction that causes an exception, use the Go command (F5). Dr. Watson will trap the exception and pass it on to CVW.

Using S3-Based Video Cards

After exiting CodeView on a machine using a video card based on the S3 chip set, such as the Orchid Fahrenheit 1280, the cursor may change color. This is due to a hardware incompatibility. To restore the correct cursor color use the MS-DOS command "mode co80" (without quotation marks).

Using the Mouse with Dual Monitor Systems

When you run CodeView in an MS-DOS session in a window the mouse will not be visible in the secondary monitor. To use the mouse in the secondary monitor you must press SHIFT+ENTER. Not all 8514 monitors support the /2 /43 switch.

Running CodeView in a Windowed MS-DOS Session

If the MS-DOS screen becomes blank while you are using CodeView for MS-DOS with the dual display option (/2), check that background processing has been enabled in the MS-DOS session. Background processing can be specified in the .PIF file used to start the MS-DOS session. You can also enable background processing by using the Settings command available on the system control menu on the MS-DOS session window.

Differences Between the /2 and -2 Options

Starting CVW with the -2 command-line option will cause CodeView to display in monochrome on the primary adapter. To start CVW using the dual display option use the /2 option instead of the -2 option.