BUG: 16-bit Executable Resources Gets Corrupted (177351)



The information in this article applies to:

  • The Resource Editor, when used with:
    • Microsoft Visual C++, 32-bit Editions 4.0
    • Microsoft Visual C++, 32-bit Editions 4.1
    • Microsoft Visual C++, 32-bit Enterprise Edition 4.2
    • Microsoft Visual C++, 32-bit Enterprise Edition 5.0
    • Microsoft Visual C++, 32-bit Enterprise Edition 6.0
    • Microsoft Visual C++, 32-bit Professional Edition 4.2
    • Microsoft Visual C++, 32-bit Professional Edition 5.0
    • Microsoft Visual C++, 32-bit Professional Edition 6.0
    • Microsoft Visual C++, 32-bit Learning Edition 6.0

This article was previously published under Q177351

SYMPTOMS

When you open a executable resource of a 16-bit file that has been modified and saved, the following error message displays:
<filename>
Cannot open resource
File is not in the correct format

RESOLUTION

Use the 16-bit Resource Editor, AppStudio, that shipped with Microsoft Visual C++ version 1.52 to edit 16-bit executable and DLL files.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create two copies of a 16-bit executable resource such as the Apstudio.exe file shipped in Microsoft Visual C version 1.52. Change the file name of one of the copies of the file.
  2. Start Developer Studio and open both files in the Resource Editor.
  3. In one of the executable files, delete all the resources by completing the following steps:

    1. Open a resource folder.
    2. Press Click+SHIFT to select the first and last items in that folder which selects all items in the list.
    3. Press the Delete key to delete all the items.
    4. Repeat for the rest of the items in the folder.
  4. Copy the resources from the second file to the first file.
  5. Open one of the resource folders such as the Version folder. Note that the resources are visible. Close the resource folder and save the file.
  6. Open the file again and click the Version folder. The error message displays indicating a corrupt file.

Modification Type:MajorLast Reviewed:12/1/2003
Keywords:kbBug kbNoUpdate kbpending KB177351