This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 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: "no buffer space available" on Win2K


Karl,

It is well-known that various VPN software causes problems with Cygwin/XFree86. The reasons for this are numerous, but it primarily has to do with the fact that these VPN packages replace various Windows system DLLs with their own versions that do not correctly duplicate all of the functionality of the Windows networking DLLs. There isn't anything we can do to fix this problem, as we certainly cannot write code to deal with x number of networking layers for Windows.

The only real solution here is to never install the VPN software to begin with, as most of them leave their modified DLLs in place when you uninstall them.

The problem would have nothing to do with the window manager.

I consider your problem solved, as there is nothing I can do to help. You could ask the Cygwin list (cygwin@cygwin.com) if you have further questions, but I would expect it to get toasty in there if you aren't offering to help :)


Harold


Karl Waclawek wrote:
Finaly someone else who has had this problem, however I have experienced it
using just cygwin ssh and just cygwin ncftp as well as once using x with ssh
forwarding. So i have only ever reported it on the cygwin list (to no
responce.) I can give cygcheck etc if anyone wants them.


I tried to duplicate it from home (over a VPN connection), but
could not get it to trigger. Btw, does anyone know about performance
problems with XWindows over VPN? It ran so slow it was unusable - data speed
was about 1KB/sec, whereas my ADSL is capable of much better.
VNC was a lot more usable, but should it not be the other way around?

Anyway, got it again this morning. The X session just crashed.
When I tried to start it again (using startxwin.sh), the shell returned:

listen: No buffer space available
xsetroot:  unable to open display '127.0.0.1:0.0'

Could it be caused by the window manager? I was using wmaker, not twm.

Karl


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