The HP 2100 simulator provides a software model of Hewlett-Packard’s 21xx and 1000 M/E/F-Series computers, a family of real-time systems built around a shared 16-bit instruction set. For engineers and technical teams interested in legacy computer architecture, it offers a way to configure a virtual system and observe processor, memory, and peripheral behavior without operating the original hardware.
Rather than reproducing a front panel, the simulator uses commands to perform actions such as starting the processor, examining memory, setting registers, attaching media, and booting from a device. Understanding this command-based approach helps users work with the model while keeping its scope and limitations in view.
What the HP 2100 simulator models
The simulator covers multiple generations of HP systems, from the 2114, 2115, and 2116 through the HP 2100 and 1000 M/E/F-Series. These machines use an accumulator-oriented, 16-bit architecture. Their base instruction set supports memory, arithmetic and shift operations, and input/output. Later models add features such as index registers, extended instructions, floating-point options, and dynamic memory mapping.
Memory and addressing depend on the configured system. The family’s logical address space is 15 bits, or up to 32K words, while supported 1000-series configurations can use memory expansion beyond that logical range. With Dynamic Mapping System (DMS) enabled, logical pages map to physical memory pages through map registers. Separate mappings support system and user programs, as well as the two data-transfer channels.
The simulator also models hardware options that affect system behavior, including Direct Memory Access (DMA), the Dual-Channel Port Controller (DCPC), memory protection, and memory expansion. This makes configuration more than a matter of selecting a processor model: the enabled options shape how software can address memory and communicate with peripherals.
Peripheral and operating-system coverage
A virtual system can include a broad selection of I/O devices. The documented models include paper-tape readers and punches, teleprinters, line printers, asynchronous multiplexers, disc and drum interfaces, magnetic-tape controllers, and a processor interconnect. Several controllers support multiple attached units; for example, one simulated disc controller may connect to several drives.
The simulator supports a range of historical operating systems, including DOS variants, RTE real-time executives, and HP 2000 time-shared BASIC systems. The guide also reports that the implementation generally passes the HP 24396 Stand-Alone Diagnostics suite. These capabilities make it possible to examine interactions among an operating system, the processor, and simulated I/O hardware.
There are important boundaries. The implementation covers 21xx and 1000 M/E/F-Series systems, but not the 1000 L/A-Series. Although those machines share the base instruction set, their I/O structure differs, and their interfaces are not interchangeable with the models provided. The guide treats an L/A-Series implementation as a separate simulator project rather than an extension of the existing device set.
Configuring devices and controlling execution
Commands at the Simulation Control Program (SCP) prompt stand in for many physical controls. GO starts or resumes execution, while RESET presets installed I/O interfaces. EXAMINE and DEPOSIT let users inspect or change memory and registers. The STEP command supports single-instruction execution, and breakpoints can be set to pause execution at selected logical addresses.
Device media is represented by image files attached through commands. For instance, attaching an image to a paper-tape reader models loading tape into that peripheral. Boot operations can be performed step by step with loader commands or through a BOOT command, which combines loading, resetting, and running the applicable bootstrap program. Loader selection and configuration depend on the processor model and the device interface’s select code.
Select codes represent I/O interface addresses. They can be assigned to many devices within the supported range, while some system components have fixed assignments. Devices can also be enabled or disabled to represent whether an interface or connected unit is present. Because device combinations and select-code assignments affect program I/O, configuration should be checked before execution.
Timing, tracing, and practical interpretation
Device operations such as disc seeks, tape transfers, and printer movement are scheduled using event ticks, generally counted as the simulated processor executes instructions. The guide describes three timing modes. Realistic timing aims to match the number of simulated instructions that would elapse during a hardware operation. Calibrated timing aligns simulated operation periods with elapsed time on the host system. Optimized timing is available as a separate mode; the supplied documentation excerpt does not specify its detailed behavior.
Timing mode matters when interpreting a run. Realistic timing is intended to preserve the relationship between device delays and the amount of simulated program execution. Calibrated timing instead relates device periods to host elapsed time. Neither should be confused with a measurement of performance on original equipment.
The simulator also provides tracing facilities for CPU and I/O activity, and can be configured to stop on conditions such as an unimplemented instruction, an I/O instruction referencing an unassigned select code, or certain device errors. These controls help users investigate execution and configuration problems in a repeatable way.
Conclusion: use the model within its defined scope
The HP 2100 simulator brings processor models, memory options, peripheral interfaces, and command-driven controls together in one configurable environment. For industrial automation and systems professionals, its practical value lies in exploring how a legacy real-time computer and its I/O ecosystem are structured—not in treating the simulation as a direct substitute for hardware-specific validation. Select the appropriate processor and devices, verify interface assignments, choose timing deliberately, and account for the simulator’s documented model boundaries when interpreting results.