This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cygwin 1.7.0-40: Socket operation on non-socket

> Subject: Re: cygwin 1.7.0-40: Socket operation on non-socket
> Steffen Sledz wrote:
> > Hmmmm? That's a pity. But as seen in the mailing lists i'm not the
> only one
> > with such problems. May be there is generic workaround for this? Or a
> guide
> > line how to identify the dodgy app?
>   Unfortunately this is not a very easy task.  The failures are
> provoked in
> different ways by different interfering applications, and what works
> around
> one has no guarantee of working for another.  Figuring out the
> responsible
> application often involves attaching a debugger to the process while an
> error
> occurs and trying to get a look at the stack, to see any OS hooks that
> might
> have been inserted.
>   You might get interesting results by running "netsh winsock show
> catalog" in
> a cmd.exe window, as that will show us if there is some other layered
> service
> provider potentially interfering with your networking.
>     cheers,
>       DaveK

Using "msconfig" from the "Run" command restart your machine with all non-Microsoft
programs stopped.
On the "Services" tag, click "Hide all Microsoft Services", then "Disable All".
On the "Startup" tag, click "Disable All".
Click "OK" and reboot.

Does the problem still occur? If not, then BLODA may be to blame.
If so, then the problem space is smaller and maybe easier to find
a test case.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]