Take a look at the slide "Upgrading to the Windows 2000 NTFS File System".
Notice that there is some reference to how multibooting is fully expected, but not for the mainstream which was largely kept unaware of it, or treated like multibooting couldn't possibly exist.
For this slide there is not awareness that this project is already an "upgrade" from W98. Mainly that you already have FAT32. But apparently if you did install W98 after W2K it would actually be considered "normal" too.
This may be like the way, sharing the same NTFS partition you can co-install NT5 (which allows easy naming of the Windows folder during install, to something like WINXP if it finds a WINDOWS folder already exists[0]), then later rename the NT5 Program Files folder to something like ProgNT5files before installing NT6 into the default Windows folder and they coexist on the same partition where the only "conflict" is the single new NT6 Program Files folder which NT5 will not be able run too many of the programs there. Especially if NT5 is 32-bit and NT6 is 64. But it boots wonderfully and you can of course install NT5 programs in the common folder later and they will run fine too.
In this W2K situation, by this slide you are being advised to retain FAT32 to allow future multibooting with earlier OS's.
[0] An empty WINDOWS folder from MKDIR in DOS was fine.
fuzzfactor•5mo ago
Notice that there is some reference to how multibooting is fully expected, but not for the mainstream which was largely kept unaware of it, or treated like multibooting couldn't possibly exist.
For this slide there is not awareness that this project is already an "upgrade" from W98. Mainly that you already have FAT32. But apparently if you did install W98 after W2K it would actually be considered "normal" too.
This may be like the way, sharing the same NTFS partition you can co-install NT5 (which allows easy naming of the Windows folder during install, to something like WINXP if it finds a WINDOWS folder already exists[0]), then later rename the NT5 Program Files folder to something like ProgNT5files before installing NT6 into the default Windows folder and they coexist on the same partition where the only "conflict" is the single new NT6 Program Files folder which NT5 will not be able run too many of the programs there. Especially if NT5 is 32-bit and NT6 is 64. But it boots wonderfully and you can of course install NT5 programs in the common folder later and they will run fine too.
In this W2K situation, by this slide you are being advised to retain FAT32 to allow future multibooting with earlier OS's.
[0] An empty WINDOWS folder from MKDIR in DOS was fine.