How to Add a System Program in Windows 98

Windows 98 may be decades old, but it still runs on legacy hardware in industrial settings, retro computing setups, and niche hobbyist environments. If you're working with a Win 98 machine and need to install a system program — whether that's a utility, driver package, or bundled OS component — the process follows a specific set of rules that differ meaningfully from modern Windows installations.

Here's what you actually need to know.

What "Adding a System Program" Means in Windows 98

In Windows 98, system programs generally fall into two categories:

  1. Windows components — built-in features that ship with Win 98 but aren't installed by default (things like accessibility tools, system utilities, or communications programs)
  2. Third-party system-level software — external programs that interact with the OS at a deep level, such as drivers, disk utilities, or diagnostic tools

The method you use depends entirely on which type you're dealing with.

Method 1: Adding Built-In Windows Components via Add/Remove Programs

Windows 98 ships with a set of optional components that aren't always installed during setup. To add them:

  1. Click Start → Settings → Control Panel
  2. Open Add/Remove Programs
  3. Click the Windows Setup tab
  4. Browse the list of component categories (Communications, Accessories, System Tools, etc.)
  5. Check the box next to the component you want to add
  6. Click OK or Apply
  7. Insert your Windows 98 installation CD if prompted — Win 98 often needs the original disc to copy system files

💿 The installation CD requirement is important. Windows 98 doesn't cache all component files locally the way modern versions of Windows do. If you don't have the original disc, you may need a mounted ISO or a network share pointing to the Win 98 installation source.

Method 2: Installing a Third-Party System Program

For external utilities or system-level software not bundled with Windows 98:

  1. Obtain the installer — typically a .exe or a set of floppy/CD files
  2. Run the installer by double-clicking the .exe or running setup.exe from the file manager
  3. Follow the on-screen wizard
  4. Restart when prompted — system programs in Win 98 almost always require a reboot to take effect, as they often modify the registry, autoexec.bat, config.sys, or win.ini

Key Files That System Programs Touch in Win 98

FilePurpose
config.sysLoads drivers and sets hardware parameters at boot
autoexec.batRuns startup commands before Windows loads
win.ini / system.iniWindows configuration and program load settings
RegistryStores persistent software and hardware settings

Understanding which files a program modifies can help you troubleshoot if something breaks after installation.

Method 3: Installing Device Drivers as System Programs

In Windows 98, hardware drivers are system programs in a practical sense — they integrate directly with the OS kernel and device manager. To install a driver manually:

  1. Right-click My Computer → Properties
  2. Click the Device Manager tab
  3. Find the device with a yellow exclamation mark (unknown or problematic device)
  4. Double-click it → click Driver tab → click Update Driver
  5. Point the wizard to the folder containing your .inf driver file
  6. Restart after installation

🔧 Windows 98 also supports Plug and Play, so some hardware is detected and configured automatically on reboot — but older or more obscure hardware often requires a manual .inf file from the manufacturer.

Variables That Affect How This Works

Not every Win 98 installation behaves the same way. Several factors shape what you'll encounter:

  • Win 98 vs. Win 98 Second Edition (SE) — SE includes updated drivers, USB improvements, and Internet Connection Sharing. Some programs specifically require SE and won't run on the original release.
  • Available disk space — System programs on Win 98 machines are typically small by modern standards, but very old hard drives may have limited free space, especially if partitioned with FAT16.
  • RAM — Win 98 officially supports up to 512MB of RAM, though real-world stability can vary above 256MB without specific patches applied.
  • Existing software conflicts — Win 98 has no robust app sandboxing. One poorly written system program can destabilize the entire OS. Installing system utilities one at a time and testing between installs is good practice.
  • Source media condition — Installation CDs and floppy disks degrade over time. Corrupt media is a common reason Win 98 installations fail mid-process.

When the Normal Methods Don't Work

Some scenarios require alternative approaches:

  • No CD drive available: You can copy the Win 98 CAB files to a local folder and point the installer to that path instead of the disc
  • Program won't run on Win 98: Check if it requires a specific runtime (like an older version of DirectX or a Visual C++ redistributable compatible with Win 9x)
  • DOS-based system programs: Some low-level utilities must be run from MS-DOS mode — accessible via Start → Shut Down → Restart in MS-DOS Mode — rather than from within the Windows GUI

The Setup Differences Across User Situations

A technician maintaining a legacy industrial PC faces different constraints than a hobbyist running Win 98 in a virtual machine or on period-correct hardware. Virtual machine users (using something like VirtualBox or VMware with a Win 98 guest) often have smoother access to ISO files and shared folders, while bare-metal users deal with physical media and real hardware compatibility limits. Someone running Win 98 SE with all unofficial patches applied is working in a meaningfully different environment than someone on an unpatched original release.

The steps above hold across most situations — but how smoothly they go, and which edge cases you hit, depends on the specific hardware, the exact version of Windows 98 you're running, and the nature of the program you're trying to add. 🖥️