> > To reiterate the basic point: The broken LSP breaks a fundamental
> > promise in the sockets API that we absolutely require. The bug is
> > completely within the LSP.
>
> ISTM that maybe what we have here is a documentation shortcoming.
> I'm thinking that our Windows FAQ ought to suggest
> troubleshooting socket-related problems by removing LSPs one
> at a time.
We used to have this, but we removed it when we aded the code that fixed
the problem in 95% of the cases. It's probably a good idea to bring it
back :-(
//Magnus
