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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: 2nd Try 1.57 on Win2k or WinXP. Not more than 16 com ports. Differences between //./comX and /dev/comX Date: Tue, 20 Apr 2004 09:58:40 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lutz_H=F6rl?= To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i3K7xJKv025343 Hello, thank you Corinna, your message removed some of my headache. May I ask to confirm and eventually add to documentation? 1. cygwin does support 16 serial deviecs with 'dev/com1' to '/dev/com16' 2. By using Windows names like '//./com1' cygwin does not recognize the interfaces as interfaces but as ordinary files. 3. If you want to use serial interfaces in a 'hardware' oriented approach (i.e. read out the modem lines DCD, DSR, change the interface settings baudrate, parity, etc. etc.) you should only use Win32-API functions. May I additionally ask? - is there a reason on limiting to 16 supported serial interfaces in Cygwin? - if no, is it an idead to increase this number? - I used the POSIX functions read() write() and select() to communicate with my serial interfaces and the Win32-API functions to set baudrate and to get modem line status. It worked until now. Are there hidden pitfalls ? Are there POSIX/Cygwin functions to do the same job ? Again, thank you very much for your Help. Lutz Hoerl M A I L lhoerl at thorlabs dot com -- 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/