Wrote a workaround for a WinSock bug (unbelievable that they can ship with these problems). Calling setsockopt with an IPPROTO_TCP option on a socket doing a non-blocking connect silently fails, despite the fact that the socket is bound irrevocably as a genuine TCP socket, just not yet readable or writeable. Just one stupid company’s stupid code.