This is a document written using ReMarkable, a shorthand syntax for generating HTML.

{	"date"		:	200608242026,
	"updated"	:	200608242026,
	"licence"	:	"cc-by",
	"tags"		:	["c64", "osnews"]

# GEOS: The Graphical Environment Operating System #


((*This article* was originally written for, and <published (//> by <> as part of an “<alternative operating system contest (//>” where it <won first prize (//>, and made the front page of <Digg (//>.))

((This is an improved version based on the original text and layout instead of the heavy alterations to layout made by osnews to fit within their content management system.))

                                                            * * *

About the Author
Kroc Camen started programming at the age of 7 on a Commodore 64 home computer. The first thing he typed into a computer was «Hello». It responded cheerfully with «`Syntax Error`». Ever since then he has been searching for emotion in computers in a variety of operating systems spanning a brief 15 years. From the O.S. you are about to see today, to all the versions of Windows, RISC OS, Amiga OS and recently Mac OS X.

Yet one thing hasn’t changed despite the difference in computing power over these years. Computers still have «`Syntax Error`»s. Is human emotion garbage, if garbage in equals garbage out? The quality of an operating system is down to the love and emotion put into it by the designers & programmers.

An Introduction To This Article
As we take time to look at the grand variety of operating systems available, it shows us that there is no one right way to ‘do it’. With hardware already a commodity, the way we interact with our computers is taken as a standard, and a given best-practice of design. The joy of alternative operating systems is the variety of Computer ↔ Human interface models available.

Even now, the modern Operating System is designed from the perspective of the engineer. Whilst actual human guinea-pig testing is done on new interfaces, it still does not make up the bulk of the design process. User involvement in design is almost an after-thought.

What we’ve come to accept as the standard way of interacting with a computer was cemented in the early days by the extremely knowledgeable and technical system engineers of the day, through a process of creating:

1.	What they felt was right
2.	What the limited hardware was capable of

So, for my article, I have decided to focus on an operating system born in the early days of consumer-available ‘{WIMP}’ interfaces, on extremely restrictive hardware.

It is my belief that «the restraint of hardware is the true muse of the software engineer». _
Good software does not come from being given unlimited resources; just take a look at the hardware requirements for modern PC games, for graphics that were reproducible (until recently) on a 300 {MHz|megahertz}, 4 {MB|megabyte} {V|video}-{RAM} Playstation 2.

A Quick History _of_ GEOS (#geos-history)
The history surrounding GEOS and its implementation within hardware restraints unimaginable nowadays makes for the most interesting parts of the O.S., rather than just the {GUI} itself. Below is a brief history of the operating system up to its heyday, where we’ll then get into usage, screenshots and technical details `:)`

This history has been carefully gathered and researched through actual GEOS manuals, <cited sources and websites (#geos-references)>.

When you think of the history of our modern day operating systems, they are either the works of individuals and volunteers based on technical ability and software beliefs, or the work of large corporations employing many programmers. Rarely is the history of an operating system based in the vibrant gaming era of the 1980s.

The Graphical Environment Operating System was released in 1986, created by Berkeley Softworks: a small company start-up by serial entrepreneur Brian Dougherty. GEOS is a classic Mac-like {GUI} running on <Commodore 64 (//> / <128 (//> hardware, then later the <Apple Ⅱ (//>, and PC.
Around 1980, Brian turned down a job at IBM to go join the games manufacturer Mattel, then maker of the <Intellivision (//> gaming system. Brian helped write games for the system for about a year, before leaving with other engineers to form <Imagic (//>, a very successful games company that rivalled Activision, before being wounded in the games industry crash of 1983. Whilst Imagic went under in 1986, Brian did not.

Dougherty formed Berkeley Softworks (later Geoworks), who in collaboration with a firm that made batteries, worked on a product for the airlines named “Sky Tray”. The concept was a computer built into the backs of the seats, and Brian and his team would develop the O.S. for it.<sup><1 (#ra)></sup>

GEOS was coded by Dougherty’s elite team of programmers, who had cut their teeth on the very restricted Atari 2600 and Intellivision games consoles of the time (usually 4 {KB|kilobyte} {ROM}). However, after the O.S. had been written, <airline deregulation (//> mandated that all in-flight extras were to be trimmed down to save weight and fuel, culling the Sky Tray project.<sup><1 (#ra)></sup>

With all that time put into an O.S., Dougherty looked at the compatible (<6502 (//> Microprocessor-based) Commodore 64. A few changes were needed and the O.S. sprang to life on the affordable home computer, complimenting the powerful graphics capabilities of the machine with a {GUI}.

Even though Berkeley Softworks started out small, with only two salespeople - the new software proved very popular because of low price for the necessary hardware (and of course the capability of the O.S.). This was due in part to the aggressive pricing of the Commodore 64 as a games machine and home computer (With rebates, the C64 was going for as little as $100 at the time). This was in comparison to an atypical PC for $2000 (which required MS-DOS, and another $99 for Windows 1.0<sup><2 (#rb)></sup>) or the venerable “Mac 512K Enhanced” also $2000.<sup><3 (#rc)></sup>

In 1986, Commodore Business Machines announced the C-Model revision of the Commodore 64 in a new Amiga-like case (dropping the «breadbox» look), and bundling GEOS in the United States.

At its peak, GEOS was the *second most widely used {GUI}*, next to Mac OS, and the third most popular operating system (by units shipped) next to MS-DOS and Mac OS.<sup><4 (#rd)></sup>

An Introduction To GEOS (#geos-introduction)
What Role Does GEOS Serve? (#geos-what-role)
GEOS is a classic Mac OS like operating system, providing a {GUI} for performing disk functions and running productivity software. It was targeted at the business user for in-office word processing, as well as the home user for tasks like desktop publishing and keeping records.

The original GEOS is no longer used, having died out in the early 90s due to strong competition from IBM, Microsoft, Apple and new trends in computer hardware. The history of what happened to GEOS and Berkeley Softworks will be covered at the end of this article.

Why Review GEOS? (#geos-why-review)
To give balance and perspective. GEOS managed to offer nearly all the functionality of the original Mac in a 1 {MHz|megahertz} computer with 64 Kilobytes of {RAM}. It also wasn’t an operating system written to run on a generic x86 chip on a moving hardware platform. It was written using absolute immense knowledge of the hardware and the tricks one could use to maximise speed. The closest thing to GEOS in this modern era is <MenuetOS (//>, written entirely in x86 assembly code.

GEOS came at a time before the World Wide Web, before home computers were PCs, before mass storage that you could afford, and long before Bill Gates and Windows were №1.

GEOS did not pioneer the {GUI}; most of its features were already present in the larger operating systems of the day, like the classic Mac (albeit, not Windows). What GEOS did show is that cheap, low-power commodity hardware and simple office productivity software worked. You did not need a $2000 machine to type a simple letter and print it. This gave some sense of perspective in the heady “Golden Age of Computing” of the ’80s and even now, as some alternative OSes struggle to port <bloated (/&__HREF__;/dependencies.jpg)> software from other platforms.

Many operating systems can claim all sorts of things, and in-fight over who invented what- first. GEOS helped drive the proliferation of the newfangled {GUI} concept to regular users without the need for the famous Apple Hype Machine (likely one reason why GEOS is now all but forgotten).

GEOS was able to introduce home users to Point & Click, Cut / Copy / Paste, {WYSIWYG|“wizzy-wig”} Word Processing and what you expect from a {GUI} without having to afford an expensive Mac or PC with Windows. Before GEOS, the home user had to go to work to even see a {GUI}.

Then there was GEOS on the PC (more about this at the end of the article), which had the “Start Menu” concept two and a half years before Windows, and a PDF-like user interface model 10 years before Mac OS X `;)`

How Is GEOS ‘Alternative’? (#geos-how-alternative)
When we speak of operating systems, the word ‘alternative’ is not quite as it is from the dictionary. Mac OS X is an _alternative_ to Windows just as much as Windows is an _alternative_ to OS X. It is simply one choice over the other. But with operating systems, ‘alternative’ has come to mean ‘niche’, ‘minority’ and ‘hobby’. How can GEOS be ‘alternative’, if it was at one time more popular than Windows?

Operating systems can change over time, even change purpose. OS/2 and BeOS are considered alternative, despite being big important OSes in their day. I believe that the same is of GEOS. At the end of this article, I will cover how GEOS has been retro-fitted by fans to add modern-day functionality, as well as the OS that came after GEOS, extending the life of GEOS well into new millennium. The fact that people still boot GEOS on real Commodore 64 hardware and make <real things (//> with them, because they can, certainly defines GEOS a hobby O.S. Because those who run it on real hardware are few and far between, that makes GEOS a minority O.S.; and because GEOS is generally only run by core C64 fans it also makes GEOS a niche O.S. `:)`

Hardware Requirements (#geos-hardware-requirements)
Although GEOS later became available on the Apple Ⅱ and then eventually the PC (more about this later), this article will be covering the Commodore 64 version of GEOS due to free availability and wealth of accessible information. I also own a real GEOS disk set for my Commodore 64 and hope to make use of them in this article.

GEOS ran on any Commodore 64 home computer. Because of the popularity of the Commodore 64 as a games machine, GEOS can also be easily run on most C64 emulators on modern computers. GEOS itself is now available for free download - more details soon.

#### The Commodore 64 ####

Commodore Business Machines released the Commodore 64 in 1982 at a price of $595<sup><5 (#re)></sup>. Designed primarily as a home computer for playing (initially educational) games and business software, its low price and powerful features made it a runaway success. Here follows some technical details of the hardware.

:: 1 {MHz|megahertz} 8-Bit MOS Technology 6510 Processor
	The 6510 was a <6502 (//>-based processor, that which can be found (as
	variants) in the Atari 2600, NES, Apple Ⅱ & BBC Micro computers. It is a <{RISC} (//>
	style processor, utilising very few registers (Just <var>A</var>, <var>X</var>, <var>Y</var> & a 256-Byte Stack)
:: 64 Kilobytes {RAM} (+20K {ROM} of which 7 KB “Kernal”)
:: 16 Colours in 40 × 25 text mode (320 × 200 resolution)
:: 8 Sprites

:: MOS 6581 (C64rA,B) / 8580 (C64rC) SID sound chip
	Three sound channels (2 {MIDI} like sound synthesisers, and one White Noise)

:: ‘Datassette’ Tape Drive, later, <1541 Disk Drive (//>
	Programs on tape cassette. Later a 5¼″ Disk Drive was released with support for 170 KB per disk.

As you can see, this is a very tight amount of space to fit a full operating system, including user-land apps! The original Mac OS was 400 KB, with 128 KB of {RAM} to play with.

#### Expansions ####

GEOS made good use of the many expansions available for the Commodore 64. As well as supporting two disk drives and many printers, you could also purchase a {RAM} expansion to add 128, 256 or 512 {KB|kilobytes} of extra {RAM} to the system. The biggest upgrade, late in the life of the C64, was the SuperCPU - a 20 {MHz|megahertz} upgrade module!

How To Get GEOS (#geos-how-to-get)
The <OSNews Contest Rules (//> state that the O.S. must be «available to the public for download or purchase». GEOS is available as a free download, and can actually be <purchased (//*rR8CV2&amp;p_id=00500&amp;xm=on&amp;ppinc=search3)>, as a set of 5¼″ disks with manuals! I personally own a GEOS 1.5 disk set with manual.

#### Get An Emulator ####

In order to run GEOS on your PC or Mac, you will need a Commodore 64 emulator to simulate the hardware. I recommend these emulators for the necessary emulation accuracy needed to run GEOS on PC/Mac.

:: <CCS64 (//> (Windows)
	Has 99.9% emulation accuracy and still in active development (for over 10 years). CCS64 can emulate almost every
	last timing quirk of the real hardware and thus is accurate enough to run GEOS (which does contain some extremely
	clever hacks that can fool most emulators) _
	Make sure to enable the mouse by pressing <kbd><kbd>F9</kbd></kbd> to bring up the menu and navigate to the input
	section. Also, for accurate disk speed ({i.e.|that is,} slow), go to the “Special” menu and disable “1541 Turbo
	speed” or GEOS may fail to boot.
:: <Power64 (//> (Mac OS 9 / X)
	There are not nearly enough emulators on Mac OS X `:(`. Power64 is a shareware app that emulates the C64 accurately
	enough to use GEOS. Whilst <Frodo (//> is free it is not accurate enough to run GEOS; it hangs at
	the boot screen. Power64 has excellent mouse support and is ideal for running GEOS. Although it’s not a universal
	binary, it runs without flaw under Rosetta on Intel Macs.

The <VICE Emulator (//> is also capable of running GEOS on just about every other alternative O.S. available. Configuration is much more complex, and if you are technically inclined you can compile the source code to produce an X11 app for Mac OS X for free.

#### Download The GEOS Disk Images ####

GEOS was made available for free download in February 2004 by CMD, makers of modern day Commodore add-ons (like the 20 {MHz|megahertz} SuperCPU)—see <the Slashdot article (//>.

Instructions on downloading GEOS and getting the disk images available here: _
< (//>

Follow the «I Agree» link, and then the first link labelled «go here». Download the GEOS 64 «1541 boot disks».

Booting GEOS (#geos-booting)
GEOS requires no installation as the Commodore 64 has no mass storage besides a floppy disk drive, and GEOS comes on floppy disks anyway.

Attach the “GEOS64.d64” disk image to the emulator on drive 8 (the first disk drive on a C64) and then start the emulator. Most emulators will allow you to double click, or “open-with” the ‘.d64’ file with the emulator to attach the disk automatically.

<"Screenshot of the C64 boot screen" /&__HREF__;/geos00.png>

This is the Commodore 64’s normal operating system. A text-mode command-driven system. In normal configuration, the system reserves just 38 {KB|kilobyte} for writing BASIC programs. The C64’s architecture is incredibly flexible however, and by switching out the {ROM} shadows in the upper areas of {RAM}, you could free up almost the entire 64 {KB|kilobytes} (if you wrote your own {I/O|input/ouput} drivers)<sup><13 (#rx)></sup>. GEOS itself ditches a large amount of the default system to fit into the memory available.

Type <kbd>load"geos",8,1</kbd> and press return. Don’t hold shift otherwise you’ll get symbols instead of letters. The C64 had a series of {ASCII}-like symbols printed underneath each key. When in normal mode, holding <kbd>Shift</kbd> and pressing a key would display the symbol, allowing you to draw {ASCII} art in the C64 character set. On the C64, this character set is known as <PETSCII (//>, as in {PET-ASCII} (The <Commodore PET (//> was an earlier education market computer).

The «deskTop» (#geos-desktop)
You are quickly presented with the GEOS «deskTop», the main interface where you’ll do basic disk & file management, configuration and launching programs.

<"Screnshot of the GEOS “deskTop”" /&__HREF__;/geos01.png>

The Commodore 64 supported several video modes. Although the resolution of the C64 was always 320 × 200 in aspect, the way it interpreted the screen data could be changed in a number of ways.

In order to produce the user interface in GEOS, the C64’s «high resolution» bit-mapped mode was utilised. A full 8 {KB|kilobyte} of memory had to be reserved to store the monochrome pixel data, where one byte represented the on/off states of 8 pixels. Rather than the screen data being ordered in a continuous stream from the left to right and then down each line, the screen data was split into 40 × 25 characters of 8 × 8 pixels. 8 bytes represented one character, running from top to bottom of the character and then left to right across the screen in characters.

Programmatically this made it difficult to draw diagonal lines unless they aligned with the 8 × 8 characters, but it meant that large block copies of memory were easy to do. It also meant that referencing the right hand side of the screen (whose pixel locations were greater than 255, what one byte allowed) was easy, because technically the screen was only 40 characters wide, each of eight bytes in height.

The downside is that whilst you get full fidelity to draw the letters manually and thus fit in more than 40 letters per line - it was monochrome. The mouse pointer is blue because the mouse is created using the C64’s hardware sprite support. A sprite could freely be moved around without erasing and redrawing the screen contents below. The C64 itself would not be fast enough to handle redrawing screen contents in the bitmap, as the mouse moved.

Although bit-mapped graphics ate 8 {KB|kilobyte} of {RAM}, it meant that the programmers could erase the 4 {KB|kilobyte} of {PETSCII} graphics from the standard text-mode, and better use these resources for storing the O.S. and freeing enough {RAM} for any user-land apps to run.

#### DeskTop Features ####

Along the top of the screen there is a “command menu”. Just like Mac OS, there is only one menu bar and it displays the menu according to what app is running. Considering that there is no multi tasking at all in GEOS, it makes little difference. The Commodore 64 has a key with the Commodore logo on it - much like the Windows or Apple key on modern keyboards.

<"The menu strip" /&__HREF__;/geos02.png>

The «disk note pad» is the main window that shows the contents of the current disk. It cannot be moved or resized and doesn’t have scrollbars. Instead, the page curl at the bottom left can be clicked either on the curl to go forward one page, or on the page behind to go back a page (also accessible with the 1-9 keys). You can have up to 18 pages depending on how many files are on the disk.

<"The disk note pad" /&__HREF__;/geos03.png>

There are no file extensions, and no subfolders! The disk contents are a confusing mix of utility applications, key system files and drivers. Whilst files inside of GEOS can have their own icon, normal C64 files from outside GEOS will always show as the “C=64” folder-like icon. Double clicking these instantly exits GEOS and loads the C64 program.

The GEOS boot disk however is not meant to be a place to store your own files, or your productivity apps. With only 170 {KB|kilobyte} per disk, each productivity app usually comes on a separate floppy disk. Once GEOS is booted you can switch disks to run new applications. When you exit the application you must insert the GEOS boot disk so that it can load the “deskTop” application. If you copy the deskTop application to other disks (or use two disk drives) you can avoid massive amounts of disk swapping.

The single button on the title bar is the close button. It does not close the window entirely, but rather ‘eject’ the disk from the system, leaving the window blank. Clicking on the disk drive symbol on the right of the deskTop will load that disk’s contents.

<"Moving a file to the border" /&__HREF__;/geos04.png>

The “border” (the blank area underneath the disk note pad which holds the current printer and the waste basket) can be used to place up to 8 files off of the disk note pad, so that you can change either pages or disks and move the files to the new location. Clicking an icon selects it in inverted graphics, and then clicking again turns the mouse into a ghost of the file icon, allowing you to move it to the border.

<"Files in the border" /&__HREF__;/geos05.png>

The icons in GEOS are all 24×21 pixels in size. This is because the Commodore 64’s sprites are always 24×21 in size which equates to 3 characters (8 pixels wide) across and almost 3 characters high. Whilst GEOS’s icons are not sprites themselves (they could be of any particular size because they are drawn dot for dot on the bit-mapped screen), 24×21 is used so that the mouse pointer (a sprite) can become a ghosted icon in drag and drop operations.

The reason for falling short of three bytes tall is so that when the 8 supported sprite images of 504 bytes each are counted it adds up to 4032 bytes, leaving 64 bytes in a 4 {KB|kilobyte} block of {RAM} to control the positions, visibility, order and colours of the 8 available hardware sprites.

The Commodore 64 also included a programmable Interrupt ReQuest controller (IRQ). Every 1⁄50<sup>th</sup> of a second, a routine in {RAM} was called. The programmer could tap into this in order to run instructions before the screen refresh, half way through (or even a few tiny instructions within the time it took for the electron beam to “fly-back” to left hand side of the screen, from the right)<sup><13 (#rx)></sup>. This gave the programmer the power to redirect the pointer to the sprite data halfway down the screen, in order to produce 16 working hardware sprites. 64 simultaneous hardware sprites have been demonstrated using this method!

Configuring GEOS (#geos-configuring)
Hardware (#geos-hardware)
GEOS must be told which drives you have connected. Double-click on the “CONFIGURE 2.0” icon on the deskTop and you are presented with a simple screen with options for the different types of drives.

<"CONFIGURE 2.0" /&__HREF__;/geos06.png>

Here, two disk drives are attached and a 512 {KB|kilobyte} {RAM} expansion. The “shadowed” option appears so that you can use the {RAM} expansion to facilitate disk copying and speed up GEOS. (Not that this is a problem in an emulator, but the disk drive could be very slow at times). It is a known problem that a hardware bug ended up in the read speed of the disk drive being much slower than it should be<sup><6 (#rf)>,<7 (#rg)></sup>. Programmers relied on ‘fast-loaders’, essentially decompression software loaded into the disk drive’s {RAM} & CPU, to speed things up again.

User Interface Customisation (#geos-ui-customisation)
The application “preference mgr” on the first page of the GEOS boot disk allows you to customise some basic U.I. Settings.

<"preference mgr" /&__HREF__;/geos07.png>

The sliders allow you set mouse acceleration and speed. If you were not the proud owner of a mouse for your C64 (hands up those who had a mouse for their {PSX|Playstation}?) you were stuck using a joystick to navigate the U.I.

The C64 has no built in battery and is unable to maintain the time between power resets. On a normal C64 you would have to (if you could be bothered) set the time every boot by selecting the “Options” command menu and selecting “set clock”. The emulator I am using (Power64) has excellent GEOS support and sets the clock for me. If you purchase a <FD-2000 (//*Zw7pi3&amp;p_id=00130&amp;xm=on&amp;ppinc=search3)> floppy disk drive or <RAM-Link (//*Jf7KL7&amp;p_id=00200&amp;xm=on&amp;ppinc=search3)>	cart from <CMD (//>, you could also add an optional extra to the configuration - a real time clock chip, allowing GEOS to keep accurate time.

<"Custom icon" /&__HREF__;/geos08.png>

Interestingly, GEOS lets you edit the mouse pointer directly in a fashion very similar to how you could <change the desktop pattern (//> on the original Mac. 

<"Colour!?" /&__HREF__;/geos09.png>

The small squares next to “Border”, “B.Ground”, “F.Ground” and “Mouse” can be clicked to cycle the colours (out of the 16 available) for that element.

If this is supposed to be a monochrome U.I., how is it doing the colour here? As stated before, the mouse (and those sliders) are hardware sprites, composited over the monochrome bitmap data, but the C64 has more tricks up its sleeve.

Though the bitmap data in memory is monochrome, the C64 could set the background and foreground colours to draw the bitmap with. Here as the light grey and dark grey combo of GEOS. In addition to this a 1 {KB|kilobyte} section of upper memory representing a 40 × 25 character gird let the computer assign changes to the chosen monochrome colours in each 8x8 pixel character.

The Preferences Manager ‘Window’ effectively aligns perfectly within the 40 × 25 grid of characters, so that the colours underneath could be changed using the colour map. The one byte that represents the colour under one of the 8 × 8 pixel characters is divided into two nybbles of 4-bits. Each of these nybbles can store a number from 0–15, representing the 16 available colours, and thus the Foreground and Background colours to use for the graphics in that character square.<sup><13 (#rx)></sup>

Productivity (#geos-productivity)
geoWrite (#geos-geowrite)
Probably the most important application of an operating system is the word processor (and now, arguably the web-browser). Long before GNOME & KDE was GNaming everythinK with odd letters, GEOS was naming their productivity apps with geo-Something.

<"geoWrite in the disk note pad" /&__HREF__;/geos10.png>

geoWrite takes up a dangerously large 35 {KB|kilobytes}. You are also provided with 7 fonts of decent variety, but Berkeley Softworks also made available an add-on font disk with 53 extra fonts. When you start the app you are presented with a simple dialog. You can also double click on geoWrite documents in the disk note pad and geoWrite will automatically load them.

<"The geoWrite title dialog" /&__HREF__;/geos11.png>

The geoWrite interface is extremely simple. There are no scrollbars, you simply jam your mouse against the top or bottom of the screen and the page scrolls.

<"The geoWrite interface" /&__HREF__;/geos12.png>

At the end of the menu strip is a page with a black rectangle representing the current visible portion of the page on the screen. By clicking the rectangle you can move it to another part of the small page and the view in the main window will jump to the relevant location.

<"The geoWrite page navigation rectangle" /&__HREF__;/geos13.png>

1 {MHz|megahertz} is barely enough to redraw an entire screen in under a second, so scrolling is naturally, very slow. Scrolling up the page is far slower than scrolling down. However selecting text is very responsive.

Once some text is selected you can either click the small squares below the ruler to set justification or line spacing, or explore the menus.

<"The font menu" /&__HREF__;/geos14.png>

Not all the fonts come in any size. Each font has a select list of sizes depending on the font and some have only one size. Whilst this may seem a problem it is really down to the very pixellated and low resolution screen. All the fonts are very carefully designed for maximum readability on the screen and on a printed page. If any size were allowed, the pixels would mash together at certain sizes making most letters illegible.

<"geoWrite’s fonts" /&__HREF__;/geos15.png>

Considering the low resolution of the screen, the provided fonts are of superb quality, providing a perfect mix of serif and non-serif fonts with lots of variations on letter widths, curve styles and clarity. For a word processor, this is probably the best set of provided fonts given the hardware, for any word processor. There are enough sans-serif professional fonts that look great at all sizes, as well as a couple of fun fonts for those wanting to experiment. A great lot of care has gone into providing for both the business user who wishes to impress their clients with professional typesetting and the home user who wants to make a fun looking flyer.

<"geoWrite’s styles" /&__HREF__;/geos16.png>

The style menu lets you select between Plain Text, Bold, Italic, Outline, Underline, Superscript and Subscript styles. The interesting Outline option even works on the most complex of fonts. This feature is not seen in any version of Microsoft Word, or any word processor that I’m aware of, outside of the classic Mac and GEOS. (Likely because the transition from bitmap fonts to true type and postscript fonts)

A Cautionary Tale (#geos-cautionary-tale)
GEOS, like other alternative operating systems, is dependent on certain hardware. GEOS might not compare with BeOS, RISC OS, or even Amiga OS for features and power, but it is easy to run today on any PC/Mac, and free.

There are also great disadvantages to this as well. Running GEOS on a TFT doesn’t compare to running it on a TV or old monitor. The chroma blurring on the C64’s rather weak RF unit caused the dithered background to look like yellow and white bands going down the screen.

This very problem was used to an advantage in some advanced C64 games, where certain colours could be dithered to create seemingly new colours. Nearly 52 colours could be faked using this method. This of course is not actually ideal in an O.S. where clarity is what’s needed, but it does help to explain the dreary greyness of GEOS, which would look significantly different and softer on a TV.

“Nothing compares to the real deal” is an important adage in any review of an alternative operating system. Whilst those that have not used GEOS first hand, or extensively played the C64 will look at GEOS’s monochrome, low resolution graphics and laugh at how it doesn’t even compare to Windows 3.1; I personally see wonderment in how a 1 {MHz|megahertz} computer with such little {RAM} can do so much. 

After-all, most games on the C64 could not afford to use the bit-mapped graphics mode as it was too slow. Thus the great variety and flexibility of geoWrite’s display is completely unseen outside of the most <hardcore (//> demo-scene disks.

Putting a disk in to a real C64 and hearing that loud clunking and whirring as 250 bytes per second come down the serial bus is not the same as a little blinking light showing disk activity in an emulator.

The Real Deal (#geos-real-deal)
Therefore, I have hooked up my Commodore 64 and booted the real GEOS for you `:)`. Find below a 17 minute guide to the Commodore 64 and GEOS, including geoWrite and geoPaint.

<video preload="none" src="/&__HREF__;/geos_tour.ogv" width="640" height="480" poster="/&__HREF__;/poster.jpg" controls>
	<"A Guided Tour of GEOS" /&__HREF__;/poster.jpg>

((This video is available only in Ogg format. You can download it <here (/&__HREF__;/geos_tour.ogv)> and play it using <VideoLAN (//>))

I hope that’s helped get across the actual responsiveness of the O.S. on the real hardware, and the visual differences caused by using a TV.

I could continue to detail every function of every app in the operating system but I don’t think that will add anything more useful. GEOS is an impressive technical feat, and at least a ‘good-enough’ O.S. considering the hardware and the price. GEOS couldn’t compare to the original Mac OS because of such vast differences in power. (The original mac was 32-bit and with 128 {KB|kilobytes} of {RAM})

Other Apps (#geos-other-apps)
A word processor and paint app an operating system do not make. GEOS is very fully featured, it would take far too long to go into great detail over GEOS’s other apps. But what I will do is list them with a basic overview and you can either try them on an emulator, or imagine for yourselves!

#### geoCalc ####

<"geoCalc" /&__HREF__;/geocalc.png>

geoCalc was the Excel (or rather VisiCalc) of GEOS. The view can be split into two so you can edit two parts of the spreadsheet at the same time as well as supporting a host of functions for calculating data. Due to {RAM} limitations graphing was handled by a separate program that you could paste your spreadsheet data into.

#### geoChart ####

<"geoChart" /&__HREF__;/geoChart.png>

geoChart can show that data in impressive charts that can really make that data speak. With text-mode fully out of the window, the data labels always lined up neatly and there were many ways you could present your sales figures.

#### geoFile ####

<"geoFile" /&__HREF__;/geoFile.png>

A Very MS Access like database application with the ability to design input forms and also mail merge to geoWrite.

#### geoPublish ####

<"geoPublisher" /&__HREF__;/geoPublish.png>

geoPublish is the largest GEOS application I’ve seen. A serious desktop publishing program supporting master pages, text orientation, patterns, shapes, guides and rulers and all the basics. A busy page is very heavy on the little computer so two disk drives and a {RAM} upgrade is a bear minimum to do any serious work. geoPublish is still being <used (//> by the most die-hard GEOS users.

Modernising GEOS (#geos-modernising)
If there’s one thing a Commodore 64 can’t do, it’s nothing.

Thanks to the rather hardcore followers of the C64, various tasks have been performed on a C64 thought impossible, including real time 3D graphics, <viewing JPGs (//>, <hosting websites (//> and of course - <viewing them (//>.

At the same time, supporters of GEOS have improved upon GEOS creating new derivative operating systems. <“Wheels” (//> is one such example of this. Wheels is an add-on for GEOS 2.0 that adds multi tasking, support for more hardware (including hard disks and {RAM} expansions up to 16 {MB|megabyte}) and new user interface with multiple movable, resizable windows whilst keeping backwards compatibility with GEOS apps.

Wheels requires at least 128 {KB|kilobyte} {RAM} expansion and ideally a 20 {MHz|megahertz} upgrade with as much disk space as you can throw at it. Even browsing the Internet is not outside the limits of Wheels, <“The Wave” (//> is a browser with hefty requirements but nether-less shows that it can be done.

Where Did GEOS Go? (#geos-where-did-it-go)
For an operating system second only to Mac OS, and surpassing Windows, where did it go? How can it be so forgotten now?

GEOS on the Commodore platform faded out for a number of reasons:

:: The IBM ‘Standard’
	The PC platform had a larger capacity for upgrades and peripherals. The Commodore was already largely dated hardware by the time the 90s rolled in. With the growing complexity and power of applications, new hardware was needed - and the PC as a more modular system could grow with new innovations. However, the Commodore 64 / 128 were stuck in time, much like a games console, something that the C64 had become in the end.

:: Commodore’s bad management
	Commodore Business Machines had begun to lose its edge after the heady success of the Commodore 64. After several bad decisions, the company collapsed and filed for bankruptcy in 1994. <sup><8 (#rh)></sup>

:: An operating system dependent on the hardware
	When GEOS was first created it was meant to be an embedded system (the Sky Tray). It was hand coded to utilise the processor to its maximum. You could not just write it in a high level language and compile for the hardware, it would take up too much {RAM} and would be slow. The 6502 processor was simple enough that a programmer could hand type the assembly code far better than any machine could. whilst this made the Commodore 64, and the 6502 in it, sing - it also meant that moving to a new processor architecture basically meant a total rewrite. This ruled out the Commodore 64 / 128’s successor - the Amiga, which used a different processor architecture.

GEOS was not entirely out of the game though; the 6502 processor was being used in several other products at the time, and additional ports of GEOS were made. Most notably, on Apple’s popular home computer the Apple Ⅱ in 1988. <sup><9 (#ri)></sup>

Geoworks (#geos-geoworks)
At the start of the 90s, Berkeley Softworks became Geoworks, and with the new name—a whole new strategy and a new O.S.

Geoworks moved into Microsoft territory by creating a PC based operating system to compete with Windows. However, in GEOS fashion, “Geoworks Ensemble” (known internally as PC/GEOS) was leaner, meaner and faster than Windows 3.0 on the same hardware. Geoworks Ensemble would run nicely on a 386 or 486 PC that would not normally be powerful enough to run Windows 95.

Bill Gates called Brian Dougherty to discuss buying Geoworks and moving the developers to Seattle to incorporate some of the innovations in PC/GEOS into Windows. PC/GEOS had the Start Menu concept a full 2½ years before Microsoft. The developers were not interested in moving, and the lead VC advised against it.<sup><14 (#ry)></sup>

|	He [Bill Gates] was actually very charming. Ballmer was the hammer. I met with Bill and several of the engineers on
|	the Windows development team first, it turns out that several of those engineers were in another small Berkeley
|	company with <Nathan Myhrvold (//>
|	that Microsoft had acquired earlier. They were complimentary of what we had done and talked about joining forces to
|	work on the next version of Windows. I should have listened to them, especially considering how {{MS|Microsoft}}
|	stock appreciated from 1989 on.
|	Ballmer was the bad cop, he came in and said, «Look if you don’t sell or license to us, we really have to crush
|	you, we can’t afford to have a competing PC operating system». I don’t think he was trying to be mean or
|	intimidating; it was just matter of fact.
|	As I look back on it, if I were in his or Gates shoes I would have had the same attitude. The PC OS standard was
|	a winner-take-all sweepstakes with billions of dollars hanging in the balance, the world doesn’t really want to have
|	to write software for multiple OSes.
|	A lot of people vanquished by Microsoft cry about their unfair business practices, I look at it differently;
|	they were there first and fought tooth and nail to defend their business. I’d have done the same in their place.<sup><14 (#ry)></sup>
| Brian Dougherty

PC/GEOS was a full pre-emptive multi-tasking, multi-threaded operating system (yes, in 1990!). It had a postscript-like imaging model, complete with outline font technology and separate rotation, translation & scaling matrices for both the application and the user interface.<sup><14 (#ry)></sup> (a leaf from Mac OS X’s book; 10 years before)

Brian Dougherty describes PC/GEOS’s user interface:-

|	The object oriented flexible user interface technology in [PC] GEOS is to this day the most sophisticated U.I.
|	technology ever built into an OS. The team at Sun that developed Java studied it and stole some of the concepts
|	but in my opinion did not achieve the same level of sophistication.
|	Applications in PC GEOS contained a generic tree of objects describing the user interface features the app
|	required with the ability to provide hints for how to realize those elements. The operating system then had a
|	specific user interface library that would map those generic UI objects to specific UI elements like menus or
|	dialog boxes.
|	The same binary of an application could be made to run under an entirely different look and feel. For example, at
|	one point we wrote a Mac UI that turned a PC running GEOS into a machine that was almost indistinguishable
|	from a Mac. You could go to preferences and select either the Mac UI or the Motif UI (Windows-like) and the
|	system would restart and all of the applications would come up under the look and feel you selected. You almost have
|	to see this live to believe how cool it was.
|	We actually got into extensive discussions with Apple about developing a low cost notebook that would run GEOS with
|	the Mac UI. It got killed by the hardware group doing Mac notebooks, but it went all the way to a board meeting we
|	attended with Scully et al before it died. <sup><14 (#ry)></sup>
| Brian Dougherty

The original GEOS still continued its life through licensing the O.S. to mobile phone and PDA manufacturers, appearing on early PDA devices like the Nokia Communicator 9000 & 9110 <sup><10 (#rj)>,<11 (#rk)></sup>. This provided users with the power of the GEOS user interface (and geoCalc) on the emerging hardware.

Whilst Geoworks Ensemble is a newer O.S. than GEOS, I am reviewing the original Commodore 64 version because I have much more experience with it, and I feel that the first version is an important factor in explaining where GEOS went later on in life. For this reason, I won’t be going into any detail about how Geoworks Ensemble functions in this article. I leave below a couple of links where you can find some more information about this system:

•	<Screenshots of Geoworks Ensemble 1.2 (1991) (//>
•	<Screenshots of Geoworks Ensemble 2.0 (1993) (//>
•	<An Introduction to the GEOS Operating System (1996) (//>

New Deal Inc. (#geos-new-deal-inc)
This company took over development of PC/GEOS, naming it “NewDeal Office” in 1996 to compete in the education space with Microsoft. NewDeal Office required far less hardware resources than Windows 95, suiting older equipment perfectly. The last version was NewDeal Office 2000 before New Deal Inc. went under and PC/GEOS passed hands once more.

•	<Screenshots of NewDeal Office r3 evaluation (//>
•	<What’s left of the New Deal Inc. website at (//*/>

Breadbox Ensemble (#geos-breadbox-ensemble)
PC/GEOS returned again in 2002, after <Breadbox Computer Company LLC (//> took up the O.S., finally licensing all the rights to GEOS in 2003. <sup><12 (#rl)></sup>

•	<The Breadbox Website (still running) (//>
•	<Screenshots of Breadbox Ensemble Lite (//>
•	<Download Breadbox Ensemble Lite (//;maincategory=Ensemble%20Lite)>
•	<Instructions to run Breadbox Lite with NT/2000/XP (>

Geoworks were eventually beaten out of the market, disappearing from the map around 2004.

Airset (#geos-airset)
Geoworks was not the end of the line; in 2003 Airena was formed to produce products for managing information with mobile phones. With some of the GEOS programmers onboard<sup><14 (#ry)></sup> their first product <“Airset” (//> is a web/java application that lets you manage bookmarks, to do lists, calendars & contacts between a PC and mobile phone.

The O.S. That Could Have Been (#geos-could-have-been)
Anybody can wax lyrical about “what could have been”, at the end of the day GEOS, both Commodore and PC versions, were genuine technical masterpieces in their own right - involving great skill. They stood true to being an affordable O.S., that got the most power out of the least hardware. GEOS might not be an open-source system but just because it’s commercial, that does not negate the clear love for engineering that went into it.

Sure GEOS is all but forgotten now, but that doesn’t mean it didn’t contribute to what helped shape computer usage in the 80s and 90s. Considering that even an O.S. as popular as GEOS was can fade away, then there is no accuracy or inaccuracy in waxing lyrical that even Microsoft could be entirely forgotten one day in the far future. These things happen.

I love Commodore/GEOS because it represents something that no longer exists in the computer industry anymore. The Commodore 64’s hardware is (programatically) beautifully designed. It is possible for one person to know the entirety of the machine, every function, every chip, every quirk. This gave the individual the power to create almost without limits, as shown by the continual modern day upgrades of the C64 and the popular demo and music scene. Today’s hardware is just too complex to fully understand the whole system. Only a small percentage of the PC’s actual power is ever used because of a rapidly moving platform that solves problems by throwing more hardware in.

Now It’s Your Choice
Alternative operating systems exist because people continue to see value in their choice of what makes a better interface. Because Windows is so prevalent, and frankly ‘good enough’ but not great as a whole, this only livens the world of alternative operating systems. Pretty much all alternative OSes do something different or better than Windows, something that gives them value and worth to their users.

Be it the Amiga WorkBench, BeOS Tracker, SkyOS’s Viewer or GEOS’s low requirements and killer apps of the day; this review has been written to only provide insight into one more ‘alternative’ system and not proclaim any religious software / U.I. / kernel beliefs. I hope that this article has been interesting, insightful and entertaining and I thank you for reading it. I only hope that you’ve been able to enjoy it from the comfort of your own chosen operating system `;)`

                                                            * * *

Special Thanks
I would like to thank the following individuals and groups for their input on this article:

•	Brian Dougherty - founder, Berkely Softworks / Geoworks,¬
	for producing GEOS, reading this article & responding to my e-mails
•	<Roland Lieger (//>, creator of the Power64 emulator on the Mac platform,¬
	which was used to record the screenshots in this article
•	<Google Video (//>, for their hosting
•	Maurice Randall & <Click Here Software Co. / CMD (//>,¬
	for making GEOS available for free

Cited Sources _and_ References (#geos-references)
1. (#ra)	<> _
		Biz Journal’s Article/Interview about Brian Dougherty (((article incorrectly states—for simplicity—that
		Berkeley softworks was called “Geoworks Corp.” at formation. The Geoworks name was not adopted until the
2. (#rb)	<> _
		Advert for Microsoft Windows 1.0 in 1986
3. (#rc)	<> _
		A brief history of the Macintosh
4. (#rd)	<> _
		The Wikipedia Article on GEOS (could do with some love)
5. (#re)	<> _
		Chronology of the Commodore 64
6. (#rf)	<> _
		The Wikipedia Article on the Commodore 1541 5¼″ Floppy Disk Drive
7. (#rg)	<> _
		Jim Brain discusses the hardware bug that resulted in the very slow disk access times of the 1541
8. (#rh)	<> _
		The Wikipedia entry on Commodore Business Machines
9. (#ri)	<> _
		GUIdebook Gallery’s GEOS timeline
10. (#rj)	<> _
		The Wikipedia article on Geoworks Ensemble, New Deal Inc. and Breadbox
11. (#rk)	<*/> _
		The Geoworks website 1996 - 2004 (from the Wayback Machine at <>)
12. (#rl)	<> _
		News from Breadbox LLC of the licensing of GEOS
13. (#rx)	~Commodore 64 Programmer’s Reference Guide~ _
		Howard W. Sams & Co., Inc. ISBN: 0-672-22056-3
14. (#ry)	Personal contact with Brian Dougherty via e-mail