fat 32 wastes a lot of space on the hard disk just to memorize the File Allocation Table at the beginning of the hard disk after the MBR. it's a bit complicated to say how a fat works here but it isn't a very good file system..let's say, it's not very efficient as NTFS or as the linux file systems are.. if anybody studied operating systems or C language, they'll understand me..this is a fat: it's a table made of two columns, on the first there are all the blocks of the hard disk, on the second, there are pointers or blocks to which the first blocks are linked..let's say a file is allocated in 3 blocks on the hard disk, 10, 11, 12.. in the fat beside the 10 there will be 11, beside 11 a 12, beside 12 an EOF(end of file).. when u open that file, it'll start reading block 10, since it points to block 11, it'll then read block 11 and this points to 12 so it'll read 12 and then it'll see EOF so it stops. this table takes a lot of unnecessary space.
