At 02:08 PM 12/6/2000, Bruce Edge wrote: >I'm opening /dev/com1 as follows: > fd = open( "/dev/com1", O_RDWR | O_NOCTTY | O_NONBLOCK | O_BINARY ); > >on NT the O_NONBLOCK works fine. >on win 95, read( fd, buf, max_len ) blocks. > >I don't think the termios stuff should affect this, at least if it did, I >should be having the same problem under NT. >Is there a fix for this? >Or, is there any way to check for chars pending before reading? >I'm already using select(), which shouldn't even drop out of the wait until >there's data. Perhaps this is related to this? http://sources.redhat.com/ml/cygwin/2000-11/msg01544.html If so, you may find some insight by reading this thread... Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Send a message to [EMAIL PROTECTED]
Re: O_NONBLOCK serial I/O blocks on 95, OK on NT
Larry Hall (RFK Partners, Inc) Wed, 06 Dec 2000 11:17:51 -0800
- O_NONBLOCK serial I/O blocks on 95, OK on N... Bruce Edge
- Re: O_NONBLOCK serial I/O blocks on 95... Larry Hall (RFK Partners, Inc)
- Re: O_NONBLOCK serial I/O blocks o... Christopher Faylor
- Re: O_NONBLOCK serial I/O bloc... Larry Hall (RFK Partners, Inc)
- Checking for 95 vs. NT at ... Bruce Edge
- Re: Checking for 95 v... Christopher Faylor
- RE: O_NONBLOCK serial I/O blocks on 95... Town, Brad
- Re: O_NONBLOCK serial I/O blocks o... Christopher Faylor
- Re: O_NONBLOCK serial I/O blocks o... Bruce Edge
- RE: O_NONBLOCK serial I/O blocks on 95... Town, Brad