| delorie.com/archives/browse.cgi | search |
On Apr 6 15:14, Lee D. Rothstein wrote: > Corinna Vinschen wrote: >> Apart from the fact that you should use slashes instead of backslashes, >> there isn't any need to use //./ in Cygwin 1.7. Just open Aux.pm. >> >> http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html >> > Can't have any files named [aA][uU][xX] dot *anything* in Windows, or > anything dot [aA][uU][xX]. Incorrect. This is a restriction in the Win32 API, it's not a restriction of the filesystem or the native NT API which Cygwin 1.7 uses for file access (almost) exclusively. > On so-called 16-bit windows systems this could cause a system crash. I > learned this the hard way. Cygwin 1.7 doesn't support 16-bit OSes. > On Windows Vista 64b with 'aux.pm' to a current directory, it tries to > write a file to \\.\aux\. > I didn't have the "heart" to let it try. > > Corinna's reference points this out, but her comments seem to ignore this. Did you read my reference? Quotes from the aforementioned Cygwin 1.7 User's Guide: "This restriction doesn't apply to Cygwin applications." This isn't an issue in Cywin 1.7 anymore since it uses the NT API. "Cygwin can create and access files with such names just fine." aux.pm is a filename like any other for Cygwin applications. "Just don't try to use these files with native Win32 applications." Given that Win32 apps choke on these files, that should be Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |