Windows 98 Batch Automated Installation Guide

Microsoft Windows 98 automated large-scale deployments using setup scripts centered around an answer file named MSBATCH.INF. By pre-populating configuration choices—such as network settings, product keys, regional options, and component selections—system administrators could bypass the manual Setup wizard. This unattended setup process relied on built-in command-line switches and a dedicated utility called Microsoft Batch 98 to streamline OS deployment across multiple machines without user intervention.

The Microsoft Batch 98 Utility (BATCH.EXE)

To avoid manually typing complex configuration directives, administrators used the Microsoft Batch 98 tool (BATCH.EXE), included in the Windows 98 CD-ROM under the \tools\reskit\batch directory.

Batch 98 provided a graphical interface that allowed administrators to:

  • Read the current system registry to automatically clone hardware settings, installed network protocols, and peripheral configurations.
  • Predefine user profiles, computer names, workgroups, and domain memberships.
  • Set installation switches to suppress specific user prompts, such as the End User License Agreement (EULA), Startup Disk creation, and Scandisk execution.
  • Export the selected configuration directly into a standardized MSBATCH.INF file.

Structure of MSBATCH.INF

The MSBATCH.INF file is an INI-style text file broken down into distinct brackets and key-value pairs that the Windows 98 Setup engine parses sequentially:

  • [Setup]: Defines general installation parameters. Key directives include Express=1 (suppresses user prompts), InstallDir="C:\WINDOWS", and EBD=0 (disables the prompt to create an Emergency Boot Disk).
  • [NameAndOrg]: Specifies the target user name, organization, and whether to prompt the user to verify them.
  • [CleanBoot]: Configures whether setup executes an automated clean boot prior to copying files.
  • [Network]: Configures network adapters, protocol stacks (such as TCP/IP, NetBEUI, or IPX/SPX), client bindings (Client for Microsoft Networks or NetWare), and computer identification strings.
  • [OptionalComponents]: Dictates whether optional accessories, system tools, communication utilities, or games should be installed or omitted using binary flags (1 for install, 0 for skip).

Executing the Automated Setup

Once the MSBATCH.INF script was generated, administrators initiated the installation from MS-DOS, a network share, or a local directory using SETUP.EXE followed by the script path:

setup.exe msbatch.inf

Setup scripts were frequently paired with standard Windows 98 setup command-line switches to eliminate remaining delays and prompts:

  • /ie: Skips the prompt to create an Emergency Boot Disk.
  • /is: Bypasses the initial Scandisk check on target drives.
  • /im: Skips checking for available conventional memory.
  • /id: Bypasses the disk space check.

Deployment Methods

Administrators deployed scripted installations through three primary workflows:

  1. Network Share Deployments: The Windows 98 installation files (WIN98 cabinet files) and MSBATCH.INF were hosted on a shared network drive. Target PCs booted via MS-DOS network boot disks, mapped the network drive, and launched Setup via an automated AUTOEXEC.BAT file.
  2. Custom CD-ROM Media: Administrators burned customized installation discs containing the source installation files alongside a pre-configured MSBATCH.INF placed directly in the root or \WIN98 directory.
  3. Local Hard Drive Preloading: Disk-cloning tools or simple batch files copied the setup files and script to a staging folder on the local hard drive (such as C:\WIN98), after which Setup was called directly from the local file system.