On Mar  5 11:42, Michel LaBarre wrote:
> 
> 
> > -----Original Message-----
> > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> > Behalf Of Fergus Daly
> > Sent: March 5, 2018 4:06 AM
> > To: The Cygwin Mailing List
> > Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on
> > FAT32
> > 
> > >> ..."or operation on FAT32 was changed by Windows updates."
> > 
> > Starting to look exactly like that. On Windows 7 there is no problem.
> > On earlier W10 machines in this office there is no problem. My machine
> > underwent a massive (time-consuming) update on or around 13-FEB to
> > Microsoft Windows Version 1709 Build 16299.248]
> > from the previous
> > Microsoft Windows Version 1703 Build 15063.936]
> > and the troubles began then:
> > 
> > ~> touch TryThis.TxT
> > ~> ls T*
> > TryThis.TxT
> > ~> dos2unix TryThis.TxT
> > dos2unix: converting file TryThis.TxT to Unix format...
> > ~> ls T*
> > TRYTHIS.TXT
> > 
> > This on a FAT32 stick. (Can anybody confirm this behaviour?) So I'm
> > guessing Windows has revised its default mount shortname syntax for
> > VFAT. Is there a way I can climb in and alter / override that, does
> > anybody know?
> 
> I have the same build 16299.248 and I get the same behaviour.
> Perhaps consider: http://www.zoneutils.com/regtricks/filesystem.htm
> for parameters to experiment with.  You can use fsutil to control some of these to avoid direct registry modifications.
> I expect it is more subtle otherwise the pervasive nature of the flags would mean that any file creation would result in UC names, not just dos2unix.
> i.e. ls > Foo.txt should produce FOO.TXT

Maybne something with overwriting existung files?  What if you call
`ls > Foo.txt' twice in a row?


Corinna

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