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:	<3A2EBA0C.97C41502@sattel.com>
Date:	Wed, 06 Dec 2000 14:13:32 -0800
From:	Bruce Edge <bedge AT sattel DOT com>
Organization:	Sattel Global Networks
X-Mailer:	Mozilla 4.75 [en] (X11; U; Linux 2.2.15-4mdk i686)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin support <cygwin AT sources DOT redhat DOT com>
Subject:	Re: O_NONBLOCK serial I/O blocks on 95, OK on NT
References:	<F10D23B02E54D011A0AB0020AF9CEFE999EE7C AT lynx DOT ceddec DOT com>

"Town, Brad" wrote:
> 
> 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.

So do I :-)

Does anyone know if anything changed WRT serial I/O on 98 or ME?
I have to support _one_ of the crappy OSs. I was wondering if an upgrade would
be worth it.

Lastly, more data:
When I'm hung up in the read(), my timer interrupt ISR stops getting called.
Only thing it seems to respond to at this point is a Ctrl-C.

-Bruce.

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

- Raw text -