One machine default boots 2000 (hereafter referred to as "the 2000 machine",
the other default boots 98SE (hereafter referred to as "the 98SE machine").
Both machines were 100% FAT 32 partitions until recently when, to make it
easier to learn about NTFS permissions and security, I converted one small
partition on the 2000 machine to NTFS. The partition converted to NTFS was
not the boot partition, and is not the partition that 2000 is installed to.
After using the Windows 2000 disk manager to convert the partition to NTFS,
the partition is indeed reported as NTFS and lots of new options shows under
permissions. Just to see what the error message looked like I tried to
access the NTFS partition via the network from the 98SE machine. Much to my
surprise, I am able read and write to the NTFS partition from Windows 98SE.
I thought this was supposed to be impossible, at least without third party
Anyone have a clue as to what is going on here? Why is 98SE able to read and
write to the NTFS partition? The possibilities that I am considering are:
1. Perhaps because the 2000 machine boots from a FAT 32 partition, and
resides on a FAT 32 partition?
2. Perhaps the 98SE machine can read NTFS because it is a dual boot machine?
3. Perhaps it is due to the partition being converted from FAT 32, instead
of originally being NTFS?
I tried Google and had no luck as to resolving this puzzle, so any
information or insights would be much appreciated.
"Tony Sivori" <TonyS...@yahoo.com> wrote in message
"Tony Sivori" <TonyS...@yahoo.com> wrote in message news:amid7o$66q9d$1...@ID-140514.news.dfncis.de...
because it's not the W98 machine that's reading/writing to the NTFS
partition. The W2000 machine is doing the disk access and sending the data
over the network to the W98 machine.
This is a rather common misconception that needlessly scares a lot of
people away from NTFS. The only time to be concerned is when you are dual-
booting W98 and W2000 on the same physical PC and you need to access the
W2000 data while running W98.
...and there are utilities that get past this problem as well.
Thanks for the info. I wasn't aware of that exception. Today was a good day;
I learned something both new, and practical. :-)