Real Mode TCP/IP Custom Blocking Hook Causes Computer to Hang

 Last reviewed: September 9, 1996
Article ID: Q137799
The information in this article applies to:
  • Microsoft LAN Manager version 2.2
  • Microsoft Windows for Workgroups version 3.11

SYMPTOMS

On your computer with the real mode TCP/IP protocol stack installed, when you run a Winsock program that uses a custom blocking hook routine, the program hangs during data transfers.

This problem does not occur with every Winsock program that uses a custom blocking hook routine.

CAUSE

Your custom blocking hook routine does not dispatch WM_TIMER messages causing your Winsock program to hang.

The default blocking hook dispatches all messages. Some programs require a custom blocking hook to provide additional functionality to the program, however, this custom blocking hook may lack the ability to dispatch WM_TIMER messages.

RESOLUTION

In the custom blocking hook routine, include a PeekMessage() call to remove WM_TIMER messages and dispatch them.

KBCategory: kbprg
KBSubcategory: nt16ap
Additional reference words: prodlm prodnt 2.20 3.11 lanman wfw wfwg



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.