Some Retail Version DLL and EXE Files Not Installed in Windows

Last reviewed: June 5, 1996
Article ID: Q151956
The information in this article applies to:
  • Microsoft Visual C++ for Windows, versions 1.5, 1.51, 1.52, 1.52b, 1.52c

SUMMARY

When Debug Kernel under Tools is chosen in Custom Installation, you may see the following message:

   "Some files in the retail version of Windows were not installed. Install
   retail versions of KRNL386.EXE, KRNL286.EXE, GDI.EXE, USER.EXE, and
   MMSYSTEM.DLL in 'C:\MSVC\NODEBUG' before trying to switch from the
   debugging to the retail version of Windows using D2N.BAT."

This message can be ignored.

MORE INFORMATION

The reason for this message is that setup has not copied the KRNL286.EXE file in the C:\MSVC\NODEBUG directory.

KRNL286.EXE should be used when debugging applications in Standard Mode and KRNL386.EXE should be used when debugging in Enhanced Mode.

REFERENCES

Readme.txt file in the CDROM MSVC15\DEBUG directory.

Tips.wri in the C:\MSVC\HELP directory.

Microsoft Windows Software Development Kit Programming Tool manual for Windows 3.1, page 73.

For additional information, please see the following articles in the Microsoft Knowledge Base:

   ARTICLE-ID: Q86171
   TITLE     : Differences Between Retail and Debug versions of Windows 3.1

   ARTICLE-ID: Q67711
   TITLE     : Using Windows User, Kernel, and GDI Symbols in CodeView.


Additional reference words: 1.50 1.51 1.52 1.52b 1.52c
KBCategory: kbsetup kbusage
KBSubcategory: CLIss vc15setup



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: June 5, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.