Re: wininet: Map socket errors to ERROR_INTERNET_CANNOT_CONNECT in create_netconn_socket.

2012-12-19 Thread Hans Leidekker
On Wed, 2012-12-19 at 12:25 +0100, Marvin wrote: > Hi, > > While running your changed tests on Windows, I think I found new failures. > Being a bot and all I'm not very good at pattern recognition, so I might be > wrong, but could you please double-check? > Full results can be found at > http://te

Re: wininet: Map socket errors to ERROR_INTERNET_CANNOT_CONNECT in create_netconn_socket.

2012-12-19 Thread Marvin
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=23542 Your paranoid android

Re: socket errors...

2008-09-09 Thread celticht32
Ok thanks... so its safe to ignore which is what I was wondering =) Chris -Original Message- From: Damjan Jovanovic <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: wine-devel Sent: Tue, 9 Sep 2008 1:01 am Subject: Re: socket errors... On Tue, Sep 9, 2008 at 5

Re: socket errors...

2008-09-08 Thread Damjan Jovanovic
On Tue, Sep 9, 2008 at 5:03 AM, Chris Ahrendt <[EMAIL PROTECTED]> wrote: > I started narrowing down some information in debugging a winemm issue > and noticed the following in my logs... > > trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags > 0, from 0x33f67c, fromlen 16, ovl (

Re: socket errors...

2008-09-08 Thread Chris Ahrendt
James Hawkins wrote: > On Mon, Sep 8, 2008 at 10:03 PM, Chris Ahrendt <[EMAIL PROTECTED]> wrote: >> I started narrowing down some information in debugging a winemm issue >> and noticed the following in my logs... >> >> trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags >> 0, fro

Re: socket errors...

2008-09-08 Thread James Hawkins
On Mon, Sep 8, 2008 at 10:03 PM, Chris Ahrendt <[EMAIL PROTECTED]> wrote: > I started narrowing down some information in debugging a winemm issue > and noticed the following in my logs... > > trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags > 0, from 0x33f67c, fromlen 16, ovl

socket errors...

2008-09-08 Thread Chris Ahrendt
I started narrowing down some information in debugging a winemm issue and noticed the following in my logs... trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags 0, from 0x33f67c, fromlen 16, ovl (nil), func (nil) trace:winsock:WSARecvFrom fd=51, options=0 warn:winsock:WSARecv