winsock:WS_setsockopt

[Rein Klazes]

On Sun, 12 Dec 2004 12:42:55 +0200, you wrote:

> It's a little bit...embracing :-)
> 
> But the program is "Lanwatch". A nice little app, which makes a lot of 
> noise (if configured correctly) when the Internet connection goes down. 
> I used it for years, but now we've got rid of the last Windows here....
> 
> I have other network monitoring tools, but it's just the acoustical 
> waring, for which I used it...I'll just attach it to the mail, OK?
> 
> It would be great, if there could be a fix for this....Also I contacted 
> the writer of the little app, but didn't got a answer...
> 
> I think, that it just tries to open a socket (with correct or wrong 
> parameters), and than gets a back a error and reports (wrongly) that the 
> Internet connection is down...It might be easy to fix (or hack 
> workaround) for it, just if you can lead me to the solution?

| fixme:winsock:convert_sockopt Unimplemented or unknown socket level
| err:winsock:WS_setsockopt Invalid level (65407) or optname (128)
| fixme:mpr:WNetGetUniversalNameA ("K:\\", 0x00000001, 0x779cf98c, 0x779cfd98): stub
| fixme:winsock:convert_sockopt Unimplemented or unknown socket level
| err:winsock:WS_setsockopt Invalid level (65407) or optname (128)
| fixme:winsock:convert_sockopt Unknown SOL_SOCKET optname 0xff7f
| err:winsock:WS_setsockopt Invalid level (1) or optname (65407)

The same output as Space Empires 4. The unknown optname 65407 or 0xff7f,
is suspiciously looking like the option SO_DONT_LINGER, 0xffffff7f, with
the high bits chopped off. Both these calls fail under Windows (win2K).

It is a good idea to ask the programmer, to see what he is trying to
accomplish here.

Also note that these errors may not be fatal at all if the program is
just ignoring them. Letting the program going through I see a fair bit
of data exchange, so communications seems to work, at least partly.

Rein.
-- 
Rein Klazes
rklazes at xs4all.nl