Stuart Tucker

Stuart G. Tucker was an IBM engineer whose work during the development of System/360 helped turn emulation from an interesting theoretical possibility into a practical computing technique. Working alongside Larry M. Moss and other IBM engineers, Tucker helped develop compatibility methods that allowed new IBM computers to execute software created for older and otherwise incompatible systems.

Tucker is particularly important to historians because he also documented the technology in contemporary technical literature. His 1965 paper Emulation of Large Systems and his 1967 IBM Systems Journal paper Microprogram Control for System/360 provide a direct technical window into what IBM engineers meant by emulation during the technology’s formative years.

The System/360 Compatibility Crisis

IBM’s System/360 project was intended to replace several incompatible computer families with a single scalable architecture. That strategy promised enormous benefits going forward, but IBM’s customers had already invested heavily in applications written for earlier machines.

The problem threatened the transition to the new platform. Businesses might appreciate faster hardware, but few wanted to discard functioning payroll, accounting, inventory, scientific and data-processing programs simply because IBM had introduced a new architecture.

IBM’s official history of System/360 describes compatibility as one of the defining goals of the new family. Yet supporting programs written for pre-System/360 computers required additional engineering beyond the compatibility built into the new product line itself.

Working With Larry Moss

Historical accounts identify Stuart Tucker and Larry Moss as leaders in the effort to combine hardware, software and microprogramming so System/360 machines could reproduce the behavior of older IBM systems.

The flexibility came from microprogrammed control. Instead of implementing every processor operation entirely through fixed circuitry, portions of the machine’s control behavior could be defined at a lower programmable level. That gave engineers the ability to teach the new machine how to interpret instruction sets that had never been part of System/360’s native architecture.

The IBM System/360 retrospective preserved by the Computer History Museum specifically names Tucker and Moss when describing the realization that the new architecture already possessed many of the registers and data paths required to recreate IBM’s older machines.

With additional circuitry, software and microcode, System/360 could present legacy programs with an environment sufficiently familiar that the old software continued to operate.

“Emulation of Large Systems”

Tucker became one of the earliest people to explain emulation formally in the technical literature. His paper Emulation of Large Systems appeared in the December 1965 issue of Communications of the ACM.

The paper addressed the software-conversion problem and described emulation as an alternative method of maintaining compatibility. It discussed both processor and input/output behavior and examined implementations that enabled IBM System/360 hardware to reproduce older IBM systems.

That publication matters because it demonstrates how quickly emulation became established as a serious technical concept. The word was no longer merely an informal label used inside an engineering project; it was entering the professional computer-science literature.

Microprogram Control for System/360

Two years later, Tucker published Microprogram Control for System/360 in the IBM Systems Journal.

The paper explained the microprogramming approach used in several System/360 models and explicitly discussed its usefulness for emulators and compatibility modifications. It described a technology that would become increasingly important as computer designers looked for ways to separate the behavior software expected from the exact circuitry implementing that behavior.

Tucker’s publications therefore occupy an unusual position in the history of emulation: he was involved in the engineering work itself and then helped document the principles behind it.

Why Tucker Matters to Video Game Emulation

Nothing Tucker was doing in the 1960s was aimed at preserving video games. The machines involved were corporate mainframes, and the goal was to protect customer software investments during a massive hardware transition.

Yet the problem was fundamentally the same one future emulator developers would face. A program had been written to communicate with one machine, while the developer wanted it to run on another. The host therefore had to reproduce the behavior the software expected.

When future programmers reproduced a 6502 processor on a PC, recreated a Super Nintendo’s graphics hardware, interpreted a PlayStation’s MIPS instructions or attempted cycle-accurate reproduction of an arcade board, they were working in a technological tradition whose early foundations included Tucker’s System/360 compatibility work.

Stuart Tucker in the History of Video Game Emulation

1960–1989: Before Console Emulation — How the Idea Was Born

Tucker appears in the opening chapter alongside Larry Moss as one of the IBM engineers whose System/360 compatibility work helped establish practical computer emulation.

Related People

Larry M. Moss — Tucker’s collaborator in IBM’s early System/360 emulation work and the engineer closely associated with applying the word emulation to the technique.