Slashdot Mirror


The Sad Parable of OS/2

Still-in-Mourning writes "IBM's first 32-bit version of its advanced PC operating system was released 10 years ago this month. It was better than anything around, yet it failed. Its hopes were pinned on many of the same things we hope today will bring Linux to the forefront. What lessons are to be learned? Will we learn them? A glimpse of a sorry chapter in computing history."

15 of 550 comments (clear)

  1. A Few Ideas... by Lethyos · · Score: 5, Interesting

    There's a few other simple reasons OS/2 might have failed. The first was that it was just too robust. You comment in the story that it was 10 years ago that it was begun. Well, think about the machines we had 10 years ago. Most people, if they even had a computer, they were in the 286 or 386 department. OS/2 is a heavy-weight. It compared more to what NT was soon to become back then. Yes, it had smaller hardware requirements, but most people's machines were just insufficient for running it. Other possibility was the amount of DOS software out there 10 years ago.

    Games and multimedia software were mostly written for DOS because authors needed direct hardware access. OS/2, while having excellent DOS support, it was still too slow and unstable to play Falcon 3.0 or what have you (although, I admit I was able to get CrystalDream II by Triton to run... only after a LOT of hacking).

    Aside from that, there were no direct hardware access API's available... ever (as far as I know). When OS had to start competing with Windows 95, Microsoft was introducing the WinG (Windows Graphics) library, the library that eventually lead to DirectX. I'm not saying that OS/2 had no multimedia support (it had a fantastic multimedia model), but it simply was not ambitious enough.

    Too bad. OS/2 was never geared towards people with lower end (average at the time) hardware and those who wanted to play games.

    --
    Why bother.
  2. IBM killed OS/2 by Eric+Green · · Score: 4, Informative
    Remember, OS/2 was originally released as part of IBM's PS/2 attempt to re-hijack the personal computer industry. The personal computer industry wasn't buying it -- they had no desire to put themselves back into thrall to IBM.

    It's hard to believe, in today's day and age when Microsoft is the "evil empire", that there was once a day when Microsoft was the scrappy upstart and IBM was the "evil empire", but that's what the situation was like for most of the 1980's. In the end it did not matter how good OS/2 became... nobody was going to put their company at the mercy of IBM again.

    By the time OS/2 Warp (32-bit OS/2) came out, if you mentioned OS/2 to anybody in the computer industry, they'd say something like "You mean that runs on something other than IBM PS/2 computers?". Unlike what somebody else here mentioned, everybody in the computer industry knew what OS/2 was and what it was capable of doing. But a) they didn't know it ran on anything other than IBM equipment, and b) they weren't interested in putting themselves back into thrall to IBM again.

    In the end, politics, not technology, doomed OS/2. The politics of Linux are completely different from the politics that doomed OS/2, and I can't think of any lesson from the OS/2 saga that applies to Linux.

    -E

    --
    Send mail here if you want to reach me.
  3. Did you know who wrote OS/2??? by Captain_Frisk · · Score: 5, Informative
    I'll give you a hint, it wasn't IBM

    Actually, it was (gasp) MICROSOFT (gasp). Think about that before you flame!

    Here are googles top 2 links with more information.

    1. Link
    2. Link

      and the google search itself
    1. Re:Did you know who wrote OS/2??? by KidSock · · Score: 4, Insightful

      Actually, it was (gasp) MICROSOFT (gasp). Think about that before you flame!

      Actually this isn't exactly true. Originally IBM did contract MS to write OS/2 however by the time they reached version 3 Windows started to gain in popularity so they focused on that and IBM took over OS/2 entirely. If you read the second link a little more carefully it claims IBM re-wrote everything starting from the 1.x base. That became OS/2 Warp and MS took said version 3 and renamed it to Windows NT.

    2. Re:Did you know who wrote OS/2??? by os2fan · · Score: 5, Informative
      Microsoft wrote some, IBM wrote some.

      Likewise, you can say IBM wrote Windows.

      The really good bits (REXX, IPF, WPS, PM, IFS, Program Manager, File Manager) are IBM stuff. The bad bits (the DOS coffin, 16-bit stuff) are Microsoft's stuff.

      IFS forst appeared in the DOS world in PCDOS 4.0. IBM wrote that.

      IBM had virtual machines before Microsoft *existed*. File and Program Manager appeared in OS/2 1.1 or 1.2. Microsoft borrowed these for the Windows 3.x shell apps.

      REXX and IPF are IBM mainframe stuff, using standard bits in different operating systems.

      WPS is IBM's invention: the shell, and even the colours were borrowed by Microsoft. The teal background first appeared in OS/2 2.11, way before Windows.

      And more, IBM tried to support existing machines, and not only the latest and greatest. IE they support the idea of using your OS on an old machine.

      --
      OS/2 - because choice is a terrible thing to waste.
  4. Re:OS/2 Still In Use.. . by neurojab · · Score: 5, Informative

    It's a little known fact that many ATM machines use OS/2... even the new ones. That means millions of people use OS/2 every day and don't even know it. The funny thing is that they WOULD know it if they used an M$ OS. How would you like the "blue screen of death" when you're in the middle of a transaction?

  5. Brings back memories... by Jack+William+Bell · · Score: 5, Interesting

    Many, far too many, moons ago I started a contract at Aldus Corporation as a SE/T (Software Engineer/Test). My job was to work with one of the first commercial applications developed for OS/2, a new version of Aldus Pagemaker.

    Because no-one at Aldus knew anything about OS/2 (they were pretty much all Mac-heads and sneered at PC's, DOS and Windows) they gave me a brand new computer, a bunch of sticks of RAM and a pile of floppies they got from IBM. "Go figure it out." So I did.

    The developers (who I was never allowed to meet for some bizarre reason) got Yesler (the codename for OS/2 Pagemaker) running about the time I was getting really bored with playing Reversi (the only real application on the OS/2 distribution I had) and I got started doing what they were paying me for; figuring out how to crash Yesler and/or OS/2 and emailing formatted dumps with my comments to the developers. It wasn't hard to find said bugs, although I was told "You can't crash OS/2, it is too solid." Hah!

    Just about the time they got Yesler stable enough that I could put together a demo script the marketroids could use to show off the program (they had to follow it exactly or it would crash) I found a way to make OS/2 have a complete spastic seizure. It involved a fairly complex series of actions that had to be followed exactly, but when you did the last one the computer would freeze and waves of color would wash over the screen. Kind of pretty in a psychodelic way.

    We called it the Colorshow bug and the developers claimed it was an OS/2 problem. This kicked off a shitstorm of finger pointing that ended with the developers working around the bug instead of IBM fixing it. Remember, at this point IBM was actually pretty happy about the Yesler project because it gave their new operating system some street cred, so it really surprised me that there was so much rancor. An earlier problem with printer drivers was fixed in a day from my reporting it.

    But the punchline happened about a week after I found the Colorshow bug. One of the marketroids came by and asked if I could demonstrate the bug for a group of suits that were waiting down the hall. No problem, bring them on (and, yes, I promise to watch my language). So the suits crowd around the desk and I walk the dog and pony (click, click, drag, click, drag, click, colors, "OOOOHH!", nervous laughter). The suits thank me and they leave.

    Then the guy sitting across from me leans over and says "You know who that was?" I shake my head. "That was Paul Brainard," (the CEO of Aldus) "and a bunch of Apple executives up here for a visit."

    OK...

    Jack William Bell

    --
    - -
    Are you an SF Fan? Are you a Tru-Fan?
  6. Re:OS/2 v.s Windows by Sloppy · · Score: 4, Insightful

    I used OS/2 at work from late 1994 until February 2002, when I finally switched to Linux. And damn, Nautilus (the Windows Explorer clone) is just plain sad. It really is just as bad as Windows, maybe even a little worse, if that's possible.

    If OS/2 had won, then GNOME and KDE would be copying a good GUI instead of copying a piece of shit. Or, to put it more generally: if OS/2 had won, things would be better, simply because the product was better. Sure, the "political" situation for would be the same (maybe even a bit more intense since OS/2 would be harder for "open source" to beat than Windows was), but the user experience would be about a decade ahead of where we are right now. So yeah, I wish OS/2 had won.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  7. Re:I don't get it. by steveha · · Score: 5, Informative

    What exactly in the in the 286 architecture prevents the use of a multitasking operating system?

    That was not the problem. The problem was writing a multiasking operating system that would run all the DOS apps (which were important at the time).

    When the 286 was in protect mode, some of the instructions worked differently than when it was in "real" mode (8086 compatibility mode). Result: you could not execute DOS apps; they wouldn't work.

    So, how about making a DOS virtual machine? Well, the 386 has features that make it easy to spin up multiple real mode virtual machines, but the 286 didn't have those features. A purely software virtual machine would be very slow.

    So, how about switching out of protect mode and running real mode code in the 286's real mode? That was the only option, so Microsoft took it. However, Intel had not designed the 286 to do this. There was an instruction to start up protect mode, but no instruction to leave it and go back to real mode! Microsoft wound up programming the keyboard controller chip to actually reset the CPU, many times per second, to switch to real mode.

    Because DOS apps ran in real mode, they owned the whole machine: all memory, all devices, etc. So if a DOS app crashed, it would take the whole machine down with it; a crashing DOS app could trash OS/2, and there was no way to prevent it.

    Even worse, the 286 did not have features that would let you virtualize the hardware, and DOS apps liked to talk directly to the hardware. All DOS apps liked to write directly to the video card, rather than going through the BIOS, and the 286 didn't really help you solve that problem.

    So the OS/2 1.x "compatibility box" could only run a single DOS app at a time.

    Meanwhile, Microsoft sold Xenix 286, which worked perfectly well. Alas your Xenix 286 programs either had to be less than 64KB each, or else they had to deal with near/far pointers (yuck), but Xenix 286 worked. Microsoft never tried to do a GUI desktop for Xenix, but it would have been possible.

    It appears to me that the article writer is trying to excuse Microsoft's lack of skill by pretending that the task was impossible.

    No, it really was impossible to write an OS that would run decently fast on the 286 hardware of the day, would multiask old DOS apps, and would be reliable. The 286 was just too broken.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  8. Re:Win95 didnt kill OS2, Microsoft did. by Locutus · · Score: 5, Interesting

    Don't forget, in 1995 Microsoft did have a monopoly on PC OS's and what they did to make Windows 95 apps NOT run under OS/2 was anti-competitive and illegal. Microsoft built Windows 95 to load a few resources up at the 1GB memory address just to prevent OS/2 from running Windows 95 apps just like it ran Windows 3.x apps. You see, OS/2 could ONLY access 512MB of address space.

    Let's not forget that in Nov 1994, at COMDEX, HP had 50% of their PC's running OS/2 the night before the show opened. Bill Gates made a phone call and by morning, NO HP computers were running OS/2.

    The list goes on. I blame IBM 10% for OS/2 not gaining more market share and the other 90% was Microsofts anti-competitive nature to do ANYTHING to prevent the consumer from making the choice.

    Speaking of choice, do you remember that Microsoft threatened to pull out of COMDEX because IBM was doing it's keynote speech about choices unless IBMs timeslot was moved to reduce the viewers. I think IBM dropped out of COMDEX the following year and all since.

    Think about it. It took MIcrosoft 10 years to build a version of Windows that is close to OS/2 v2.0... well maybe v2.1 is a better comparison since it had better legacy Windows support and the 32bit graphics system updates. TEN YEARS!

    WHERE DO YOU WANT TO GO TODAY??? With Microsoft?
    Nyet.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  9. Re:Windows 95 applications killed OS/2 by sconeu · · Score: 4, Informative

    Heh, and now that MS has a stable OS, the apps have all gone down the shitter.

    What apps? Just about every commercial application on the market five years ago has been replaced by a Microsoft clone.


    He's right, and the exception that proves the rule is Quicken. The only reason Quicken still exists is that the FTC (for reasons that are still unknown, given how merger-happy it seemed then, and still does) nixed the MS buyout of Intuit.

    --
    General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
  10. and Windows in an Elevator is a scary thing! by teambpsi · · Score: 5, Funny

    The elevator in our building has a little LCD screen in it that displays time/temp/weather information as well as the individual company names of the floors its on.

    Last week the marquis application crashed and had a blue screen of death on it....NO ONE USED THE ELEVATORS until the building management rebooted the display software and sent out a notice that windows was only used for the marquis, and NOT in the operation of the Otis elevator

    --

    Old age and treachery almost always overcome youth and skill.
  11. Crap by Greyfox · · Score: 5, Insightful
    2.0 ran perfectly on my OEM Laptop at the time. 2.1 was the ultimate in stability and performance for OS/2. It was down hill from there. Most of the changes in Warp are either cosmetic or lame attempts to hack around the OS/2 shortcomings that the market was demanding fixes to.

    As far as I could tell, no one outside IBM was buying the PS/2. At least, I've never seen a single one outside the company. At the height of its popularity, it was estimated that OS/2 had over 10 million users.

    IBM could have stayed ahead and taken over the industry, but a lot of factors conspired to prevent it from happening. Much of it was due to IBM attitude. First off, mainframe mentality ruled (And still rules, to a large extent) the company. Upper management still viewed the PC as a toy. Certainly they would never have dreamt that a user might actually want to multitask with it, even though OS/2 featured preemptive multitasking.

    Further there was the IBM tendency to do a thing and then sit back and rest on their laurels. They go into maintenance mode and don't continue active research and development of innovative new features. IBM business process is still not geared toward a completed project where live development is still taking place.

    As for marketing, well it is said that IBM couldn't market eternal life if they had sole rights. They had no idea of their target demographic and they tried to market the product to Joe Average User. This resulted in Joe Average User getting pissed off with the painful installation process. And the installation was painful. IBM could have done something about that, but they were resting on their laurels (See previous point.)

    Furthermore, IBM's own software did not strive to show off the operating system at all. Most of the utilites they shipped were straight windows ports. This resulted in poor performance on the platform. I made a comment in a forum at one point that Netscape for Windows 3.1 actually did a better job of multi-threading than the OS/2 web explorer did. I actually ended up using the DOS version of the document explorer that IBM shipped for documentation because the OS/2 version would block the system input queue while it indexed documents, thus hanging the entire system.

    Most people will agree that the death blow was PCCO's refusal to preload OS/2 on their systems (Due to illegal Microsoft bullying.) Since the install process never improved and there was no way to get the system preloaded, that was pretty much all she wrote.

    There are still some companies out there using OS/2, and they're paying IBM a lot of money to maintain the product. It's mostly banks or other shops with other IBM iron. OS/2 always did talk to the mainframes very well. But OS/2 lost its chance to be a (or THE) mainstream desktop OS when Microsoft introduced Windows 95. Windows 95 was less stable, still didn't feature preemptive multitasking for all programs and had a far less robust interface, but it was good enough that most people didn't care.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  12. 1.0 vs. 2.0 by Eric+Green · · Score: 5, Informative
    2.0 was designed from the get-go to run on pretty much any 32-bit hardware out there. IBM had abandoned the notion of trying to hijack the personal computer industry by that time. The problem is that by the time it came out, everybody in the computer industry was operating under the notion that OS/2 was for the PS/2. Which was true, in the beginning.

    Regarding IBM and Microsoft and OS/2, I've read some reminiscing by one of the industry pundits who was there at the meeting where IBM blew off Microsoft. Bill Gates showed up with all these charts showing Windows as a little side project on top of IBM/Microsoft OS/2, and IBM blew him off. Yep, that's right, IBM blew off Microsoft -- NOT the other way around. That was apparently when Bill decided that Windows was going to be a totally seperate operating system not reliant upon anything IBM (Chairman Bill does NOT like being blown off by arrogant IBM execs!), and that was when Bill decided he was going to borrow some tactics out of the IBM monopoly handbook, such as bundling, "vaporware", and per-CPU pricing.

    Now, I'm not going to argue about whether the Microsoft monopoly on personal computer desktops is good or bad. I'll just point out that an OS/2 monopoly would probably have been even worse -- because IBM is a hardware company as well as a software company, and undoubtedly would have used their hardware muscle to squeeze out the kind of white box clone business that kept Linux alive for many years before the major vendors discovered Linux.

    -E

    --
    Send mail here if you want to reach me.
  13. OS/2 Screenshots by searleb · · Score: 4, Informative

    In case you have never used OS/2 and you are interested in what it looked like (as I was), this essay is chock full of screenshots.