Access Official Technical PDF

Share Summary:LinkedInEmail

Q-bus computer systems were designed to bring flexible computing to technical, commercial, and industrial environments. Digital Equipment Corporation’s supermicrosystem family included the 32-bit MicroVAX I and MicroVAX II, alongside the 16-bit MicroPDP-11/23, /73, and /83. Although these machines used different processor architectures, they shared a modular hardware approach centered on the Q22 bus. That common foundation shaped how systems could be configured, expanded, and connected.

What defined a supermicrosystem?

DEC described its supermicrosystems as low-cost, medium- to high-performance computers intended for realtime, timesharing, and batch workloads. The family served settings such as laboratories, factories, medical organizations, and engineering groups, as well as commercial offices. The systems were not a single interchangeable computer design: MicroVAX models implemented the 32-bit VAX architecture, while MicroPDP-11 models used the 16-bit PDP-11 architecture.

That distinction mattered for software and compatibility. MicroVAX systems could run software developed for larger VAX computers, while MicroPDP-11 systems aligned with the broader PDP-11 ecosystem. Both families offered operating systems, programming languages, information-management software, and development tools suited to their respective architectures.

The Q22 bus as a shared hardware foundation

The 22-bit Q-bus, also called the Q22 bus, carried data, address, and control information among the CPU, memory, and device interfaces. In practical terms, it provided a common path for connecting core computing components and supported compatible options across the supermicrosystem family.

The bus also supported four-level interrupts and block-mode direct memory access (DMA). DMA allows a device interface to transfer blocks of data to or from memory without requiring the CPU to handle every transfer step. The handbook describes physical-memory support of up to 4 Mbytes for MicroPDP-11 systems and the MicroVAX I, and up to 9 Mbytes for the MicroVAX II system configurations described there.

Sharing a bus and many options could simplify system planning. Memory, storage, communications interfaces, and other components were available across multiple models, although compatibility depended on the particular configuration. Common components could also make migration between systems more practical when processing needs changed.

Choosing between MicroVAX and MicroPDP-11

Processor selection was one of the central design decisions. The MicroVAX I and II used different CPU implementations of the VAX architecture. The MicroPDP-11/23, /73, and /83 likewise used distinct PDP-11 processors, with differing performance and features. The systems ranged from configurations intended for moderate-speed realtime work to those designed for larger multiuser and multitasking workloads.

The handbook gives indicative concurrent-user capacities, but emphasizes that actual user counts depended on both the application and the system configuration. For example, it lists the MicroVAX II and MicroPDP-11/83 as able to accommodate over 30 concurrent, active users under suitable conditions. These figures should be understood as configuration-dependent guidance, not as a universal measure of workload capacity.

Modular configuration: enclosure, memory, and peripherals

Systems could be packaged in floorstand, pedestal, tabletop, rackmount, or cabinet enclosures. Depending on the enclosure, the chassis provided a backplane, power supply, control panel, input/output distribution, cooling, and space for mass-storage devices. Available backplane sizes and device capacity differed by enclosure, making physical layout part of the configuration process.

Beyond the CPU and enclosure, system planners selected from several classes of options:

  • Memory and performance: memory modules and, for supported configurations, floating-point processors or accelerators.
  • Storage: disk controllers, fixed and removable disks, flexible disks, cartridge tapes, streaming tape, and CD-ROM-related equipment.
  • Communications and realtime interfaces: asynchronous and synchronous interfaces, plus interfaces intended for realtime applications.
  • Operator and user devices: terminals, printers, and modems.

Because these systems were modular, configuration meant matching processor, memory, storage, interfaces, and enclosure to the workload—not simply selecting a CPU in isolation. Slot availability, bus compatibility, and the intended devices all influenced the final design.

Software and networking extended system roles

The software portfolio covered operating systems, high-level languages, data and information-management tools, programmer productivity products, and communications software. MicroVAX and MicroPDP-11 systems had software tailored to their architectures, while both families offered capabilities in areas such as development, data handling, and system communications.

Networking supported both standalone use and distributed processing. DECnet could connect systems to share files, programs, and resources, while Ethernet provided a local-area networking option. The handbook also describes Internet software for communications with other manufacturers’ equipment using supported protocols, and Packetnet connections through public X.25 packet-switched networks. These choices allowed a supermicrosystem to operate as an individual computer or as part of a wider computing environment.

Practical implications for system planning

For engineers and technical decision-makers, the supermicrosystem approach illustrates the importance of evaluating an entire platform. Processor architecture determines software compatibility; the bus influences which modules can be integrated; and memory, storage, interfaces, enclosure, and network links determine how well the configured system fits its intended role.

DEC’s MicroVAX and MicroPDP-11 families brought these decisions together in a shared, modular Q22-bus environment while preserving distinct 32-bit and 16-bit architectures. The practical lesson is that system capability depends on the combination of components and software, not on a processor specification alone. Careful configuration was essential to matching a system to realtime, multiuser, data-processing, or networked applications.

Access Official Technical PDF

About The Author