No we do not have MSDN docs available at Cygwin/Xfree86. It not allowed to resdribute MSDN docs, also there is no available bug entry, of which i am aware. I was told by someone at the Cygwin/Xfree86 mailing list because we were experiencing strange behaviors on Windows ME. The person who explain was from IEEE Organization. We (actually he) did a work around via Cygwin.dll. I do not think there is a very simple solution to it, except to adjust your code so it feels happy seeing M$ crap, that is what he did. Xfree86 select() on Windows ME was leaving sockets open and with seconds was creating over 2000 listing ports -- very bizzare, and a very good crap in Microsoft socket.
Suhaib -----Original Message----- From: David Thompson To: [email protected] Sent: 4/18/2001 4:22 PM Subject: RE: [opendx-dev] Windows--winsock Now that I can believe. I was wondering if this is where it was having problems. Do you guys on the Cygwin/XFree86 project have any MSDN doc numbers on this bug? Do you have an idea of how to program around it? Is it straight forward? David > > >> in the "select" and the socket's "write" there is sometimes a >> >> non-conclusion happening. Anybody want to offer me a suggestion? >> >> > >Well actually it is a crapy bug in select() on Windows since years. We >discovered it >at Cygwin/Xfree86 project, last week. Select was doing bizzare things on >Windows ME, someone from IEEE.ORG pointed >out to the bugs in Winsock, which according to him M$ developers do >intentionally as an >inginious way to get things working. Nothing much can be done about it, >except to code >DX in a way to work around M$ bugs. > >Suhaib -- ........................................................................ ..... David L. Thompson The University of Montana mailto:[EMAIL PROTECTED] Computer Science Department http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812 Work Phone : (406)257-8530
