Microsoft KB Archive/199434

{|
 * width="100%"|

BUG: Winsock 2 Issue when Not Using the FD_CONNECT Notification

 * }

Q199434

-

The information in this article applies to:


 * Microsoft Win32 Software Development Kit (SDK), on platform(s):
 * the operating system: Microsoft Windows 95
 * the operating system: Microsoft Windows 98

-

SYMPTOMS
If a Winsock 2 application connects to a peer application and then only sets FD_WRITE in the lNetworkEvents bitmask when calling WSAEventSelect, but does not also set FD_CONNECT, then the application will hang in WSAWaitForMultipleEvents after the socket gets connected.

RESOLUTION
A simple workaround solution to this is to simply set FD_CONNECT in the lNetworkEvents bitmask when calling WSAEventSelect, even if a connection has already been established using connect or WSAConnect.

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

Additional query words: kbDSupport

Keywords : kbnetwork kbAPI kbSDKPlatform kbOSWin95 kbOSWin98bug kbWinsock kbGrpDSNet

Issue type : kbbug

Technology : kbWin32SDKSearch kbAudDeveloper kbSDKSearch kbWin32sSearch