FATDRVCE allows lowercase chars in filename about toolchain HOT 9 OPEN

I've also been experiencing random resets and filesystem corruption, but I'm not sure if that's the libraries fault or my fault.
It might be because I'm not calling msd_Close in usb.c, but that's because with my 16GB SanDisk Cruzer Micro, msd_Close causes my calculator to freeze. I might create an issue for that, but I suspect the bug might be specific to this 1 flash drive, since my other spare flash drive that works with my calculator, a 128MB "Nexdisk" that might actually be 20 years old, doesn't encounter that bug. However, the Nexdisk is super slow, the Cruzer is not, and I don't have any other flash drives that work with my calculator, so it is what it is. :(

from toolchain.

I believe it should actually be an error if lowercase letters are used. Additionally, I think your code has an issue here: https://github.com/TheMiningTeamYT/TI84CE-Blocks-3D/blob/main/src/usb.h#L6-L8

Note that the callback types have to be specified before including the appropriate header, like in the example.

from toolchain.

Well, as of now lowercase names are completely allowed.
Throwing an error if lowercase letters are used isn't the best idea IMO because typically (such as on DOS) lowercase letters are converted to uppercase for short file names, rather than being considered invalid entirely.

Also, thanks for letting me know about those defines. However, for what it's worth, fixing that didn't change the compiled code so far as I can tell.

from toolchain.

I'm trying to decide if it is better to specify what is on the drive though. Having a lowercase name that doesn't actually exist doesn't make much sense? Why do you think the name the user supplies should be modified?

from toolchain.

The reason is that it's the typical behavior of operating systems dealing with FAT32 short names. Even operating systems that support LFN names will convert the filename to uppercase (and truncate it to 8.3), then add an LFN entry for the full lowercase filename.

from toolchain.

Also -- to quote the FAT specification -- "Lower case characters are not allowed."

And -- "Short file names passed to the file system are always converted to upper case and their original case value is lost."

https://academy.cba.mit.edu/classes/networking_communications/SD/FAT.pdf, section 6.1, pages 24-25

from toolchain.

So I've gotten some sleep and time to think about this and I realize I wasn’t being very clear with my reasoning or doing a very good job understanding your argument.

Lowercase letters are not allowed in FAT short (8.3) filenames according to the spec (as @mikaey pointed out). So, you have to do something to get rid of those lowercase letters. I don’t believe we should throw an error because the FAT spec calls for converting lowercase letters to uppercase, for the purposes of short filenames, rather than throwing an error, and every FAT implementation I’ve ever used follows this behavior, except for this one.

That’s why the name the user supplies should be modified. It’s what the spec calls for, and it’s what everyone else does, and not doing so causes compatibility problems, as I documented in the original issue.

from toolchain.

I've also been experiencing random resets and filesystem corruption, but I'm not sure if that's the libraries fault or my fault. It might be because I'm not calling msd_Close in usb.c, but that's because with my 16GB SanDisk Cruzer Micro, msd_Close causes my calculator to freeze. I might create an issue for that, but I suspect the bug might be specific to this 1 flash drive, since my other spare flash drive that works with my calculator, a 128MB "Nexdisk" that might actually be 20 years old, doesn't encounter that bug. However, the Nexdisk is super slow, the Cruzer is not, and I don't have any other flash drives that work with my calculator, so it is what it is. :(

By the way, should I make an issue about this? About msd_Close causing my calculator to freeze?

from toolchain.

I think you've convinced me - hopefully in your program you can work around it your code for now until I get the time to fix it. Yes, please make another issue and document the drive you are using (maybe an Amazon link too)

from toolchain.