X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 29 May 2008 13:12:37 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: serial ports not visible with 1.7 under Vista Message-ID: <20080529171237.GA16039@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <7c5010d60805290558o3717c302u959dd34f396cdb81 AT mail DOT gmail DOT com> <005a01c8c196$587b9b50$2708a8c0 AT CAM DOT ARTIMI DOT COM> <7c5010d60805290726s4faa42e2l4dc276e0118b8808 AT mail DOT gmail DOT com> <007901c8c19c$cd9bd520$2708a8c0 AT CAM DOT ARTIMI DOT COM> <7c5010d60805290811i38d4464y7da05d2d62f2061 AT mail DOT gmail DOT com> <008001c8c19f$ad1bcbe0$2708a8c0 AT CAM DOT ARTIMI DOT COM> <7c5010d60805290840s300f607ep999ff62720fedadb AT mail DOT gmail DOT com> <008701c8c1a7$251d8550$2708a8c0 AT CAM DOT ARTIMI DOT COM> <20080529165211 DOT GC15731 AT ednor DOT casa DOT cgf DOT cx> <7c5010d60805291002hbf4096dvb528407f9d12a9c8 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7c5010d60805291002hbf4096dvb528407f9d12a9c8@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Thu, May 29, 2008 at 07:02:40PM +0200, Giovanni Maruzzelli wrote: >Correction, my last post was ambiguous: > >\\\\.\\com6 gives me "Device or resource busy", while all other com* >give me "not existing". >So, it is definitely better, it finds something! But do not yet works. This is a red herring. It is not going to work: "It won't recognize it as a serial device." >====> Opening and read/writing to COM6 with native win32 API (readfile >etc) works well, both compiled with and without -mno-cygwin -mno-cygwin and native win32 apis really have little bearing on Cygwin. I'm regenerating a snapshot which translates /dev/ttyS0 -> //Global??/COM1 and /dev/com1 -> /??/com1, using the same "symlink" as is used by the windows api. I would appreciate it if you could try the snapshot when it becomes available and report if both /dev/ttyS5 and /dev/com6 work as you expect. cgf -- 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/