Windows NT 3.5 Hangs If Command Window Cursors are 80x80 Pixels

 Last reviewed: June 6, 1995
Article ID: Q130803
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

From a Command Prompt (CMD.EXE), you started an application that uses the CreateCursor() API and creates a cursor that is 80 x 80 pixels or larger. Windows NT appears to stop responding (hang) and does not react to mouse movements or keyboard input, however, you can still access this computer's shares from other workstations.

RESOLUTION

Microsoft has modified the file, WINSRV.DLL to correct the problem.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem was corrected in Windows NT version 3.51.

KBCategory: kbnetwork kbbug3.50 kbfix3.51
KBSubcategory: ntgeneral
Additional reference words: prodnt 3.50 crashes freezes

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: June 6, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.