KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q141726: Streets 4.0: GP Fault or System Lock Up on Windows NT 3.51

Article: Q141726
Product(s): Microsoft Automap
Version(s): WINDOWS:4.0; winnt:3.51
Operating System(s): 
Keyword(s): kbbuglist
Last Modified: 28-JUL-2000

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Automap Streets for Windows, version 4.0 
-------------------------------------------------------------------------------

SYMPTOMS
========

When you start Automap Streets version 4.0 on a computer running Microsoft
Windows NT 3.51, you may receive a General Protection (GP) Fault containing
various filename references, or the computer may stop responding (hang).

CAUSE
=====

This problem occurs if the Windows NT Virtual Memory settings are set too high.

RESOLUTION
==========

To resolve this problem, lower the Virtual Memory settings in Windows NT 3.51.

To determine the optimal settings for your system, consult your Windows NT 3.51
documentation.

STATUS
======

Microsoft has confirmed this to be a problem in Microsoft Automap Streets
version 4.0. We are researching this problem and will post new information here
in the Microsoft Knowledge Base as it becomes available.

Additional query words: auto auto-map automap reference kbmm multimedia multi-media mult media map NT

======================================================================
Keywords          :  kbbuglist
Technology        : kbHomeMMsearch kbAutomapSearch kbAutomapStreets400
Version           : WINDOWS:4.0; winnt:3.51

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

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.