monty77 said:
...
I've had a Google and OS X should support read/write to FAT16/32 so what gives? Anyone else have this problem?
Cheers!
Adam
It is likely a problem supplying power to the key, or perhaps it is damaged. Once you get the data off, you might consider formatting the drive in FAT32. That will give you longer file names with out too much loss of space on your drive.
File
Allocation
Table, sometimes instead of Table people use Tree. This is a Microsoft protocol that has become the De facto standard. It can be used by most OSs, and Microsoft hasn't made it proprietary, unlike NTFS, or Apple's proprietary AFS, HFS, HFS+. I just wish that both M$ and Apple could get along better.
The number after it is the number of bits that each cluster of data can contain. FAT12, 12 bits -FAT16, 16 bits etc... The limitations basically are in the size of the name for the file, and the size of any one particular file, and the total accessible drive size. It's not efficient for processing, but it is compact and space efficient, so a small sized medium (like old floppies or small flash cards) benefits from this compactness. The down side is that clusters tend to spread across the medium- this slows the access time, which can be improved by decrementing.
NTFS (New Technology File Structure) and HFS (Hierarchical File System) allow a lot more versatility, but the down side is that they are very verbose. So the up side is that the cluster size can be variable, file names long and nested, and medium size large, there is a down side, that is the amount of information needed to store a file is large, and could potently exceed the size of very small storage media.
), so I second (or third) that it might be a power issue... or, less chance but worth looking into, maybe a bad disk? Have you tested it on any other machines (Mac or PC)?
