How Windows 98 Handled Dual-Boot with Windows NT

During the late 1990s, running both Microsoft Windows 98 and Windows NT on a single machine was a common strategy for users who needed the gaming and multimedia compatibility of the consumer 9x line alongside the stability and security of NT. This article explains how dual-booting worked between the two operating systems, focusing on boot loader architecture, installation sequence requirements, file system limitations, and system management.

The Role of the NT Boot Loader (NTLDR)

Windows 98 relied on the traditional MS-DOS boot mechanism (IO.SYS and MSDOS.SYS), which could not natively manage multiple operating systems on its own. Windows NT, however, used a dedicated boot manager consisting of NTLDR, NTDETECT.COM, and the boot.ini configuration file.

To achieve a functioning dual-boot system, Windows NT’s boot loader had to control the startup process. When NT was installed on a system already containing Windows 98, the NT setup program read the existing Windows 98 boot sector, saved it as a hidden file named BOOTSECT.DOS in the root directory of the primary boot drive, and wrote its own boot code to the Master Boot Record (MBR). During startup, NTLDR displayed a menu defined by boot.ini. Selecting Windows 98 prompted NTLDR to load BOOTSECT.DOS into memory, effectively chaining execution back into the standard Windows 98 startup process.

The Critical Installation Order

The order of installation was essential to avoid boot corruption:

  1. Windows 98 First: The correct method was to install Windows 98 first. Because Windows 98 was unaware of Windows NT's modern boot mechanism, its installer would unconditionally overwrite the drive's boot sector with standard DOS boot code.
  2. Windows NT Second: Installing Windows NT afterward allowed its installer to detect the existing MS-DOS/Windows 98 installation automatically. NT preserved the 98 boot sector, generated BOOTSECT.DOS, and created a boot menu entry typically labeled "Previous Operating System on C:" or "Microsoft Windows".

If a user installed Windows 98 after Windows NT, the NT boot loader was overwritten, making Windows NT inaccessible until the boot sector was manually repaired using the Windows NT Emergency Repair Disk (ERD) or the NT Setup CD.

File System Compatibility and Partitioning

File system differences created the largest functional divide between the two operating systems:

  • FAT16: Universally supported by both Windows 98 and Windows NT, but limited to partition sizes of 2 GB (or 4 GB under specific NT configurations with 64 KB clusters).
  • FAT32: Introduced prominently in Windows 98, allowing larger partitions and more efficient cluster sizes. However, Windows NT 4.0 had no native support for FAT32.
  • NTFS: Windows NT’s native file system offered advanced security, permissions, and reliability. Windows 98 had no native support for NTFS.

To make the dual-boot work smoothly, the primary partition (C:) generally had to be formatted as FAT16 so both operating systems could access the initial boot files. Users typically kept operating systems on separate partitions: a FAT16 or FAT32 partition for Windows 98 and an NTFS partition for Windows NT. Data sharing between the two OS environments was usually handled via a shared FAT16 partition, as third-party read/write utilities for FAT32 on NT or NTFS on 98 were prone to instability.

Driver and Application Separation

Windows 98 and Windows NT ran on completely distinct kernels. Windows 98 relied on Virtual Device Drivers (VxDs) and early Windows Driver Model (WDM) architecture, while Windows NT used the NT kernel driver model. Hardware components, such as graphics cards and sound cards, required two separate driver packages installed independently in each operating system. Similarly, applications could not simply be shared across the two systems; software requiring registry entries, shared system DLLs, or specific kernel calls had to be installed twice—once while booted into Windows 98, and once while booted into Windows NT.