The information in this article applies to:
SUMMARYThe Winsock 2 socket flag WSA_FLAG_OVERLAPPED needs to be set if the socket will be used in non-blocking mode when running on Windows NT 4.0. Failure to set this flag can result in subsequent Winsock API failure. For example, on Windows NT 4.0, WSAConnect fails with error code 10022, WSAEINVAL if the socket was created without this flag and the socket is placed into non- blocking mode prior to it being called. MORE INFORMATION
A socket must be created with its overlapped I/O attribute set if
overlapped I/O is to be performed using the socket. This can be done either
by creating the socket with the WSASocket API with the WSA_FLAG_OVERLAPPED,
or by creating the socket via the socket API. However, if the socket will
be set to non-blocking mode (on Windows NT 4.0), the socket must also be
created with its overlapped attribute set, even if no overlapped I/O will
be performed with the socket. A socket is placed into non-blocking mode
when either the WSAEventSelect or WSAAsyncSelect APIs are called or if the
FIONBIO command is used in the ioctlsocket API.
Additional query words:
Keywords : kbnetwork kbAPI kbNTOS kbSDKPlatform kbWinOS95 kbWinsock kbGrpNet |
Last Reviewed: October 15, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |