"no buffer space available" on Win2K [cgf, please comment]
Harold L Hunt II
huntharo@msu.edu
Sat May 3 05:26:00 GMT 2003
All,
See, the problem I have with this argument is that, as usual, Exceed
doesn't have the same problem that we do. Thus, it means that there is
a way to avoid this problem through some careful coding technique. I
want to know what that technique is and what we need to do to implement it.
Karl --- Of course, you are free to go, as this problem is quite general
in nature and not specific to your situation. Thanks for your help.
Harold
Karl Waclawek wrote:
> ----- Original Message -----
> From: "Christopher Faylor" <cgf@redhat.com>
> To: <cygwin-xfree@cygwin.com>
> Sent: Friday, May 02, 2003 11:36 PM
>
>
>>On Fri, May 02, 2003 at 01:39:07PM -0400, Karl Waclawek wrote:
>>
>>>>http://www.google.com/search?&q=cygwin+WSAENOBUFS (Note: You will need
>>>>to look at "cached" copies of most links.)
>>>
>>>There is also a thread in google groups:
>>
>>http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=7be06644.0204221456.10fd2bc6%40posting.g
>
> oogle.com
>
>>Which shows that this isn't a cygwin-specific problem.
>
>
> I never said that, and I also don't expect a solution
> from the Cygwin team - considering that Cygwin is free,
> and that my problem does not seem to affect a lot of users.
>
> I also have to congratulate you to the excellent work
> you guys are doing.
>
> However, I have to say this:
> There are millions of of 2000 systems out there.
> The likelyhood of MS fixing the problem and a major portion
> of these systems getting patched is close to zero.
>
> So here is the real-life lesson about MS:
> You have a problem with a buggy MS product - you find a workaround.
>
> I tried, but failed. Time to move on.
>
> Karl
>
>
>
More information about the Cygwin-xfree
mailing list