The Altos 8600 was announced by Altos in 1980 as the "ACS 16000" and was launched in November of 1981. It was based on the Intel 8086 processor with a 8089 communications co-processor. This is the first Altos machine that supported the Xenix operating system. The disks were 8" based, both for floppy and hard disks. The entry level unit was equipped with 128kByte RAM and a single 1MB floppy drive for $8990. The high-end version of this computer had 512kB RAM and a 40MB hard drive, and cost a whopping $18980 at launch. These computers propelled Altos to become the leading 8086-based Unix vendor by 1983.

The Altos 8600 was a multiuser microcomputer and targeted at the small business and departmental computing markets. Altos Computer Systems, based in San Jose, designed the machine to deliver minicomputer-style functionality at a much lower cost, leveraging the new generation of 16-bit CPUs. The 8600 typically shipped with between 256 KB and 1 MB of RAM, Winchester hard drives for mass storage (commonly 10 MB or 20 MB configurations), and a set of serial ports to connect multiple terminals. Its system architecture was optimized to support multiuser operating systems, making it a strong platform for environments where several employees needed concurrent access to shared resources.

Operating system support was a key differentiator for the Altos 8600. It ran Microsoft’s Xenix, a Unix derivative, as well as MP/M-86 (Digital Research’s multitasking, multiuser version of CP/M-86). With Xenix, the Altos 8600 could support four, eight, or even more terminals, each logged into a separate shell session, with true multitasking and multiuser isolation. MP/M-86 offered a lighter-weight alternative for those coming from a CP/M background, still providing multitasking and resource-sharing features but with less of the Unix complexity. The availability of these operating systems turned the Altos 8600 into a capable small-office computing server, handling accounting, word processing, and database tasks simultaneously for multiple users.

In the marketplace, the Altos 8600 competed with early minicomputers from DEC and Data General, as well as other 8086-based multiuser micros like the Cromemco and Fortune systems. Its relative affordability, combined with the robustness of Xenix, gave it a niche among small to medium-sized businesses that needed serious computing power without the expense of a full minicomputer installation. For retrocomputing enthusiasts today, the Altos 8600 represents an important transitional machine—showing how Unix and multiuser computing were brought into the microcomputer space, and how companies like Altos helped shape the path between the CP/M era and the workstation/server market that Unix would later dominate.

Xenix was Microsoft’s port of AT&T Unix to microcomputer platforms, beginning in the early 1980s, and represents one of the first serious attempts to bring Unix down from minicomputers and workstations into the 16-bit microprocessor world. It was derived initially from Version 7 Unix and later System III, adapted to run efficiently on hardware like the Intel 8086/8088, Zilog Z8000, and later the Motorola 68000. Unlike MS-DOS, Xenix was a fully preemptive, multitasking, multiuser system, exposing the same hierarchical file system, permissions model, process control primitives, and interprocess communication features familiar from its minicomputer ancestors. For developers, this meant that on relatively modest hardware, one could run a standard C compiler, link editor, assembler, and make use of pipes, redirection, and shell scripting—capabilities nearly absent from DOS at the time.

One of Xenix’s key engineering challenges was adapting Unix’s relatively heavy kernel model to machines with limited RAM and no memory management hardware. The 8086 implementation, for instance, had to work within a segmented memory model, forcing Microsoft’s engineers to fit process address spaces into 64 KB segments and implement kernel/user separation in a constrained way. Despite these limitations, Xenix supported demand-paged swapping, multiple terminals connected via serial interfaces, and block-structured file systems with mountable volumes. Device drivers were modular, and the system could support Winchester hard drives, tape backups, and various terminal types. For systems like the Altos 8600 series, this meant Xenix could handle up to 8 or more users running concurrently, each with their own shell and processes.

