This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: "no buffer space available" on Win2K
- From: "Karl Waclawek" <karl at waclawek dot net>
- To: <cygwin-xfree at cygwin dot com>
- Date: Thu, 1 May 2003 14:25:27 -0400
- Subject: Re: "no buffer space available" on Win2K
- References: <3500515B75D9D311948800508BA37955014BDA86@EX-LONDON> <000401c30f20$b336d0b0$9e539696@citkwaclaww2k> <3EAFEC4F.2060403@msu.edu> <00a201c30f2f$31bdd5b0$9e539696@citkwaclaww2k> <3EAFF5C2.1090704@msu.edu> <005701c30f6b$c0ca0c10$0207a8c0@karl> <3EB1263E.7030206@lucent.com> <001f01c30ff7$235a11f0$9e539696@citkwaclaww2k> <3EB1409F.3060502@msu.edu>
- Reply-to: cygwin-xfree at cygwin dot com
----- Original Message -----
From: "Harold L Hunt II" <huntharo@msu.edu>
To: <cygwin-xfree@cygwin.com>
Sent: Thursday, May 01, 2003 11:43 AM
> > I tested on a different machine (a training machine) and could not
> > trigger the "no buffer space available" error. I tried with ssh and telnet.
> > So, it seems it is a problem local to my machine.
> >
>
> As I suspected. Now we just need to find out which piece of hardware,
> which driver, or which piece of software is to blame. Only you can do
> that for us.
Well, I tried these things:
Newest Windows update. No help.
I applied the registry settings from MS Knowledge Base article 196271:
http://support.microsoft.com/default.aspx?scid=kb;en-us;196271
This appeared to extend the time until the error happened, but it still
happened, especially when I opened a second instance of Kylix remotely,
which seems to put a heavy load on X.
At this point I am giving up - I spent already more time than I should,
considering I have access to Exceed licenses.
Thanks to everybody for their help,
Karl