Windows 95 Network Boot Disk Creation Utility

During the Windows 95 era, deploying operating systems over a local area network or performing network-based recovery required specialized startup floppies loaded with network interface card (NIC) drivers. The primary Microsoft tool designed to generate these disks was the Network Client Administrator, supported by native utilities like Server-Based Setup (NETSETUP.EXE) and the Microsoft Network Client for MS-DOS. This article explains the utilities used to build custom Windows 95 network boot disks, how they functioned, and the critical real-mode drivers required to connect to network shares.

The Primary Tool: Network Client Administrator

The dedicated utility for generating automated network boot disks during the Windows 95 deployment lifecycle was Network Client Administrator (NCADMIN.EXE). Although hosted on Windows NT Server, Microsoft specifically designed this administrative utility to streamline the deployment of Windows 95 across corporate networks.

When launched, Network Client Administrator provided an option labeled Make Network Installation Startup Disk. This feature guided administrators through creating a single 3.5-inch MS-DOS bootable floppy disk containing:

  • A minimal MS-DOS boot environment (IO.SYS, MSDOS.SYS, and COMMAND.COM).
  • The Microsoft Network Client 3.0 for MS-DOS redirected software.
  • Network adapter drivers matching the client target hardware.
  • Network protocol stacks, typically NetBEUI, NWLink (IPX/SPX), or real-mode TCP/IP.
  • Preconfigured AUTOEXEC.BAT scripts that automatically mapped a drive letter to the Windows 95 distribution files on a central server and launched SETUP.EXE.

Windows 95 Server-Based Setup (NETSETUP.EXE)

Within Windows 95 installation media itself, Microsoft provided Server-Based Setup (NETSETUP.EXE), located in the \ADMIN\NETTOOLS\NETSETUP directory on the Windows 95 CD-ROM.

While NETSETUP.EXE primarily configured shared installation directories on network servers, it worked in tandem with network boot floppies. It prepared server shares so that remote-boot workstations or systems booted via network startup disks could run Windows 95 either entirely from the network (diskless workstations) or execute automated, unattended setups using custom configuration files (MSBATCH.INF).

Components of a Custom Windows 95 Network Boot Disk

Administrators who did not have access to Windows NT Server frequently customized the native Windows 95 Startup Disk (created via the Add/Remove Programs applet in the Control Panel) to include network functionality. A fully functional Windows 95 network boot disk relied on several key real-mode components:

  • NDIS 2.0 or ODI Drivers: Windows 95 operated in protected mode once loaded, but booting required 16-bit real-mode network card drivers (typically ending in .DOS, such as EL90X.DOS for 3Com cards or NE2000.DOS).
  • Protocol Manager (PROTMAN.DOS): The driver that coordinated communication between the network adapter driver and network protocols.
  • Network Binding Interface (NETBIND.COM): An executable invoked in AUTOEXEC.BAT to bind the protocol drivers to the network adapter.
  • PROTOCOL.INI: A configuration file defining the specific settings for the network card (interrupts, I/O base addresses, and transceiver types) and the active protocol bindings.
  • Basic Redirector: Software modules such as PROTMAN.EXE, NDISHLP.SYS, and NET.EXE to enable basic NET USE drive mapping commands before the full operating system booted.