exim 4.12-3 winsock problem (was Re: 1.3.21)

[Pierre A. Humblet]

At 09:22 PM 2/24/2003 -0500, Jason Tishler wrote:
>On Mon, Feb 24, 2003 at 10:44:21PM +0100, Corinna Vinschen wrote:
>> On Mon, Feb 24, 2003 at 04:34:31PM -0500, Pierre A. Humblet wrote:
>> > Corinna Vinschen wrote:
>> > >   $ net helpmsg 10107
>> > > 
>> > >   A system call that should never fail has failed.
>> > > 
>> > > That's sarcasm, isn't it?  And so helpful.
>> > 
>> > More helpful than
>> > $ net helpmsg 10107
>> > 10107 is not a valid Windows NT network message number.
>> > 
>> > Must be that system call that should never fail has failed
>> > is a recent phenomenon!
>> 
>> That's the error message on XP.
>
>And Win2K too.

Here is more info from MSDN

WSASYSCALLFAILURE
OS dependent         <<=====
System call failure. 
Generic error code, returned under various conditions. 
Returned when a system call that should never fail does fail. For example, 
if a call to WaitForMultipleEvents fails or one of the registry functions 
fails trying to manipulate the protocol/namespace catalogs.

Returned when a provider does not return SUCCESS and does not provide an 
extended error code. Can indicate a service provider implementation error.