FIX: GPF When Selecting .alx Files in Template Wizard

 Last reviewed: December 18, 1997
Article ID: Q168274
The information in this article applies to:
  • Microsoft Visual InterDev, version 1.0

SYMPTOMS

A General Protection Fault (GPF) will occur when choosing an .ALX file that contains Double Byte Character Set (DBCS) characters in the Template Page Wizard.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in Visual Studio 97 Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Steps to Reproduce Behavior

To reproduce this problem, first obtain an .alx file that contains DBCS characters.

  1. Open or create a web project.

  2. Select File\New\File Wizards\Template Page Wizard.

  3. Provide a file name in the "File name" textbox and click OK.

  4. In the "Template Type" combobox, select "2-D Layout files (*.alx)."

  5. In the "Which template would you like to use" listbox, choose an .alx file that contains DBCS characters.

Result: GPF 
Keywords          : VS97FixlistSP3 VS97FixlistSP2 VS97FixlistSP1
Version           : 1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

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

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