Well, here's the issue. First off, you'd never be able to run the OS from an NTFS drive, it would require far too major changes to the closed source kernel we don't have access to. It's not very hard to write a program to read/write NTFS drives, maybe by the use of a simple virtual real mode driver. However, when you speak of system wide NTFS support, you are talking a far more complex job. In order to natively support a different file system, and have explorer, amongst all Windows applications be able to write to NTFS as if it were nothing, you'd have to implement the support at the kernel level. Again, when you speak of file systems in the kernel, being closed source makes this a whole hell of a lot more difficult. All of the GUI in Windows, including the applications, deal very little with the actual disk access of the operating system. How it works is that a basic write command in the code is sent (such as C++ or VB). When compiled, this code speaks to the APIs for that programming language, which are specifically written differently for each operating system to inferace with the kernel and other lower level code. It is THAT code, that then deals with the physical disk, and therefore, the file system. So the changes would have to be made at that level to pass up the benefits to all applications, and even Windows Explorer, which is just a basic Windows program, set as shell in boot.ini. My guess as to why no one has bothered to implement this in Windows 98 is because it never really crossed paths that much when Windows NT began to rise up, and now, there's far too few Windows 98 active users where anyone would take the initiative, time, and energy required to make this undertaking.