Long filename problems in 2022?
-
How long filenames are we talking about? More than 260 characters?
Wrong is evil and must be defeated. - Jeff Ello
Oh gosh no. Maybe 20 characters, with spaces. Stuff like "Bionic Commando (U).nes"
To err is human. Fortune favors the monsters.
-
Oh gosh no. Maybe 20 characters, with spaces. Stuff like "Bionic Commando (U).nes"
To err is human. Fortune favors the monsters.
Maybe the empty spaces?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Maybe the empty spaces?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Shoot. Work distracted me from troubleshooting what the root issue was and forgot all about it. I should dig into that. :)
To err is human. Fortune favors the monsters.
-
Maybe the empty spaces?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Any software that has ever been in contact with *nix or *nix developers, even if "ported" to other OSes, is likely to have problems with spaces in filenames. Also be prepared for non-*nix path separators and non-7bitASCII being a potential source of trouble. Even after "porting", expect issues with letter casing.
-
Any software that has ever been in contact with *nix or *nix developers, even if "ported" to other OSes, is likely to have problems with spaces in filenames. Also be prepared for non-*nix path separators and non-7bitASCII being a potential source of trouble. Even after "porting", expect issues with letter casing.
line breaks, return carriage and end of file can give / have given some headaches too
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Shoot. Work distracted me from troubleshooting what the root issue was and forgot all about it. I should dig into that. :)
To err is human. Fortune favors the monsters.
hope you find it. :)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I just spent two hours debugging a problem with my handheld NES emulator (ESP32 based) not loading a bunch of the ROMs that I have. When I read certain files I was getting nothing but zeroes back. The file was the right size but it's like all the data was zeroed. I was pulling my hair out because the same copy of the file on my PC read fine. The one on the SD card I copied from the PC did not. Turns out the copy was bad somehow. Nothing wrong with my code. However, it seems like (I think, but I need to test more) that if I copy them with long names intact they don't work. If I rename them to a shorter name first, they work. Either way, everything looks like it works until you open the file.
To err is human. Fortune favors the monsters.
It's me.
-
Shoot. Work distracted me from troubleshooting what the root issue was and forgot all about it. I should dig into that. :)
To err is human. Fortune favors the monsters.
For what it's worth, I've seen FAT32 implementations in the wild that didn't handle space characters in filenames correctly or didn't like complete file paths longer than a value much less than Windows' 260 characters. For example, the sound system in my car let you plug a FAT32 Flash drive in and it would play any MP3's it found. There were some limitations however. You could only have 99 files per folder, and 99 folders hanging from the root. File path length had to be <16 characters.
Software Zen:
delete this; -
So the doohickey uses the old Windows 95 file scheme? Where your could "name" your file something long but in reality it made an 8.3 name for the file in the background?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
-
Oh gosh no. Maybe 20 characters, with spaces. Stuff like "Bionic Commando (U).nes"
To err is human. Fortune favors the monsters.
