delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Message-ID: | <3CFE6697.C041242@mvista.com> |
Date: | Wed, 05 Jun 2002 12:29:27 -0700 |
From: | Michael Eager <eager AT mvista DOT com> |
Organization: | MontaVista Software, Inc. |
X-Accept-Language: | en |
MIME-Version: | 1.0 |
To: | Cygwin Mailing List <cygwin AT cygwin DOT com> |
Subject: | DOS Special Names |
I've run into a problem creating a regular file with the name COM20000. I can create this file from Windows, either using fopen() or in a Command window, but not when using Cygwin. Windows does prevent creating files named COMx, where x is a single digit. The code in winsup/cygwin/path.cc checks to see if the file name is COM followed by any integer, not just a single digit. Is this intentional or an error? Shouldn't Cygwin check to see if there is an installed driver named COM (or AUX, etc.) rather than just assume that all COMxxxx are supposed to be devices? -- Michael Eager eager AT mvista DOT com 408-328-8426 MontaVista Software, Inc. 1237 E. Arques Ave., Sunnyvale, CA 94085 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |