Guest post by GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. It wasn’t an OS written to run on a generic x86 chip on a moving hardware platform. It was written using immense knowledge of the hardware and the tricks one could use to maximise speed. Note: After a small break, here is another one of the articles for the Alternative OS contest.
1. 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:
- What they felt was right
- 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, 4 MB VRAM Playstation 2.
2. A Quick History of GEOS
The history surrounding GEOS and its implementation within hardware restraints unimaginable nowadays makes for the most interesting parts of the OS, 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.
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 OS 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 II, 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 OS for it.
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 RAM). However, after the OS 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.
With all that time put into an OS, Dougherty looked at the compatible (6502 Microprocessor-based) Commodore 64. A few changes were needed and the OS 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 OS). 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) or the venerable Mac 512K Enhanced also $2000.
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 US.
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.
3. An Introduction to GEOS
3.1 What Role Does GEOS Serve?
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.
3.2 Why Review GEOS?
To give balance and perspective. GEOS managed to offer nearly all the functionality of the original Mac in a 1 MHz computer with 64 Kilobytes of RAM. It also wasn’t an OS 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 No.1.
GEOS did not pioneer the GUI; most of its features were already present in the larger OSes 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 software from other platforms.
Many OSes 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 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 UI model 10 years before Mac OS X 😉
3.3 How is GEOS ‘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 OSes, ‘alternative’ has come to mean ‘niche’, ‘minority’ and ‘hobby’. How can GEOS be ‘alternative’, if it was at one time more popular than Windows?
OSes 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 OS. Because those who run it on real hardware are few and far between, that makes GEOS a minority OS; and because GEOS is generally only run by core C64 fans it also makes GEOS a niche OS. 🙂
3.4 Hardware Requirements
Although GEOS later became available on the Apple II 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 C64 in 1982 at a price of $595. 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 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 II & BBC Micro computers. It is a RISC style processor, utilising very few registers (Just A, X, Y & a 256-byte Stack) - 64 Kilobytes RAM (+20K ROM of which 7 KB Kernal)
- 16 Colours in 40×25 text mode (320 x 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 userland 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 of extra RAM to the system. The biggest upgrade, late in the life of the C64, was the SuperCPU – a 20 MHz upgrade module!
3.5 How To Get GEOS
The OSNews Contest Rules state that the OS must be “available to the public for download or purchase”. GEOS is available as a free download, and can actually be purchased, 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 F9 to bring up the menu and navigate to the input section. Also, for accurate disk speed (i.e. 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 OS 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 SuperCPU) – see the Slashdot article.
Instructions on downloading GEOS and getting the disk images available here:
http://cmdrkey.com/cbm/geos/geos1.html
Follow the ‘I Agree’ link, and then the first link labelled ‘go here’. Download the GEOS 64 ‘1541 boot disks’.
3.6 Booting GEOS
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.
This is the Commodore 64’s normal OS. A text-mode command-driven system. In normal configuration, the system reserves just 38 KB 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 (if you wrote your own IO drivers). GEOS itself ditches a large amount of the default system to fit into the memory available.
Type
load"geos",8,1
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 Shift 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).
3.7 The deskTop
You are quickly presented with the GEOS ‘deskTop’, the main interface where you’ll do basic disk & file management, configuration and launching programs.
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 UI in GEOS, the C64’s “high resolution” bit-mapped mode was utilised. A full 8 KB 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 of RAM, it meant that the programmers could erase the 4 KB of PETSCII graphics from the standard text-mode, and better use these resources for storing the OS and freeing enough RAM for any userland 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 ‘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.
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 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.
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.
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 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-50th 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). 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!
4. Configuring GEOS
4.1 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.
Here, two disk drives are attached and a 512 KB 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. Programmers relied on ‘fast-loaders’, essentially decompression software loaded into the disk drive’s RAM & CPU, to speed things up again.
4.2 UI Customisation
The application ‘preference mgr’ on the first page of the GEOS boot disk allows you to customise some basic UI Settings.
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?) you were stuck using a joystick to navigate the UI.
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 floppy disk drive or RAM-Link cart from CMD, you could also add an optional extra to the configuration – a real time clock chip, allowing GEOS to keep accurate time.
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.
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 UI, 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 section of upper memory representing a 40×25 character gird let the computer assign changes to the chosen monochrome colours in each 8×8 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.
5. Productivity
5.1 geoWrite
Probably the most important application of an OS 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 takes up a dangerously large 35 KB. 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 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.
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.
1 MHz 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.
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.
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.
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)
5.2 A Cautionary Tale
GEOS, like other alternative OSes, 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 OS 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 OS. 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 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.
5.3 The Real Deal
Therefore, I have hooked up my Commodore 64 and booted the real GEOS for you :). Find below a link to a 17 minute guide to the Commodore 64 and GEOS, including geoWrite and geoPaint.
Link to Google Video Screencast
I hope that’s helped get across the actual responsiveness of the OS 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 OS but I don’t think that will add anything more useful. GEOS is an impressive technical feat, and at least a ‘good-enough’ OS 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 128KB of RAM)
5.4 Other Apps
A Word Processor and Paint app an OS 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 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 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
A Very ‘MS Access’ like database application with the ability to design input forms and also mail merge to geoWrite.
geoPublish
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.
6. Modernising GEOS
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) and new UI with multiple movable, resizable windows whilst keeping backwards compatibility with GEOS apps.
Wheels requires at least 128 KB RAM expansion and ideally a 20 MHz 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.
7. Where Did GEOS 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. -
An OS 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 II in 1988.
7.1 Geoworks
At the start of the 90s, Berkeley Softworks became Geoworks, and with the new name – a whole new strategy and a new OS.
Geoworks moved into Microsoft territory by creating a PC based OS 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.
“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 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.”
PC/GEOS was a full pre-emptive multi-tasking, multi-threaded OS (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 UI. (a leaf from Mac OS X’s book; 10 years before)
Brian Dougherty describes PC/GEOS’s UI:-
“The object oriented flexible user interface technology in [PC] GEOS is to this day the most sophisticated UI 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.”
The original GEOS still continued its life through licensing the OS to mobile phone and PDA manufacturers, appearing on early PDA devices like the Nokia Communicator 9000 & 9110. This provided users with the power of the GEOS user interface (and geoCalc) on the emerging hardware.
Whilst Geoworks Ensemble is a newer OS 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)
7.2 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.
7.3 Breadbox Ensemble
PC/GEOS returned again in 2002, after Breadbox Computer Company LLC took up the OS, finally licensing all the rights to GEOS in 2003.
- The Breadbox Website (still running)
- Screenshots of Breadbox Ensemble Lite
- Download Breadbox Ensemble Lite
- Download Breadbox Ensemble Lite
- Instructions to run Breadbox Lite with NT/2000/XP
Geoworks were eventually beaten out of the market, disappearing from the map around 2004.
7.4 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 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.
8. The OS that 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 OS, 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 OS 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 / UI / Kernal 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
A. Cited Sources and References:
Websites
- http://www.bizjournals.com/entrepreneur/2005/06/23/1.html?page=1
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 90s) - http://www.guidebookgallery.org/ads/magazines/windows/win10-powerwindows-8
Advert for Microsoft Windows 1.0 in 1986 - http://oldcomputers.net/macintosh.html
A brief history of the Macintosh - http://en.wikipedia.org/wiki/GEOS_%288-bit_operating_system%29
The Wikipedia Article on GEOS (could do with some love) - http://www.islandnet.com/~kpolsson/c64hist/index.htm
Chronology of the Commodore 64 - http://en.wikipedia.org/wiki/Commodore_1541
The Wikipedia Article on the Commodore 1541 5¼” Floppy Disk Drive - http://www.binarydinosaurs.co.uk/Museum/Commodore/c64/c64notes.php
Jim Brain discusses the hardware bug that resulted in the very slow disk access times of the C64 - http://en.wikipedia.org/wiki/Commodore_Business_Machines
The Wikipedia entry on Commodore Business Machines - http://www.guidebookgallery.org/timelines/geos
GUIdebook Gallery’s GEOS timeline - http://en.wikipedia.org/wiki/GEOS_%2816-bit_operating_system%29
The Wikipedia article on Geoworks Ensemble, New Deal Inc. and Breadbox - http://web.archive.org/web/*/http://www.geoworks.com
The geoworks website 1996 – 2004 (from the Wayback Machine at archive.org) - http://www.breadbox.com/newsdetail.asp?id=40
News from Breadbox LLC of the licensing of GEOS
External Sources
- Commodore 64 Programmer’s Reference Guide
Howard W. Sams & Co., Inc. ISBN: 0-672-22056-3 - Personal contact with Brian Dougherty via e-mail
- 15 Years programming and usage experience on the Commodore 64
ii. 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 OS 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 OS is down to the love and emotion put into it by the designers & programmers.
Kroc Camen.
If you would like to see your thoughts or experiences with technology published, please consider writing an article for OSNews.
Haven’t read the article yet, but GEOS was pretty amazing. If you had a ramlink and a hdd, it flew on a c64. There are people out there that still use other OSes for the c64 like WiNGS and Wheels on a daily basis. The c64 has a lot of life left in it
…Excellent article!
I was a huge fan of GEOS back in the day, and ran it on my Commodore 128, and I later ran Geoworks Ensemble on my PC. GEOS in all it’s incarnations was truly an amazing OS, and way ahead of it’s time in many repsects. It truly is a shame that it’s achievements have been overlooked and left behind in the past.
…but, I wouldn’t label GEOS as “Alternative OS”, it was pretty widespread back in the days…
How right you are. AOL for DOS 1.0 – 1.5 used GEOS as it’s interface.
So were BeOS and OS/2, but they’re pretty alternative now. I think it’s slightly narrow minded to point at an OS and say, I don’t think you’re alternative enough. I think that’s up to the users of the OS to decide.
Heck, to run GEOS natively, you have to use a Commodore 64 from the eighties, or a 286/386 PC.
Edited 2006-08-25 07:24
I still have GEOS sitting here in my cabinet in the original box, with the original manual and all of the paperwork (including the reg card).
In the basement, carefully packed away, in it’s original box, I have a Commodore 64, two floppy drives, tape drive, mouse, game controllers, okidata printer, some enhancement cards, and a collection of 5.25 floppies.
I miss the days of simplicity.
In the basement, carefully packed away, in it’s original box, I have a Commodore 64, two floppy drives, tape drive, mouse, game controllers, okidata printer, some enhancement cards, and a collection of 5.25 floppies.
~snif~ You have my childhood packed in your basement.
(All of that stuff went bye-bye when a friend [borrowing it — it was now the spare computer] totaled his truck in an accident and it somehow disappeared in between the scene of the accident and the tow-yard the next day.)
What an enjoyable read. Amazing what they managed to squeeze out of that hardware!
Interesting seeing it on real h/w as well
Thanks. Very nice informative thorough article. Really enjoyed it.
Great article. I remember running Geoworks Ensemble which came packaged with my Laser 286 computer; it was excellent; I took it to college with me and used the word processor a lot.
The great thing about Geoworks was it had some great print technology, such that my Radio Shack dmp-105 could do very nice wysiwyg with it. It did this by making several passes over the page. It took forever, but looked great. No small feat for the dmp-105, which was a _7_ pin dot matrix printer.
Back in the late 80s I was in college, and when my Okidata printer would turned great wysiwyg text, one professor asked me how I was managing to get so much quality into my papers. GEOS was my silver bullet. I also remember clacking away at monochrome DOS in the basic comp-sci. class I was taking and laughing all the way back to my dorm to my full-color stereo graphic OS C-64. I knew that I was being taught the past, and getting to play with the future.
Great article! The early GEOS era was just before my time so it was very informative and fun to read.
This article almost brought a tear to my eye…my first computer was in fact a C-128D, and this brought back many old memories of tinkering with it as a child. Ahh the days of typing in pages upon pages of binary generators from RUN magazine.
Excellent article, Kroc
Browser: Mozilla/5.0 (Danger hiptop 2.0; U; AvantGo 3.2)
I recall thinking, must have been a lifetime ago how geos should put windows 3.0 in an early grave or would have had the two been competing strictly on their merits.
…another one bites the dust. Makes me sort of sad to be remembered of this. Though i never owned a “Commie”, i used Geoworks Ensemble on top of PTS/DOS, some russian thing also mostly, or wholly coded in ASM. Well, what can i say? It blasted me away speedwise, but was sort of
useless without the applications i had under other OSSes then. Makes me think of what could have been if TRON http://en.wikipedia.org/wiki/TRON_Project , http://tronweb.super-nova.co.jp ,or something like General Magic http://en.wikipedia.org/wiki/General_Magic had made it. When one thinks further about it, which i advise against, because it tends to make aggressive, one could come to the conclusion we are all running around in ball&chain.
This was a refreshing look at such a classic OS. I used this when I was little (I mean I was three when this came out), but don’t remember it at all. It’s impressive how much power it offered the user… for the time.
The Macintosh mutations that used the Motorola 68000 were not truly 32 bit processors: they had a 24 bit address bus, a 16 bit data bus, and also did have some instructions that would work on 32 bit data, but… they were not truly 32 bit processors. Were they better than the 8088/8086 available then? Most certainly! For a given clock speed (and the Macintosh started at about 8 Mhz) it was more efficient per clock cycle, and it also had more registers, but it still wasn’t a true 32 bit chip.
Other than that, it was a great article.
If you are going to nit-pick, please nit-pick with more accuracy. 😉
> also did have some instructions that would work on
> 32 bit data
The 68000 was fully 32-bit internally. So, it wasn’t just ‘some instructions’ that operated on 32-bit data, but most instructions since its general-purpose registers were all 32-bit.
Yes. It did have a 16-bit data bus and a 24-bit address range (the address bus was actually 23 bits wide – it took some extra magic to access odd addresses). Thus it was usually billed as a 16/32-bit CPU.
> The 68000 was fully 32-bit internally.
To nit-pick myself, that’s not quite true, either. 😉
The ISA was 32-bit, but the 68000 was mostly 16-bit internally.
The 68000 have 8 *TRUE* 32 bits data registers, not extended registers like on x86. I’m an assembler coder for various CPU, and the 68000 is really a good piece of hardware !
The 68000 have a 24 bits address bus which allows addressing 16 MB flat memory (where x86 could only access 640 KB, or 1 MB if A20 used). The data bus is 16 bits, thus reading/writing a 32 bits data needs two access.
With the 68020 (the *FIRST* full 32 bits CPU ever), the address bus *AND* the data bus are spread to full 32 bits, both internaly AND externaly…
ONLY after that Intel followed with the 386 that was 32 bits as well…
Kochise
The ST in Atari ST stood for Sixteen/Thirtytwo.
The later and last ones with 68030 in them where called TT. Reminds me of the 386SX somehow, but that came much later, didn’t it?
> Motorola 68000 were not truly 32 bit processors:
Truly? There is no such things as truly or not truly cpu ^_^
68000 has full 32bit ISA (7 years ahead of intel), who cares what was under the hood? !!!
Do you need 32bit address bus for a couple of megabytes of RAM? NO!!! It would be just a waste of transistors.
32bit ALU did not fit in their transistor budget, so 32bit data was processed in 2 chunks in 16bit alu.
Pentium4 also has 16 bit ALU, so why you didn’t call it 16 bit cpu????
one of my favorite things about this article is that the presentation comes across as being completely informative and factual in nature. A+++.
I didn’t have to suffer through countless jabs at other OS’s, or hear about how this one was the best OS ever built.
very nice indeed.
Nice to pick GEOS to write about. The author really seem to know a lot about it. The article is a bit to long to keep me intrested all the way. I think the author should try to write more efficent next time. But over all a very nice article.
It had a postscript-like imaging model, complete with outline font technology and separate rotation, translation & scaling matrices for both the application and the UI. (a leaf from Mac OS X’s book; 10 years before)
Here it sounds like GEOS did this 10 years before anybody else, which is a bit far fetched. Mac OSX is really NeXTstep version 5. NeXTstep had real display postscript right from the start, and had its first release in 1988. I think this makes for a closer race than the article indicates.
I don’t know the history of GEOS, but I gather that it was originally released in 1986. Did it incorporate the “postscript-like imaging model” at this point? Did it even have it before NeXT? (And postscript-like doesn’t mean actual Postscript(tm), right?)
I can’t say I know a lot about NeXT systems, so indeed, you may be true. There are two main strains of GEOS, the 6502 version, and the x86 version. Both are entirely different operating systems. PC/GEOS which included the object orientated UI model, was started around 1989.
PC/GEOS’s UI model had a few extra tricks up its sleeve though. PC/GEOS’s UI was entirely object orientated. When Brian describes being able to change one thing into another, he isn’t talking about fancy skins. The UI elements in an app were described in data, and the UI would represent that data according to the UI being used.
For example, a menu in a program could be realised as a menu, or a bullet list, or a folding tree structure, or, anything you could imagine with that dataset. This goes far beyond simple skinning in KDE, or even Cocca on OS X.
Thanks for elaborating, this sounds really interesting. The UI is data in Cocoa as well though. It sounds like GEOS and NeXT has alot in common here.
My comment on the “10 years before” business is strengthened by your reply. Mac OS X is a direct descendent of a system which had display postscript before GEOS picked up a similar idea. Apple reimplemented it as display PDF, but that was only done because the license fees involved with Postscript made the system too expensive for the home user market.
To continue on with the UI concepts. The UI had about a dozen basic classes you could pick from. You would create the object you wanted, and specify hints that told the OS what the object was for. The OS would figure out how to visually represent the object.
It really made UI programming so much simpiler than in other GUIs, where you have a seperate class with a different API for each variation of widget.
Also, by default, the UI of a GEOS app ran on a seperate thread from the processing. That made sure the UI always ran smoothly.
I know nothing about the Commadore version, but PC/GEOS was started in 1988, with the first release in 1990. The imaging model was definitely in there from the start.
Right. NeXTstep was started in 86 and released in 88. I think we can conclude that the article’s claim about the 10 years was a result of Kroc not knowing the roots of OS X.
Not to forget SUNs NeWS.
http://en.wikipedia.org/wiki/NeWS
Great OS, I remember installing a copy everywhere I could, just to show what could be done with small hardware. I used it as my Primary OS for years, as I was comming from Atari ST and feeling disapointed by the PC.
In 1991 ou 1992, I bought the developer guide (only) for Geoworks Ensemble (which cost about 150 €). About 4 kilograms of very interesting reading, nice APIs, all object and C.
But, to make a “Hello, world !”, you needed 2 PCs, one with Windows, and one with Geoworks, and a laplink cable linking them. I didn’t have to many computers at this time.
I think that’s a reason why there where so few apps : too difficult to develop, even if you could find some help on newsgroups (Internet was slowly appearing in France). And I was not skilled enough.
I still own a little compaq notebook, simply installed with a DOS 5 and Geoworks. Sometimes I boot it, just to remember how nice it was.
Edited 2006-08-25 08:10
You needed 2 PCs and a standard $10 null modem. You didn’t need Windows, although most people used it on the coding PC.
The need for two PCs was because of the debugging. Any time you hit a breakpoint in the debugger, it would stop the entire OS. Doing this made debugging multithreaded code MUCH easier. Also, putting the debugger on a seperate machine meant your code wasn’t trashing the debugger as it ran. It was an expense, but, you didn’t need anything fast for the 2nd machine. I just used my old 286 as the debugging machine.
GEOS wasn’t hard to develop for at all. The APIs were VERY nice actually. The UI in particular was so much easier to develop for than any other UI toolkit. The myth of GEOS being hard to develop for was created by people who spent a lot of time learning MFC and didn’t want to admit that it wasn’t very good.
As for my basis of comparison there, I spent a summer trying to learn Windows coding with Visual C++ 1.0, not really making any progress. I then got the GEOS SDK, and within a few weeks impressed Geoworks enough to get an offer for an internship the following summer.
I’m still so spoiled by the ease of the GEOS APIs that I won’t go near Win32/MFC.
I got to use GeoWorks Ensemble 1.2 (I think) in the early ’90s, running on a 8MHz 286 PC on full multi-task mode, and it completely blew the crap out of MS Windows 3.1 runing on a 386 16MHz!! People just stared jaw opened at the sheer speed of the GUI, and the running programs.
It printed beautifully on 9 and 24 pin printers, something MS Windows couldn’t do at all then!
Pity it didn’t pick up.
This is one of the more in-depth article that I have ever read on this website and the author managed to get me interested through the whole thing. I felt as much pleasure reading this as I did on the article about MorphOS.
I´m so glad that he didn´t spend more than one or two paragraphs describing the installation compared to other “reviews” that we see out there. This must be one of the supidest thing to do when reviewing an OS since you (ideally) only do it once!
I was old enough to use computers back then but I only got the chance to play with the MSX besides the IBM PC.
Kudos, Kroc. Thank you for a very good read.
Fantastic article – amazing how in-depth this article was for an OS that is such a relic today. I first tried GEOS just as it came out because the Commodore press was really excited about it. I remember the excitement of WYSIWYG word processing and using multiple fonts. Unfortunately my system was tied up hosting a BBS most of the time so I didn’t get much of a chance to do much of anything else
I stupidly sold off of my C=64 in college but I have a few relics from GeoWrite lying around, including some old printouts of BBS adverts for my system using the super-retro-l33t computery Cory font (which I see you include in one of the screenshots in the article).
I used Fleet System 2 to write papers for school. I can’t remember why I forego GeoWrite’s WYSIWYG-ness for it (FS2 was pretty fully featured – maybe the most fully featured of all Commodore word processors, but it didn’t look cool, and wasn’t WYSIWYG). I was actually somewhat resistant to that whole graphical environment for reasons I cannot recall, using IBM DOS WordPerfect over the Mac offerings in college.
Looking back now on some of the data you provided, it seems even more amazing now, given my memories of what was available for the 8 bit “bittyboxes” at the time.
Anyway, fantastic article – this is what I come to osnews.com for. Thanks for taking the time to write up something in such detail about a piece of software that has sunk into obscurity over time. Top shelf.
Unfortunately my parents bought me an Atari 99/4a computer and not an Apple II or C64. It wasn’t until a few years later when I bought a pc that I bought GEOS and got to experience it.
One of the selling points on the PC/PC laptop side was that it looked as exactly the same as it could (Windows didn’t look the same on desktops and laptops at the time).
The only downside was that Windows looked prettier when it did come out. And sorry to say too many people chose pretty over great functionality. The same was true between OS/2 and Windows 3.1 and Windows ’95.
Thanks for the walk down memory lane even if it was on a C64 which I wasn’t lucky to have back then.
Errm, you mean Teaxas Instruments 99/4A? Like here?
http://en.wikipedia.org/wiki/TI_99/4A
I was a PC/GEOS user since the first release of GWE 1.0, and I was fairly active in the GeoWorks forums on AOL for a time. What memories. 🙂 I loved this environment, and I still use GeoDraw from time to time.
Kudos to the author for a VERY well-constructive and informative article!
It’s sad that so many people didn’t know about GEOS running on Apple IIs, or that GEOS continued on into the PC era (obviously, many early AOL users probably STILL don’t realize they were using GEOS).
It was a great desktop environment, and would have probably hit even loftier heights had it gained continued momentum. I remember NewDeal talking up a good talk about entering the market and taking MS on; apparently that went nowhere.
I sure wouldn’t mind seeing the platform revived and continued, but the world seems to have moved on somewhat. If someone could open-source this thing, who knows what you could end up with. . .
I suppose GEOS is considered a small OS, by those still using it today. However I’d consider it a “Failed”, “Struggling”, or “Abandoned” Commercial OS. I propose that TriangleOS, StormOS, ZotOS, Unununium, UnOS, etc. meet the definition for really small OSes.
Still, I like GEOS as a functional and interesting OS that can run on equipment otherwise only suitable for DOS/Windows 3. I actually have a vintage IBM computer that boots DOS (286? 386?), but don’t think I have the Commodore version for my 128D.
-Bob
Boy did this article bring back memories!
I very clearly remember GEOS but I do not remember actually having ever used it. I do remember it as being revolutionary (in my mind), especially in a time where the mouse was being introduced to the public and most people didn’t know what to use it for.
I started on a VIC 20 and later the C64. If it wasn’t for my desire to write video games instead of waste time being beat by them, I never would have become the professional software developer I’ve been for the better part of the past 15 years.
OSNews needs more nostalgia like this.
“I actually have a vintage IBM computer that boots DOS (286? 386?),…”
Can’t edit my previous post, but it should read “Vintage IBM computer that boot GEOS…”
“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 RAM). ”
Actually this is incorrect. It wasn’t anywhere near “usually 4kb” RAM, and the author might be confused by the ROM address space for cartridges (which was 4kb and up with bankswitching).
The 2600 had 128 bytes of RAM (yes, that’s bytes not kb). Later in its life, some companies added their own ram in to their carts effectively doing calculations and such on board before sending it for display on the 2600.
The Intellivision had about 2kb of RAM *if* you add up the regular ram plus graphics and scratchpad ram. Otherwise the main ram was 704 bytes.