What makes AmigaOS different.
AmigaOS did in 1985 what other personal computers took ten to fifteen years to reach, in a fraction of the memory. It still works unlike any other operating system, and that is why we build on it.
Here is what sets it apart, idea by idea: what AmigaOS does, and how most other systems do the same job. Then the price it pays for being that way, and what we keep.
Small, quick and open to change.
AmigaOS was designed together with the Amiga's custom chips by a small team, for a machine with very little memory. Nothing could be wasted, so the system is a handful of cooperating parts that trust each other, instead of a large kernel guarding everything. Every idea below comes from that.
256 KB
The memory the first Amiga shipped with, running a pre-emptive multitasking OS with windows, sound and colour.
512 KB
The Kickstart ROM from AmigaOS 2.0 onwards: kernel, graphics, windows, file system and boot, ready at power on.
Still growing
AmigaOS 3.2.3 runs on the same machines today, and the same programs from the late 1980s still run on it.
A kernel that gets out of the way.
Exec is the kernel, and it does very little: tasks, messages, memory and libraries. Everything else is built from those four.
Real multitasking on 256 KB
The Amiga 1000 shipped in 1985 with a pre-emptive multitasking kernel, Exec, in 256 KB of memory. A tiny scheduler hands the processor between tasks many times a second, so a disk copy, a paint program and a Shell all keep running at once.
Most other systemsHome computers of 1985 ran one program at a time. The Mac waited for Mac OS X in 2001 for pre-emptive multitasking, and most home PCs for Windows 95.
Messages passed, not copied
Tasks talk by sending messages to each other's ports. A message is a pointer to memory both sides can already see, so sending one costs almost nothing, however big it is.
Most other systemsEach process lives in its own walled-off memory, so data crossing between programs is usually copied, or mapped with the kernel's help.
The whole OS is a set of libraries
Graphics, windows, files, maths and fonts are all libraries, opened by name and version number. Each one is a table of jump instructions, so a newer library slots in under old programs without them noticing.
Most other systemsShared libraries exist everywhere, but the core of the system sits behind a fixed system-call interface that only the vendor changes.
Anyone can improve the OS
One call, SetFunction, swaps any entry in a library's table for new code. That is how forty years of patches, speed-ups and fixes have reached machines nobody could ship a new ROM to.
Most other systemsChanging how the system itself behaves needs the vendor, a driver signed by the vendor, or a hack the next update breaks.
Ready at power on, arranged your way.
The ROM holds the system, and AmigaDOS lets you lay out your disks however you like.
The OS lives in ROM
From the A500 and A2000 of 1987, the heart of AmigaOS has sat in the Kickstart ROM, ready the moment the power comes on. Libraries, devices and the boot code are resident modules found and started in order at reset.
Most other systemsThe system is loaded from disk every time, so a damaged disk can leave the machine unable to start.
Names, not drive letters
Assigns give a name to any folder, or to several at once: LIBS:, FONTS:, C: and any you make up. Programs ask for the name, and you decide where it points, on whichever disk you like.
Most other systemsPaths are tied to a drive letter or a fixed folder tree, and moving things means telling every program.
Drop-in file systems and devices
File systems, handlers and devices are separate pieces you mount. A new disk format, a network share or a CD is one more handler, and every program can use it straight away.
Most other systemsFile systems are part of the kernel, and adding one needs a kernel driver.
A RAM disk that sizes itself
RAM: grows as you put files in it and shrinks as you take them out. RAD: goes further and keeps its files through a reset.
Most other systemsA RAM disk, where there is one, is a fixed size you pick before you use it.
A desktop where programs work together.
Intuition, Workbench and the Shell give every program the same windows, screens, formats and scripting.
Screens you can pull down
Each program can open its own screen with its own resolution and colours. Drag one down and the screen behind shows through, both live at once, because the custom chips change display mode part-way down the picture.
Most other systemsOne desktop, one resolution, with every program in a window on it or taking over the whole display.
Teach every program a new format at once
Since AmigaOS 3.0, pictures, sounds, text and animations are read through datatypes. Add one for a new format and every program that uses datatypes can open it, with no update to the program.
Most other systemsEach program carries its own decoders, so a new format waits for every program to add it.
Every program can be scripted
From AmigaOS 2.0, ARexx came in the box. Programs open an ARexx port, so one short script can drive a paint program, a word processor and a terminal together.
Most other systemsScripting between applications came much later, and differs from program to program.
Icons that travel with the file
A file's icon, its tool types and its default tool live in a .info file beside it. Copy the pair anywhere and the icon and its settings go too. Workbench and the Shell share one system, so you use whichever suits the job.
Most other systemsIcons and settings sit in a central database or registry that a copied file leaves behind.
The price of trusting every program.
AmigaOS is fast and small because its parts share one memory and trust each other. The same design is its weakness, and we say so plainly.
One bad program can stop the machine
There is no memory protection, so a program that writes in the wrong place can bring everything down with a Guru Meditation or a Software Failure.
A crash can leave memory behind
The system does not track what each program has opened, so a program that dies without cleaning up keeps its memory until the next reset.
Built for one person
There are no user accounts or file permissions in the Unix sense. An Amiga belongs to whoever is sitting at it.
What we keep.
Decades of Amiga software are written for these rules, so our open replacements follow them: the same libraries, the same jump tables, the same messages, the same assigns and the same boot order as AmigaOS 3.2.3. Where 3.2.3 hangs, crashes or gives a wrong answer, ours does not copy the fault, and we list each one with how we know.
Amiga and AmigaOS are trademarks of their respective owners. AmiCradle is an independent project.