The information in this article applies to:
SYMPTOMSIf the Windows Sockets setsockopt() API is called with the IPX_RECVHDR option set, the call will return a status of "success," but IPX headers will not be received when the recv() API is called. CAUSEThere is a problem in the Windows Sockets support using the Microsoft IPX/SPX-compatible protocol, in that IPX headers are not returned with the WinSock data, even though it appears that the IPX_RECVHDR option is successfully set when calling setsockopt(). RESOLUTIONThis issue is resolved by the following updated file for Windows 95 and OEM Service Release 2 (OSR2), and later versions of this file:
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and
OEM Service Release 2 (OSR2). An update to address this problem is now
available, but is not fully regression tested and should be applied only
to computers experiencing this specific problem. Unless you are severely
impacted by this specific problem, Microsoft does not recommend
implementing this update at this time. Contact Microsoft Technical Support
for additional information about the availability of this update.
MORE INFORMATION
The DS field in the IPX packet header is generally available to be used
by IPX-aware programs, and can be accessed using the real-mode ECB (Event
Control Block) API. The only supported method for accessing this
information in the Win32 API set is by using the Windows Sockets APIs.
With this update, Win32 programs running in Windows 95 can use the WinSock
APIs to interact with NetWare Loadable Modules (NLMs) and legacy programs
that make use of the DS field in the IPX header.
Q171352 Large Data Transfer Using WinSock Over SPX May Not Work For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base: Q161020 Implementing Windows 95 Updates
Keywords : kbnetwork kbpolicy win95 kbAPI kbSDKPlatform kbWinsock kbGrpNet |
Last Reviewed: June 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |