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 X-Envelope-From: tdabbs AT staktek DOT com Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: FW: comport problem Date: Tue, 24 Aug 2004 15:24:55 -0500 Message-ID: <14CEE0B69DBDFC41A192613D8B4098CA10559C@XCH-CORP.staktek.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Terry Dabbs" To: X-Spam-Score: -2.6 X-Spam-Flag: NO X-Spam-AWL-Adustment: 0.0 X-Spam-Level: X-Spam-Status: No, hits=-2.6 required=5.0 X-Spam-Processed-By: dbcheck.staktek.com X-Spam-Checker-Version: SpamAssassin 3.0.0-rc1 (2004-08-15) on dbcheck.staktek.com X-Spam-Report: -2.6 points, 5.0 required * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list X-Spam-Bayes-Result: 0.0000 X-IsSubscribed: yes Note-from-DJ: This may be spam Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i7OKPF6f004318 Brian, You are correct. I used gcc-2 because that is what downloaded by default. Previously, I just used "com2", and it was acceptable, and worked fine. I read the code in the some of the other emails in the forum and noted that it was in the form "/dev/com2". I changed to format, and it now works great. Thanks, Terry Dabbs On Mon, 23 Aug 2004, Terry Dabbs wrote: > I've used a version of cygwin from June of 2003. I've loaded a new > version, and apparently gcc is now gcc-2. No, gcc-2 was a package of the old gcc-2.95.x compiler. It was pulled from the distribution because of bugs. gcc is currently version 3.3.3. > The problem is that I can't open the comport with the program that > previous worked well under the old cygwin/gcc. I noted references in my > search for the solution about gcc-2 or cygwin not accepting the name > com1, com2 etc. I' love some direction here. This is not a gcc problem at all. Cygwin will let you open COM1, COM2, etc., but it will treat them as regular files. If you are trying to use POSIX functionality (termios, etc.) with that file descriptor, please use the corresponding POSIX device name listed here instead: http://cygwin.com/cygwin-ug-net/using-specialnames.html#AEN825 to open the port. Doing so should eliminate your problem. HTH -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/