SGML: Insufficient Memory Followed by Initialization Failure

 Last reviewed: August 5, 1997
Article ID: Q126376
The information in this article applies to:
  • Microsoft SGML Author for Word, version 1.0
  • Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c

SYMPTOMS

You may receive an insufficient memory error, followed by an initialization failure when you abruptly quit a conversion to SGML. In addition, after you restart Windows, you will no longer be able to perform conversions.

This behavior occurs under the following conditions:

- You have 32-bit file access enabled.

- You pressed CTRL+ALT+DEL during the conversion process and then pressed 

  ENTER to close Word.

WORKAROUND

Disable 32-bit file access.

To change this option:

  1. From Windows Program Manager, open the Main group.

  2. Choose the Control Panel icon.

  3. Choose the 386 Enhanced icon.

  4. Choose the Virtual Memory button.

  5. Choose the Change button.

  6. Clear the Use 32-bit File Access check box. Do not make any other changes.

  7. Choose OK in the Virtual Memory dialog box.

  8. Choose Yes when asked if you are sure you want to change the Virtual Memory settings.

  9. Choose the Restart Windows button.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SGML Author for Word, version 1.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: 1.0 sgmlword 6.0 6.0a 6.0c winword
KB_SGMLAUTHOR insufficient memory initialization failure failed out of
word6 memory error 32-bit 32 bit file access
Keywords : kbsgml kbusage
Version : 1.0 6.0 6.0a 6.0c
Platform : WINDOWS

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