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
Message-ID: <429C7923.2090507@ieee.org>
Date: Tue, 31 May 2005 15:48:03 +0100
From: Jason Pearce <jason.pearce@ieee.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Using Perl to access serial ports
References: <429C1E0A.3050503@ieee.org> <Pine.GSO.4.61.0505310955190.24415@slinky.cs.nyu.edu>
In-Reply-To: <Pine.GSO.4.61.0505310955190.24415@slinky.cs.nyu.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Igor Pechtchanski wrote:

>Just FYI: /dev/ttyS* devices are numbered from 0, so /dev/com1 corresponds
>to /dev/ttyS0...  Also, if you have a sequence of shell commands that
>should work but don't (e.g., stty followed by echo followed by read/cat),
>could you please post them, along with an equivalent program (whether perl
>or C) that does work?
>	Igor
>  
>
Ahh. That explains why /dev/com3 did nothing but /dev/ttyS3 gave me 
permission denied (I have an internal modem on COM3, but no COM4 port). 
I'll have another go at using the /dev method again then and let you 
know what I find.

Jason






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

