| Year 2000 technical summary |
| 4 | Filesystem Issues | << >> |
| 4.0 | Contents |
| 4.0 Contents | ||
| 4.1 Filesystem Issues | ||
| 4.2 Filesystems | ||
| 4.2.1 FAT12 | ||
| 4.2.2 FAT16 | ||
| 4.2.3 FAT32 | ||
| 4.2.4 NTFS | ||
| 4.3 Filesystem APIs | ||
| 4.3.1 MS-DOS | ||
| 4.3.2 Windows |
| 4.1 | Filesystem Issues |
| 4.2 | Filesystems |
| 4.2.1 | FAT12 |
| The FAT12 filesystem is typically used on small volumes, such as floppy disks, to minimise filesystem overhead. Other than that, it functions identically to FAT16. |
| 4.2.2 | FAT16 |
The FAT16 filesystem stores a "last update" date and time for every file
and directory.
The date is encoded in a 16bit word as:
In addition to long filenames, Windows 95 provided little known additions to the FAT12/16 filesystem, including the "last accessed" date (the "last-accessed" time field is always zero). The date encoding is the same as format as the last update. |
| 4.2.3 | FAT32 |
| Incomplete at this time (1999-11-18). |
| 4.2.4 | NTFS |
| Incomplete at this time (1999-11-18). |
| 4.3 | Filesystem APIs |
| 4.3.1 | MS-DOS |
| There are no inherent Y2K related issues in the filesystem APIs for any version of MS-DOS V5.x/V6.x. See also Chapter 3 §3.2.2 (OS Issues, MS-DOS API) |
| 4.3.2 | Windows |
| There are no inherent Y2K related issues in the filesystem APIs for any English version of Windows. See also Chapter 3 §3.3.1 (OS Issues, Win16 API), Chapter 3 §3.3.3 (OS Issues, Win32 API). |
|