From a systems perspective, Xenix was significant because it created a bridge between the proprietary minicomputer Unix systems and the personal computing world. It brought features like multiuser time-sharing, background jobs, and networking primitives (in later releases) to machines typically seen as “single-user” boxes. Many third-party ISVs wrote business applications specifically for Xenix, including accounting packages, word processors, and database systems, leveraging its stability and multiuser design. Although eventually eclipsed by DOS and later Windows in the Microsoft ecosystem, Xenix seeded a Unix culture into the microcomputer world and influenced later efforts such as SCO Unix, which inherited much of Xenix’s base and kept it alive into the 1990s. For retro computing enthusiasts, it remains a fascinating example of Unix squeezed into 16-bit constraints yet still delivering an authentic multiuser Unix environment.

CP/M-86 was the 16-bit successor to Gary Kildall’s original CP/M (Control Program for Microcomputers), which had dominated the 8-bit microcomputer market in the late 1970s. Introduced in 1981, CP/M-86 was adapted to run on Intel’s 8086 and 8088 processors, providing a familiar environment for developers and users migrating from 8-bit systems like the Intel 8080 and Zilog Z80. It retained the fundamental architecture of CP/M: a resident operating system split into the BIOS (hardware-dependent routines), BDOS (the core file and device management logic), and the CCP (Console Command Processor, which provided the user’s command interface). With this modular design, vendors could customize CP/M-86 for their hardware while maintaining compatibility with application binaries.

Technically, CP/M-86 offered a flat file system with 8.3 filename conventions, sequential or random file access methods, and support for user areas (a primitive form of directory segmentation). The BDOS interface provided consistent system calls for file manipulation, console I/O, and device access, allowing software to be written once and deployed across different machines. Because the 8086 architecture used segmented memory addressing, CP/M-86 had to manage memory in 64 KB segments, but unlike MS-DOS it did not adopt the same FCB (File Control Block) compatibility hacks. Instead, it extended some of its BDOS functions to better utilize the wider word size of the 16-bit environment, though its lineage remained evident in the command set and utility structure inherited from the 8-bit CP/M.

Despite its technical merits, CP/M-86 struggled in the marketplace. It was priced higher than Microsoft’s competing MS-DOS and often shipped later than DOS on the same hardware, such as the IBM PC. While CP/M-86 could run a growing library of native software and offered a smoother transition for CP/M-80 developers, its limited adoption meant fewer commercial applications and reduced support over time. By the mid-1980s, MS-DOS had effectively displaced CP/M-86, though its influence persisted in the modular OS structure and command conventions that many users carried forward. For retrocomputing enthusiasts, CP/M-86 represents an intriguing “what-if” moment—an alternate trajectory where the dominant 8-bit operating system of the late ’70s attempted to evolve into the 16-bit world but was ultimately overshadowed by Microsoft’s more aggressively marketed DOS.

The 8086 CPU from Intel is a 16-bit microprocessor and was designed between 1976 and 1978. The 8086 is the foundation of the x86 cpu architecture which is Intel's most successful line of processors.

The 8086 used the same microarchitecture as the 8-bit 8008, the 8080, and the 8085. This allowed assembly language programs to run seamlesly on the 8086. New instructions and features were added and the bus structure was designed to allow for collaboration with co-processors, such as the 8087 that was released later.

The Intel 8089 Input/Output Coprocessor (IOP), introduced in the early 1980s, was designed as a companion chip to the Intel 8086/8088 CPUs. Its primary purpose was to offload complex I/O tasks from the main processor, enabling more efficient multitasking and data transfer. The 8089 featured its own instruction set, internal registers, and control logic, allowing it to independently manage peripheral devices such as disks, printers, and communication interfaces. By handling I/O operations asynchronously, it reduced CPU overhead and improved system throughput, particularly in multitasking operating systems and environments requiring high-performance data management.

The 8089 could coordinate multiple I/O channels simultaneously, using a specialized structure called Task Blocks to define control parameters for each operation. This design enabled efficient Direct Memory Access (DMA)-like transfers and real-time communication between memory and peripherals without constant CPU intervention. Architecturally, the 8089 was sophisticated for its time, providing mechanisms for priority handling, interrupts, and concurrent task execution. Though not as widely adopted as other Intel support chips, it represented an early step toward intelligent peripheral controllers and laid groundwork for later advancements in bus-mastering I/O and dedicated DMA engines.