Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 6 Dec 2000 14:47:24 -0500 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: O_NONBLOCK serial I/O blocks on 95, OK on NT Message-ID: <20001206144724.C9721@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from btown@ceddec.com on Wed, Dec 06, 2000 at 02:46:30PM -0500 On Wed, Dec 06, 2000 at 02:46:30PM -0500, Town, Brad wrote: >Christopher Faylor [mailto:cgf@redhat.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. FWIW, I have tested serial I/O on w9x so it probably isn't something simple. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com