Feeds

Apple releases previously SECRET OPERATING SYSTEM SOURCE CODE

OK, fanbiois, start your assemblers

SANS - Survey on application security programs

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. ®

3 Big data security analytics techniques

More from The Register

next story
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Oh no, Joe: WinPhone users already griping over 8.1 mega-update
Hang on. Which bit of Developer Preview don't you understand?
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
Internet-of-stuff startup dumps NoSQL for ... SQL?
NoSQL taste great at first but lacks proper nutrients, says startup cloud whiz
IRS boss on XP migration: 'Classic fix the airplane while you're flying it attempt'
Plus: Condoleezza Rice at Dropbox 'maybe she can find ... weapons of mass destruction'
Ditch the sync, paddle in the Streem: Upstart offers syncless sharing
Upload, delete and carry on sharing afterwards?
New Facebook phone app allows you to stalk your mates
Nearby Friends feature goes live in a few weeks
Microsoft TIER SMEAR changes app prices whether devs ask or not
Some go up, some go down, Redmond goes silent
prev story

Whitepapers

Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Top three mobile application threats
Learn about three of the top mobile application security threats facing businesses today and recommendations on how to mitigate the risk.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.