Part 2: The Plan| OS | FAT16 | FAT32 | NTFS | NTFSv5 | Ext2 |
| Dos6.22 | Y | N | 3 | 3 | N |
| Win95 pre-OSR2 | Y | N | 3 | 3 | N |
| Win95 post-OSR2 | Y | Y | 3 | 3 | N |
| WinNT 4.0 pre-SP4 | Y | 3 | Y | N | N |
| WinNT 4.0 post-SP4 | Y | 3 | Y | Y | N |
| Win 2000 | Y | Y | Y | Y | N |
| Linux | Y | Y | Y/N/3 | ? | Y |
|
Another thing to note is that while NT4 post-SP4 can read and write to NTFSv5 formatted drives, it can not do any low level operations on those partitions (like Chkdsk). Also, when Win2K is loaded, it automatically changes the NTFS partitions to NTFSv5 (nice, ain't it?). So, if you install Win2K with NT4, make sure you have installed the latest service pack for NT4. |
The Roadmap:
|
So, now that we know what our objectives are, and what tools we are going to be using, let us see have a look at the brochure for our destination. This is what your system will look like when you are done. |
|
The first partition is a Primary FAT16 partition. The
rest of the partitions are Logical Partitions inside a large Extended
partition. This is because of a limitation of Win95, in that it can only
see one Primary partition (Win98 no longer has this limitation), and one
extended partition; therefore, this is the easiest configuration to put
the system into, so that a shared DATA drive can be employed, and seen
by all systems. |
The Plan:
|
One of the first rules of multi-booting is to always
have the partition you are booting off as FAT16. The reason for this is
simple: Should anything go wrong, or need to be changed, you are able
to edit the files in this partition using a DOS boot disk. There is no
need to have special utilities to deal with the latest File Systems. I
even recommend having a small FAT16 system partition on large NT
servers, for this exact reason. |