Files with all uppercase letters shown as lowercase

[steve6375]

FAT32 filesystem

[a1ive]

It's a bug in Windows. File rename doesn't always work.You have to create a new file or make a copy.

…

On Sat, Mar 14, 2020, 17:45 Steve Si ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/1469350/76679371-dab6ab80-65d7-11ea-9a39-dbb2af757721.png> [image: image] <https://user-images.githubusercontent.com/1469350/76679446-73e5c200-65d8-11ea-818b-34d4556a9ee4.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#135>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRNAGSQFHBLXSJ27OJUQYTRHNG2LANCNFSM4LIW3CNQ> .

[steve6375]

Even when creating a new file?

[steve6375]

FAT entry is in capitals

[steve6375]

Ok if long filename

[a1ive]

[steve6375]

So linux and grub2 lie - Windows tells the truth?

[steve6375]

Seems the default in many OS's is to use lowercase for shortnames on FAT volumes
http://lkml.iu.edu/hypermail/linux/kernel/0503.3/1450.html

[steve6375]

I guess it may break case-sensitive menus already created by other users if this was changed to 'mixed' (as is correct)!

[a1ive]

grubfmx64.efi.zip

[a1ive]

Now dirname is UPPERCASE in grub. Strange.

[steve6375]

If dir is 8.3 then will be uppercase.
Will changing behaviour cause issues with current user menus?

[a1ive]

no. fat is always case-insensitive.

…

On Sat, Mar 14, 2020, 19:25 Steve Si ***@***.***> wrote: If dir is 8.3 then will be uppercase. Will changing behaviour cause issues with current user menus? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRNAGQL6UBHYZ55ON6GABLRHNSRNANCNFSM4LIW3CNQ> .

[steve6375]

OK. so should not cause any issues. So OK to commit change?

[a1ive]

I don't think so. This solution is not perfect (dirname).

…

On Sat, Mar 14, 2020, 19:32 Steve Si ***@***.***> wrote: OK. so should not cause any issues. So OK to commit change? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRNAGRME2GXJJSZPH3PDTLRHNTOJANCNFSM4LIW3CNQ> .