Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 19 Apr 2004 21:37:11 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 2nd Try 1.57 on Win2k or WinXP. Not more than 16 com ports. Differences between //./comX and /dev/comX Message-ID: <20040419193711.GA22404@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Apr 19 20:14, Lutz H?rl wrote: > Hello, > > thank you Dave, thank you Larry. > > But unfortunately your advice to use "//./devX" did NOT solve the problem. No, it can't. When using the Win32 device names, the files are not recognized as devices by Cygwin but instead they are treated like normal files. If you want Cygwin support, you must use POSIX device names. If you want to access the serial interfaces using Win32 functions anyway, I'd suggest to use Win32 functions throughout and not rely on Cygwin. This already begins with using CreateFile instead of open. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.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/