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

ID: Q137799

2.20 3.11 WINDOWS kbprg

The information in this article applies to:

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

Keywords          : nt16ap 
Version           : 2.20 3.11
Platform          : WINDOWS

Last Reviewed: September 10, 1996