Boot Windows 98 to Command Line: Crucial Files

Microsoft Windows 98 was built on an MS-DOS 7.1 foundation, meaning it could start directly into a command prompt without launching the graphical user interface. Booting into this pure real-mode environment relied on a minimal set of core bootstrap files, configuration scripts, and a command interpreter located on the root directory of the boot drive.

The Essential Core Files

To successfully reach a functional command line prompt in Windows 98, three foundational system files were strictly required:

  • IO.SYS
    This is the primary real-mode operating system kernel. During the boot process, the Master Boot Record (MBR) and Volume Boot Record (VBR) locate and execute IO.SYS. In Windows 98, IO.SYS combined many legacy MS-DOS functions, initializing essential hardware components, basic memory routines, and standard input/output devices. It serves as the foundation before any user interface or configuration scripts load.

  • MSDOS.SYS
    Unlike earlier versions of standalone MS-DOS where this was a compiled binary kernel, Windows 98 turned MSDOS.SYS into a plain text configuration file. It contained crucial directives that dictated how the system booted. Setting BootGUI=0 inside MSDOS.SYS prevented the Windows graphical environment (WIN.COM) from launching automatically, instructing the operating system to halt at the command line.

  • COMMAND.COM
    This is the default command-line interpreter. Once IO.SYS finished initializing system resources and processing boot directives, it handed execution over to COMMAND.COM. This file provided the interactive prompt (C:\>), handled internal commands (such as DIR, COPY, and DEL), and managed batch file execution. Without COMMAND.COM (or an alternative shell specified via configuration), the boot sequence would halt with an error stating the command interpreter could not be found.

Secondary Configuration and Driver Files

While the core trio could deliver a bare-bones prompt, stable and fully functional command line operation typically required additional files:

  • CONFIG.SYS
    A text file processed by IO.SYS during startup to configure device drivers and system memory parameters. It allowed users to load device drivers using DEVICE= statements and configure file allocation limits with commands like FILES= and BUFFERS=.

  • AUTOEXEC.BAT
    A batch script executed automatically by COMMAND.COM upon loading. It set environment variables such as PATH and PROMPT, initialized resident utilities (TSRs) such as mouse drivers (MOUSE.COM), and configured keyboard layouts.

  • HIMEM.SYS
    An extended memory manager commonly loaded via CONFIG.SYS. While a basic prompt could run in the base 640 KB conventional memory without it, HIMEM.SYS was essential for enabling access to memory above 1 MB (XMS) and high memory areas (HMA), which many DOS-era utilities and software required.