Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 23 Oct 2005 09:38:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Socket read problem on Windows XP Pro & Cygwin Message-ID: <20051023073820.GF27476@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20051022035348.RADA2767.eastrmmtao03.cox.net@[172.18.52.8]> <4359C50C DOT 76649CA1 AT dessent DOT net> <4359EB14 DOT E677A317 AT dessent DOT net> <435AAAB9 DOT 27CDE133 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Oct 22 21:50, Todd Rearick wrote: > Brian Dessent 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. You should nevertheless use /dev/com4 or /dev/ttyS3. I might be wrong but it still looks like you don't quite see what Brian was up to. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- 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/