winsock:WS_setsockopt

[Rein Klazes]

On Sun, 12 Dec 2004 21:35:44 +0200, you wrote:

> Well, if the setting is win98 instead of win2k, than the output differs 
> a little. The program tries to connect to a http server and gets the 
> HEAD of the server / page. That's what's actually doing. Right now it 
> just fails, i.e. no connection, so there is one (even iexplore connects 
> happily).

It connects here and receives plenty of data (some 30kB before I shut
the program up). Sound does not work under wine here ATM ( a kernel
problem I think), but communication is OK as far as I can tell.

Run wine as WINEDEBUG=+winsock wine ... to follow the communication
activity.

(I have win version set as winxp btw, for no particular reason)

> 
> I think this is a problem of the ?Unimplemented or unknown socket level? 
> and returns a error. This is what the program checks. So if it could 
> fetch the HEAD of the server, everything would be fine, if not, it 
> sounds the alarm.

I don't think the program checks that. To be sure, edit
dlls/winsock/socket.c. Around line 2469, you will find the "invalid
level ..." message. Change the following "return SOCKET_ERROR;" by
"return 0;" and recompile.

> 
> I tried contacting the author, but no reply as of now....Maybe we can 
> just satisfy the program in an other way, i.e. return it a socket? Any 
> ideas?

Look for other failures then these errors (eg. in the +winsock log). The
programs seems to want to run from the systray, you may want to try the
last patch that Mike Hearn has uploaded to wine-patches.

Rein.