Workbench 1.1
Version: 1.1
Released: 1985
License: Freeware
Museum Exhibit — Workbench 1.1
The First Revision
Release: Amiga Workbench 1.1
AmigaOS generations: V31 / V32
Year: 1985
Primary machine: Amiga 1000
Processor: Motorola 68000
Chipset: Original Chip Set (OCS)
Kickstart: Disk-loaded
Regional variants: NTSC and PAL
A computer that was still finding its identity
Workbench 1.0 had introduced the Amiga to the world, but the Amiga 1000’s operating system was not finished evolving when the first machines reached customers.
That is an important distinction when looking back at the Amiga today. The familiar blue Workbench desktop, the mouse-driven interface and the extraordinary multimedia capabilities of the machine can make the original system seem like a fully formed product from the beginning. In reality, Commodore and the Amiga engineering team were moving rapidly. The first year of the Amiga’s life would see several significant operating-system revisions.
Workbench 1.1 was one of the first.
Released in 1985, it retained the fundamental architecture and appearance of Workbench 1.0 while addressing problems in the launch software and, critically, expanding the Amiga beyond its original NTSC market.
The official AmigaOS version history identifies V31 as Kickstart 1.1 for NTSC and V32 as Kickstart 1.1 for PAL. These were separate regional operating-system revisions rather than simply two display settings inside one universal release.
That seemingly small distinction tells us something important about the Amiga’s early history:
The Amiga 1000 that entered an American home and the Amiga 1000 intended for a European home did not necessarily run the same Kickstart software.
Two Americas, two televisions, one Amiga
The original Amiga 1000 launch environment was NTSC.
This made sense for Commodore’s initial American market, but the Amiga was intended to become an international computer. Europe presented a different television and video environment, dominated by PAL.
Workbench 1.1 therefore introduced two operating-system variants.
V31 — NTSC
The NTSC version is generally identified as Kickstart V31.34.
V32 — PAL
The PAL version is identified as Kickstart V32.34.
The official documentation explicitly classifies V31 as NTSC-only and V32 as PAL-only.
Workbench 1.1
│
├── NTSC
│ └── Kickstart V31.34
│
└── PAL
└── Kickstart V32.34
This is one of the earliest examples of an issue that will become increasingly important throughout the Workbench story: the name printed on the box doesn’t necessarily identify the exact software running inside the machine.
Still a disk, still a ritual
The Amiga 1000 had not yet acquired the permanent Kickstart ROM that would become familiar on later Amiga models.
Kickstart was still something that had to be loaded.
The basic experience therefore remained:
POWER ON
│
▼
Bootstrap
│
▼
Insert Kickstart disk
│
▼
Kickstart loads into memory
│
▼
Insert Workbench disk
│
▼
Workbench desktop
The first Amiga 1000 systems used a special memory arrangement in which the Kickstart image could be loaded into Writable Control Store. The Kickstart disk contained approximately 256 KB of operating-system code, while the Workbench disk supplied the graphical environment and additional software.
For someone accustomed to modern computers, this is one of the strangest aspects of the early Amiga.
Today we think of an operating system as something installed onto a computer.
In 1985, an Amiga owner could quite literally have the operating system sitting in a plastic disk box.
Lose the disk, and you had lost an essential part of the machine’s ability to start.
What did 1.1 actually change?
Workbench 1.1 was not the spectacular transformation that 2.0 would eventually become.
The desktop remained recognizably the same.
The blue screen remained.
The icon-driven environment remained.
The basic Workbench/AmigaDOS architecture remained.
This was an evolutionary release, not a redesign.
Much of the work was beneath the surface, correcting problems discovered in the first public release and improving the reliability and usefulness of the operating environment.
This distinction matters because operating-system history is often written around visually obvious changes.
Workbench 2.0 looks dramatically different from 1.3, so it is easy to remember 2.0 as an important release.
Workbench 1.1 looks almost the same as 1.0, so it can be tempting to dismiss it.
For the people actually using an Amiga in 1985, however, improvements that prevented crashes, corrected system behavior or made the computer work correctly with their television standard could be much more important than a new visual effect.
The birth of recognizable version information
Another small but historically significant development around this period was the emergence of more systematic version identification within AmigaOS.
The Amiga software architecture used version information associated with system components, and the version.library mechanism became part of the early system.
That eventually allowed users and developers to determine more precisely what operating-system components were present.
This becomes increasingly important as the AmigaOS family grows.
By the time we reach 1.2, 1.3 and especially Release 2, there are numerous revisions of individual libraries and programs.
The modern AmigaOS documentation describes version strings as an integral part of Amiga software identification, with software components carrying their own version and revision information.
That tradition can be traced back to these very early releases.
The Workbench experience
For someone opening Workbench 1.1 for the first time, the experience remained remarkably futuristic.
The desktop was blue.
A mouse moved a pointer across the screen.
Icons represented disks and other objects.
The user could open a disk icon and see its contents in a window.
Applications could be launched from their icons.
Menus were pulled down from the screen’s title area.
Windows could overlap one another.
The Amiga could continue performing other work while an application was running.
This last point is easy to overlook today.
The Amiga’s graphical environment wasn’t simply a visual shell placed on top of a conventional single-tasking operating system. The underlying Amiga architecture had been designed around multitasking from the beginning.
The modern AmigaOS documentation describes the operating system as a collection of libraries and system components rather than a monolithic kernel in the traditional Unix sense. The original exec.library, for example, provided the fundamental executive functions upon which applications and other system components depended.
So when a user looked at that little blue desktop, there was an unusually sophisticated system underneath it.
A desktop designed around objects
The terminology introduced with Workbench 1.0 continued into 1.1.
A disk was represented as an object.
A directory became a drawer.
An executable was a tool.
A document was a project.
The terminology made the computer feel less like a machine operated by commands and more like a workspace.
This was particularly significant because the Amiga’s audience was broader than professional programmers.
Someone could sit down, insert a disk and begin exploring the computer without knowing DOS commands.
The system nevertheless retained a command-line environment for experienced users.
That combination—graphical Workbench above and command-line AmigaDOS underneath—would remain one of the defining characteristics of the platform for years.
The Amiga 1000’s unusual operating system
Workbench 1.1 also belongs to a very specific hardware era.
It was primarily an Amiga 1000 operating environment.
The Amiga 500 and Amiga 2000 would soon change the relationship between Kickstart and the computer itself. Those machines moved Kickstart into ROM, eliminating the need for the user to load it from a floppy each time the machine started. The later machines therefore required only the Workbench disk for a normal floppy-based boot.
This makes the early 1.x releases particularly interesting.
Workbench 1.1 sits at the end of the original “Kickstart is a disk” era.
Workbench 1.2 is where the story begins to transition toward “Kickstart lives in ROM.”
That transition would fundamentally alter the Amiga’s startup experience.
What was inside the box?
The software environment surrounding Workbench 1.1 was more than a single disk.
The early Amiga distribution was organized around separate system and application disks. Kickstart supplied the essential system software; Workbench supplied the desktop environment; additional disks provided utilities, programming tools and instructional material.
For preservation purposes, this distinction is critical.
A modern archive should not simply have:
Workbench 1.1 disk image
Instead, ideally it should preserve the entire software package:
Workbench 1.1 collection
├── Kickstart
├── Workbench
├── Extras
├── programming material
├── tutorial material
├── documentation
└── physical packaging
Where individual disk revisions can be identified, they should receive separate catalog records.
A release born from necessity
The speed with which Workbench 1.1 followed 1.0 tells its own story.
The Amiga was a new architecture.
Its operating system was new.
Its custom chips were new.
Its graphical user interface was new.
Its development tools were new.
And Commodore was simultaneously trying to bring the machine to markets using different television standards.
That meant the first public release was inevitably going to expose problems that could not all have been anticipated during development.
Workbench 1.1 represents the first significant opportunity to refine that launch experience.
It is therefore best understood not as a flashy sequel but as the first stage of stabilization of the Amiga platform.
The PAL milestone
Of all the things associated with Workbench 1.1, PAL support deserves special emphasis.
PAL was not simply another resolution option.
The video standard affected the timing and behavior of the display system. Supporting PAL required corresponding operating-system support.
The existence of V31 and V32 therefore demonstrates something larger than Commodore adding another checkbox to the specifications.
It demonstrates that the Amiga’s operating system was tightly integrated with the machine’s custom hardware.
The software had to understand the hardware.
And the hardware had to operate within the video environment of the market in which the computer was sold.
This intimate relationship between AmigaOS and the custom chipset would become increasingly important as the platform developed.
The end of the first chapter
Workbench 1.1’s life was short.
The Amiga team was already moving forward.
Workbench 1.2 would introduce another major step in the platform’s development, including the arrival of Kickstart ROMs on the new Amiga 500 and Amiga 2000. The official AmigaOS chronology identifies V33 as the 1.2 generation.
The difference between 1.1 and 1.2 would therefore be considerably more visible in the hardware landscape.
But Workbench 1.1 occupies a fascinating position between those two worlds.
It was:
The Amiga as originally conceived, being rapidly refined for the world beyond its launch market.
The Amiga 1000 still required the unusual Kickstart loading ritual.
The desktop was still the original blue Workbench.
The operating system was still young.
But the platform was beginning to spread.
And the next generation of Amigas was about to make the machine dramatically easier to use.
Submitted by CopperByte Games