Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
From:	Todd Rearick <trearick_news AT cox DOT 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 DOT 76649CA1 AT dessent DOT net> <loom DOT 20051022T083200-857 AT post DOT gmane DOT org> <4359EB14 DOT E677A317 AT dessent DOT net> <loom DOT 20051022T153140-747 AT post DOT gmane DOT org> <435AAAB9 DOT 27CDE133 AT dessent DOT net>
Mime-Version:	1.0
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/

- Raw text -