The Golden Years—the most successful version of OS/2
In October 1994 IBM released OS/2 Warp, the most popular version of OS/2 and arguably one of the coolest operating systems ever (Warp Connect even said so on the box—“The totally cool way to run and network your computer”—so it must be true). It was so good that some people used it for many years after the release. Its underpinnings weren’t all that different from OS/2 version 2.11 but it was a great leap forward in terms of usability.
OS/2 Warp was also IBM’s most serious and best attempt at gaining dominance on the PC desktop, or at least winning a significant market share. At one point and in some countries, OS/2 Warp may have accounted for 5% of the desktop market or more, but it is extremely difficult if not impossible to get reliable figures. OS/2 certainly had a significant foothold in the banking and insurance industries, both traditional IBM customers.
Similarly to OS/2 2.1, there were two versions of OS/2 Warp available: basic Warp without Win-OS/2 called “Red Spine” because of the appearance of the box (labeled “Enhances your existing DOS and Windows”). This version was prevalent because most people already owned Windows 3.1, whether they wanted to or not. And of course Red Spine was cheaper too. The other version was Warp with Win-OS/2 called “Blue Spine” (the box said “Includes DOS and Windows application support”). Both these versions were avaliable on floppies or CD-ROMs. By this time the floppy versions were fairly rare, especially because it was possible to create floppies from the CDs; it could make sense to buy the CD version even for people who couldn’t directly install from CD (or not yet).
In mid-1995 the Warp family got two new members with the introduction of Warp Connect (again in Red and Blue Spine versions), extending the choice to whopping four possible versions, not counting different distribution media.
OS/2 Warp had several things going for it (in no particular order):
- It was a reliable, efficient 32-bit OS. It did not rely on the shaky foundation of DOS as Windows 3.1 and later Windows 95 did.
- It offered excellent compatibility with DOS and Windows 3.1 applications. In IBM’s words OS/2 Warp was “better DOS than DOS” which was often true.
- It was a great communications tool and many people ran utilities like BBS servers in the background, with OS/2 allowing normal use of their PCs.
- It was reasonably easy to use, with the powerful user interface of the Workplace Shell.
Naturally OS/2 Warp suffered from a few weaknesses as well (again in no particular order).
- It offered excellent compatibility with DOS and Windows 3.1 applications (no, this is not an error). Many application vendors argued that by developing a DOS or Windows app, they would reach the OS/2 market in addition to DOS/Windows markets and they didn’t develop native OS/2 applications.
- Tough competition from Microsoft who did their best to damage OS/2. Their most effective tools were locking OEMs into Windows preload agreements and preventing ISVs from developing OS/2 applications.
- Perceived (or even real) lack of commitment from IBM. Things like IBM not preloading OS/2 on some IBM hardware did not help customers gain confidence in OS/2 at all.
- IBM’s poor marketing. IBM just didn’t know how to sell OS/2. They were traditionally very good at targeting corporate customers but mass marketing is a very different subject.
And now let’s take a closer look at the improvements over the previous versions of OS/2. First the technical differences:
- OS/2 Warp supported an improved executable format offering much better compression (not compatible with OS/2 2.11 and earlier). Unfortunately few developers used it, precisely because it wasn’t compatible with older versions.
- Improved display and printer driver models, making it easier for developers to write drivers for these devices. Even so, writing a display driver was a massive undertaking. This fact contributed to the lack of drivers.
- Improved multimedia, adding support for TV cards, video capture boards and similar devices.
- Much larger selection of available drivers (OS/2 2.1 really didn’t have many).
There were numerous usability enhancements as well:
- The ability to temporarily alter the boot process with Alt-F1. This was many users’ favorite. Up to version 2.1, the fixed boot sequence one of the worst usability problems. OS/2 users could not afford to live without having bootable floppies handy until Warp.
- Improved desktop layout, new icons, more attractive color scheme.
- Greatly improved and much better looking tutorial program for novice users.
Here’s what OS/2 Warp looked like right after installation:
Cleaner and nicer than OS/2 2.11 wich one brand new feature—the LaunchPad at the bottom of the Desktop. The LaunchPad was a neat feature and demonstrated the power of the WPS with full drag-and-drop support.
I installed OS/2 Warp without Win-OS/2 (Red Spine), the more popular version. It came in a nice glossy cardboard box and contained two 3½” HD floppies and two CDs (obviously this was the CD-ROM version). One CD contained the operating system, drivers and sample multimedia files (sounds and movies). The other CD held the Bonus Pak, a set of applications and tools of which the two most important ones were IBM Works and IBM Internet Connection for OS/2. Also in the box was a nice User’s Guide and a directory of OS/2 ISVs and consultants.
Installing OS/2 Warp on a test system (a Pentium III-600 with 256MB RAM and a 32MB Matrox G400) was straightforward after building updated boot floppies with the latest IDE and floppy drivers. Installing from a CD didn’t even take long. Once the basic OS was set up, drivers for the Matrox graphics card were installed and the system was ready for use.
The test system was later upgraded to OS/2 Warp Connect with Win-OS/2 (Blue Spine).
The Big Thing
The biggest new thing in OS/2 Warp was of course the Internet. OS/2 suported the Internet long before Microsoft even realized its importance. This time the catchphrase on the box read “Your on-ramp to the information superhighway”.
The “superhighway” stuff was contained on the second CD, the BonusPak disk. Next to FaxWorks, VideoIn or IBM Works there was IBM Internet Connection for OS/2. It was aimed purely at dial-up users and contained an IBM dialer plus “Dial Other Internet Providers” (DOIP) dialer, at that time only supporting SLIP and not the newer and later prevalent PPP.
Basic Internet client software was also supplied—FTP, Telnet, e-mail, news, WWW (very rudimentary at that time). Plus support for some protocols that are completely extinct nowadays, such as Gopher.
The IBM Internet Connection was a very scaled down version of IBM’s TCP/IP kit which had been available since OS/2 1.3 days.
As mentioned above, in 1995 IBM introduced OS/2 Warp Connect. This was basically a bundle of several existing IBM products. In addition to the base system and BonusPak, Warp Connect included IBM’s LAN client (with optional peer functionality), Novell NetWare requester, TCP/IP support and LAN Distance (remote LAN access). Thus Warp Connect was indeed very well connected.
This merging of several previously standalone products made things a little confusing, especially for newcomers. For basic networking support there was MPTS (Multi-Protocol Transport Services) which was required by all the other products. The IBM LAN Requester had not changed much since OS/2 1.x days, still supporting the familiar NET command. IBM Peer was a very scaled down version of the LAN Server without most administration tools. Perhaps the most interesting of the pack was the TCP/IP support. Again it was a somewhat scaled-down version of IBM’s TCP/IP kit without NFS support, X server and similar esoteric software. What it did include however was full support for TCP/IP transport protocols and a number of client applications: FTP, Telnet, Gopher, e-mail, news (NNTP) and WWW—much like the IBM Internet Connection in plain OS/2 Warp.
This is what Warp Connect looked like after installation (with IBM Peer and TCP/IP installed):
There are quite a few more folders than in plain Warp and there could be even more if all options had been installed. This is what WebExplorer, one of the early web browsers, looked like:
Even this old WebExplorer 1.01 can still render some of the web’s most interesting pages.
Users of OS/2 Warp could choose from a relatively wide palette of applications. There were word processors, spreadsheets, database programs, development tools, communications programs. After taking a brief look at several vector drawing programs, word processors and application development tools I decided that now there’s time for image manipulation programs.
There is one very technical reason for this: Image manipulation programs need high resolution—especially high color resolution—and there were no drivers for the test system’s Matrox G400 which would work on OS/2 2.11 or earlier, and none of the image manipulation programs looks particularly good on 16 colors. But the Matrox drivers worked fine with OS/2 Warp.
The first application examined is the oldest and perhaps best known: ColorWorks from SPG, proudly called by its authors “The Artist’s Ultimate Power Program”. The first version of ColorWorks was released in 1995 and was later followed by versions 1+ and 2. It wasn’t exactly cheap (the box sported a $329.99 price tag) but also not more expensive than other similar programs (e.g. Adobe Photoshop).
For the most part ColorWorks was similar to other image manipulation apps but it had at least two unusual and probably unique (at the time) features: DIMIC and SMP Smart Threading. DIMIC stood for Dynamic In-Memory Image Compression and it referred to a technique ColorWorks could use to store the images compressed in RAM at the expense of processing speed. This allowed ColorWorks users to edit much larger images than they’d normally be able to. SMP Smart Threading was nothing other than multithreading support. ColorWorks could split its workload into several threads which would run concurrently. While this had no real effect on single processor machines, it could significantly speed up processing on SMP machines (at that time those would be running OS/2 2.11 SMP):
While SPG promised linear increases in performance up to 64 CPUs which is technically impossible (due to memory bandwidth bottlenecks), it is very likely that on 2-4 way SMP machines the performance increase was quite impressive.
At any rate ColorWorks was a capable program, as evidenced by one of the sample images supplied with it:
ColorWorks had all you’d expect from such a program—drawing functions, color manipulation, filters, all the works.
The other graphics program was TrueSpectra Photo>Graphics. It is difficult to say what kind of program it was exactly—it was an interesting hybrid between a bitmap and vector oriented drawing program. Photo>Graphics worked in a unique way: its output is a bitmap but it is not stored as a bitmap, but rather as a collection of objects (which can be bitmaps), text and effects—more akin to a vector oriented app. This has two important benefits:
- The output image can be rendered at different resolutions for screen, printer etc.
- The image can be very easily edited by breaking it down to the individual “atoms” and rearranging them as desired.
TrueSpectra Photo>Graphics looked like this—the screenshot is from an old beta from early 1996, the oldest easily obtainable version:
With Photo>Graphics it was easy to change the text and images or alter the result in any way the user desired. The output was turned into a single bitmap only when it was printed or exported to disk.
OS/2 in the Marketplace
OS/2 didn’t have it easy—outside or inside IBM. It is well documented that at the time of Windows 95 release, Microsoft was putting serious pressure on the IBM PC Company, refusing to sign the Windows 95 OEM license until the last moment and requesting much higher payments from IBM than from other OEMs.
There was also one internal IBM project that had great bearing on the future of OS/2: OS/2 for PowerPC. It was a somewhat nebulous project which kept changing directions during its lifetime. It is hard to tell what was at the beginning of this project, if there indeed was any clearly definable beginning at all. At some point in the early 1990’s IBM decided that it would be wonderful to have this cool Workplace OS. It was to be a microkernel-based, object oriented uber-OS running on a RISC platform (a very ominous collection of buzzwords). It was to be able to run several operating systems at the same time. Nobody can agree anymore on which OSes exactly those were but it is certain that they included OS/2, Windows NT, MacOS and Solaris. Why anyone would want to run all these OSes on a single machine at the same time is something IBM never adequately explained and probably didn’t even think about hard enough. Obviously “because we can” was not a correct answer.
At any rate, IBM kept changing the goalposts and the project ended up as OS/2 for PowerPC, officially called in the final stages OS/2 Warp Connect, PowerPC Edition. IBM was hyping this product quite heavily between 1993 and 1995. There were many articles written about it, and there were beta versions of the PowerPC SDK available. There were porting workshops going on and companies like Stardock or Sundial Systems ported their products to OS/2 for PowerPC (reportedly without much difficulty).
As the release date for OS/2 Warp Connect, PowerPC Edition neared, the hype subsided. And when OS/2 for PowerPC was supposed to be released, IBM was suddenly quiet. The product was stealthily released but almost impossible to get.
There were multiple reasons for the failure of the OS/2 for PowerPC project. Some were external to IBM, others were purely internal:
- Nobody actually needed the Workplace OS, whatever it was called
- There are many stories about serious mismanagement of the project, about middle managers lying to their superiors about project status etc.—classic software development woes
- The project hinged on the success of the PowerPC architecture and that didn’t pan out
On the whole, OS/2 for PowerPC was a spectacular failure and had grave consequences for OS/2. The PSP division (Personal Systems Products) was seriously weakened and didn’t survive for long. Billions of dollars were spent and effectively wasted for the most part, even though several technologies developed for OS/2 for PowerPC later resurfaced in OS/2 Warp 4 and elsewhere. One can only wonder what would have happened if IBM had spent those billions on the Intel version of OS/2 instead.
There is one very important lesson to be learned from this debacle: don’t believe industry pundits. They can’t see into the future even though they like to pretend that the opposite is true. From late 1980’s until mid-1990’s the conventional wisdom was “CISC is dead, RISC is the future”. Well, they were right, but there was one fatal flaw. These pundits predicted that Intel x86-compatible CPUs as the most typical CISC processors were out and would be replaced by a new RISC based architecture, such as the PowerPC (or perhaps Alpha or MIPS). But the engineers at Intel and other x86 compatible CPU vendors (AMD, Cyrix) weren’t stupid. What they did was build CPUs with a RISC core and a x86-compatible front end. Thus they achieved what the pundits didn’t expect: RISC performance while retaining 100% backwards compatibility with CISC. And so OS/2 for PowerPC was doomed even if it hadn’t been plagued by all its other problems.
I should have my copy of ColorWorks somewhere. Probably a good time to image the floppies… if I can find the box. I don’t think I ever had Micrografx Designer disks but I can probably still find the files. Will think about how to share that.
I’ve got ColorWorks v2 on CD. I’ll try to find time to image it in the hopefully-near future. I still owe Michael some photos of some DevCon CDs, I think…just need to find time to dedicate to this stuff, which has been scarce of late.
Ah, cool! It seems like a great deal of the commercially released OS/2 software hasn’t made it onto the web. I suspect much of it once was in the form of warez, but most of those sites and message boards are probably long gone, along with the software they had.
Somewhere I’ve got a copy of DeScibe v4 (and IIRC, a beta copy of v3) kicking around. I need to get that imaged as well.
I’m managed to pick up a copy of ColorWorks V2 myself! I’ve uploaded it to WinWorld (though it’s not up yet) and I intend to put it on VetusWare at some point soon. Still would be nice to get Designer at some point.
Yay, I still haven’t found my ColorWorks box 🙂 Designer just showed up on vetusware, please let me know if it works. I just created the floppy images from self-extracting files and haven’t tested it, though I know it worked earlier.
During most of this, I was an employee of the IBM PC Company. And I can understand that IBM appeared from outside to be severely schizophrenic.
You have to understand, that like many large companies that there were a lot of verticals, the PC Company the Software Group, Global Services, etc and surprisingly little communication between them. And every group would have their own missions and targets. There was no large top-down push to get OS/2 support everywhere, and some people were even quite hostile towards OS/2.
OS/2 was being developed by the software group, and even within the software group, different development teams would have different targets. So some software products only ever saw a Windows release, or the OS/2 release was an after thought.
Likewise for the PC company, the target was to sell PCs. And the larger market wanted Windows, so that is what was primarily catered to. Especially after Win95 was released, the interest to support OS/2 outside of corporate PCs declined significantly. So much that it was often very difficult to install OS/2 on something like an IBM Aptiva.
Thanks. Having seen large organizations from inside, I can totally understand the different pushes and pulls in different corners of IBM. For outsiders it was often difficult to comprehend that there was no “IBM” but rather a number of groups within IBM, and those groups were each a good sized organization with its own priorities and significant inertia.
I experienced the tail end of OS/2 support at IBM in the early 2000s. At that time, IBM had certain desktop and laptop models supported by OS/2. This was actually IMHO quite sensible, IBM didn’t need to support a wild variety of hardware but for customers who wanted that, it was easy to find an IBM machine that ran OS/2 well.