This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New Cygwin 1.7.0-18 in release-2

On Jul 31 15:30, Corinna Vinschen wrote:
> On Jul 31 15:23, Corinna Vinschen wrote:
> > On Jul 31 08:59, Charles Wilson wrote:
> > > Corinna Vinschen wrote:
> > >
> > >> Illegal?  The only illegal chars are slash and backslash, even on
> > >> case-insensitive mounts.  Does it really occur often that you have two
> > >> filenames in the same dir only differing by case?
> > >
> > > I'd imagine aux and prn are still "illegal", right? The numbers are fewer, 
> > > these days, but there are still source packages out there that have 'aux/' 
> > > subdirectories.
> > 
> > No.  Aux is fine now.  As is nul, prn, com, ...
> Btw., the list of changes attached to my original mail starting this
> thread
> already mentioned that.  This is one result of using NT functions
> exclusively for file access.
> What still won't work, though is to start an application called, for
> instance, "aux.exe".  The reason is that the CreateProcess call in
> spawn/exec is still a Win32 call which will treat this filename as a
> DOS device.

Hang on, I have a workaround for that problem.  It works fine when
using the long path prefix \\?\ in the call to CreateProcessW.
Unfortunately I had to add code to remove the \\?\ prefix for paths
which fit into 260 chars to avoid problems with native Win32 apps so
that's kind of a chicken-egg.  Hmm, tricky.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]