FIX: EXEHDR Hangs on Windows-Based Apps Using VERSIONINFO

Last reviewed: September 18, 1997
Article ID: Q116448
3.00 3.10 MS-DOS kbtool kbbuglist kbfixlist

The information in this article applies to:

  • Microsoft EXEHDR Utility for MS-DOS, version 3.0 (included with C/C++ for MS-DOS, version 7.0)
  • Microsoft EXEHDR Utility for MS-DOS, version 3.1 (included with Visual C++ for Windows, version 1.0)

SYMPTOMS

The EXEHDR utility may hang or generate error message U1107, "unexpected end of resident/nonresident name table", if you use it on a Windows application containing a VERSIONINFO resource. (Actually, in this situation, version 3.0 of EXEHDR is more likely to generate the U1107 error message, while version 3.1 of EXEHDR is more likely to hang.)

RESOLUTION

Make sure that the application does not use any symbol names longer than 128 bytes in the VERSIONINFO section of the .RC file.

STATUS

Microsoft has confirmed this to be a problem in EXEHDR, versions 3.0 and 3.1. The problem was corrected in EXEHDR, version 3.2 (included with Visual C++ for Windows, version 1.5).

MORE INFORMATION

You can use the NWPOPUP application, supplied with Windows version 3.1, to illustrate this problem. To use EXEHDR, simply run the program with the name of the .EXE in question as the argument:

   exehdr nwpopup


Additional reference words: 3.00 3.10 buglist3.00 buglist3.10 fixlist3.20
KBCategory: kbtool kbbuglist kbfixlist
KBSubcategory: TlsMisc
Keywords : kb16bitonly
Solution Type : kbfix


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