Problem with TCP Option 0x00000008
Hello, i have a problem with a program that uses a network license manager. I've installed native DCOM using the winetricks script. When i start the program i got the message "fixme:winsock:WS_setsockopt Unknown IPPROTO_TCP optname 0x00000008" after the loading of native rpcltccm.dll. To work around this i've compiled a modified wine 0.9.44 with an empty case statement for 0x00000008 in socket.c. It doesn't help much, the program just fails a bit later. The TCP Option 0x00000008 is defined as TCP_ATMARK in ws2_ipdef.h in the Windows SDK. Does anyone know how this should be mapped ? Cheers, Christian
On Friday 14 September 2007 12:09:25 Christian Mahnke wrote:
The TCP Option 0x00000008 is defined as TCP_ATMARK in ws2_ipdef.h in the Windows SDK. Does anyone know how this should be mapped ?
Hm, I'll need to dig a bit, I guess. I've just returned from my vacation, so I'll need some time to catch up with other things, but I'll put this on my list. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.
On Monday 17 September 2007 22:44:05 Juan Lang wrote:
The TCP Option 0x00000008 is defined as TCP_ATMARK in ws2_ipdef.h in the Windows SDK. Does anyone know how this should be mapped ?
Is this SIOCATMARK?
I don't think so. SIOCATMARK is an WSAIoctl/ioctlsocket option in the winsock api, too. We don't seem to handle that in WSAIoctl, it seems, patch coming up. As I wrote in my other email, I obviously need to update the PSDK I have installed in Wine to get the header file. I'll look into that a bit later. I assume that TCP_ATMARK could be similar to SO_OOBINLINE, but that's a wild guess. I will need to write some test setup for this. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.
I don't think so. SIOCATMARK is an WSAIoctl/ioctlsocket option in the winsock api, too. We don't seem to handle that in WSAIoctl, it seems, patch coming up.
Fair enough, I didn't investigate it further than with grep.
As I wrote in my other email, I obviously need to update the PSDK I have installed in Wine to get the header file. I'll look into that a bit later. I assume that TCP_ATMARK could be similar to SO_OOBINLINE, but that's a wild guess. I will need to write some test setup for this.
I also don't have this header file or definition on my (latest, I believe) PSDK. --Juan
"Juan Lang" <juan.lang(a)gmail.com> wrote:
As I wrote in my other email, I obviously need to update the PSDK I have installed in Wine to get the header file. I'll look into that a bit later. I assume that TCP_ATMARK could be similar to SO_OOBINLINE, but that's a wild guess. I will need to write some test setup for this.
I also don't have this header file or definition on my (latest, I believe) PSDK.
I have here PSDK edition that is called "Microsoft Windows Software Development Kit Update for Windows Vista" and it contains ws2ipdef.h with '#define TCP_ATMARK 8'. -- Dmitry.
On Friday 14 September 2007 12:09:25 Christian Mahnke wrote:
The TCP Option 0x00000008 is defined as TCP_ATMARK in ws2_ipdef.h in the Windows SDK. Does anyone know how this should be mapped ?
What version of the SDK is that? It's not in the one I currently have installed. Arguably, my version is a bit older. I don't seem to have that header file at all. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.
participants (4)
-
Christian Mahnke -
Dmitry Timoshkov -
Juan Lang -
Kai Blin