Workbench 1.2
Version: 1.2
Released: 1986-1987
Maintainer: Hyperion Entertainment
License: Commercial
Workbench 1.2
The Amiga Becomes a Product
Release: Amiga Workbench 1.2
AmigaOS generation: V33
Era: 1986–1987
Primary hardware: Amiga 1000, Amiga 500, Amiga 2000
Processor: Motorola 68000
Chipset: Original Chip Set
Kickstart: V33 generation
Major milestone: Kickstart ROM becomes part of the standard Amiga experience
From revolutionary prototype to a computer people could actually buy
If Workbench 1.0 represents the moment the Amiga arrived, and Workbench 1.1 represents the first attempt to refine that arrival, Workbench 1.2 marks the point at which the Amiga began to become a mature computer platform.
The difference wasn’t simply what appeared on the screen.
The biggest change was happening inside the computer.
With the arrival of the Amiga 500 and Amiga 2000, Commodore was moving away from the unusual Amiga 1000 startup procedure in which Kickstart had to be loaded from a floppy disk. Kickstart 1.2 could now reside in ROM on the newer machines.
That single change transformed the relationship between the owner and the operating system.
The Amiga no longer needed to be taught how to become an Amiga every time it was switched on.
The operating system was becoming part of the machine.
The official AmigaOS version history identifies V33 as the Kickstart 1.2 generation.
The Amiga 500 arrives
The Amiga 500 was one of the most consequential computers in Commodore’s history.
Unlike the Amiga 1000, which had been introduced as a relatively expensive and unconventional machine, the A500 was designed to bring Amiga technology to a much broader audience.
It placed the Amiga’s 68000 processor, OCS graphics and sound hardware andmultitasking operating system into a compact home-computer design.
And, crucially, the operating system was no longer something the owner had to load from a Kickstart floppy.
That mattered enormously.
Imagine the difference from the perspective of a family buying its first Amiga.
Amiga 1000
Power on
↓
Insert Kickstart
↓
Wait for Kickstart
↓
Insert Workbench
↓
Wait again
↓
Workbench desktop
Amiga 500
Power on
↓
Kickstart ROM
↓
Insert Workbench
↓
Workbench desktop
The computer was suddenly much more approachable.
The Amiga 500 could power up and immediately display its familiar startup screen, waiting for the user to insert a Workbench disk.
That may seem like a small improvement.
It wasn’t.
It changed the Amiga from an intriguing technical machine into something thatcould realistically sit beside a television in an ordinary home.
Kickstart moves into ROM
The distinction between Kickstart and Workbench becomes especially important here.
The two names are sometimes casually used as though they mean the same thing, but they do not.
Kickstart contained the core operating-system components required to bringthe Amiga to life.
Workbench was the graphical desktop environment and associated software.
On the original Amiga 1000, Kickstart was loaded from disk.
On the newer machines, Kickstart could be permanently stored in ROM.
This was a major architectural milestone.
The operating system was no longer entirely dependent upon removable media.
It also meant that Commodore could ship machines with a known, fixed version of the core operating system already installed.
The user could still change the Workbench environment by using different disks, but the fundamental system software was now built into the computer.
For preservationists, this creates an important dividing line:
The Amiga 1000 belongs to the disk-loaded Kickstart era; the A500 and A2000 usher in the ROM-Kickstart era.
What was V33?
The official AmigaOS documentation identifies V33 as Kickstart 1.2.
Several individual Kickstart builds existed within the V33 generation, and theseare worth preserving separately.
One commonly encountered version is:
Kickstart 33.166
Later V33 revisions also appeared.
This is one of the recurring problems faced by anyone attempting to constructa serious historical Amiga archive.
A label saying:
Workbench 1.2
does not necessarily tell you the exact software contained on the disks.
Likewise, saying:
Kickstart 1.2
does not uniquely identify a particular ROM image.
The internal revision number matters.
A museum database should therefore record at least three layers:
Commercial designation:
Workbench 1.2
Operating-system generation:
V33
Exact software revision:
For example, Kickstart 33.166
That distinction becomes increasingly valuable as we move deeper into AmigaOS history.
AutoConfig — making expansion easier
Another major development associated with this generation was AutoConfig.
The Amiga was designed to support expansion hardware, but expansion introduces a problem.
A computer has to know:
- What hardware has been installed?
- Where should it appear in memory?
- Which address should the expansion occupy?
- How much memory or hardware space does it require?
- Are there conflicts with other devices?
On earlier computers, users could be expected to configure hardware manually through switches, jumpers or software settings.
The Amiga’s AutoConfig architecture was designed to make this process much easier.
Compatible expansion hardware could identify itself to the system, allowing the operating system to configure the available address space automatically.
This was an elegant example of the Amiga philosophy:
hardware and software were designed together.
The operating system knew about the machine’s expansion architecture, while expansion hardware was designed to cooperate with the operating system.
For an ordinary owner, the benefit was simple:
adding hardware didn’t necessarily mean becoming a hardware engineer.
The Amiga 2000
If the A500 represented the Amiga’s expansion into the home, the Amiga 2000 represented its expansion into professional and expandable computing.
The A2000 provided a substantially more expandable system architecture than the compact A500.
It could accommodate expansion cards and additional peripherals, making it attractiveto users who wanted to build a more sophisticated Amiga system.
This was the beginning of something that would become central to the Amiga’s identity:
The Amiga wasn’t one computer.
It was becoming a family of computers sharing a commonoperating-system architecture.
That distinction would become increasingly important as Commodore introducedmachines aimed at different markets.
A person could own:
- a compact home Amiga,
- a professional expandable Amiga,
- a later AGA machine,
- or a specialized Amiga system,
while still encountering the same fundamental Workbench concepts.
The desktop remains familiar
Despite all of these underlying changes, Workbench 1.2 didn’t suddenly look like a different operating system.
The blue desktop remained.
The familiar icons remained.
Drawers remained drawers.
Tools remained tools.
Projects remained projects.
The Workbench environment still had the characteristic Amiga visual language established in 1.0.
This continuity was important.
Commodore was changing the machine underneath the user without forcingthe user to relearn the entire desktop.
That is one reason the early 1.x releases can look so similar when viewed decades later.
The underlying technology was changing faster than the appearance suggested.
A growing software ecosystem
By the time Workbench 1.2 appeared, the Amiga was attracting software developerswho were beginning to exploit the machine’s unusual capabilities.
The operating system was no longer merely a way to launch programs.
It was becoming a platform.
Applications could make use of:
- Intuition windows and gadgets
- graphics.library
- AmigaDOS
- multitasking
- custom graphics modes
- hardware-supported scrolling
- digital audio
- device drivers
- system libraries
This encouraged developers to create applications that looked and behaved like native Amiga software.
The result was a growing body of software that felt fundamentally different from programs written for DOS-based PCs.
Games were only one part of this story.
The Amiga was also becoming a serious platform for:
- desktop publishing
- graphics
- animation
- music
- programming
- video
- education
- telecommunications
The operating system was one of the reasons this ecosystem could develop.
The Workbench disk becomes the user’s operating environment
Although Kickstart was now stored in ROM on newer machines, Workbench remaineda disk-based environment.
The user would insert the Workbench disk and the system would load the graphical desktop.
That created an interesting hybrid architecture:
AMIGA 500 / 2000
│
┌──────┴──────┐
│ │
Kickstart ROM Workbench Disk
│ │
│ ▼
│ Desktop + Tools
│
▼
Core AmigaOS
The distinction would survive for many years.
Even when AmigaOS became much more sophisticated, the relationship between Kickstart and Workbench remained one of the platform’s defining characteristics.
The floppy disk was still king
Despite the improvements to the operating system, the Amiga of the 1.2 era remainedheavily dependent upon floppy disks.
The standard Amiga floppy could hold approximately 880 KB, an impressive amount for the era but still tiny compared with modern storage.
This meant that Amiga software developers had to think carefully about disk space.
A Workbench disk could not contain everything.
Additional software was frequently placed on separate disks.
Applications could require their own disks.
Games commonly booted directly from floppy.
Utilities could be distributed separately.
For the user, swapping disks was simply part of owning a computer.
For today’s preservationist, those disks have become incredibly valuable evidence.
The disk label, filesystem, boot block, directory structure and individual file revisions can all help establish exactly what a particular historical release contained.
The Amiga as a television computer
The A500 was particularly important because it was designed to work comfortably in the home.
Its ability to connect to a television made the Amiga attractive to people who might never have considered purchasing a dedicated computer monitor.
This was part of Commodore’s broader strategy.
The Amiga wasn’t merely competing with professional computers.
It was competing for space in the living room.
And Workbench was central to that experience.
A user could switch on the Amiga, load Workbench, insert a game disk, experiment with graphics, learn BASIC or explore a drawing application.
The operating system was the common foundation beneath same machine could be a game console, creative workstation, educational computer and programming system.
The operating system was the common foundation beneath all of those identities.
The beginning of the mass-market Amiga
Workbench 1.2 is therefore much more significant than its incremental version number might suggest.
Workbench 1.0 introduced the technology.
Workbench 1.1 refined it.
Workbench 1.2 helped put it into the hands of a much larger audience.
The arrival of the A500 transformed the Amiga’s commercial prospects.
The A2000 simultaneously demonstrated that the platform could scale upward into more serious expandable systems.
And Kickstart in ROM made the machine much easier to live with.
The Amiga was no longer simply an exotic new computer.
It was becoming a platform.
Why Workbench 1.2 matters
Workbench 1.2 occupies one of the most important positions in Amiga history.
It is the bridge between the original Amiga 1000 concept and the mass-marketAmiga family.
It retains the unmistakable visual identity of the first Workbench while introducing an operating environment capable of supporting the new generation of Amiga hardware.
Most importantly, it marks the transition from:
“The operating system is something I load.”
to:
“The operating system is part of my computer.”
That change would become permanent.
The A500 would go on to become one of the most recognizable home computers of its generation. The A2000 would establish the expandable Amiga workstation. And Kickstart 1.2 would become a foundational generation of the operating system.
The blue Workbench screen looked almost unchanged.
But underneath it, the Amiga was becoming something much bigger.
Submitted by CopperByte Games