Filer

I have just come up against this with a USB stick and a Pi, which uses Fat32FS.

I have a feeling that Jeffrey Doggett posted somewhere that Fat32fs (based on the efsl library) is designed to do that with filenames that will fit into the DOS 8/3 format. Long filenames honour the case correctly when renaming.

Although I have found a solution to my immediate problem, your reply has prompted me to have another look. It is not quite as straightforward as I thought.

I transfered the files over ShareFS to the USB stick, and the copied filenames all went to initial caps, except those over 8 characters. I could not then change that by renaming. I can add uppercase characters, but as soon as I revert to the original name I am back to initial caps. Other files that I copy from the same machine seem to retain their case, but my tests have not been really comprehensive. It is certainly odd, and does seem to relate to the 8.3 format in some way.

I have a feeling that Jeffrey Doggett posted somewhere that Fat32fs (based on the efsl library) is designed to do that with filenames that will fit into the DOS 8/3 format. Long filenames honour the case correctly when renaming.

That would be this thread.

I think it depends on what is displaying the filename rather than the stored characters, or something like that. Certainly when writing new ROMs to my BB -xMs uSD card the filenames revert to caps when viewed via SDFS/SCSI whereas files written from those appear initial letter capped only in Fat32FS.

have a ‘move to’ menu entry.

Or a ‘Move’ tickbox in the Copy savebox.

Or perhaps trigger the move if you shift-drag the icon, since that would match the behaviour for the main filer window.

Another request for the list: Being able to control which operations recurse through image files systems. At the moment recursing through image files systems is turned on for ‘find’, ‘stamp’, and ‘set access’, but that might not be what the user wants. E.g. Sunfish stores saved mounts as an image file within its choices folder. When I search for a file in !Boot, I don’t want to start searching all my network drives! Also I can’t imagine many situations where you’d want to update the contents of an image file with permissions that you’ve applied to the file itself (if you want to lock an image file to prevent changes, you only need to mark the file as read-only, not the contents)