Executable Modules Must Be Processed by Resource Compiler

 Last reviewed: July 22, 1997
Article ID: Q43295
3.00 3.10 WINDOWS kbtool

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows versions 3.1 and 3.0

SUMMARY

The Resource Compiler (RC.EXE) must process each executable module developed for the Microsoft Windows environment. This requirement applies both to applications and to dynamic-link libraries (DLLs). Failure to process an executable module with RC can cause problems because Windows will use "previous version compatibility" behavior for that application. Windows versions 3.0 and 3.1 display a warning dialog box when the user launches an unmarked application.

MORE INFORMATION

An application should be processed by RC, even if it does not have any resources. In versions of Windows earlier than 3.0, it was common practice to create a null resource file containing only a comment to provide RC with acceptable input. The RC provided with Windows versions 3.0 and 3.1 supports marking an application that has no resources with the following syntax: 

   RC [switches] module.EXE
RC updates the file header to include the correct version stamp information. The switches parameter is optional. One switch is -T which marks an application as running only under protected mode Windows. Additional switches are listed in the Microsoft Windows Software Development Kit (SDK) documentation.

Additional reference words: 3.00 3.10
KBCategory: kbtool
KBSubcategory: TlsRc
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.