Feeds

Apple releases previously SECRET OPERATING SYSTEM SOURCE CODE

OK, fanbiois, start your assemblers

The essential guide to IT transformation

The Computer History Museum has scored something of a coup, publishing – with Cupertino's permission – the source code for the Apple II's DOS, version 3.1.

The archeological code, posted here, is the whole 4,000-plus – that's thousands of lines of code, not millions in a misprint – complete with comments like “if it ain't 3 don't reloc”.

As Computer History Museum notes on its release page, the DOS – which included a file manager, a BASIC interface, and various utilities – was written for US$13,000 (a little over three dollars a line) by Paul Laughton, a contractor for Shepardson Microsystems.

The code was written between April and June 1978 – a fair achievement for a brand new DOS – and by October, according to meeting minutes posted by the Museum, Apple and Shepardson were already working through the bug fixes and discussing the documentation. This kind of discussion still rings true to anyone looking at software development.

For example, there's this exchange involving Laughton and Randy Wigginton (employee number six, and creator of MacWrite):

“Paul has received questions directly regarding our DOS. Evidently he has been in computer stores, etc. when someone was asking questions about the Apple DOS. He also was surprised that we were shipping documentation on the Read/Write a track and sector routine. He felt that documentation on interfacing to the file manager portion of the DOS was more useful. Randy pointed out that documentation does not exist on the file manager.”

Another amusing insight covers “bug #1”:

“There was some controversy as to whether bug #1 was or was not actually specified in the original spec. Paul felt that bug #1 involved some major rework, and was a result of not having a written spec on the DOS.”

As the Museum notes, the Apple II couldn't compile anything, so Laughton had to write the DOS on punch cards for compilation on a National Semiconductor IMP-16, which would spit the assembled code out onto a paper tape. Steve Wozniak, who was responsible for creating the disk controller for the machine, also made a plug-in card to read the paper tapes so that Laughton could debug the code.

Laughton describes more of the history here. ®

Secure remote control for conventional and virtual desktops

More from The Register

next story
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Munich considers dumping Linux for ... GULP ... Windows!
Give a penguinista a hug, the Outlook's not good for open source's poster child
Intel's Raspberry Pi rival Galileo can now run Windows
Behold the Internet of Things. Wintel Things
Linux Foundation says many Linux admins and engineers are certifiable
Floats exam program to help IT employers lock up talent
Microsoft cries UNINSTALL in the wake of Blue Screens of Death™
Cache crash causes contained choloric calamity
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
Linux kernel devs made to finger their dongles before contributing code
Two-factor auth enabled for Kernel.org repositories
prev story

Whitepapers

Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 10 endpoint backup mistakes
Avoid the ten endpoint backup mistakes to ensure that your critical corporate data is protected and end user productivity is improved.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.