Farewell to Dr Tim King, one of the key minds behind AmigaDOS

Dr Tim King, one of the engineers closely associated with the creation of AmigaDOS, died at the end of July 2026. His name may not be as widely known as the Amiga brand itself, but his work sits right at the heart of the machine’s operating system. King’s main contribution came through TRIPOS, an operating system developed in academia and later adapted into the foundation of AmigaDOS. That software became responsible for many of the everyday jobs an Amiga had to handle, including files, directories, devices, scripts and command-line operations. In practical terms, AmigaDOS was the part of the system users met whenever they worked beyond the graphical desktop.

From Cambridge to TRIPOS

King studied computer science at the University of Cambridge, graduating in 1976 before completing a PhD in 1979. His early work covered databases and operating systems, and he later held academic posts at Cambridge and the University of Bath. A major part of that work involved TRIPOS.

TRIPOS was a portable operating system written largely in BCPL, a programming language that predated C and had a strong influence on early systems software. The idea behind TRIPOS was fairly straightforward: build an operating system that could move between different hardware platforms without starting again from scratch each time. That became particularly useful when the Amiga entered the picture.

TRIPOS had already been adapted for Motorola 68000 processors. Since the original Amiga also used a Motorola 68000, there was an obvious technical fit. Commodore needed a working DOS component for the new machine, and TRIPOS offered a base that could be adapted far more quickly than building a completely new system.

How TRIPOS became AmigaDOS

King joined British software company MetaComCo in 1984 as director of research and development. He brought the 68000 version of TRIPOS with him, and MetaComCo went on to develop it into AmigaDOS. That distinction matters because AmigaDOS wasn’t the entire Amiga operating system.

The Amiga’s software architecture combined several major components. Exec handled low-level multitasking and system services. Intuition dealt with much of the graphical user interface. AmigaDOS handled files, directories, commands, devices and other jobs normally associated with a disk operating system.

It was a mixture of technologies built by different teams. The TRIPOS roots remained obvious in the early versions. AmigaOS 1.x used an AmigaDOS implementation written largely in BCPL, and many ideas from TRIPOS carried across into the finished machine. Some of them became familiar Amiga features.

Instead of relying only on fixed drive letters or rigid disk paths, AmigaDOS used named devices and logical assignments. Users regularly encountered names such as SYS:, RAM: and DF0:. Programs could also refer to assigned locations instead of depending on one specific physical disk or directory. That gave the system a surprising amount of flexibility for a home computer released in the mid-1980s.

More than a disk interface

AmigaDOS wasn’t limited to copying files and listing directories. Its command-line environment supported scripts, input and output redirection, background execution and a broad set of system commands. Users could automate repetitive jobs, launch programs from scripts and combine commands in ways that went well beyond basic disk management.

And because the Amiga already had pre-emptive multitasking through Exec, command-line tasks could run alongside other software. The early BCPL design wasn’t without problems. As more Amiga software moved toward C and assembly language, the differences between BCPL and the rest of the system became harder to ignore. Passing data between different programming conventions could complicate development, and the original implementation carried technical baggage from its TRIPOS origins.

Commodore eventually addressed that. With AmigaOS 2.x, large parts of AmigaDOS were rewritten in C. The system kept the familiar behaviour and interfaces software relied on, but the underlying implementation became better aligned with the rest of the Amiga development environment.

Work after AmigaDOS

King left MetaComCo and founded Perihelion in 1986. There, his work continued to focus on operating systems, but the hardware was very different. Perihelion developed Helios, a distributed Unix-like operating system designed for parallel computers. It became particularly associated with systems using Inmos transputers, processors created with parallel computing and high-speed communication between chips in mind.

That wasn’t a complete break from King’s earlier work. Operating systems, communication between processes and distributing work across hardware remained central themes. In 1994, King moved into the growing internet business and founded UK Online with backing from Olivetti. The company became an early UK internet service provider and was sold to the EasyNet group in 1996. He later worked in technical consultancy, technology investment, intellectual-property matters and related fields.

The AmigaDOS connection

For Amiga users, though, King’s most direct contribution remains AmigaDOS. The operating system inside the original Amiga wasn’t designed as one single project from the beginning. It came together from several technologies, and TRIPOS solved a very specific problem at a crucial stage: Commodore needed a functioning DOS layer, and it needed one quickly.

King’s work helped provide that foundation. The result became part of every early Amiga user’s daily experience, whether they were opening a command-line window, running a script, assigning a directory, copying files or accessing a device.

AmigaDOS changed considerably in later versions, but its early structure came directly from TRIPOS and the work carried into MetaComCo by Tim King. That places him firmly in the technical history of the Commodore Amiga, not at the edges of it, but inside one of the operating system’s core components. Our sincere condolences to his family and friends.

Spread the love

From Cambridge to TRIPOS

How TRIPOS became AmigaDOS

More than a disk interface

Work after AmigaDOS

The AmigaDOS connection

MORE AMIGA & RETRO NEWS