Win32s Message Queue Checking

Last reviewed: November 2, 1995
Article ID: Q97918

The information in this article applies to:

Microsoft Win32s versions 1.1 and 1.2

Win32-based applications that are designed to run with Win32s need to check the message queue through a GetMessage() or PeekMessage() call to avoid locking up the system. With Windows NT this is not a problem, because the input model is desynchronized. That is, each thread has its own input event queue rather than having one queue for the entire system. In a synchronous input model, one application can block all of the others by allowing the single system queue to fill up with its messages. With Windows NT, an application that lets its input queue fill up will not affect other applications.

For more information, please see chapter 3 of the "Win32s Programmer's Reference".

Additional reference words: 1.10 1.20
KBCategory: kbprg
KBSubcategory: W32s

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