Penguin

Differences between version 2 and predecessor to the previous major change of FAT32.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 2 Last edited on Sunday, September 28, 2003 8:17:14 am by AristotlePagaltzis Revert
Older page: version 1 Last edited on Saturday, November 16, 2002 8:17:51 pm by PerryLorier Revert
@@ -1,6 +1,3 @@
-[FAT32] was the next evolutionary step from [FAT16]. Bigger disks were needed , so [FAT32 ] expanded the amount of space it could address once again. Also Microsoft was getting hassled by Apple and other operating systems about it' s 8 .3 charactor filenames so it added support for a file to have a long and a short filename. Filenames can be up to 256 charactors long , although the path can still only be 63 charactors long
+[FAT32] is the successor to [FAT16] in the line of FileAllocationTable [FileSystem]s , designed for use with current [HardDisk ]s. It was a bigger evolutionary step from its predecessor than the one from [FAT12] to [FAT16] , not only in terms of added FileAllocationTable entry bit width, but also in terms of internal structure which had not changed between [FAT12] and [FAT16]
  
-Everyone decided this was a kludge, it barely fixed any of the problems, and introduced new ones . It still had the notorious [FAT], and still had it at the beginning of the disk[1]. [FAT32] had no permission models or anything. So , finally, Microsoft moved everyone over to using [NTFS] with Windows 2000.  
-  
-  
-[1]: Had microsoft placed it at the middle of the disk, then it would have reduced the average amount of time taken to seek to it from either end of the disk from n to n/2, but nooo..
+[FAT32] uses a fixed DiskCluster size of 4Kb . Since it can address 2^32 clusters , this is sufficient for 16TB of storage