Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
To: cygwin@cygwin.com
From: Todd Rearick <trearick_news@cox.net>
Subject:  Re: Socket read problem on Windows XP Pro & Cygwin
Date: Sat, 22 Oct 2005 21:50:58 +0000 (UTC)
Lines: 19
Message-ID:  <loom.20051022T234629-996@post.gmane.org>
References:  <20051022035348.RADA2767.eastrmmtao03.cox.net@[172.18.52.8]> <4359C50C.76649CA1@dessent.net> <loom.20051022T083200-857@post.gmane.org> <4359EB14.E677A317@dessent.net> <loom.20051022T153140-747@post.gmane.org> <435AAAB9.27CDE133@dessent.net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Brian Dessent <brian <at> dessent.net> writes:

> What I was trying to emphasize is that passing "COM4" to open() in a
> Cygwin program sets you up for a world of hurt...
> 
> Brian

It's even worse than you think.  In this case...COM4 is not even a real serial
port...but a "virtual" serial port constructed by a USB driver.  Fortunately for
me...because it's not a real port...I don't actually need to configure it at
all....

I'm actually quite impressed that I can even open COM ports and write to them
and it all seems to work OK via cygwin.  Thanks for the warning and the help.

Todd





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/