Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<F10D23B02E54D011A0AB0020AF9CEFE999EE7C@lynx.ceddec.com>
From:	"Town, Brad" <btown AT ceddec DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: O_NONBLOCK serial I/O blocks on 95, OK on NT
Date:	Wed, 6 Dec 2000 14:46:30 -0500
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

Christopher Faylor [mailto:cgf AT redhat DOT com] wrote:
> Serial I/O in cygwin uses MS overlapped I/O.  Maybe this 
> isn't completely
> implemented on w9x.

Microsoft's overlapped I/O for serial ports is fully implemented, though
it's just different enough to drive you crazy.  I've had times when serial
I/O code (straight Win32 API stuff) would work perfectly under NT/2000, but
would fail under Win9x because some parameters were considered invalid.  I
wish I could remember the details.

Brad Town

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -