It's not a problem with SDIO but the OS was not tested with these high capacities and read/write speeds suck on 3DS. FAT32 needs better read speeds at these capacities because the File Allocation Table is very large which slows down the OS a lot.
Good point.
A 2TB partition with 32k clusters has a fat table which is sized at 256MB. The 3ds has 128MB RAM so it won't fit in memory.
It may crash or, at least, be painfully slow.
The wii has the same problem with large hdd. I found that writes are particularly slow, because of empty space lookups, I guess.
I have a 256GB card in my N3DSXL and it's like half full and I think I have like all the emulators I would want to run and every game I would want to play for it. Really overkill but it's fine lol
Good point.
A 2TB partition with 32k clusters has a fat table which is sized at 256MB. The 3ds has 128MB RAM so it won't fit in memory.
It may crash or, at least, be painfully slow.
The wii has the same problem with large hdd. I found that writes are particularly slow, because of empty space lookups, I guess.
It won't crash. The FAT driver on 3DS doesn't even cache a lot. It will have to scan the whole 256 MB for free space when writing files and you can imagine it takes a while at max. 16 MB/s. Certain apps could crash however when they see these huge numbers they were not tested for.
It won't crash. The FAT driver on 3DS doesn't even cache a lot. It will have to scan the whole 256 MB for free space when writing files and you can imagine it takes a while at max. 16 MB/s. Certain apps could crash however when they see these huge numbers they were not tested for.
they can also read the free space wrong and claim there's no free space left to save or create extra data, like the psp does when it has over 32gb free