There's a thread about this from a few months back.
IIRC, the consensus seemed to be that it was a (slightly paranoid) precautionary measure on Amazon's part because of inherent limitations of the FAT32 filesystem (possibly compounded by the fact that it's implemented in a slightly tricky manner on Kindle for... reasons).
Making use of a nested directory structure might help (unless you have a shitton of top-level folders, or highly unbalanced content (which seems to be your case, here), no matter what you do).
Last edited by NiLuJe; 07-10-2019 at 12:12 AM.
|