Architecture News

Unearthing the Digital Past: From Paper to Open Source

The Genesis of a Digital Archeological Project

The journey to open-source 86-DOS 1.00 commenced on its 45th anniversary, with Microsoft announcing its availability on GitHub. This release is more than a simple file upload; it represents a triumph of historical preservation. Unlike modern software, the initial versions of 86-DOS were not digitally archived, presenting a unique challenge for those seeking to safeguard its legacy.

The Challenge of Non-Digital Archives: Transcribing History

Tim Paterson, the original creator of DOS, possessed the sole remaining copies of the source code for various essential components, including assemblers and critical utilities like CHKDSK. These were not digital files but physical printouts. To transform these paper records into a usable, downloadable format for GitHub, an intensive process of manual transcription and scanning was required.

A Dedicated Team's Commitment to Computing History

The monumental task of digitizing these invaluable historical documents was spearheaded by a committed group of historians and preservationists. Led by Yufeng Gao and Rich Cini, this team meticulously worked to locate, scan, and accurately transcribe Paterson's collection of DOS-era source listings, bridging the gap between paper archives and the digital realm.

The Origins of 86-DOS: A Quick and Dirty Start

For those unfamiliar with its early days, 86-DOS was conceived by Tim Paterson for an Intel 8086-based computer kit marketed by Seattle Computer Products. Pre-dating the version made public, an even earlier iteration of the OS was colloquially known as QDOS, an acronym for "quick and dirty operating system." This origin story humorously colors the perception of the term 'DOS' as 'Dirty Operating System' for some.

Microsoft's Acquisition and Renaming: The Birth of MS-DOS

Microsoft's involvement began when it licensed 86-DOS for the groundbreaking IBM PC 5150. Following this, Tim Paterson was brought on board in 1981 to continue the operating system's development. By 1982, the OS was rebranded as MS-DOS, though it maintained the version numbering established by 86-DOS.

A Growing Repository of Open-Source History

This release is part of a broader effort by Microsoft to make historical operating system source codes publicly available. Previous releases include MS-DOS 1.25, 2.0, and 4.0, all accessible through the same DOS History GitHub repository. For enthusiasts of computing history, this growing collection offers an unprecedented opportunity to explore the foundational code that shaped modern personal computing. A particularly nostalgic addition for some is the open-sourcing of Microsoft 3D Movie Maker from 1995, offering a glimpse into the creative tools of a bygone era.

Valve: "We're bummed, but committed to quality amidst global supply woes."

Valve's Hardware Vision: Initial Excitement and Unexpected Setbacks

Valve introduced its ambitious hardware trilogy, featuring the Steam Controller, Steam Machine, and Steam Frame, generating considerable anticipation. The Steam Controller was the first to emerge, launched on May 4th of this year, and has garnered positive feedback. However, the Steam Machine, initially slated for an early 2026 release, has faced postponements. Despite the enthusiasm, the company grapples with persistent questions regarding its official launch date.

Behind the Delays: Navigating a Turbulent Supply Chain

Valve representatives Steve Cardinali and Lawrence Yang openly discuss the company's disappointment regarding the Steam Machine's delayed availability. Yang points to widespread industry challenges, including shortages and price increases for critical components like RAM and memory. These market instabilities have made it difficult to finalize pricing and release schedules, impacting all hardware products that rely on these parts.

Engineering Frustration: The Quest for Resolution

Cardinali expresses the frustration felt by the engineering team, who find themselves confronting unexpected hurdles at the final stages of product development. Despite these setbacks, the team is working diligently to find solutions and overcome the production challenges. Their primary goal remains to ensure the Steam Machine is released as soon as these issues are adequately resolved.

Strategic Prioritization: Launching the Steam Controller First

Despite the shared developmental lineage and simultaneous announcement of Valve's hardware lineup, the company recognized early on that the Steam Controller might ship independently. Yang clarifies that there was no intention to artificially synchronize the releases; instead, each product would launch when fully prepared. The decision to release the Steam Controller ahead of the Steam Machine was a practical one, driven by its readiness and the logical progression of product integration.

Addressing Market Speculation: Commitment to Product Readiness and Stock

Yang addresses rumors about Valve deliberately holding back the Steam Controller. He asserts that the controller's release timeline was solely based on its readiness, including finalized firmware and sufficient stock to meet anticipated demand. Cardinali corroborates this, emphasizing the importance of having ample supply to prevent immediate sell-outs upon launch, even as they acknowledge the possibility of exceeding expectations. Valve remains confident in its ability to manage stock for the Steam Controller, though the true extent of demand will soon be revealed.