BUG: RW1012 Error or Crash When Building on Windows NT 3.51

 Last reviewed: August 8, 1997
Article ID: Q142890
The information in this article applies to:
  • Microsoft Visual C++ for Windows, version 1.52

SYMPTOMS

When attempting to build a Windows-based application on Windows NT 3.51, Visual C++ reports one the following problems:

  • RC : fatal error RW1012 : Can't find file RCPP.EXE

    -or-

  • The MS-DOS Subsystem reports an illegal instruction from ntspawn.exe

This occurs even when Rcpp.exe is in your Msvc\Bin directory, and that directory is included in the PATH environment variable or in the Visual C++ executable files path (accessible by choosing Directories from the Options menu).

CAUSE

This problem occurs because Ansi.sys is included in the Config.nt file on the computer that is running Windows NT.

RESOLUTION

Remove Ansi.sys from your Config.nt file. If you have MS-DOS applications that require Ansi.sys, you could create .pif files (program information files) to run those applications.

In the .pif files, you can specify a custom configuration file that loads Ansi.sys.

For more information on creating .pif files, please see the "Creating Program Information Files" section in Chapter 11 of the System Guide in the Windows NT Books Online.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 

Keywords          : kb16bitonly VwbIss kbtshoot
Version           : 1.52
Platform          : WINDOWS
Issue type        : kbbug

================================================================================

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: August 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.