A Technical History of Apple's Operating Systems

An anonymous reader writes "As part of his 1680-page book Mac OS X Internals: A Systems Approach, Amit Singh of kernelthread.com wrote a very detailed technical history of Apple's operating systems. Since he had to cut down on the history chapter because of the book's already too-large size, most of this chapter didn't make it to the printed book. Singh has made available the history chapter as a free PDF. The file is 140 pages long, and is generously filled with figures and screenshots. It starts with the internals of the original Apple I and goes through a tour of all operating systems Apple dabbled with, including internals of A/UX, Lisa OS, and such. It even covers details of outside influences like the Xerox Alto, STAR System, Smalltalk, and Sketchpad, and closer to home things like Mach, NeXTStep, and OpenStep."

Comments

Apple ][

[BWJones]

One of the coolest things about the Apple I and Apple ][ was that Apple Computer included the schematics for *all* of the motherboard and CPU design. Everything was documented so that users could build interfaces with both the software and the hardware with a minimum of fuss. So, even though Amit Singh calls the manual included with the Apple ][ as a "preliminary manual, it was remarkably complete.

Despite how far we've come, there are time I really miss my old Apple ][.

Re:Apple ][

[Whiney Mac Fanboy]

was that Apple Computer included the schematics for *all* of the motherboard and CPU design.

God, we have come a long way haven't we - now Apple will cease & desist you for linking to their Service Manual.

God, how I miss the old Apple :-(

Re:Apple ][

[beadfulthings]

My Aged Mum, now in her eighties, bought the first Apple ][ ever sold in her small Southern city and shortly thereafter traded up to the ][c. She was an artist by trade. The first thing she did was to construct a couple of cables that she needed for her work (video was one that I recall). Then she sat down with the manuals, learned Applesoft BASIC, and wrote a program or two that enabled her to generate patterns for complex weaving with a large loom. Eventually she acquired an interface that allowed the Apple to actually drive the loom--it was a complicated system of switches and relays that raised and lowered the various harnesses or frames on the loom. She did all of this when she was past fifty and with no prior training at all, though she was regular in attendance at users' group meetings once a users' group was formed.

I still have (and treasure) bits of cloth of complex, intricate design, created and produced with the aid of that Apple. She truly made it an extension of herself.

Re:Apple ][

[booch]

I think that's what they wanted you to do. Even if you didn't buy a Sony TV, a substantial percentage of people will, so Sony wins by making you buy a new TV instead of fixing your old one. Or they win by charging you an outrageous price for the schematics and repair manuals.

And the reason that they do this is that they (and you) don't have to pay the real cost of disposing of the old TV. Instead of recycling the TV and reclaiming all the materials, you'll probably just toss the old TV in the trash. And the hazardous chemicals will leak into the soil. Our descendents will have to clean that shit up eventually, which will cost tons of money. But we don't have to pay that, so we just go get a new TV cheap.</rant>

Re:Apple ][

[Mattintosh]

If companies would package their products to include tech specs and schematics, people who don't want to mess with their purchased property wouldn't have to, but the people who want to modify, repair, or extend their purchased property could do so with ease.

And don't give me the old, tired, whiny excuse that people would simply build their own from the specs they got from a friend. It's not true. As you alluded to, most people aren't hobbyists and don't want to be bothered to build their own. And there isn't a problem from a commercial competitor, either, since patents and copyrights are there to protect against this exact form of abuse. There are adequate legal protections against ripoffs.

Companies should be required to include specs with every electronic and mechanical device they sell, whether it's as small as a wristwatch, or as large as a car.

Amit's Book

[TheRaven64]

I did a technical review of the book, and I can thoroughly recommend it (I got a free copy). It's very technical in places (lots of code snippets) but does a very good job of explaining the 'why' as well as the 'what' and 'how' of XNU.

I did

[LKM]

Daring Fireball wrote about this recently. Here's the most important quote of the article:

The difference between the old Mac OS and Mac OS X isn't that it used to suck but now it's great. The difference is that Mac OS X's appeal is broader; it is good in more ways than the old Mac OS was.

Yeah, I did use and like Mac OS 9, Mac OS 8 and System 7. I did smoke lots of weed, but that had nothing to do with it. There are two things to consider: First, it went up against crap like Windows 3.11 and Windows 95. Second, it was the prettiest, most easy-to-use OS, even with cooperative multitasking and lack of memory protection.

Mac OS X added a lot to what makes a Mac great, but Mac OS 9 had a lot going for it, too.

Re:I did

[99BottlesOfBeerInMyF]

... it was the prettiest, most easy-to-use OS, even with cooperative multitasking and lack of memory protection.

Memory protection used to be explained in the following way:

• UNIX - if a program needs more memory, the system gives it more memory
• MacOS - if a program needs more memory, the system tells you and you have to give it more manually and try again.
• Windows/DOS - if a program needs more memory, your computer just crashed.

For all practical purposes this was the state of things for many years.

Re:I did

[Haeleth]

For all practical purposes this was the state of things for many years.

It's a rather misleading description, though. More accurately:

• UNIX/Windows NT/OS X - if a program needs more memory, the system gives it more memory; if there is no more memory to give, the program is terminated.
• Windows 9x - if a program needs more memory, the system gives it more memory; if there is no more memory to give, your computer crashes.
• MacOS 8/9 - if a program needs more memory, the system tells you and you have to fiddle around with a fussy little dialog box to give it more manually and try again, at which point another program will complain that it no longer has enough memory. Repeat ad infinitum, all the while gritting your teeth and reciting the mantra "this is better than Windows, this is better than Windows" until you almost believe it.

Archeological dig

[OakDragon]

From TFPDF:

Lisa was discontinued in 1985. In September 1989, Apple buried about 2700 Lisa computers in the Logan landfill in Utah. The value of the computers had depreciated so much that the tax break received from scrapping the computers resulted in more money for Apple than could be obtained by selling them.

Anybody feel like digging? :)

Re:Archeological dig

[boarder8925]

I'll go with you, just so long as we make a video of it like these guys did when they dug up E.T. the Extra-Terrestrial for the 2600. ;)

Lisa OS

[MooseDontBounce]

My CS Prof. at the time (Summer of 1982 or 1983, an old retired IBM'er who worked on the first computers for the Military) had a daughter that worked for Apple on the Lisa project. He had a pre-production model on his desk with a serial number under 300. She needed Steve Jobs personal okay to send him the computer for his testing. (So I was told) I remember it was the coolest thing I'd every seen back then. We took the cover off and his daughter's name was one of the names inscripted on the inside cover. Blew away the Apple II & Trash-80's we were using at the time.

Re:What I want to know is

[TomHandy]

It's not so much that Apple "decided" to stick with the classic Mac OS for so long despite Win95/98 as much as that they were just in a total mess in terms of their next gen OS stuff. Apple spent a lot of the 90's trying to figure out a new Mac OS, and a lot of the future was supposed to be in the original projects codenamed Copland and Gershwin (the original Mac OS 8 and Mac OS 9...... what eventually came out as Mac OS 8 and Mac OS 9 had little to do with this). Copland was originally supposed to be a totally modern OS, and Gershwin would apparently have had even more radically new elements, a lot borrowed from the Taligent collaboration with IBM on an OS codenamed "Pink". But none of this ever panned out, and all Apple could do was release the commercial Mac OS 8 and Mac OS 9 OS's as stopgaps. Apple had considered buying BeOS once it became clear that the internal Copland project wasn't working out, and they ultimately ended up buying NeXT. For all intents and purposes, Apple became NeXT, and Mac OS X can be seen in many ways as the ultimate development of NextStep, rather than the classic Mac OS.

Not as good as the Beeb though

[Space cowboy]

For me, the best 8-bit computer ever was the BBC micro - I doubt it ever gained any traction over here in the US, but *man* was that a well-designed and elegant machine.

The OS was fully vectored and modular, the BASIC language had procedures and functions, as well as a built-in assembler that could access BASIC variables, but the hardware design was what made it stand out. It had every i/o port under the sun - serial, parallel, "user i/o", other dedicated ones for a network (Econet), to support floppy disks and hard disks, and even plug in a second co-processor (there were 8086, Z80 and 32000 variants I think). You could get Pascal and C for it, and it supported 80-column text on a monitor.

And to bring it slightly back on-topic, the documentation was simply excellent - the "Advanced user guide" told you just about everything you needed to know about the machine, from the event i/o to interrupt-programming, documenting the OSxxx calls, and all the port i/o etc.

Nothing since has come close to the flexibility of that machine given the design limitations at the time, and it's a tribute to the designers.

Of course, such largesse can be abused [grin] See My first and only virus-writing incident ...

Simon

Re:What I want to know is

[TomHandy]

Actually, looking through the Mac OS X Internals PDF, there's a whole section there about Apple's quest for a new OS........ this goes into a lot of detail about all the options Apple considered. This is actually some great reading if you're curious about all of this.