files bigger than FFFFFFFF (I think 4,294,967,296 bytes) cause a freeze
a really interesting one too
you can exit the hex editor to unfreeze but whenever you open the file it moves to the end and freezes
when would you encounter a file of this size though?
Never. But it's a bug. I'd assume the system runs out of memory for the buffer.
How did you figure this out? I'm pretty sure the max file size for fat32 is around approximately 4,100,000,000 B [4.1GB].
Also, FFFFFFFF = 4,294,967,295.
This is probably because the biggest line that the hexeditor can view is FFFFFFFF [only has 8 digits]. If you were to reprogram the HexEditor to have support for, say, 10 Digit max lines, then the max you could read would probably be FFFFFFFFFF. This is simply the HexEditor not being written to accommodate such large files.
What @ihaveamac and @SirNapkin1334 said. Sure, 4GB is a limited, but the max FAT file size is also 4GB - 1.
It's also a cosmetic thing. You don't really think it would make sense to enlarge the address row to more than 8 hexadecimal digits, just because of a hypothetical issue?
Leaving this open cause I want to know how @eiiiiix found that. I assume by enabling ExFAT support.
How do you enable ExFAT support?
Short answer: you don't cause it makes no sense. The 3DS OS can't deal with it.
If you absolutely must try this, you learn how FATFS works and edit the config.
i was just fooling around with some stuff
i decided to make a 4gb dummy file so i could see how much randomisation goes into pulling bytes from other files but when i opened it it froze the hex editor
but you can't actually have a file on fat32 larger than 0xFFFFFFFF (4,294,967,295 bytes), so...
I guess that means the problem exists with files almost 4GiB in size. @eiiiiix can you find out exactly how big that file was?
4,294,967,295
Most helpful comment
Short answer: you don't cause it makes no sense. The 3DS OS can't deal with it.
If you absolutely must try this, you learn how FATFS works and edit the config.