Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <3E5A8FE7.BFA23E2C@ieee.org> Date: Mon, 24 Feb 2003 16:34:31 -0500 From: "Pierre A. Humblet" X-Accept-Language: en,pdf MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: exim 4.12-3 winsock problem (was Re: 1.3.21) References: <20030221153741 DOT GA26756 AT redhat DOT com> <20030221180822 DOT GB1408 AT tishler DOT net> <3E566E49 DOT 53BE7CBE AT ieee DOT org> <20030221191209 DOT GE1408 AT tishler DOT net> <20030224200201 DOT GA2348 AT tishler DOT net> <20030224211828 DOT GE1677 AT cygbert DOT vinschen DOT de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > > On Mon, Feb 24, 2003 at 03:02:01PM -0500, Jason Tishler wrote: > > wsock_init(): wsastartup() returned 10107 > > $ 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! Pierre