File name differences SCSI & FAT32FS

Looking at the boot partition for my BB -xM via Loader all is correctly capitalised whereas via FAT32Fs only the first character of each filename is. Why?

Due to some oddities earlier this week with uSD cards failing to boot the BB after I’ve updated stuff in the filecore (??) partition I’m now keeping a spare in a card reader to regularly update. Might FAT32Fs’ behaviour be a future booby trap?

Is it safe to update the FAT partition via FAT32Fs or better to do it via SCSI & Loader?

Looking at the boot partition for my BB -xM via Loader all is correctly capitalised whereas via FAT32Fs only the first character of each filename is. Why?

Not just the boot partition. I find the same with any usb memory device, eg the CF or SD card from a digital camera. Have just done a test to a 120GB SSD attached via usb, copying a file TEST/TXT, and the filer window shows it as Test/txt. Same for TEST, shows as Test. However, if you copy a directory, the capitalisation is preserved. I guess it is something for the author of Fat32Fs.

I guess it is something for the author of Fat32Fs.

Fat32fs was intended to be similar to Win95fs, which showed the 8.3 capital filenames in that manner, so this is how I did it. It’s arguable whether I made the right decision all those years ago!

Is it safe to update the FAT partition via FAT32Fs or better to do it via SCSI & Loader?

If the file already exists then the name is not altered when updated.

If the file already exists then the name is not altered when updated.

But is if copying between FAT and Filecore?

Jeff, just a note on the use of Fat32Format, I found formatting a CF card with defaults and the card would not be recognised by my camera, and could not be reformatted by my camera, unless I used Fat32Format again with the -o option, then everything is fine. For me, always using the -o option will be the default from now on, as no machine has ever had a problem with finding a partition. A lot of USB sticks do come new without a partition table, I have seen one like this failed to be recognised intermittently by Fat32Fs.
I’m wondering if anyone else has found similar problems with non partition type formatting. It is easy to say this has been working on RISC OS fine, but the acid test is when the flash drive is circulating on various machines I think.