Visual C++ CONFIG.WRI Part 2: Notes on Applications

Last reviewed: July 22, 1997
Article ID: Q111238
1.50 WINDOWS kbreadme

The information in this article applies to:

  • Microsoft Visual C++ for Windows, versions 1.5

SUMMARY

The text below presents information from Part 2 of the CONFIG.WRI file distributed with Microsoft Visual C++ version 1.5. Setup installs CONFIG.WRI in the MSVC\HELP directory.

MORE INFORMATION

Part 2: Notes on Applications

Using CodeView to Debug Applications on an 80286-Based System

To debug applications running on an 80286-based system, copy the following files to a directory on the 80286-based system:

CodeView for MS-DOS:

   CV.EXE
   EMD1D1.DLL
   EED1CAN.DLL
   EED1CXX.DLL
   NMD1PCD.DLL
   SHD1.DLL
   TLD1LOC.DLL

CodeView for Windows (CVW):
   CVW4.EXE
   EMW0W0.DLL
   EEW0CAN.DLL
   EEW0CXX.DLL
   NMW0PCD.DLL
   SHW0.DLL
   TLW0LOC.DLL

To use CVW on an 80286-based system, you must run CVW4.EXE using the /2 (dual display) option. Single-screen debugging in CVW is not supported under standard-mode Windows.

Using the Updated TCP/IP Protocol Stack

The memory-resident TCP/IP protocol stack (TCPIP.EXE) from Novell(R) included with LAN WorkPlace for DOS v. 4.01 can put random data in the high- order bits of the EAX and EDX 32-bit registers at random intervals. Because applications built with the /G3 option in the Visual C++ compiler use 32- bit registers, Novell's memory-resident protocol stack could alter data in the high-order bits of the EAX and EDX registers while those applications are running. If the registers are altered by the protocol stack, the applications' subsequent behavior is undefined. If you are using Novell's LAN WorkPlace for DOS v. 4.01, call the Novell support department at 1-800- NET-WARE and ask Novell for version 4.10 of the protocol stack (TCPIP.EXE). This version eliminates the problem.

Uninstalling Visual C++

To uninstall Visual C++ you must delete all its component files, and remove modifications to the SYSTEM.INI file. Delete the following files:

All files in the Visual C++ directory and its subdirectories.

These files in the Windows system directory:

   HLPTAB.DLL
   GRID.VBX
   VC.LIC
   TECHNOTE.DLL
   MFC250.DLL
   MFCO250.DLL
   MFC250D.DLL
   MFCD250.DLL
   MFCD250D.DLL
   MFCO250D.DLL
   MFCOLEUI.DLL

These files in the Windows directory:
   MSVC.INI
   TECHNOTE.INI
   APSTUDIO.INI

Delete all lines in the [386Enh] section of the SYSTEM.INI file that list files located in the Visual C++ directory (by default,\MSVC\BIN).

Installing MASM Version 6.1 Together with Visual C++

If you plan to install MASM version 6.1 in the same directory as Visual C++, consult the Tools Overview and Update file (TOOLS.WRI) for further configuration information. The TOOLS.WRI file can be viewed using the viewer labeled Tech Notes in the Visual C++ program group.


Additional reference words: 1.50
KBCategory: kbreadme
KBSubcategory: VCGenIss
Keywords : kb16bitonly


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.