08-01-2022, 09:12 PM
Perhaps I'm missing something, but I don't understand how you'd format a large drive it with FAT16 in the first instance?
The only way I can think to do it with a large disc would be to create a tiny partition that is small enough to be supported by FAT16, and hope that the machine - if it does now recognise the disc - will re-write the partition table and reformat the partition(s) it creates as necessary. But that all feels a bit incredible to me. Prepared to learn, though
When disc management tools report "unallocated" space, that usually means no partition is present in that space. Obviously a brand new hard drive would have no partition table on it - that has to be done before formatting can take place, but that step is often carried out "invisibly" by the OS installation if you accept the default recommendation - I normally spend a bit of time partitioning up a new disc to have a D and E drive in addition to the default C.
The fussiness I mentioned with my digital sound desk earlier is because of with hardware incompatibilities with certain controller ICs used in USB memory sticks - nothing to do with the file format as such - and these sorts of things are quite common when using propriety firmware rather than an established OS like Windows or Linux. Thinking about it, I've just remembered that my Rigol 'scope can be fussy too, and fails to recognise some sticks (I upgraded the firmware in our fleet at work a few months back, and it took me several goes to find a USB that would play nicely). I've never tried using the USB interfaces on my TV, but I wouldn't be surprised if I ran into similar issues, and that's why I'm suspecting Gary might be having this problem. Of course, some TVs use Linux/Android, so you might expect those to less fussy, perhaps.
The only way I can think to do it with a large disc would be to create a tiny partition that is small enough to be supported by FAT16, and hope that the machine - if it does now recognise the disc - will re-write the partition table and reformat the partition(s) it creates as necessary. But that all feels a bit incredible to me. Prepared to learn, though
When disc management tools report "unallocated" space, that usually means no partition is present in that space. Obviously a brand new hard drive would have no partition table on it - that has to be done before formatting can take place, but that step is often carried out "invisibly" by the OS installation if you accept the default recommendation - I normally spend a bit of time partitioning up a new disc to have a D and E drive in addition to the default C.
The fussiness I mentioned with my digital sound desk earlier is because of with hardware incompatibilities with certain controller ICs used in USB memory sticks - nothing to do with the file format as such - and these sorts of things are quite common when using propriety firmware rather than an established OS like Windows or Linux. Thinking about it, I've just remembered that my Rigol 'scope can be fussy too, and fails to recognise some sticks (I upgraded the firmware in our fleet at work a few months back, and it took me several goes to find a USB that would play nicely). I've never tried using the USB interfaces on my TV, but I wouldn't be surprised if I ran into similar issues, and that's why I'm suspecting Gary might be having this problem. Of course, some TVs use Linux/Android, so you might expect those to less fussy, perhaps.
