Date: Thu, 18 Jan 2007 10:53:56 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem open(...) serial port /dev/com20 and tcgetattr(...)
Message-ID: <20070118095356.GD27843@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <45ADF0D2.8080809@sauvages.be> <20070117114719.GG28312@calimero.vinschen.de> <45AE13FA.2050901@sauvages.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45AE13FA.2050901@sauvages.be>
User-Agent: Mutt/1.4.2.2i
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Jan 17 13:18, Stan Pinte wrote:
> Dear Corinna,
> 
> Thanks for your quick follow-up!
> 
> I tried the more POSIXy /dev/ttySxx, and they work until /dev/ttyS16.
> This, and the next ones (I tested up to ttyS20) fail with a "No such
> file or directory" error.
> 
> One note: I am using VSPD5 from eltima software to create virtual serial
> ports under windows XP. However, all my other windows applications seem
> to be perfectly able to taok to these virtuals serial ports.

Hmm, I can only test up to COM16.  Cygwin allows names up to /dev/ttyS63
and converts them up to \\.\com64.  The conversion works, but the Windows
function to open the device fails when I use ports > \\.\com16.  Which
makes sense, given that only COM1 - COM16 exist on the system.

Sorry, but you're on your own here.  Somebody who has more ports has to
debug this.  http://cygwin.com/acronyms/#PTC


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/