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."

550 comments

  1. OS/2 by shankark · · Score: 3, Funny

    One of my professors in undergraduate school often quipped that IBM's OS/2 was exactly that, an OS by half.

    1. Re:OS/2 by Blaze74 · · Score: 1

      heh, the old OS/2, Half an operating system joke :P

    2. Re:OS/2 by Anonymous Coward · · Score: 0, Informative

      I did, but he says he preferred 5 year old boys more and was soon arrested for sodomizing his own nephew. Sick bastard. But hey, that's what you get from those freaks at Berkeley.

    3. Re:OS/2 by cybrthng · · Score: 3, Interesting

      Actually with OS/2 the interface was seperate from the OS.

      I remember dropping the GUI all together and using a text based switcher to run my BBS in.. didn't need a gui, just a alt-tab interface to the os2 cmd prompt so i can run PCBoard 15.1 and play sierra games at the same time.

    4. Re:OS/2 by Anonymous Coward · · Score: 1, Interesting

      I was an OS/2 Developer for almost 5 years. It was a great run. Solid OS. Good stuff. I built many systems ontop of OS/2 and it almost never let me down. It was and is far beyond Windoze, NT, and XP.

      Make no mistake, M$ killed OS/2. They will kill Linux given the chance. They will kill the Mac, given the chance. They will kill Solaris, given the chance....

    5. Re:OS/2 by Anonymous Coward · · Score: 0

      GNU Linux should be Linux/2.

    6. Re:OS/2 by SuperDuperMan · · Score: 1

      I'm no windows lover but I can tell you I was seriously disappointed in OS/2. I bought in right up until OS/2 Warp and found it to be a painful experience.

      Massive CONFIG.SYS and AUTOEXEC.BAT files and the GUI wasn't smooth running with multiple I/O queues like NT/XP/2000.

    7. Re:OS/2 by Com2Kid · · Score: 3, Funny

      "Massive CONFIG.SYS and AUTOEXEC.BAT files "

      Oh yes, the Windows Registery is just SOOO much more managable!

      ::reachs down to pick eyes up off of ground::

      Sorry, then just rolled right on out!

    8. Re:OS/2 by ScottKin · · Score: 1

      hmmm...

      and how do YOU spell PARANOIA???

      --
      I don't give a rat's behind about "karma" here or anywhere else. Don't like what I have to say here? Deal with it!
    9. Re:OS/2 by Anonymous Coward · · Score: 0

      Hmm...

      P A R A N O I A ???

    10. Re:OS/2 by Anonymous Coward · · Score: 0

      Beat the pants of those endlessly corrupted binary "INI" files that OS/2 used.

      If you can't remember the single input queue issues and CONFIG.SYS voodoo, I would guess that your eyes rolled under your desk sometime in the early 90s.

    11. Re:OS/2 by Anonymous Coward · · Score: 1, Interesting

      I work for a state government that still uses OS/2 Warp 3 for one of our in house applications. When you put Warp next to NT/2K, immediately the Windows machines jump out as more intuitive and far better supported (ever tried navigating IBMs site for OS2 info?). However, when you dig a little deeper and look at some of the community efforts that have sprung up leveraging OS2s' capabilities...it's really suprising. For example, there are OS2 ports of Xfree86 and quite a few ported GNU utils. There is also a Win32 API compatability project [Odin] out there. When everyone talks about OS2 being dead, ironically, it's not for a lack of functionality. There are still people extending that. The real coffin nail for OS2 is the $250 retail price it STILL carries. If one were really so inclined, you could use OS2 as a bridge for legacy DOS apps, Win32 support (via Odin), and *nix Apps (via the EMX library, GNU ports, and XFree). Truth is, with better handling, OS2 could still be something.

    12. Re:OS/2 by Anonymous Coward · · Score: 0

      Could be worse. You could be running Linux instead!

    13. Re:OS/2 by operagost · · Score: 1

      But which OS? Surely if OS/2 is 1/2 an OS, then Windows 3.0 (the only MS offering when OS/2 2.0 came out) was less than a quarter. Get real.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    14. Re:OS/2 by Anonymous Coward · · Score: 1, Insightful

      Just shows you professors can make utterly moronic statements. I'd wager he had never even seen, never mind used the OS.

    15. Re:OS/2 by j_w_d · · Score: 3, Informative

      I don't think it was the greatest. The user interface was locked in. Much like NT (microsoft). So I never really cared for it.

      You plainly never used OS/2 enough to know it. Presentation Manager (PM) was partially object oriented, while the WPS (work place shell) was fully OO. Companies like Stardock produced terrific desktops that were nothing like the default PM or WPS layouts. One of the cool things about Stardock's products was the addition of properties to file types based on inheritance, such as the property that text files were inherently editable. Click on a text file and it came up in an editor. Stardock's interface for OS/2 is very similar to KDE or GNOME, with multiple desktops, and a small windowed desktop selector. Windows 95 actually copied the OS/2 WPS or PM interface, which was quite clean and easy to use. OS/2 WARP was also the first desktop OS, besides Linux (and at that time it was not automated in Linux as it was in OS/2 WARP), to come with built-in communications (beyond some communications program such as ProComm) and internet connectivity, while Gates was still pushing that glorified BBS from Microsoft. At the time you still had to download winsock utilities from MS and install them if you wanted to use the internet. Micorsoft's prucahse of the parent program that became Internet Exporer was driven by the need to answer OS/2 and provide internet services. WAIS, Gopher, FTP and Web connections in OS/2 could be dropped as icons on the desktop. Click on them and the modem would automatically dial and connect. OS/2 was not as stable as Linux, but even when it went down, it came back with less trouble than Windows, and you could easily back step to a previous configuration, if a program installation clobbered the system with an incompatible driver or something. There was also never any necessity to reinstall OS/2 as the installation aged. This is still a common occurence even with modern versions of Windows when the registry becomes so clogged with crap the system becomes inherently unstable. OS/2's configuration files were simple, text based, and easy to fix with an editor. There is still a lot to like about it.

      --
      ------ The only greater hazard to your liberty than n politicians is n+1 politicians.
    16. Re:OS/2 by Anonymous Coward · · Score: 1, Insightful

      Boo hoo

      IBM has been clueless about what a PC OS is since the beginning. The last thing I'd ever want to see is them controlling the PC OS monopoly.

      At least Microsoft has had a vision, and knows they have to be ready to change it on the fly. Stop blaming Microsoft for the mid-east crisis, terrorism and the leaning tower of pisa, and find a way to beat them.

    17. Re:OS/2 by corp_dude · · Score: 1

      How many of you actually USED OS/2? How many of you actually experienced OS/2's preemptive multitasking - compared to whatever it is that Windows has?

    18. Re:OS/2 by Anonymous Coward · · Score: 0

      Oh yes. The famous wit/2.

    19. Re:OS/2 by mirabilos · · Score: 1

      In Germany we say
      Ohne Speicher nur die Hälfte (1/2)

      It translates to
      without memory only the half

      ;) truly, with 8 MB OS/2 Warp was no fun...
      I still have my CD, but never gotten any updates
      to networking / inet functionality (they were for
      Warp 4 only IIRC).

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
    20. Re:OS/2 by Anonymous Coward · · Score: 0

      How many OS/2 users had used a real multitasking multiuser OS like UNIX? All I ever saw out of that crowd was lame comparisons with Windows 3 and denial about the stability issues and input queue lock problem. It wasn't bad enough for the masses, but the main problem was that it really wasn't good enough for the elites.

    21. Re:OS/2 by egal2_de · · Score: 1

      I think the man who said that is extremely stupid.

    22. Re:OS/2 by egal2_de · · Score: 1

      A multiple Message Queue does not help if the whole Kernel crashes... And a corrupt Windows Registry is not better than the OS/2 Config.sys.

    23. Re:OS/2 by Anonymous Coward · · Score: 0

      This is something, I can't understand - did you ever try out the possibilities of the os/2 - gui and compared it with windows 9x or NT ? In my office i'm forced to use windows (NT - the best of the worse), at home I recover by using OS/2, knowing that I'm one of those rare people. Why shall I drink vinegar, when I can have an ten year old Brunello da Montalcino instead ?

    24. Re:OS/2 by UnknownSoldier · · Score: 2

      > How many of you actually experienced OS/2's preemptive multitasking - compared to whatever it is that Windows has?

      Which version of Windows?

      Win3.1 -- cooperative multitasking

      Win95/98 -- pre-emptive multitasking (but for only 32 bit apps) The 16-bit subsystem can stall the kernel, since Win32 is built on top of it.

      WinNT/2K/XP -- pre-emptive as well. The Win16 subsystem is cooperative, since it emulates Win3.1, but can never stall the kernel, since it sits on top of Win32.

      OS/2 pre-emptive multitasking isn't any better then NT's.

  2. Wasn't it obvious? by Anonymous Coward · · Score: 0

    It was the marketing, or lack there of. No one had heard of it.

    1. Re:Wasn't it obvious? by mlsemon2 · · Score: 3, Insightful

      That's not totally true. I remember Super Bowl ads for it and a few ads in the months following it. Of course, that was a while before Windows 95, and for the most part, you are correct. The marketing I read and saw during the Windows 95 era was almost nonexistent.

      What a great article. Just today, when I pulled up to the ATM machine and saw the beloved TRAP=0002 hex dump black screen of death, and I had to let out a little sniffle for my former fave OS.

      Will Linux learn the lessons of OS/2? Who knows? For my time in OS/2, the company and the users were nice, knowedgeable, and professional. There were not many exaggerations and very few of Microsoft-style false promises. The lesson I got out of it is that consumers can't handle a straightforward approach, always going for smoke and mirrors and gold glitter sparkles. It doesn't matter if something exists, only that the something is "just around the corner."

    2. Re:Wasn't it obvious? by lseltzer · · Score: 1

      I remember the IBM OS/2 Fiesta Bowl on New Years Day, probably 1992. The announcers made frequent jokes about how they had no idea what hell it was.

    3. Re:Wasn't it obvious? by Greyfox · · Score: 3, Insightful
      Linux has thus far managed to avoid making most of the mistakes that killed OS/2.

      1) Active developent continues. IBM was always terrified of breaking "legacy" application support, which is why there was never a proper fix to the Single System Input Queue problem.

      2) There are practically no barriers of entry into Linux development. Compiler's free. Tons of libraries are free. Tons of programmers tools are free. The operating system is free. All the stuff that IBM charged you for and Microsoft charges you for, free, free, free. A 12 year old could afford to install the OS and tinker with it. Many do.

      3) Marketing. Well... marketing in Linux is an interesting phenomenon. Largely it's word of mouth between clueful engineers. Linux takes a company over one computer at a time and management never has a clue. They just blink in their bovine way and ponder their managerial effectiveness which must be why no one ever complains about the file server crashing anymore...

      4) Installation. Redhat install is pretty much point and click. The OS/2 install was painful. I did it for a living for a while. We had a document which specified the exact order in which you had to install our company's assorted software. Deviate at all from that order and you'd trash the Workplace shell and never get any icons, forcing you to fdisk, format and reinstall. The installation process was guaranteed to take 8 hours. I'd prefer Linux installs any day of the week.

      The main thing is the system keeps evolving, bugs keep getting fixed, Linus doesn't mind doing major revisions if he thinks a design isn't right and if you ever have a question, you can always ask the guy who wrote the package you're having trouble with (Assuming you can find him.) Other factors might potentially kill Linux (I could see it getting made illegal in the current legal climate) but repeats of OS/2's mistakes will not be a factor.

      --

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

    4. Re:Wasn't it obvious? by ksflock · · Score: 2, Funny
      Other factors might potentially kill Linux (I could see it getting made illegal in the
      current legal climate) but repeats of OS/2's mistakes will not be a factor.


      Would not that make every computer literate a criminal? We all got a copy, don't we? Would you trash your copy, just because the OS became illegal? Don't think so.:o)

      --
      Don't realy nead a sig..:o)
    5. Re:Wasn't it obvious? by ScottKin · · Score: 1
      Would not that make every computer literate a criminal? We all got a copy, don't we? Would you trash your copy, just because the OS became illegal? Don't think so.:o)

      Typical Linux-o-phile onanism - thinking that everyone who is "computer-literate" has a copy of Linux on their system.

      Frankly, I wouldn't trust an OS that was cobbled-together by an ad-hoc committee of hackers (read "LINUX") as far as I could spit.

      LINUX - "Linus, I Now Understand Xenophobia" (and the previous posts confirm this statement!)

      --
      I don't give a rat's behind about "karma" here or anywhere else. Don't like what I have to say here? Deal with it!
    6. Re:Wasn't it obvious? by ScottKin · · Score: 1

      1) More like "Active Bug Fixes and patches for Gaping Security Holes" - nothing like the buffer overflow bug in lpr that allows arbitrary programs to be run to ruin your day.

      2) A case of Linux-o-phile onanism - try giving RH to your Grandma so she can install it on her Tandy 2000; she'll disown you. Most 12-year-olds who play with Linux are socially-challenged geeks who get a thrill out of typing "nmake"

      3) We now see the Marketing Strategy of Linux unfolded - market penetration by subtefuge and deception.

      4) Totally dependent on the target systems hardware configuration. And the "Workplace" shell problem is one of the underlying instability issues with OS/2 (half-an-OS). Remember that OS/2 was mostly written by the biggest of the "Big Iron" computer companies, who revel in complicated systems.

      In addition, your comment about Linux becoming "illegal" is nothing but pure, assenine FUD. Making Linux "illegal" would be equal to making Crystal Radio sets illegal, or even typewriters. Good deduction there, Sherlock!

      --
      I don't give a rat's behind about "karma" here or anywhere else. Don't like what I have to say here? Deal with it!
    7. Re:Wasn't it obvious? by Genjuro+Kibagami · · Score: 1
      1) More like "Active Bug Fixes and patches for Gaping Security Holes" - nothing like the buffer overflow bug in lpr that allows arbitrary programs to be run to ruin your day.

      Not at all like an email client which autoexecutes dynamic html enclosed in email and includes a convenient propogation system over the net, or the myriad excuses for software that MS writes on top of it's already mediocre OS just brimming with holes that would make a piece of swiss cheese look stable.

      And yet simultaneously the vendor claims said holes don't exist

      2) A case of Linux-o-phile onanism - try giving RH to your Grandma so she can install it on her Tandy 2000; she'll disown you. Most 12-year-olds who play with Linux are socially-challenged geeks who get a thrill out of typing "nmake"

      Try giving your gradma MS DOS 6.22 or any offering thereafter from Microsoft to install on her Tandy 2000. Most docile bovinesque snapperheads who play with windows are intellectually challenged fuckwits who consider themselves enlightened because they can create a dial up networking connection.

      3) We now see the Marketing Strategy of Linux unfolded - market penetration by subtefuge and deception.

      Subterfuge and deception of aforementioned bovinesque vacant clusterfuck management sounds just fine by me. The strategy strikes as much more ethically acceptable than any of the ones outlined in the article used by MS in the OS/2 War.

      In addition, your comment about Linux becoming "illegal" is nothing but pure, assenine FUD. Making Linux "illegal" would be equal to making Crystal Radio sets illegal, or even typewriters. Good deduction there, Sherlock!

      I get it, it would never be done because it's stupid, and the government would never do something that was stupid!

      If you want an example of pure assinine FUD look no further than the mirror.

    8. Re:Wasn't it obvious? by Enahs · · Score: 1, Offtopic
      Typical Linux-o-phile onanism - thinking that everyone who is "computer-literate" has a copy of Linux on their system.

      More like typical humorless f**k who can't take a joke.

      Frankly, I wouldn't trust an OS that was cobbled-together by an ad-hoc committee of hackers (read "LINUX") as far as I could spit.

      Funny, I notice you've managed to post this. What do you use, a steam-powered computer with a steam-whistle calliope(sp) acting as an analog modem? Eh? Point me toward a marginally-accepted non-hacked-together OS. If you point me toward an Apple or Microsoft product, it'll be proof that their marketing departments have done their jobs.

      Don't know what I'm talking about? Remember the hype about Win95 being a total rewrite? Remember the lack of fanfare when it was discovered that wasn't true?

      As for your "humorous" LINUX acronym, I can only suppose you're a BSD zealot if you're bashing cobbled-together OSes and Linux in particular. As such you have no room to talk about xenophobia. ;-D

      --
      Stating on Slashdot that I like cheese since 1997.
    9. Re:Wasn't it obvious? by Anonymous Coward · · Score: 0

      I disagree, there was quite a bit of adds for "Warp" before it came out, as I remember these fondly back in high school.

      I also remember the first time I heard of "OS/2 2.0". Was in the local computer store where you could 'rent' it ;) A guy ahead of line with me at the store (the store was run out of a house in town), noticed me looking at it with confusion. I remember him saying "that thing can run that game you are about to rent, and several others all at the same time, its really powerfull". I honestly thought he was nuts, how could something like that exist, I mean how could an application, just stop using the memory that it was loaded into? Regretably I never 'rented' it, nor have never used it, but after reading this, I sort of feel bad that I didn't try it out. Its still around by all means, but perhaps that one extra user might have made a difference...even if it was a 'rented' edition.

    10. Re:Wasn't it obvious? by Anonymous Coward · · Score: 1, Insightful

      Classic IBM Marketing Disaster. Big National Championship game, everyone's tuning in. Put something incomprehensible like "OS/2" in the middle of the football field, and then run lots of commercials for something called "Ultimedia" with mimes dancing around.

      I imagine that Joe Sixpack was dumbfounded, it didn't sell a single copy of OS/2, but lots of fatcat IBM customers got boxseats for the game.

    11. Re:Wasn't it obvious? by Anonymous Coward · · Score: 0
      [List of reasons Linux can't possibly fail continued...]

      5) Buggy apps. Non-hacker users love to use buggy apps which crash when they do perfectly normal things, which is why so many bugs have been left in.

      6) Incomplete documentation. There is no reason to finish docs off at the end of a project. Developers don't read docs anyway, and since it is open source, they can always just read the source if they want to know what the API is and how it works. Besides, developers in a corporate environment are never under any kind of time pressure to get work finshed, so they have lots of time to read and understand source written by someone else.

      7) Non-ease of use. If it was hard to write, it should be hard to use (thanks's for that quote Brent, even though it wasn't about Linux). Therefore, there's little reason for putting in all the little helper bits like dialogs, wizards, etc. that will make software easy to use and configure by non-hacker users (who would want their kind using our OS, anyway).

      8) Backwards incompatibility. Users love sorting through version compatibiliy issues, and companies enjoy having to provide a new binary release for every new kernel, so little things like backward compatability can be overlooked.

      These are not a troll, just my observations. Of course, I suppose I could have too high of expectations for a 10+ year old OS (Linux predates NT).

    12. Re:Wasn't it obvious? by ScottKin · · Score: 1

      Do us all a favor and drop the posturing - it does nothing but show frustration at your inability to sucessfully rebut my comments.

      We're talking about present-day systems and not MS-DOS 6.22. Welcome to the 21st Century. Things *have* changed in Personal Computing since 1995. Keep it current or keep it to yourself.

      It's a common tactic of people who can't successfully argue their point to resort to 3rd-party namecalling, and attempts at denigration of the previous comments.

      Additionally - as being a member of the Windows NT DevTeam (Kernel, API & Test Group), I know the MS .vs IBM debacle all too well - care to illustrate where MS was wrong?

      Have a nice day!

      ScottKin

      --
      I don't give a rat's behind about "karma" here or anywhere else. Don't like what I have to say here? Deal with it!
    13. Re:Wasn't it obvious? by Genjuro+Kibagami · · Score: 1
      Do us all a favor and drop the posturing - it does nothing but show frustration at your inability to sucessfully rebut my comments.

      The same could, albeit more reasonably, be said of yours.

      We're talking about present-day systems and not MS-DOS 6.22. Welcome to the 21st Century. Things *have* changed in Personal Computing since 1995. Keep it current or keep it to yourself.

      This coming from a member of the NT Development team? Beautiful Irony how I love thee. Your comment makes no sense in context, either, you were commenting on how linux would not run on grandma's Tandy 2000, I was commenting on how nothing from Microsoft past MS DOS 6.22 would run on said Tandy 2000 either, so your comments on modern linux viability on outdated hardware whilst trying to justify NT viability were bunk.

      They still are.

      It's a common tactic of people who can't successfully argue their point to resort to 3rd-party namecalling, and attempts at denigration of the previous comments.

      denigrate Pronunciation Key (dn-grt) tr.v. denigrated, denigrating, denigrates To attack the character or reputation of; speak ill of; defame. To disparage; belittle: The critics have denigrated our efforts.

      You keep on using that word, I do not think it means what you think it means.

      The entire point of an argument / disagreement / productive debate is to point out how your opponent is in fact, wrong.

      As for third party name calling, I didn't call any third parties names, I called you assinine and foolish, basically. I guess I could've been construed as calling Microsoft names, but it turns out seeing as you're in the employ of said company, even they're not really a third party.

      Additionally - as being a member of the Windows NT DevTeam (Kernel, API & Test Group), I know the MS .vs IBM debacle all too well - care to illustrate where MS was wrong?

      All depends on your definition of wrong, would you care to argue that OS/2 was an inferior product to any of the windows releases at the time? Would you care to argue that MS blatantly shoving vapourware on the market was a viable and ethically acceptable tactic? (I wouldn't care to argue on the legallity of it so don't even bother to ask)

      Or are you referring to some off topic MS vs IBM chapter which has nothing to do with OS/2, this being the case in point.

      Just give up, you're not good at this

  3. Warp by flikx · · Score: 1

    First for Warp.

    I used it 'back in the day'.

    --
    One future, two choices. Oppose them or let them destroy us.
  4. Sad by Cryptopotamus · · Score: 0

    Elron Hubbard is the Way!

    --


    Humpty Dumpty was pushed.
  5. Why OS/2 failed... by Anonymous Coward · · Score: 0

    It lacked support for Beowulf clustering.

    Thank you.

  6. OS/2 Still In Use.. . by Anonymous Coward · · Score: 0

    Our companies voicemail system uses OS/2. Has not dropped a beat in the past 8 years.. .

    1. Re:OS/2 Still In Use.. . by Anonymous Coward · · Score: 0

      Ours too.

    2. 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?

    3. Re:OS/2 Still In Use.. . by zaffir · · Score: 1

      Knowing M$, you could just enter in 100 numbers for your PIN and gain access to a whole bunch of accounts at once.

      I love buffer overflows.

      --
      "Upon attaching the waterblock to my penis, I began to notice that I know nothing about computers." -- JRockway
    4. Re:OS/2 Still In Use.. . by Anonymous Coward · · Score: 1, Informative

      In the Netherlands Windows-NT is being used for ATM's.... and it shows!
      Though relatively stable, I've seen 'em crash causing the Windows-NT splash screen to be shown and rendering the ATM inoperable.

    5. Re:OS/2 Still In Use.. . by LoveShack · · Score: 1

      I've seen gas pumps that use Windows. They'll either be blue screened or at a desktop with an illegal operation up. The first time I saw it, I laughed for a good five minutes.

    6. Re:OS/2 Still In Use.. . by danielrose · · Score: 1

      Must be one of the only remaining type of ATM with NT (3.51 i think you will find)
      All the newer ATM's I've worked on (and these are all brand new out of the factory) have been OS/2.
      Never had a problem (except the machine that took 30 minutes to boot up!)
      What brand of ATM are they there?

      --
      i hate pansy republicans
    7. Re:OS/2 Still In Use.. . by red_crayon · · Score: 3, Interesting

      I too have heard this---from someone at IBM, no less.

      Interestingly, he told me that this was one of the obstacles to open-sourcing OS/2. The banks are worried about people having the source to the OS that runs their ATMs.

      --
      "Never bullshit a bullshitter" All That Jazz
    8. Re:OS/2 Still In Use.. . by mtnbkr · · Score: 1

      Not too long ago, I was traveling and stopped at a gas station to get some fuel. While I was there, they had a power outage. I got to see the ATMs reboot and flash the OS/2 screens. Kind of cool...

      Chris

    9. Re:OS/2 Still In Use.. . by Spoons · · Score: 1
      It's a little known fact that many ATM machines use OS/2

      I'll give you a big shine new nickel if you can tell me what the "M" stands for in "ATM Machine".

    10. Re:OS/2 Still In Use.. . by neurojab · · Score: 1

      I'll give you a big shine new nickel if you can tell me what the "M" stands for in "ATM Machine".

      :) It stands for Money. ATM=All The Money.

      Now excuse me while I listen to my CD discs and watch a couple flicks on my VCR recorder.

    11. Re:OS/2 Still In Use.. . by Anonymous Coward · · Score: 1, Interesting
      FYI, OS/2 is currently being used for the scheduling system at Ford's Wayne Assembly plant. They make Focus and Expeditions. The scheduling system arranges for all the parts to get to where they need to be from the time the order comes in until it goes out....both having all parts available and having conveyors bring them to the right spot at the right moment to be installed.


      But not for long...its so old maintenance is too much of a burden, so a new system is being developed.

    12. Re:OS/2 Still In Use.. . by Anonymous Coward · · Score: 0

      No matter what it stands for, you still have to enter your PIN Number.

    13. Re:OS/2 Still In Use.. . by erroneus · · Score: 2

      Well, actually, you're correct on that observtion though when I worked at an ATM company, managing an ATM network, everyone invariably assumed I was working on "ATM" technology rather than on a banking network. So, while ATM without "machine" added to it is more correct, "ATM Machine" is more correct... rather like "NIC Card."

    14. Re:OS/2 Still In Use.. . by k98sven · · Score: 1

      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?

      The ATM machines run by SparBanken in Sweden use Windows 95!!!!!!!!

      And YES, I -have- seen the machines both crash (software) and blue-screened!

      One can only hope they fired the SOBs who came up with -that- idea.

  7. FP :P by Anonymous Coward · · Score: 0

    Ask Microsoft what is behind their 2000 OS...

    1. Re:FP :P by Anonymous Coward · · Score: 0

      More VMS than anything else (e.g. Dave Cutler was primary architect for the NT kernel).

    2. Re:FP :P by Anonymous Coward · · Score: 0

      OS/2 NT

    3. Re:FP :P by mirabilos · · Score: 1

      Actually, first it was called "NT OS/2", but
      when the API got designed, the team got orders
      from high above, and they first designed the
      API for easy translation from Win32s, then showed
      it IBM who asked "could you not please include
      at least _one_ OS/2 API?"
      Then IBM left, but the concept of "Personalities"
      (Win32, POSIX and OS/2 v1) stayed.
      Then, the name changed to "Windows NT" (without
      version number these days).

      Check it out, there's a book about it from one
      of the programmers.

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
  8. OS/2 by applejacks · · Score: 1

    I thought it was ok. : opinion
    I don't think it was the greatest. The user interface was locked in. Much like NT (microsoft). So I never really cared for it.

  9. Windows 95 Killed OS/2 by kevin42 · · Score: 3, Insightful

    I'm sad to say it, but I think it's true. I was a hard core OS/2 user through OS/2 Warp (I think that was 2.1). It was very good, but when windows 95 came out and was more stable, plus had better application support, I couldn't see why I should continue using it. OS/2's windows compatibility only got worse over time.

    Don't get me wrong, I wish OS/2 took over and we were all using it instead of windows, I think we'd be far better off.

    Hopefully the linux world can learn something from that. If Microsoft ever gets the upper hand in the areas where Linux excels, it will be very bad for Linux. Not as bad as it was for OS/2 though, if for no other reason than the price of Linux.

    1. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 1, Insightful

      You mean like stability? Neither Win2k or XP have ever crashed on me? How about database or web server performance? I'm afraid once again, Win2k has run Linux into the ground on that one. Security? I find both to be atrocious, but provided the administrator is competent and patches machines within 6 months of the release of updates, I'd say there on equal ground. What DOES Linux still have going for it over MS?

    2. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      >"What DOES Linux still have going for it over MS?"

      Cost, and flexibility.

    3. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      > stability... database or web server performance... Win2k has run Linux into the ground... Security... there [sic] on equal ground...

      LOL!

      > What DOES Linux still have going for it over MS?

      It doesn't have so many trolls, for one...

      bukharin

    4. Re:Windows 95 Killed OS/2 by Mr+Windows · · Score: 2, Insightful
      How about portability, flexibility, reliability, consistency, standards-compliance, and attitude :)

      Seriously, though, GNU/Linux is still a much more standards-compliant OS (that's standards as is "open standards", not as in "the standards that we just made up") than Windows. Can you run Windows (anything) on your PowerPC? How about your ARM? Is the first thing that you see when you install Linux "convince me that you're not a thief"?

    5. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      What do architectures have to do with open standards? While we're on the topic, are you aware that there is a difference betweens "boots" and "runs"? I can assure you that the majority of platforms that Linux "runs" only merely boots (sometimes) and not much else.

    6. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      There was nothing stated in his/her original post that was false, chief. You can't troll with facts.

    7. Re:Windows 95 Killed OS/2 by Some+Dumbass... · · Score: 2

      Security? I find both to be atrocious, but provided the administrator is competent and patches machines within 6 months of the release of updates, I'd say there on equal ground.

      6 months?!?! Try 6 hours (max)!

      Pal, I think I know the security is so "atrocious" on your systems.

    8. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      The reference was to worms like Nimbda that were released 6 months after the patch was released, "Dumbass." Keep trying, though.

    9. Re:Windows 95 Killed OS/2 by Hostile17 · · Score: 2

      What DOES Linux still have going for it over MS?

      a $200 per seat price tag.

      --
      Fascism should more properly be called corporatism, since it is the merger of state and corporate power - Benito Mussoli
    10. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Trollerific!

      The unique blend of "my opinions and experiences reflect everyone else's" coupled with the classic (*BSD/Linux/etc is dying) injection, creates a post that nobody in their right mind can possibly resist replying to.

      Bravo! Excellent troll.

    11. Re:Windows 95 Killed OS/2 by edi.werner · · Score: 1

      Stability of Windows XP? On my new notebook with a preinstalled Windows XP I had about 10 bug-reports (mostly crashing IE 6) and two bluescreens within the first hour. And I was just downloading files I wanted to work with! The mandrake-8.2beta4 on the other hand hasn't crashed yet although it's used much more often.

    12. Re:Windows 95 Killed OS/2 by alexhmit01 · · Score: 2

      By Windows anything I assume you mean the DOS based Windows 4.x series (95, 98, ME)... Certainly you are discounting Windows NT 3.51 SP 5 (latest NT 3.51 SP) and Windows NT 4.0 SP 3 (latest NT 4.0 service pack to support PPC when Motorola and IBM dropped support).

      GNU/Linux can knock Microsoft off the desk's of technical shops that are fed up with Microsoft's crashing. However, the real area of contention is going to be the non-PC computers. Tivo uses Linux.

      In reality, people that have PowerPC computers aren't looking at Windows, they are looking at MacOS X. For the embedded PPC market (much bigger) Linux is a contender against QNX, WinCE, etc.

      GNU/Linux won't win by being an open standards desktop because Windows is the current de facto standard. GNU/Linux will do well in the embedded space because of price and source availability.

      Alex

    13. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      You have a hardware problem. Mandrake just didn't bang on the same bad DRAM cell that XP did.

      You need to send the notebook back while it's still under warranty, or the glitch will catch up with you sooner or later no matter what OS you run.

      Like, duh.

    14. Re:Windows 95 Killed OS/2 by sconeu · · Score: 2

      And a lack of BSA jack-booted thug audits.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    15. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Why must everybody post their pointless little anecdotal "evidence" about stability?

      I couldn't care less about your very limited experience with one machine. It doesn't matter one iota because for every story like yours, theres another from the opposite side of the fence.

      Guess what? I haven't rebooted XP on my machine since I installed my new Radeon 8500 two weeks ago (not even to install the driver for the bloddy thing).

    16. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      a $200 per seat price tag.

      and full source code

    17. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      So you're going to better the situation by posting your own anecdotal evidence of stability? Really, if you are the original poster, you haven't made anything but anecdotal claims. Give me some numbers to back it up and then you'll have a little more credibility.

    18. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      What was stated in the original post that was factually incorrect? I didn't see anything.

    19. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      That's why it was a great troll. Everyone "knows" it's wrong, but they can't really say why. That makes their replies even funnier to read.

    20. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      There wasn't anything in the parent post that was provably true either.

      So since nothing universally true nor false was stated in the post, we return to asking what the point was again?

    21. Re:Windows 95 Killed OS/2 by danielrose · · Score: 1

      Considering the cheap-ass audience, I'd guess the fact that it is cheap-to-free?

      --
      i hate pansy republicans
    22. Re:Windows 95 Killed OS/2 by saintlupus · · Score: 2

      Can you run Windows (anything) on your PowerPC?

      There was a port of NT 4.0 to the PPC. The six people who actually bought it were disappointed when the line was killed.

      How about your ARM?

      Er, don't a lot of those fancy-pants personal organizers that run WinCE use ARM processors?

      Not that I use Windows (I'm a Mac geek), but those were some pretty piss-poor examples.

      --saint

    23. Re:Windows 95 Killed OS/2 by mark_lybarger · · Score: 2

      not only is the OS free, there's a RDBMS, a web server, a jsp container, MTA's, fax servers, development tools, etc. it's not about a free OS, it's about freedom of software.

    24. Re:Windows 95 Killed OS/2 by danielrose · · Score: 1

      my software doesn't particularly need to be free (either free as in beer, or free as in "free the animals!") I don't have a problem paying ONCE for something, but when it gets to pay per month, free software may be the choice..

      --
      i hate pansy republicans
    25. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Yeah and guess what I haven't rebooted my Linux RH 7.1 machine in over 1 month and 1/2 once. The big difference here is my Linux box didn't go down to hybernate like yours does...and idiot MS'ers continue to count that on the uptime after they bring it out of hybernation....lol

    26. Re:Windows 95 Killed OS/2 by Some+Dumbass... · · Score: 2

      The reference was to worms like Nimbda that were released 6 months after the patch was released, "Dumbass." Keep trying, though.

      I hate to tell you this, but most exploits come out in less than six months. Sometimes they even come out before the patches. My point is still correct.

      P.S. "Nimda".

    27. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      What's the advantage of paying for something, when you can get the same functionality (from a business standpoint) in Linux?

    28. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Hey jackass, NT 4.0 runs on Alpha, i386, MIPS, and PowerPC. Try again, okay?

    29. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      You mean with it missing all of the functionality and the ability to ACTUALLY get work done? Yeah, I thought so.

    30. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      ... And a free grammar checker. Oh wait.

    31. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Anybody who bought the NT 4.0 CD-ROM got the port of NT 4.0 for PPC as part of the package. Along with the port to Alpha. Because it was all on the same release CD.

      And that even means OEM-sold CD's. The NT 4.0 CD that Compaq bundled with their machines (until later when 'recovery CDs' became the norm) contained the binaries for the Alpha and PPC machines too. Even back in the era when Compaq sold nothing that had a DEC Alpha inside.

      So there's no way of claiming 'the six people who actually bought it. There could be six, or 600,000 people who bought NT 4 and installed it on PPC hardware.

    32. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      The big difference is that all of these Slashdot Linux success stories are on NAT boxes with 0.0 load averages, while Windows runs all the apps. LOL!

    33. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Why are you using an old version (NT 4.0) as an example? How many architectures does XP Pro run on? One.

      Now go tell the MIS guys that they should "upgrade" to NT and replace that $BIGBUCKS server with a cluster of x86 boxes, and see what sort of response you get.

    34. Re:Windows 95 Killed OS/2 by toriver · · Score: 1
      Can you run Windows (anything) on your PowerPC? How about your ARM?

      The old NT (the one that was released as 3.51) was written for portability, and you could get it for e.g. DEC Alpha machines. At some point they seem to have abandoned that idea...

    35. Re:Windows 95 Killed OS/2 by corey_lawson · · Score: 1

      I've had win2000 crash on me, although it was probably just "protecting" me: Unplug a USB device like a USB CDROM w/o "shutting down" the device ala PCCards.

    36. Re:Windows 95 Killed OS/2 by Anonymous Coward · · Score: 0

      Win 9x in reality is a broken version of OS/2!
      Have you checked the Win 9x DDK lately, there are still references to OS/2.

    37. Re:Windows 95 Killed OS/2 by dxkelly · · Score: 1

      Hmm.. I haven't had a crash yet. Of course as soon as I turned it on I installed all the available patches.

  10. Re:first post by Daveman692 · · Score: 0, Offtopic

    Nope

  11. 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.
    1. Re:A Few Ideas... by DR_glock · · Score: 1
      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.

      On a somewhat related note, I can remember running the original Alone in the Dark on my 486/25SX in windowed mode on my OS/2 desktop way back when (a feat that you still can't accomplish to this day on a Win9x box). It ran great too, faster than a full-screen DOS session. OS/2 had a very extensive set of tweaks for running native DOS programs. Sort of reminded me of an early "wine".

      The good ol' days... ;(

    2. Re:A Few Ideas... by Locutus · · Score: 2

      WinG huh? It wasn't until IBM showed ID's Doom running in a window on OS/2 that Microsoft got off their ars and build WinG. IBM build DIVE with IDs help but something happened in the process and ID dropped out of the partnership. I think it had to do with culture clashes. Just a guess. From what I remember, there were huge groups of people around the OS/2, Doom-in-a-window demos at COMDEX.

      Gesh, OS/2 v3.0 had OpenGL support builtin too, though it never got hardware OGL support.

      There is very little, if anything, Microsoft ever did first in the computer industry. Most was just copied and they dominated by the anti-competitive leveraging of their monopoly. IMHO.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    3. Re:A Few Ideas... by dunkelfalke · · Score: 1

      i remember playing dark forces under os/2 warp with a 486 sx25 and 4 megs of ram. i couldn't play it under plain dos because the game needed eight megs and memory was really damn expencive (for me at least). so os/2 was my last hope and it worked. slow, tho, but it worked.

      i still love os/2. warp 4 had a perfect gui, still the best one. maybe i'll install warp again, on an old machine. *sigh*

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    4. Re:A Few Ideas... by chafey · · Score: 1

      I remember trying out OS/2 when it first came out. My machine had the minimum required RAM (I think it was 12 megs?) and although I could get it to boot up, it was constantly swapping and completely unuseable. I accidently started up 8-10 applications and then logged out hoping it would reset itself. Unfortunatley it rememberd the applications I had open and tried to reopen them at login. I gave up at that point and uninstalled it.

    5. Re:A Few Ideas... by adamsc · · Score: 3, Interesting

      Developer support was a big problem with OS/2, but IBM did have DIVE and DART to provide direct access to video and audio hardware. They never did anything significant with them but there *was* an API.

    6. Re:A Few Ideas... by operagost · · Score: 1
      Read manuals much? Hold down CTRL-SHIFT-ESC while the desktop is coming up. Sheesh. By the way, ever use Win95 with 4 MB RAM? That's the minimum for that OS. Wonder what it's like? Yup, it constantly swaps.

      The first release would have been 1.0, which only required 6 MB, so I think what you had was something much later.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    7. Re:A Few Ideas... by CaptnMArk · · Score: 1

      Good old days...

      I remeber playing DOOM II under OS/2 dos emulation in 4MB ram, because OS/2 had much more efficient paging algorithms than DOOM had internally (DOOM needed 8MB ram to run well).

    8. Re:A Few Ideas... by Anonymous Coward · · Score: 0

      Ahh, yes. .I had a similar machine my trusty ol sx 33, clocked at 50 Mhz, with 8mb of RAM. Remember especially playing Beneath a steel sky (DOS) while copying floppy games in the background. Fabulous multitasking in OS/2 (or so I remember at least)!

    9. Re:A Few Ideas... by DrCode · · Score: 2

      Actually OS/2 had DIVE and DART, which gave the same sort of performance you get from SDL. And Warp 3.0 ran fine on my 486 with 8Mb, certainly not an above-average machine at the time.

  12. My favorite quote. by Anonymous Coward · · Score: 0

    "the fact that a lot of Team OS/2 members were Trekkies in much the same way that most Ross Perot supporters believe in UFOs."

    I always knew there was something off about OS/2 advocates (Ross Perot supporters too, now that I think of it). I always imagined that when they weren't expounding the virtues of an OS most (read: normal) people didn't care about, that they were off sniffing gasoline and trying to run over furrey wood-land creatures. ;) -smiley included for the humour impaired.

    1. Re:My favorite quote. by flikx · · Score: 3, Funny

      Yeah, I tried to distance myself from that stuff. Same thing with the fact that I use linux today. Too many groupies and wild eyed zealot fanatics foaming at the mouth really helps denigrate an operating system.

      All through these OS fads, I've still used BSD. BSD will outlive all of this crap. Good ol' low-key BSD.. it's always been there for me.

      --
      One future, two choices. Oppose them or let them destroy us.
    2. Re:My favorite quote. by Anonymous Coward · · Score: 0

      Indeed, Warp 4 ruled my desktop, at least from ~'96 to 2000, from FixPak to FixPak (and I'd consider keeping it around today, but for the mess that patching it became; I had no cash for the final WarpUp? release, and eComStation's too expensive and ugly). Then again, I was always the type who would've rather been using an Amiga, though I won't go to *that* new OS4.x until they sort out the introduction of protected mode..

      Indeed, if something's become my new DOS- the system I use when I don't want to think about what system's on a box- BSD is it. It's been there, it will be there, and once all the libh/OS5 work is done on FreeBSD, it may as well be OS/2, but for the lack of good ol' shadows in the interface (and the option of JFS, sigh).

      For those trolling that BSD is dead, I urge them to poke the corpse of OS/2. *That* was a dead system, and yet, like Novell has for some, it worked flawlessly for me for years. Moving from OS/2 to BSD is like moving from the boonies to.. Berkeley. :)

    3. Re:My favorite quote. by james_sorenson · · Score: 1

      Darn skippy. I still have a hard time understanding how Linux became more popular than FreeBSD. BSD is so much easier to maintain, and is a lot less finicky with network protocols. Even Apple recognized this when they picked BSD as the core for Darwin (the kernel for MacOS X).

    4. Re:My favorite quote. by OpenSourcerer · · Score: 1

      >I still have a hard time understanding how Linux became more popular than FreeBSD. BSD is so much easier to maintain, and is a lot less finicky with network protocols

      what about BSD Vs GPL and how a closed unit of "great men" not letting anyone else in? May be the reason why pseudo opensource companies like apple sucks up to BSD, with its take-all-but-give-none-back-license. Sure BSD lives, some what like a cryofreezed organism in suspended animation. Before you quote apple, let'em opensource their GUI library. Then we will talk

    5. Re:My favorite quote. by subgeek · · Score: 1

      Even Apple recognized this when they picked BSD as the core for Darwin

      there is no proof that this was because of bsd or linux being worse or better. the easiest explanation is liscenses, but that's another argument entirely.

      --
      you probably shouldn't have read this.
    6. Re:My favorite quote. by mirabilos · · Score: 1

      I would have liked to use BSD, but then when OS/2
      Warp 3 came out, I was only 13 or 14 and didn't
      even really understand English.
      I got it at seventh grade, after Latin...

      - now a happy OpenBSD user,

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
  13. OS/2 Failed Because it was IBM Of Old by quakeaddict · · Score: 2, Insightful

    That is...its our way or the highway.

    Everyone took the highway.

    --
    I'm still working on a clever footer.
  14. not even close by mmusn · · Score: 2, Insightful
    It was better than anything around, yet it failed.

    Not even close. There were plenty of other operating systems and GUIs around at the time: NeXTStep, UNIX workstations and GUIs, Smalltalk-based systems, to name just a few.

    NeXTStep alone beat OS/2 technologically in just about every area. The only major OS that OS/2 was clearly better than was DOS/Windows, but that was not exactly hard to do.

    OS/2 was an attempt by IBM and Microsoft to corner the market with a proprietary operating system and proprietary APIs. It is poetic justice that the effort went down in flames as far as IBM was concerned. It is unfortunate that the effort succeeded as far as Microsoft is concerned, which apparently moved bits and pieces of OS/2 into NT.

    The lesson to be learned from this? Either be the monopolist, or go with open source and open APIs. That's why IBM is pushing Linux now and Microsoft is pushing Windows.

    1. Re:not even close by Locutus · · Score: 2

      I think NextSTEP was in another league at the time. OS/2 was still very much a DESKTOP OS while the others were either workstation or server OS's.

      I ran MicroPort UNIX on my 286 and Consensus UNIX System V on my 386 but X11 was a few years away still and the desktop hardware just wasn't quite powerfull enough at the time. Going from UNIX to OS/2 was a real pleasure. I had a very short time with DOS/Windows between UNIX and OS/2 with some NT beta's in there before running with OS/2.

      You know Microsoft originally marketed NT as the replacement for DOS/Windows until they realized it was a bloated pig and moved the marketing to say it was a "workstation" OS. In 1991, Microsoft told me to wait for Chicago for the next great desktop OS from Microsoft.

      I'm with you that the OS should be opensource. It's time.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    2. Re:not even close by rjamestaylor · · Score: 1
      And all the while the Dar Horse, NeXTSTEP, sneaks past MS (Windows) and IBM (Linux) re-incarnated and with new powers as OS X.

      I *love* OS X.

      --
      -- @rjamestaylor on Ello
    3. Re:not even close by mmusn · · Score: 2, Insightful
      That doesn't really seem very persuasive to me. As far as proprietary systems on low-end hardware go, Amiga seemed like a much better system than OS/2. And if X11 really was too much (I had no problem with it on a 386 at 20MHz), IBM could have used a UNIX kernel and developed a simple GL on top of it.

      What it comes down to is that OS/2 really was the best only if you look at operating systems that run on the PC platform and that are similar to Windows. And in that category, it really only had one competitor, which OS/2 admittedly handily beat: Windows. But I have used OS/2 and I'm not sad to see it gone: in the grand scheme of things it didn't innovate and it was proprietary.

    4. Re:not even close by Anonymous Coward · · Score: 0

      OS/2 was really a "workstation" OS also. It was too heavy to run on your Average PC until about 1995 or so, and really required you to part out your hardware with OS/2 compatibility in mind. It was also fairly expensive ($300 for the base install).

      The original idea was that it was supposed to be the replacement for DOS. However, the actual product was never marketed that way. (I see people bitching about MS and OEM contracts, but for the most part 90% of the PCs OEMs shipped wouldn't run OS/2 anyway, therefore it wasn't really an option for them.)

    5. Re:not even close by Anonymous Coward · · Score: 0

      You're comparing NeXTStep and the Unix with GUI of the day with OS/2? That is totally ludicrous - both of those had insane hardware requirements - a basic machine from NeXT was something like $10k and the PC version required 24Mb RAM just to get the system to boot plus it had essentially no support for 90% of PC hardware.

      OS/2 on the other hand was a powerful robust OS with relatively negligible hardware requirements.

  15. Marketing Failures.. by antis0c · · Score: 2, Flamebait

    I remember when OS/2 Warp 3 first came out. The Commercials were stupid. I mean, sure a lot of commercials are stupid, but at least they show the product they are peddling. IBM's OS/2 commercials just showed a bunch of guys crowded around a monitor going "Wow! I can't beleive it can do that! Wow that's amazing!" but the Camera view was from behind the monitor so you didn't see anything they were doing. Then it had some catchy IBM slogan and that was it. All the commercials I can remember were like that, and I never knew what it was. I did however buy it after seeing it at a local computer shop. I think I bought it at Walmart, all 45 Floppy Disks. It ran BBS's well. It's sad it never made it very far.. I hear banks still use it though for certain applications.

    --

    ..There's a-dooin's a-transpirin'
    1. Re:Marketing Failures.. by Nohea · · Score: 1

      One time i was at the Chase ATMs. One had crashed and failed at reboot. It was OS/2.

      I actually thought, "Wow, must be pretty good i only saw one crash screen out of thousands of visits to Chase ATMs.

    2. Re:Marketing Failures.. by Rhone · · Score: 1

      This is exactly why I never gave OS/2 a chance. The commercials just showed a bunch of computer geeks going "Wow that's so cool!" and didn't show the actual OS or even say WHY it was so cool. Stupid commercials that insult my intelligence will bias me against a product pretty quick.

  16. Windows 95 applications killed OS/2 by Anonymous Coward · · Score: 3, Insightful
    Windows 95 didn't kill OS/2, the apps did. The apps wouldn't run on OS/2, so people had to use Win95 even though it was less stable. The users needed the apps, but didn't have a stable platform to run them on until 6 years later (2001) when Windows 2000 showed up.

    How they survived those intervening 5 years is a long story, but it has a lot to do with IT people committing massive fraud and computers being horribly unreliable.

    Heh, and now that MS has a stable OS, the apps have all gone down the shitter. You just can't win. Keeps the IT folks employed, though, so you win if you're a MSCE.

    1. Re:Windows 95 applications killed OS/2 by Pathetic+Coward · · Score: 1

      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.

      Developing for Windows is corporate suicide.

    2. Re:Windows 95 applications killed OS/2 by Anonymous Coward · · Score: 0

      "What apps? Just about every commercial application on the market five years ago has been replaced by a Microsoft clone. Developing for Windows is corporate suicide."

      Lotus 1-2-3 and WordPerfect were playing catch-up to Microsoft every since GUI versions came out; the Microsoft version were not clones. Frontpage, Visio, FoxPro, Great Plains... bought out by Microsoft for tidy sums. Hardly corporate suicide. Even IE4 was technically superior to Netscape 4, hardly a "clone" anymore than any other Web Browser.

      Real DTP and graphics apps like CorelDraw, PhotoShop, Pagemaker are still around. Perhaps the people who made cheap-ass bundled-with-a-scanner photo-editing software have been replaced by Microsoft Photo Editor, but that's about it.

    3. 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.
    4. Re:Windows 95 applications killed OS/2 by clontzman · · Score: 3, Funny

      "Developing for Windows is corporate suicide."

      Compared to what? Developing for Linux? I take it you haven't checked your portfolio at finance.yahoo.com lately....

      I'd still rather be Macromedia or Adobe than any of the corporate Linux development houses, what few there are.

    5. Re:Windows 95 applications killed OS/2 by Zeinfeld · · Score: 3, Insightful
      Windows 95 didn't kill OS/2, the apps did. The apps wouldn't run on OS/2, so people had to use Win95 even though it was less stable

      Err, what apps? When Windows 3.1 came out all you got was a pretty GUI interface to start your character cell based program. Lotus, Wordperfect and co were both sitting on the fence waiting to see whose GUI O/S would win the battle.

      Ten years ago IBM was considered the big monopolist threat in both hardware and software. When OS/2 launched IBM gleefully told the world that it intended to tie the O/S to its increasingly proprietary hardware systems.

      Microsoft offered the hardware manufacturers a GUI O/S that was not controlled by a competitor. They also cut through the problem of waiting for the applications by writing their own GUI wordprocessor etc.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    6. Re:Windows 95 applications killed OS/2 by _Sprocket_ · · Score: 2

      To be fair... I wouldn't classify Macromedia or Adobe as a "Windows" development house either. Their products cover windows. And they cover other environments too (although I'd like better support for Linux, but hey).

    7. Re:Windows 95 applications killed OS/2 by snarfer · · Score: 1

      Lotus, Wordperfect and co were both sitting on the fence waiting to see whose GUI O/S would win the battle.

      This is bullsh*t. Lotus and WordPerfect were doing everything they could to get their apps working but for SOME reason the API info they were given by Microsoft just didn't seem to be right!

      Word and Excel took over the market because Microsoft illegally used their monoloply power to force their apps onto the customers. With Lotus and WordPerfect they did it by keeping many API calls secret.

      Then, for good measure, the Windows license forbade the OEMs from shipping with anythingbut Microsoft apps.

    8. Re:Windows 95 applications killed OS/2 by duren686 · · Score: 1
      Then, for good measure, the Windows license forbade the OEMs from shipping with anythingbut Microsoft apps.


      When was this? I bought a computer in 1996, and it came with Corel Wordperfect Suite 7. And it worked much more beautifully than my friend's Office 2000 some years later.
      --
      Y2K Compliant since the late 1890s
    9. Re:Windows 95 applications killed OS/2 by Zeinfeld · · Score: 2
      This is bullsh*t. Lotus and WordPerfect were doing everything they could to get their apps working but for SOME reason the API info they were given by Microsoft just didn't seem to be right!

      Who told you that porky?

      Mitch Kapor himself complained that the Lotus management failled to develop the GUI version of 123.

      At the time Microsoft was aggressively courting Lotus and Wordperfect because support for those apps might be critical in deciding whether OS/2 or Windows won. Both refused to back either camp until there was a winner.

      What they found out when they tried to catch up was that design of a GUI version of their apps turned out to be more of a drastic change than they expected. Microsoft meanwhile had been designing apps for the Mac for years and knew what was required.

      The 'Microsoft keeps the API's secret' is the favorite excuse of bad engineers.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    10. Re:Windows 95 applications killed OS/2 by Anonymous Coward · · Score: 0

      "This is bullsh*t. Lotus and WordPerfect were doing everything they could to get their apps working but for SOME reason the API info they were given by Microsoft just didn't seem to be right!"

      Wrong wrong wrong wrong.

      Lotus & Wordperfect refused to write for Windows 3.x when it came out.

      There were 2 reasons:

      1) They were still committed to IBM and OS/2

      2) More importantly, these guys never liked MS, because they understood that Windows was just a GUI. It was an environment. Microsoft not only controlled the environment, but they had competing programs.

      So these guys just didn't write for MS Win 3.0. They figured if they didn't sell apps for it, then it would fail. They were wrong, and it put both companies out of business.

      Even after they did write for Win 3.1 (which was a big improvement stability-wise), they wrote crappy programs.

      So Lotus & WP shot themselves in the foot, but it was an easy mistake to make.

      No, it wasn't the hidden API's that did these guys in.

    11. Re:Windows 95 applications killed OS/2 by fred911 · · Score: 1

      "Even after they did write for Win 3.1 (which was a big improvement stability-wise), they wrote crappy programs."

      Are you serious? One of the main reasons many used OS/2 was proper control of serial I/O and sharing of IRQ's that worked in OS/2 and never worked with Win3. I know of a number of CNC shops that used OS/2 for storage of machine code.
      If I remember correctly, up to a year ago they were all some type of serial network. It worked and worked flawlessly.

      --
      09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    12. Re:Windows 95 applications killed OS/2 by CptQuant · · Score: 1
      Compared to what? Developing for Linux? I take it you haven't checked your portfolio at finance.yahoo.com lately....

      Yeah but if you checkout finance.yahoo.com using netcraft and you'll find Yahoo running FreeBSD!

      Also, Yahoo at $11 billion is worth more than Adobe.

  17. 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.
    1. Re:IBM killed OS/2 by Anonymous Coward · · Score: 0

      .... er ... does "business brownshirt" rhyme with " webfoot weenie" ? Elitist, inbred, tribal, fsckall ... huhhh ... Too close for comfort, I'd say ---

    2. Re:IBM killed OS/2 by Anonymous Coward · · Score: 0, Funny

      What is a "PS/2"? The Playstation 2 didn't come out that long ago so I'm guessing it is something else.

    3. Re:IBM killed OS/2 by Eric+Green · · Score: 3, Informative
      The PS/2 was a computer that IBM released in, I think 1986. Compaq and a number of other companies had come out with wildly successful clones of the original IBM PC, and IBM realized that they'd given away the personal computer market. So they created a new computer bus -- the MicroChannel Bus -- incompatible with the bus in the original IBM PC (the bus that Compaq and others used). They created a new operating system -- OS/2 -- in conjunction with Microsoft, that ran only on their PS/2 (Personal System/2). Then they dropped all their "old" PC-compatible machines, and you could only buy a PS/2-compatible machine from IBM. They felt that business would buy PS/2 machines from IBM because business bought IBM, and they would not license the patents to their Microchannel bus to other personal computer vendors, so they would have control of the personal computer market once again.

      But it didn't work like IBM planned. It was an unmitigated disaster. IBM sold only a few thousand machines, and had been geared up to sell millions. 16-bit OS/2 on a 16 mhz 80286 microprocessor took a half hour to boot, and there were no expansion cards for the new 16-bit MicroChannel Bus. They swiftly rushed their old "PC-compatible" machines back into production (calling them the PS/1 and other names like that to imply that they were only half as good as their PS/2 machines), but the damage was done -- IBM was never again the #1 maker of personal computers. The PS/2 lingered on for another couple of years as IBM continued to try to push it, and was mercifully put out of its misery when the industry migrated from the 80286 (16-bit) processor to the 80386 (32-bit) processor.

      Whenever you think about the eventual fate of OS/2, you have to recall how it originated -- and what IBM was trying to do when it created OS/2 in the first place.

      -E

      --
      Send mail here if you want to reach me.
    4. Re:IBM killed OS/2 by reflective+recursion · · Score: 1

      A 286 (maybe 386 too, I'm not sure). It was an IBM model. Came with VGA monitor. It's those small footprint computers you used to see in school. Tiny, for their age. They also came with a mouse. I'm thinking the release date is something like 1986 or 87. Could be wrong, though..

      --
      Dijkstra Considered Dead
    5. Re:IBM killed OS/2 by nickynicky9doors · · Score: 2

      Wasn't IBM the business model for Bill Gates to emulate? Didn't IBM wage a battle with the DOJ and didn't IBM use every concievable ploy, including submitting a warehouse of hard documents that numbered so high as to be impossible for the DOJ to ever peruse? With OS/2 and MicroChannel Architecture IBM made a concerted effort to capture the PC market but I think they underestimated the size and the savy of the market.

      --

      heuristic algorithm seeks stochastic relationship
    6. Re:IBM killed OS/2 by weave · · Score: 2
      Pretty good, but a few points. The original PS/2 line included some models with 80386 processors in them. I'm sure there has to be a PS/2 history web site out there...

      Ah yes, a quick google search turns up this PS/2 history page

      In 1987, IBM came out with five PS/2 models, model 30 (8086), model 50 and 60 (286s) and models 70 and 80 (386s). The 60s and 80s were tower units.

      The Model 50 was a dog. Had wait states and a slow-ass (80ms) hard drive. They later came out with a model 50Z where Z meant zero wait states.

      God, we're so much better off now. Look at the prices those things were. Imagine where we can be 15 years from now if we don't destroy each other first...

    7. Re:IBM killed OS/2 by Anonymous Coward · · Score: 0

      > Whenever you think about the eventual fate of OS/2, you have to recall how it originated -- and what IBM was trying to do when it created OS/2 in the first place.

      They just weren't as good at building and maintaining a monopoly as Microsoft. Ehh, they're getting better with their Java and Linux efforts, but Lotus anything is still a proprietary pile of shit. Good God, how I hated working with Lotus in my last job, between stability problems to lame user interface to confusing administration tools to being completely proprietary to absolutely worthless technical support who often couldn't find a solution to our problems but thought it would be cool to charge us rediculous prices anyway, all because the CIO was in bed with IBM. Give me a good scripting language and a SQL database any day.

    8. Re:IBM killed OS/2 by jht · · Score: 3, Informative

      It wasn't quite as bad a disaster as that - PS/2 sold fairly well, but not well enough to kill the cloners. And there was a 386 in the line from the get-go, though ALR and Compaq had released the first 386 PC's a few months prior. The actual release of the PS/2 was in early 1987. Micro Channel was a much more advanced bus than ISA represented - mind you, this was before the whole industry coalesced around the (not yet invented) PCI bus. Feeling the pressure from IBM, the rest of the industry got together and devised EISA (extending ISA to 32-bit goodness and backwards-compatibility) - a decent Micro Channel competitor that carried the clone market for a few years in the interim before Intel pushed PCI out.

      The goal was definitely to lock up a new standard, though. At first. IBM offered to license Micro Channel, but at very high royalty rates that effectively left no room for competitiors. OS/2 started out as a vaporware project that relied heavily on Microsoft to manage big chunks of it, and ultimately became IBM's flagship OS and their "open" competition to a rising Microsoft. Windows 3.0, OTOH, started out as a way for Microsoft to hedge their bets against slow adoption of OS/2 - after the first couple of years IBM had opened up to the reality that they needed to support the cloners, too. When Windows took off and the big MS/IBM split happened, Microsoft got to keep the OS/2 3.0 project that was being planned at that point. IBM decided their future was in porting OS/2 to their new Power series chips. Which ultimately fizzled out.

      The Microsoft part of the project became Windows NT. OS/2 itself (Warp was a marketroid decision to add the codename to the product) had wonderful Win16 capabilities back in the Windows 3.x days - but Windows 95 came out conveniently after IBM's license to Windows source expired and that was the commercial death of OS/2.

      I think the last PS/2 was canned around 1995 or so, maybe a hair later. There were some good products made for the MCA bus, mostly connectivity products. It was a far better bus than ISA, but the market (and IBM) killed it easily.

      The legacy that PS/2 left us in the end was mainly the mini-DIN connectors for keyboards and mice. IBM sold a decent number, but not enough to justify a separate line of PC from the mainstream. Apple's really the only folks who have ever pulled off a different standard over the long term.

      (This is also a good argument as to why Apple should never go to Intel as chip vendor - IBM had a good alternative OS, a neat box, and a better mousetrap, but couldn't differentiate themselves enough to thrive.)

      I may be slightly off on a detail or two, but I think my recollection is fairly clear on this. Feel free to correct specifics, folks!

      --
      -- Josh Turiel
      "2. Do not eat iPod Shuffle."
    9. Re:IBM killed OS/2 by javiercero · · Score: 1

      I guess you should do your homework before trying to rewrite history:

      a) IBM Included ISA machines in the PS/2 lineup (8086 models). However they felt that MCA was a better alternative for a possible 32bit bus (it had both 32 and 16bit versions). ISA was the 16bit defacto. In fact MCA was the better 32bit bus around for PCs until PCI came out. The PS2 line was around until the mid 90's, and it included 486 and pentium models.

      b) OS was fast! 1.0 did not take longer to boot that normal MS-DOS, yet it offered multiple sessions on a single machine.

      c) OS/2 did run on non PS-2 machines. We used to have few IBM/ATs running early versions of OS/2 w/o any problem.

      d) Just like many people around here you chose to speak out of your arse rather than do some actual research on your facts. You knew nothing about the subject, but lord knows that didn't stop you from opening yer mouth.

    10. Re:IBM killed OS/2 by NutscrapeSucks · · Score: 2

      C) IBM Released a version of OS/2 called "Extended Edition" which supposedly only ran on PS/2 machines. This lead to the perception that OS/2 only ran on PS/2 period (when in fact even OS/2 EE ran on some clones).

      What was true is that IBM was very slow in promoting 3rd party compatibility for OS/2. After Microsoft ditched them, you couldn't get a Hardware Compatibility List or any such information that didn't only list IBM model numbers. The most infamous thing about OS/2 2.0 was that out-of-box it would only print to IBM-branded printers, for example.

      Also, the marketing materials continually linked OS/2 and PS/2 -- Look at the names! IBM certainly wanted you think that they were peas-in-a-pod. (Which was a PR disaster for OS/2 as people rejected MCA.) So it should be understandable that people think that OS/2 only ran on PS/2 -- that's exactly the message IBM was spreading.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    11. Re:IBM killed OS/2 by paganizer · · Score: 1

      "Everybody in the COmputer industry"?
      Huh.
      When WARP came out I had a small computer store in TN; At the time, I really thought it had a chance of blowing '95 out of the water.
      In my showroom, I set up 2 486DX-40 systems, my standard "game" models (512MB HD's, 2MB Video, 16MB ram...real screamers) on the WARP machine I had 2 windows, 1 running DOOM, and the other running a video of some sort. The other machine was running the final beta of '95. I invited EVERYONE to decide for themselves which op-sys was better. all the people who tried WARP and were honestly shopping bought it.
      I STILL think if IBM released OS/2 as open source, it would blow windows away. probably just wishful think though.

      --
      Why, yes, I AM a Pagan Libertarian.
    12. Re:IBM killed OS/2 by Anonymous Coward · · Score: 0

      "When WARP came out I had a small computer store in TN; At the time, I really thought it had a chance of blowing '95 out of the water."

      Then you were naive.

      By the time Windows 95 came out, the game was so over, they were just getting out the brooms to clean up the mess.

      Everybody in the industry at the time knew the answer to that one.

      It didn't help that the Windows 95 GUI was prettier (if not as functional) as OS/2. But the GUI on OS/2 was just freaking confusing, and I used it for 2 years. Just horrible to do things like change an icon. And they should never have put Win16 compatibility with it. It just killed it in the end.

    13. Re:IBM killed OS/2 by James+Youngman · · Score: 1
      I can't think of any lesson from the OS/2 saga that applies to Linux.

      How about: Just being technically better isn't enough.

    14. Re:IBM killed OS/2 by Geezle2 · · Score: 1

      "the Windows 95 GUI was prettier". . .What? When did that happen? It was. . .and always will be, I'll bet, lame beyond description. . .I have always gotten a kick, for an example, out of having to select the 'START" button to shut the bitch down (a feature that seems to work reliably only when when you are not pressed for time). Beauty is more than just expensive icons (not skin deep? I guess you would never hear a microserf supporting THAT idea!). For some, function is an element of beauty. "the GUI on OS/2 was just freaking confusing". . .The you most certainly DIDN'T use it for ten minutes. . .much less 2 years. . .Perhaps you occasionally had contact with OS/2 over a two year period, but I know you didn't USE it. "change an icon"? OK. . .for someone habituated with the strange rituals needed to make Windows work the idea of a 'Context Menu' (simply right-click the object?) would be completely alien. . ."Oh! that's what that other mouse button is for!" . . . In the future, don NOT admit that the OS/2 GUI confused you in front of people who might have actually used the OS. . .it sorta brands you as a dumbass that runs on autopilot. . .(WTF. . .OS/2 more confusing than WinXX? Weird!).

    15. Re:IBM killed OS/2 by Geezle2 · · Score: 1

      "the Windows 95 GUI was prettier". . .What? When did that happen? It was. . .and always will be, I'll bet, lame beyond description. . .I have always gotten a kick, for an example, out of having to select the 'START" button to shut the bitch down (a feature that seems to work reliably only when when you are not pressed for time). Beauty is more than just expensive icons (not skin deep? I guess you would never hear a microserf supporting THAT idea!). For some, function is an element of beauty.

      "the GUI on OS/2 was just freaking confusing". . .Then you most certainly DIDN'T use it for ten minutes. . .much less 2 years. . .Perhaps you occasionally had contact with OS/2 over a two year period, but I know you didn't USE it.

      "change an icon" is "just horrible"? OK. . .for someone habituated with the strange rituals needed to make Windows work the idea of a 'Context Menu' (simply right-click the object?) would be completely alien. . ."Oh! that's what that other mouse button is for!" . . .

      In the future, don NOT admit that the OS/2 GUI confused you in front of people who might have actually used the OS. . .it sorta brands you as a dumbass that runs on autopilot. . .(WTF. . .OS/2 more confusing than WinXX? Weird!).

  18. Reminds me of my old bumper sticker by 3ryon · · Score: 2, Funny

    Mind you I was an IBMer at the time:

    OS/2 on a PS/2, half an Operating System on half a Computer.

    I'm not a big fan of any operating system that doesn't have a native TCP/IP stack.

    1. Re:Reminds me of my old bumper sticker by The+Ape+With+No+Name · · Score: 2

      You must have really, really hated Win3.1/Win95A:

      THE DEVIL.....

      --
      Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
    2. Re:Reminds me of my old bumper sticker by tb3 · · Score: 2

      I was working for a major bank who bought a ton of PS/2s when they first shipped. OS/2 was still moths aways. The joke I remember was:

      PS/2 : yesterday's hardware today.

      OS/2 : yesterday's softwre tomorrow.

      --

      www.lucernesys.comHorizon: Calendar-based personal finance

    3. Re:Reminds me of my old bumper sticker by Alt-kun · · Score: 1

      I'm not a big fan of any operating system that doesn't have a native TCP/IP stack.

      This comment says a lot about OS/2's lack of success. Inaccurate rumours like this just got propagated all over the place, until people thought it was the whole truth without bothering to learn any different.

      There's no accusation here; probably you're just generalizing about the version you were exposed to. (which must have been very old). But the remark still illustrates the problem of inaccurate rumours that plagued (and continue to plague) OS/2...

      OS/2 has come shipped with built-in TCP/IP and SMB networking in every version since 3.0 Connect -- during the days that Windows 3.11 was MS's latest offering...

    4. Re:Reminds me of my old bumper sticker by Anonymous Coward · · Score: 0

      Win 95A had a native TCP/IP stack. I dropped Trumpet Winsock when I got the Win95 _preview_ in my hands.

    5. Re:Reminds me of my old bumper sticker by netsharc · · Score: 1

      Aah, Trumpet Winsock.. reminds me of the good old days of Windows 3.1, making sure the dial-up script was right and watching the program does it magic as it connected to the internet, accompanied with the sound of the modem handshaking. I wonder how that company is doing, after all I thought Windows 95 put them out of business.

      --
      What time is it/will be over there? Check with my iPhone app!
    6. Re:Reminds me of my old bumper sticker by Locutus · · Score: 2

      I had OS/2 machines running v2.1 with TCP/IP, X11, and Netware. We paid around $200 for the TCP/IP and PMX Server but on 10MB of memory it was a kick arse desktop compared to Dos/Windows.

      Our UNIX guys couldn't believe a PC could do what OS/2 did. Heck, Texas Instruments had a multi-DSP design board that used OS/2's multi-tasking to debug in realtime the DSP board. Again, the techies were loven what OS/2 could do. The catch was that the department manager had a system we just could not get OS/2 installed on. I forget what it was but since he could not run it on his desktop it didn't make to onto more than a dozen systems.

      It's still a pretty awesome OS. IMHO.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    7. Re:Reminds me of my old bumper sticker by Anonymous Coward · · Score: 0
      Here here, in addition OS/2's GUI was absolutely kick ass. Waaaay ahead of its time. So much so in fact that many people still think it was "too hard to use". It did stuff back in the OS/2 2.0 days that Windows XP and KDE 3/GNOME 3 still haven't even started thinking about yet.


      Back in 92, we used to write programs using the OO features of the presentation manager to do stuff like implement "ftp folders" where you could drag and drop files from remote sites to local folders and vice versa, all in a few lines of REXX. In OS/2, unlike pretty much every other gui before and since, everything was an object that you could inherit from and override to do with what you wanted. It was fantastic, and it was all accessible with REXX and with a lot of good documentation.

    8. Re:Reminds me of my old bumper sticker by K-Man · · Score: 2

      Yes, I fondly remember the 2.x TCP/IP installation. I paid a few hundred for it back when the equivalent Windows setup was something like $500. Then I got paid $30 an hour to get the latter working on some computer at PG&E, a task which took weeks.. I think I ended up bringing in my OS/2 stuff to show them how it should work, with X and everything.

      The cool part was that OS/2 never messed up the classic /etc setup files. It would actually create an etc directory to hold everything: resolv, hosts, services, you name it. I was actually surprised when I got to linux and found how "nonstandard" its config files were.

      Later on when the browser and TCP/IP were bundled with the OS, they built a graphical configuration notebook, which gave access to all the stuff that was in the /etc files. I was expecting the worst, like a Windows registry or something, but I could go in and edit a bunch of stuff, close the notebook, and find everything copied into the etc files same as ever.

      --
      ---- "If we have to go on with these damned quantum jumps, then I'm sorry that I ever got involved" - Erwin Schrodinger
    9. Re:Reminds me of my old bumper sticker by Anonymous Coward · · Score: 0

      Windows For Workgroups shipped with TCP/IP support. No PPP dialer tho for you home users.

    10. Re:Reminds me of my old bumper sticker by Anonymous Coward · · Score: 0

      Functionally the OS/2 GUI was Kick Ass. Visually it was Looks Like Ass.

      Whoever drew those icons should be rounded up and shot. Also who was the genius that thought that a 5-level deep folder structure was a good way to find your programs? Final thought: Drives Object, the only file manager ever that made you want to run WINFILE.EXE

    11. Re:Reminds me of my old bumper sticker by Anonymous Coward · · Score: 0

      "I paid a few hundred for it back when the equivalent Windows setup was something like $500. "

      I recall paying $300 per machine for OS/2 TCP/IP while our NT 3.5 and WfW machines came with TCP/IP included. Trumpet was more like $50, so I have no idea what you were buying.

    12. Re:Reminds me of my old bumper sticker by K-Man · · Score: 2

      If you were buying NT then it was after that time. There was a period when the only TCP/IP setups for Windows were third-party.

      --
      ---- "If we have to go on with these damned quantum jumps, then I'm sorry that I ever got involved" - Erwin Schrodinger
  19. Don't blame Microsoft by Anonymous Coward · · Score: 0

    IBM dumped OS/2 itself, and not Microsoft. Moreover to that, IBM's devotion to OS/2 could have been seen as a competitor to its Unix line. So if IBM was about to fully support OS/2, that could have been considered as killing the Unix line. So I believe that IBM did the right thing. IBM killed OS/2 not Microsoft...

    1. Re:Don't blame Microsoft by foonf · · Score: 2
      Moreover to that, IBM's devotion to OS/2 could have been seen as a competitor to its Unix line. So if IBM was about to fully support OS/2, that could have been considered as killing the Unix line.


      Absurd. IBM actually talked for some time about porting OS/2 to the PowerPC (as discussed in that article), but it never happened. Mainly because they explicitly didn't want to sell cheap PowerPC machines that would compete with their own RS/6000s, but rather they wanted someone else (Apple, who never actually did) to adopt their PReP standard and sell the hardware for them. This is also why there was briefly a PowerPC port of Windows NT. As it was though, you could never actually run OS/2 and AIX on the same hardware, so they weren't exactly competitive (also IIRC, AIX was supposed to be ported to their microkernel also).
      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    2. Re:Don't blame Microsoft by Anonymous Coward · · Score: 0
      IBM actually talked for some time about porting OS/2 to the PowerPC (as discussed in that article), but it never happened.


      This is incorrect. What IBM talked about for the longest time was an operating system called "Workplace OS". The idea was to have a single microkernel core, and multiple "personalities" to give the OS the look and feel of various other OS's. They wanted this for a number of reasons, most prominently was the idea that they could replace all their operating system code bases (OS/2, VM/CMS, AIX, etc) with a single code base that supported all of them. Theoretically this was a very very good idea that would have reduced development and support costs, but it took so long to do even the basic OS/2 version of WPOS that they simply killed the project because it cost way too much money to develop. Since this took up all the development effort post-Warp, the old intel version of OS/2 sat around getting bug fixes and nothing else while every other operating system on the market made huge strides forward.


      I actually sat in front of WPOS-OS/2 running on a PREP PowerPC box and tried it for a few minutes. It crashed quick, but it looked and felt pretty much the same as OS/2 on Intel.

    3. Re:Don't blame Microsoft by Anonymous Coward · · Score: 0

      1) They didn't just talk about OS/2-PPC, they wrote it, it was late and it sucked, so they didn't release it. (Something to do with OS/2 IPC not playing well with the Mach kernel they used.)

      2) IBM did very badly want to sell cheap PowerPC machines running OS/2 or NT in order to steal marketshare from Intel and recapture the lead in the PC business. They spent billions in the effort to do so. It failed when nobody bought the things. (FWIW, those "PowerPersonal" machines also ran AIX.)

  20. OS/2 Warp Seti Team by Phosphor3k · · Score: 1

    There is a OS/2 Warp Seti team that is in the top 40 of all teams.

    In fact, they are number 29.

    Take a look at the top 200 teams here: http://www.statsman.org/setistats/html/

    1. Re:OS/2 Warp Seti Team by Anonymous Coward · · Score: 0

      yeah? so? there are loads of Amiga Lusers on there too - SFW?

    2. Re:OS/2 Warp Seti Team by Anonymous Coward · · Score: 0

      You have some taco snot on your lip.

  21. Pain in the ass for HW guys by Waffle+Iron · · Score: 2
    I was in PC hardware design when OS/2 betas were first circulating (IIRC, it was originally called DOS 5 or something similar). This was the first time that PC memory > 640K got a real workout (random access outside of a 64K peephole). Back then, extended memory often was kludged on with things like piggy-back expansion boards.

    Of course, many machines in the field promptly croaked when the new OS stressed their extended memory for the first time. Our work ground to a halt for weeks as we tracked down flaky RAM-related problems.

    Chasing those types of ghosts was never any fun: Hook a logic analyzer to the memory bus, let it run overnight, find out that the impedance of the logic analyzer probes suppressed the bug, start again from square 1.

    I'm guessing that memory interface designers today use better engineering practices than we did back then.

  22. OS/2 v.s Windows by garett_spencley · · Score: 3, Insightful

    I always hear people saying how they loved OS/2 and think everyone would be better off if it had "won" instead of windows.

    However, I believe that it would be no different. It would still be open source v.s the big giant. The big giant would just be IBM instead of Microsoft. Don't forget they too are a huge gigantic corporation with no interest except profit just like MS.

    Everyone would instead say "geez I miss windows. I wish it had won on the desktop instead of OS/2. Sure the application support wasn't as good. And OS/2 compatibility in win9x got a lot worse over time but it was still a far better OS IMO."

    Think about it.

    --
    Garett

    1. Re:OS/2 v.s Windows by Anonymous Coward · · Score: 0

      I think you're right on the fact that there would be still a monopoly on the x86 OS market. But would people say "Windows was better" ? I don't think so.
      As someone else pointed out in an earlier post, technologicaly, OS/2 was better, to the point that some of it's code was used for NT (which eventually evolved to XP - so in a way, OS/2 is still used by a lot of people, altough they don't know it, but that is another topic).

      I think regrets would have been more about "NeXTSTEP" or other exotic (please excuse-me) Systems.

    2. 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.
    3. Re:OS/2 v.s Windows by Locutus · · Score: 2

      Good point. I really hoped that OpenDOC would have taken off too. I used HP's NewWave way back when and a data-centric system is the best. IMHO.

      I see KDE is picking up some of this with KParts and I hope it really takes off. Just like Linux is far more stable as a component-based OS, applications will be far better when components do specific tasks. Think about it, why do we need a spell checker in every application? It's wasteful.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    4. Re:OS/2 v.s Windows by Anonymous Coward · · Score: 0

      Exactly. OS/2 may have been just the same monopoly-OS, but at least we would have had a 32 bit true multitasking operating system 10 years before Microsoft "programmers" (really marketing flaks who took night classes to learn C) got off their fat asses and threw NT together (mostly by copying the OS/2 source code and replacing "OS/2" with "NT" almost everywhere).

    5. Re:OS/2 v.s Windows by Anonymous Coward · · Score: 0

      However, I believe that it would be no different. It would still be open source v.s the big giant. The big giant would just be IBM instead of Microsoft. Don't forget they too are a huge gigantic corporation with no interest except profit just like MS.

      If you think the gentle buttsex that the PC industry has recieved at the hands of Gates has been bad, you can't even imagine the brutal buttraping that IBM's salesmen had planned for you.

      IBM represents a stangant culture of compliant customers that willing suck down $500 price tags for text editors and TCP/IP stacks and pay for their computing jobs per cycle. OS/2 was their attempt to push that repugent monopoly culture into personal computing space and control your petty computing problems from end-to-fucking-end.

      Meanwhile the worst thing that's been said about MS is that they give shit away for free. They're moneygrubbing basterds, sure, but at least they have their eyes on growing the business and pushing out new technology, where IBM has been nothing more than a glorified Fortune 500 shakedown artist.

      Sometimes worse really is better.

    6. Re:OS/2 v.s Windows by Bnonn · · Score: 1

      I think you're right. And really, which would you rather have: a company with a manopoly on software, or a company with a manopoly on hardware and software? I think that if IBM had come out on top things might even be much worse than they are now; with their software manopoly they could possibly have done some nasty things to the entire PC market.

    7. Re:OS/2 v.s Windows by Anonymous Coward · · Score: 0

      Mod this guy up.

      He's hit the nail on the head. He's clearly a guy who lived through IBM and understands what they were before they become he kinder, gentler, "We love Linux" hippies we've got today.

      They're still a hidebound culture under the skin, its just that they're better at hiding it these days.

      You kids think you're so insightful, but you can't even see a bucket of shit being poured over your head.

    8. Re:OS/2 v.s Windows by CaptnMArk · · Score: 1

      >If OS/2 had won, then GNOME and KDE would be
      >copying a good GUI instead of copying a piece of >shit.

      100% correct!

    9. Re:OS/2 v.s Windows by SCHecklerX · · Score: 2

      Where are my moderator points when I really need them? Somebody mod the parent up, please!!!!

  23. My experience of OS/2 by shoor · · Score: 2, Interesting

    I was working for a small software house when version 1.0 (I think that was the version) came out and I was given the job of porting some of our products to it. I was pretty impressed. It was the first time I think I ever programmed with threads, etc. and I got our product working pretty well. Then the next version came out and everything I'd done was broken. I couldn't even figure out a way to fix some of the critical things that needed to be done in the new version which seemed to have a completely different philosophy. I heard stories about a team in England having rewritten it, don't know if any of that is true. But my boss swore off Os/2 forever after that.

    --
    In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
  24. Windows Combatability killed it by brodiedreamyou.ca · · Score: 2, Insightful

    The author of the article seems to think that windows compatablity played a part in the death os os/2.

    He argues that because programmers could make just one version that one run on both os's, they didnt bother marketing an os/2 only version, which would have be optimized for the os/2 platform.

    I hope this isn't going to happen with wine/linux. Its quite obvious that windows programs will never quite work perfect in wine, and I hope developers dont use wine as an excuse to not bother developing linux applications.

    1. Re:Windows Combatability killed it by Anonymous Coward · · Score: 0

      As a guy who ran OS/2 from 2.0's release until Win2k came out, I can tell you firmly that you've got it backwards. Developers will develop for an installed OS base. If you have compatibility, people can try the "different" OS, and keep it. If it's truly "better", it can "become" the standard. If you lack compatibility, fencesitters will never try the "different" OS, or won't stick with it, so the install base remains small. OS/2 failed to ever develop a really decent install base. Linux in fact has this exact problem, but the evangelists won't see it. You NEED Win32 compatibility. Hell, I need Win32 apps. Linux doesn't run them. That's why I don't run Linux. I have dozens of applets that simply don't exist on Linux. Yes, I COULD get by without them (did I mention I stuck with OS/2 until Feb. 2000?) But here's the big question: why the hell would I want to?

    2. Re:Windows Combatability killed it by foonf · · Score: 2
      I hope this isn't going to happen with wine/linux. Its quite obvious that windows programs will never quite work perfect in wine, and I hope developers dont use wine as an excuse to not bother developing linux applications.


      Lindows aside, I don't think we have to worry about this. You could literally just pop in the installation disks for most (non-MS) 16-bit windows software and install it and run it under OS/2. Wine is considerably more, err, byzantine. And plus it doesn't work very reliably for the software (well, Word, IE and Outlook) that most people want to use, and it seems like the developers are more interested in using the code for proprietary emulation for running specific programs (games, plugins) or porting (corel stuff, etc.) than producing a general, Free, universal windows emulator.
      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    3. Re:Windows Combatability killed it by The+Pi-Guy · · Score: 1

      Windows Combatability killed it

      No kidding. Whichever way you meant it, that Windows was combatting it, or that it wasn't compatible with Windows, it was true.

      --joshua

    4. Re:Windows Combatability killed it by Anonymous Coward · · Score: 0

      He argues that because programmers could make just one version that one run on both os's, they didnt bother marketing an os/2 only version, which would have be optimized for the os/2 platform.

      A couple points -- Windows compatiblity was added to OS/2 before Windows got very popular. It wasn't done after the fact like Wine.

      There's lots of other good explainations for the lack of apps on OS/2. For example, they would only give you the SDK if you kissed the right ring and paid them lots of money. The OS also never had more than about 5% marketshare.

      Second, anyone in doubt about the value of WinOS2, shoud ask themselves how long OS/2 would have lasted without Windows compatiblity. It was used by 99% of the userbase.

      Third, the major reason for Linux's success is compatibility with UNIX. It's only recently that devs have started with "Linux" specific stuff and not targetting your generic Unix system.

    5. Re:Windows Combatability killed it by Spoing · · Score: 2
      Lindows aside, I don't think we have to worry about this. You could literally just pop in the installation disks for most (non-MS) 16-bit windows software and install it and run it under OS/2. Wine is considerably more, err, byzantine.

      OS/2's Windows support was hokey. By the time Windows programs were really taking off, they were for Win32s (Win95-style, not Win3x). Those programs worked poorly at best under OS/2 if they worked at all. Good Win32s support was always promised just around the corner, and it never came.

      Many of those same programs now work -- and install -- under Wine with much better sucess.

      And plus it doesn't work very reliably for the software (well, Word, IE and Outlook) that most people want to use, and it seems like the developers are more interested in using the code for proprietary emulation for running specific programs (games, plugins) or porting (corel stuff, etc.) than producing a general, Free, universal windows emulator.

      Wine is not emulation. Here's what the FAQ-o-Matic says;

      1. [Wine] calls native libraries...not an emulated environment.

        1. WINE stands for Wine Is Not an Emulator. It implements native code to the function calls present in the Windows DLL's. An emulator is something that duplicates the environment that an application runs in. WINE doesn't bother.

      1. ...a common emulator for Linux would be VMware -- a commercial Intel-based hardware emulator to run any Intel OS inside a virtual computer. This requires a real copy of the OS (ie, Windows) and a fast computer, of course; and the program itself can cost more than Windows. WINE is significantly faster than a real emulator with less overhead, currently at the cost of stability and ease of use. (But it's free too.)

      As for your other points, no current versions of Word, IE, or Outlook work under OS/2, yet old versions do work under Wine and current versions should be there shortly; remember Lindows MS Office support is based on Wine. Track the progress on the Wine mailing lists and on appdb.codeweavers.com. Some non-Lindows Wine screen shots are available here; wine.godmonkey.com.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    6. Re:Windows Combatability killed it by foonf · · Score: 2
      WINE stands for Wine Is Not an Emulator. It implements native code to the function calls present in the Windows DLL's. An emulator is something that duplicates the environment that an application runs in. WINE doesn't bother.


      I'm well aware of what their acronym means and their arguments therein. But what does emulate actually mean: 1. To imitate the function of (another system), as by modifications to hardware or software that allow the imitating system to accept the same data, execute the same programs, and achieve the same results as the imitated system. Now, what does WINE do? Is it windows? Clearly not. So windows is "another system". What is its goal? Clearly it puports to "achieve the same results as another system". I don't see any qualifiers in the definition requiring emulation to involve the original [windows] binaries or a virtual machine environment. It doesn't [i]need[/i] to emulate hardware because it is already running on x86-compatible PCs.

      OS/2's Windows support was hokey. By the time Windows programs were really taking off, they were for Win32s (Win95-style, not Win3x). Those programs worked poorly at best under OS/2 if they worked at all.


      Thats not the point. If you take a Windows program from the time OS/2 2.0 was released, it works totally transparently. Obviously a big part of that was the access to the Windows 3.0 source code, which nobody working on WINE or anything else has for current versions of Windows. I cannot simply take a windows binary of any kind and run it under x86 unix without any configuration. You have to install wine and grapple with it, and if you are lucky it will work.

      As for your other points, no current versions of Word, IE, or Outlook work under OS/2


      No kidding, they postdate any serious work on the Win-OS2 code by many years. But if you take any program with comparable ubiquity from the early nineties, it will work with the level of transparency I've described (and I wouldn't necessarily count Microsoft's office software as ubiquitous at this time...they really took over the world in that department about the time that OS/2 was being destroyed.).

      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
    7. Re:Windows Combatability killed it by Eccles · · Score: 1

      I hope this isn't going to happen with wine/linux. Its quite obvious that windows programs will never quite work perfect in wine, and I hope developers dont use wine as an excuse to not bother developing linux applications.

      If developers are going to develop for Linux, it'll be because it's cost-effective to do so. A version that doesn't work loses customers and costs more in tech support, so they'll make sure it works if they're going to sell it.

      If you're talking open-source, Windows-only open source stuff seems pretty darned rare.

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    8. Re:Windows Combatability killed it by Spoing · · Score: 2

      While I disagree on Wine's status as an API layer, and how good the Windows wrapper was under OS/2...well, let's just say we disagree. :)

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  25. I don't get it. by blang · · Score: 3, Interesting

    From the article:

    Microsoft found it all but impossible to develop a useful multitasking operating system for the 286. This was not Microsoft's fault -- the design of the chip simply wouldn't allow much useful to be done with it.


    What exactly in the in the 286 architecture prevents the use of a multitasking operating system? I seem to remember MS once touted Xenix, and there were also other Unixen out there. There were multitasking versions of CPM before the 286. Is the article writer missing something, or am I missing something. You don't need to have built in multiple instruction pipelines in the proceessor to multitask. It is almost trivial to write that into an operating system. Remember Andrew Tannenbaum's Minix that came on floppies included in his book "Operating Systems"?.

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

    --
    -- Another senseless waste of fine bytes.
    1. Re:I don't get it. by Kymermosst · · Score: 2

      In fact, you can implement preemtive multitasking on any CPU that has a way of generating regular interrupts. Even old Apple IIcs and gs's can do it. Just because nobody did it, does not mean it's impossible.

      Granted that the '386 has features that make multitasking a LOT easier.

      --
      "Alcohol, Tobacco, Firearms, and Explosives" should be a convenience store, not a government agency.
    2. Re:I don't get it. by Anonymous Coward · · Score: 2, Informative

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

      The lack of memory protection. The x86 line didn't have an MMU that could be configured to protect apps from each other until the 386.

    3. Re:I don't get it. by Tony+Hoyle · · Score: 2

      The biggest problem with the 286 was once you entered protected mode, you couldn't get out again... no DOS compatibility. So MS' problem wasn't that you couldn't multitask but that their operating system was so heavily dependent on DOS there was no way they could do it. This was agruably Microsofts fault, but it's more the fault of history.

    4. Re:I don't get it. by dashjosh · · Score: 1

      you can implement preemtive multitasking on any CPU that has a way of generating regular interrupts

      Memory Protection is nice too. Especially when all existing applications(DOS programs) assumed they could write to any memory location they pleased.

      The 286 had a protected mode but programs had to be rewritten to run in it. The 386 made multitasking feasible because each legacy DOS app thought it had complete control over the processor.

    5. 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
    6. Re:I don't get it. by OzTech · · Score: 0, Flamebait

      I really get annoyed when I hear people continually sprouting the Microsoft line that they discoverd how to clutch start the 286 processor to get back to real mode. What most Lemmings forget is that Novell had been doing this for years with their Non-Dedicated version of Advanced Netware 2.0

      Let's get it clear, like many other great technological breakthroughs which Microsoft make claim to, they simply copied it from someone else who wasn't into all the self-promotion. This sort of thing happens so often in this industry, and it is really annoying.

    7. Re:I don't get it. by steveha · · Score: 3, Interesting

      I didn't say Microsoft discovered this trick; I said they used this trick in OS/2.

      And I couldn't forget that Novell had done it first, since I never knew Novell had done it in the first place. I would thank you for the information, but your abrasive tone makes me feel somewhat less grateful. Don't you feel good knowing you made my day a little less cheerful?

      Pardon me--I have to go jump off a cliff into the ocean now.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    8. Re:I don't get it. by Kymermosst · · Score: 2

      True... it's very nice to keep rogue processes away from other areas of memory.

      The virtual 86 mode of the 386+ CPUs is quite interesting, and useful for things like dosemu!

      --
      "Alcohol, Tobacco, Firearms, and Explosives" should be a convenience store, not a government agency.
    9. Re:I don't get it. by OzTech · · Score: 0

      The abrasive tone wasn't meant Steve. Although no matter how I read your original post, the inference is that Microsoft discovered it. Probably much like, no matter how you read my post, it sounds hash :)

    10. Re:I don't get it. by steveha · · Score: 2

      I'm curious to know why Novell was using this trick, anyway. Why did they need to be able to run real-mode code on a Netware server? I would have thought they could just recompile all their server software for protect mode. Were there plug-in modules for Netware, with which they needed to preserve binary compatibility?

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    11. Re:I don't get it. by Anonymous Coward · · Score: 0

      One of the sales points of early versions of Novell was that you didn't need a dedicated server. You could load up the NetWare stuff and then type some command and have a 1MB real mode DOS enviornment to work with. That saved you the cost of an extra machine. (That feature was still there in NetWare 4.1, the last version I ever touched.)

      There was also a NetWare server that ran in the penalty box under OS/2 2.x. Saw a few people using that so that they could combine NetWare with some comm gateway or whatever.

    12. Re:I don't get it. by Anonymous Coward · · Score: 0

      I used Microport SystemV/AT on a '286. Why would I want to multitask old DOS apps? uP SV/AT was reliable (after patching), secure, and it worked. That's more than can be said for Windows 3.1 and its successors.

  26. Two Things that annoyed me about OS/2 by zairius · · Score: 1

    Needed your A Drive to be 3 1/2. Granted that didn't stop me, but it turned off some people who didn't have the inclination to jack around with their hardware. No stable Gravis Ultrasound Support. Yeah someone had written a driver but it was still flakey as hell. Wave Table synthesis smashed the hell out of FM synthesis and I wasn't going to play my games in FM anymore.

    Supreme Bunny Overlord Zairius

    1. Re:Two Things that annoyed me about OS/2 by Anonymous Coward · · Score: 0

      you got that right!

    2. Re:Two Things that annoyed me about OS/2 by foonf · · Score: 2
      No stable Gravis Ultrasound Support. Yeah someone had written a driver but it was still flakey as hell. Wave Table synthesis smashed the hell out of FM synthesis and I wasn't going to play my games in FM anymore.


      Thats true of linux too. The only driver that supported all of its features does not compile against modern kernels or with modern compilers.

      With modern versions of Linux (and windows also, actually) there's no Synthesizer support at all.
      --

      "(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
  27. 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 Sloppy · · Score: 2

      Actually, it was (gasp) MICROSOFT (gasp).

      Yeah, and it's just just coincidence that OS/2 didn't actually become a decent product with a good UI, until the early 90s... after the Microsoft/IBM breakup. Coincidence, I tell ya! :-)

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:Did you know who wrote OS/2??? by lseltzer · · Score: 1

      The UI, Presentation Manager, and the GPI, were always IBM code. MS contempt for PM & GPI was one of the early reasons for friction between the companies.

    3. Re:Did you know who wrote OS/2??? by Locutus · · Score: 2

      A Microserf wrote the HPFS filesystem too. Windows NT v3.1 and 4.0 apps ran faster on the HPFS filesystem than they did on HPFS. I found this out running the Watcom compiler on a dualboot system when doing a proof-of-concept port of an OS/2 app to NT 4.0. Now why didn't they support HPFS in NT? Could it be that it had SOMETHING to do with OS/2?

      I wonder why they called the hpfs driver PINBALL.SYS????

      Microsoft will do anything to keep it's monopoly. Look at how they spread the browser all over the OS and even into the installation process. Brilliant I say, brilliant. NOT.

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    4. 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.

    5. 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.
    6. Re:Did you know who wrote OS/2??? by BakaMark · · Score: 1
      Now why didn't they support HPFS in NT?

      There was a Legacy HPFS Driver for Windows NT 3.1, and probably 3.50 and 3.51 as well. Just as there is a Legacy FAT16 Driver.

      Microsoft dropped the support for the HPFS file system when Windows NT hit version 4.0

      The purpose of supplying the driver in the first place was to give people a chance to read the HPFS file systems from OS/2 systems on NT boxes.

      Why the support was dropped is debatable. Either Micorosft said that there was not enough market, or IBM said or did something.

      I have heard of major corporates continuing to use OS/2 past the point where IBM dropped it completely, because the OS would only run the Apps that they were supposed to, and the users would have trouble loading games onto the systems.

    7. Re:Did you know who wrote OS/2??? by Anonymous Coward · · Score: 0

      The NT 3.x docs indicated that HPFS support was for migration (of Microsoft or IBM OS/2 boxes) only and that you should CONVERT to NTFS.

      Of course HPFS was faster -- It had no ACLs for example.

    8. Re:Did you know who wrote OS/2??? by Florian+Weimer · · Score: 2

      In addition, before the big IBM/Microsoft quarrel, the system now known as Windows NT was expected to be released as OS/2 3.0---with about the same architecture as NT, but of course featuring a Presentation Manager GUI and an OS/2 subsystem.

      Until NT 4.0, Microsoft still could switch to a PM GUI rather easily (and there was even a PM 1.x subsystem, complementing the OS/2 1.x subsystem).

    9. Re:Did you know who wrote OS/2??? by markhahn · · Score: 1

      this is revisionism. for instance, the PM interface was specified by IBM - as a gratuitously different version of existing interfaces. the code was most definitely done by Msft, though (I was there).

      basically, IBM committee-designed OS/2 into oblivion, and Msft simply gave up on it, since they had two routes around: windows on the low-end, and NT OS/2 (yep) on the high end. discarding ia32 in favor of risc chips and microkernels was pretty fashionable at the time.

  28. microsoft ibm contract by Anonymous Coward · · Score: 0

    It's my understanding that Microsoft and IBM had a technology sharing agreement/contract. And they had agreed that Windows would be developed as an os for the home while OS/2 would be developed for business. Then MS decided to develop Win 95. They didn't want os/2 to be win 95 compatible (they would have had to let it be according to their contract with IBM), so they delayed it until the contract ran out.

    So, if Linux just doesn't sign a contract with Microsoft...:-)

  29. Lessons to learn by Bozovision · · Score: 1

    I used OS/2 for some time. I wrote software for it and on it and did systems integration with it. I am agnostic abou platform.

    1. Spending a bucket load of money doesn't mean that you will gain users. It's a network econmony dummy - it has to be safe for users to test and migrate before they can migrate.

    2. Don't make an OS with some really good features but forget the fundamentals that have shaped computing... the file system sounded great in concept, but proved to be difficult because it used different paradigms from the ones that users were used to.

    3. It matters how things look. It matters a *lot*. Windows 95 and later just looked much better.

    4. It matters that the applications that you are used to work flawlessly (and with no work on the part of the user) on the new OS. Otherwise people won't transition.

    5. Speed matters. OS/2 sometimes felt slow slow slow. I used a dual boot machine. Windows at the time felt faster.

    6. Don't sell the OS as something that doesn't crash when it does.

    7. Support a huge range of hardware. It makes it difficult to switch if you have to buy new hardware. By contrast Windows pretty much worked on most hardware.

    1. Re:Lessons to learn by Anonymous Coward · · Score: 0
      It matters how things look. It matters a *lot*. Windows 95 and later just looked much better.

      Hey, some of us like the look of a dog's ass! Even with my "Dog's Ass" wallpaper for Windows ME, I have been unable to reclaim that special feeling of dog's ass that OS/2 gave me. The thing is, when you used OS/2, you not only saw the dog's ass in every aspect of the GUI, but the experience was so rich that you could actually smell the dog's ass, and even taste the dog's ass, if you so desired. Windows may be able to give me superficial dog's ass visual suggestions, but when you used OS/2, you became one with the dog's ass. It was magic.

      So I find it very offensive that you think people chose Windows 95 because it looked "better." No. Windows 95 just looked less like dog's ass, that's all, and it seems that most people enjoyed that. But the hardcore of the of dog's ass community continue to tout OS/2 as the ultimate GUI experience.

  30. OS/2 by Anonymous Coward · · Score: 0

    I liked OS/2 a lot better than Windows 95, but there wasn't much software out for it. It was a beautiful operating system though.

    Deepak

  31. lesson learned - use GPL by argoff · · Score: 3

    seriously, it is a siple fact that with propriatary technologies - the best one always fails. The whole IT industry is built on the corpses of technologies that were better, but failed because propriatary forces kept them from reaching their maximum potential. think RISC vs CISC, intel vs motorolla, mac gui software vs mirosoft gui software, Amiga vs x86, tcp/ip vs token-ring, novell vs ms networks, etc... We shouldn't be sorry they failed, it is our own fault for beliving that it's ok to gain value by legally restricting the ability of others to copy through crack-pot licensing instead of trying to gain competitive advantages by service and speed of development.

    1. Re:lesson learned - use GPL by Anonymous Coward · · Score: 0

      Amiga vs x86? Eh?

    2. Re:lesson learned - use GPL by demaria · · Score: 1

      > tcp/ip vs token-ring

      I think you mean ethernet vs token-ring

    3. Re:lesson learned - use GPL by danielrose · · Score: 1

      It didn't fail. IBM still sells OS/2 for the princely sum of $284.00 USD.
      Nobody buys it you say?
      Then how do Diebold use it on their old, and new ATM's? Because they buy copies of it. From IBM. (although they do get a discount of some sort, my guess is) They make a lot of ATM's, worldwide.
      GPL something that still makes them money? What a good idea..

      --
      i hate pansy republicans
    4. Re:lesson learned - use GPL by Anonymous Coward · · Score: 0

      Not that token-ring is particularly good, as the cabling standards and error tollerance aren't as good as ethernet. And ethernet has been extended againt and again to continue to be faster and more robust (do you remember when ATM was supposed to be the end-all of networking? Ethernet evolved and ATM didn't really do anything).

  32. You can appreciate how sad the state of OS/2 is by Anonymous Coward · · Score: 0

    when you realize that even the trolls do not bother writing "OS/2 is dying" anymore.

  33. 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?
    1. Re:Brings back memories... by Locutus · · Score: 2

      I remember loading the wrong file on Photoshop for Windows 3.x and not being able to stop it for something like 15 minutes. No multitasking and no multithreading, just the hourglass. At least with OS/2, I could have killed that WinOS2 session. Multi-threaded apps are FANTASTIC but it took Microsoft about 7 years to finally get that working in desktop Windows.

      I also thought I read somewhere about a graphics developer porting their app to OS/2 and Microsoft telling them to kill it because it ran better on OS/2 than it did on Windows 3.x. It was killed and the Windows 95 app came out something like 3 years later.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    2. Re:Brings back memories... by Anonymous Coward · · Score: 0

      I remember putting a floppy into my Apple ][ and when I tried to load a file, it just sat there. Just like Windows 3.1

      Boy, that Apple sure sucks huh?

    3. Re:Brings back memories... by smilinggoat · · Score: 1

      waves of color would wash over the screen. Kind of pretty in a psychodelic way.

      wow, that must've been where they got the idea for the old OS/2 cable commercials with the swirling pyschedelic patterns. if only Windows had a prettier crash screen, they could've used it for marketing.

      "Where do you want to go today? Windows has encountered a fatal error" *note pulsing techno music and fast paced visuals*

    4. Re:Brings back memories... by Anonymous Coward · · Score: 0

      I actually used the OS/2 version of PageMaker for some time back when it was released. I may still have a copy of it somewhere. It was FAR faster and more responsive than the Windows (3.x) (or was it Win 2.x) version was. Same version number of the app in either case). Both were still 16 bit apps at the time. I did have a few problems with printing, although I believe that was more likely related to bad print drivers than the product itself. That was obviously an issue with an app whose purpose was printing.

      From what I recall, the OS/2 version was very multi-threaded and that was supposed to be the primary reason behind the improvement in performance.

      I also saw somewhere at the time that they sold very few copies of it after spending a bundle on development. That's obviously not a good thing for going forward with a product...

  34. Failed? by brandonsr · · Score: 1

    To say it failed is a bit harsh. From what I remember it was successful in some circles for quite a while. It had it's use in the early 90's, but it's long gone now. I'll miss it. :)

  35. man it was cool by BurpingWeezer · · Score: 1

    I remember when I moved from DesqView to OS/2 for my BBS. Things were so much faster. Multi node BBS on the same box that could barely handle 2 lines. I was so happy that it could do things like share IRQs for the COM ports. The UI sucked but it ran windows apps, and supported DOS apps, AND had a great scripting language. For my needs it was way ahead of the rest of the pack. In fact based on 2.1 I went out and bought Warp, even got Warp 4 for crying out loud. It was good for serving but as a client OS sucked ass.

  36. Other lessons - grass roots marketing by os2fan · · Score: 3, Insightful
    The Linuxers do well to learn from the experiences of the OS/2 and Amiga grass roots campaigns.

    Like Linux, many OS/2 users chose and stuck with their OS because they wanted, and because they changed.

    OS/2 users often multibooted, and were quite familiar with Windows systems. Often far better than the Windows users themselves. :) This is in part because fixing the problems up in OS/2 often required a bit of poking around, and this habit passed onto fixing Windows systems.

    What we do not really need is this "death threat" thing when advocates turned nasty.

    OS/2 trives even now, not because of IBM or Microsoft, but, like Linux, because of the users themselves. It aims at a different market to Linux, but both have vigourous grass roots. No monopolist likes that :).

    --
    OS/2 - because choice is a terrible thing to waste.
  37. OS/2 Microsoft by Veteran · · Score: 2

    OS/2 was by far the best work that Microsoft ever did.

    There was a wonderful quote from the head of the marketing team for Windows 95 who said words to the effect that " If you asked anyone at Microsoft they could have told you that OS/2 was a far superior operating system to Windows 95 - our job was to keep anyone else from discovering that."

    The Microsoft marketing team did a great job and foisted off on the public the worst operating system ever on any computer.

    By the way - if you doubt that W95 is the worst OS ever - here is a simple test: name an OS that was less stable - less secure - and more virus prone that W9x. There isn't one. Like I said; W95 is the worst operating system ever put on a computer.

    -- I think that Microsoft supporters ought to be known as 'Renfields'. They have similar motivations, and like Dracula's servant they are on an "all the bugs you can eat" diet. --

    1. Re:OS/2 Microsoft by Anonymous Coward · · Score: 0

      Win95 sucks indeed, but IMHO was nowhere near as bad as Macintosh System 7.5.2 to 7.5.5. I used to get "Error 11" (total crash) at least 4 times a day. It was finally fixed starting with 7.6 but by then the damage was done.

    2. Re:OS/2 Microsoft by cqnn · · Score: 2

      Windows for Workgroups, or Windows 3.x.

      Whatever you might think of it, W9x was far
      ahead of those older versions. More stable,
      at least as secure, and only more virus prone
      as a "virtue" of extending new technology over
      the old DOS/Windows design.

      For something that you consider the worst OS,
      it would install on my system of that time when
      OS/2 would not. I don't praise W9x for that,
      nor do I hold it against OS/2; in neither case
      were we shown examples of comprehensive OS design.

    3. Re:OS/2 Microsoft by smash · · Score: 2, Funny
      By the way - if you doubt that W95 is the worst OS ever - here is a simple test: name an OS that was less stable - less secure - and more virus prone that W9x. There isn't one. Like I said; W95 is the worst operating system ever put on a computer.

      I think its called Windows 98/ME (with the included Internet Explorer which enables the internet to explore your computer, and the e-mail client that will help you mirror your personal documents over the world (ala sircam). or something)

      smash.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    4. Re:OS/2 Microsoft by Anonymous Coward · · Score: 0

      Like I said; W95 is the worst operating system ever put on a computer.

      Except for the fact that it was compatible with the most devices and the most software programs. It supported DOS drivers for obscure hardware back to about 1984 or so. It loaded proprietary network protocols drivers designed for Windows 3. It ran 99.5% of DOS business apps.

      I don't think anyone at MS believed that Win95 was superior to Windows NT (1993) or OS/2. Just that even with their great marketing powers they knew there was only so much breakage that the customerbase would withstand. Unlike IBM, they were arrogant enough to push an entirely different OS (NT) down their customers throats just yet. Already tried it with OS/2 and failed.

    5. Re:OS/2 Microsoft by Anonymous Coward · · Score: 0

      "here is a simple test: name an OS that was less stable - less secure - and more virus prone that W9x"

      youve obviously never used macOS 7.5x i dont think ive ever seen a case of it running for more than a couple minutes without a fatal crash of some sort. & it seemed to come with viruses preinstalled. & it could only multitask in a theoretical sense, sure you could RUN 2 programs, but you only get to use 1 of them. and only until it crashes.

      os 7.5x did more for the PC world than anyone couldve asked.

  38. Java.... by burtonator · · Score: 2

    Unfortunately... I think the fate of OS/2 might just befall Java.

    1. Re:Java.... by droleary · · Score: 2

      Unfortunately... I think the fate of OS/2 might just befall Java.

      I think you misspelled "fortunately" . . .

  39. another little known fact. by www.sorehands.com · · Score: 3, Interesting
    Many cash registers run OS/2 version 1.0.


    When I was at the MIS center for Designs by Levi, I saw them configuring OS/2 1.0 text mode for one of the cash registers.


    While on a contract job in 2000 for a cash register company, some of their cash registers still run under OS/2. And, they run their central control systems under OS/2.

    1. Re:another little known fact. by crivens · · Score: 1

      The TD Canada Trust bank uses OS/2. The people in the bank log on to the TD Canada Trust servers through some kind of terminal app, and everything is then text based. It looks scary to use!

      I remember the Natwest bank in England used NT, and the one time I actually sat down with someone do some personal banking there, they couldn't use the computer system, as the they couldn't log onto the server.

    2. Re:another little known fact. by Anonymous Coward · · Score: 1, Interesting

      About 5 years ago, I witnessed a voicemail system that was running Microsoft OS/2 1.3.

      Apparently there was still some secret phone number you could call at Microsoft and order the software (licences only, not media), even though it was off the pricesheet. IBM would only sell OS/2 2.0 and up, according to the tech.

      I'd be curious if Microsoft still offers this service now that NT Embedded or whatever has shipped.

    3. Re:another little known fact. by Anonymous Coward · · Score: 1, Interesting

      I would guess that since Windows NT has an OS/2 version 1 subsystem built into NT (that runs directly on the NT kernel, alongside the Win16, Win32, and Posix API layers), that they would push users toward running NT instead. And users who wanted a 'pure OS/2' environment could do just that, and not install any GUI Win32 apps, and probably get away with using it just fine.

    4. Re:another little known fact. by Anonymous Coward · · Score: 0

      Natwest were good for NT a few years back. At one point, they switched to NT on their ATM's. They switched back to their old (Possibly OS/2 but probably custom job) system after only a few months. During those few months, I saw the NT Logon screen, the NT BSOD, the NT Access Violation...everything. Trying to find a working cash machine at any given time came to be a problem.

      As far as I know, no other banks decided to switch to NT after that. Odd. ;)

  40. Not exaclty timely... by nigelthellama · · Score: 1

    This article is from Sept. 1997. More than 4 years old. Not that it isn't important....but it's not exactly timely.

  41. OS2 failed for the same reason MacOS failed. by HanzoSan · · Score: 2

    Theres only one reason why OS2 failed, it failed because Microsoft had an illegal monopoly, exclusive OEM contracts never gave OS2 a chance.

    When I wanted to buy my first computer i tried to get OS2 warp, i even wanted mac. However to get OS2 warp I'd have to spend an extra $200, to get mac I'd have to spend an extra $1000.

    Because Windows came with the PC itself, to buy or use anything else would be a waste of money, after all windows works, and it comes with the machine so why use anything else?

    Face it, you could have had OSX out back when Windows95 was around and Windows95 would still have won because people never even had the OPTION to choose what OS came with their system, it was Windows95 or Windows95.

    This is why Windows95 won.

    I'm sick of people saying MacOS did this wrong and OS2 did that wrong.

    No, thats not it, Its Microsoft had exclusive contracts and backroom deals.

    Period, thats all it came down to.

    OS2 can be better, it doesnt matter if no machines came with OS2, even IBMs own machines didnt come with OS2!!!

    --
    If you use Linux, please help development of Autopac
    1. Re:OS2 failed for the same reason MacOS failed. by bcrowell · · Score: 2
      The comparison with MacOS is interesting, but the title of your post asks us to swallow a pretty big assertion: that MacOS failed. Is 5% market share your definition of "failure?" So far 5% seems to be a big enough pot of money to allow Apple to survive, and not just survive but innovate. MacOS X was pretty pathetic at first, but 10.1.3 is really pretty darn good, aside from poor peripheral support and a couple of bundled apps that are dogs.

      But it does seem to be true that nobody can carve away a big slice of MS's desktop market, due to its use of its monopoly leverage.

      It is interesting to compare the story about OS/2's difficult installation procedure with Linux's installation mess. But MacOS is extremely easy to install -- always has been -- but that hasn't meant that the whole desktop market flocked to it, even in the days when the OS didn't come preinstalled on the hard disk. And anyway, Linux is a different critter, since it's open source. The same rules don't apply.

      to get mac I'd have to spend an extra $1000.
      This is a silly myth. Macs have always been about the same price as a Windows box with similar features. It's just that people compare a mac with 24-bit color against a PC with 8-bit color; a mac with a good OS against a PC with an OS that's 10 years behind it in evolutionary terms; a mac with built-in sound input and output versus a PC with no sound card; etc.

    2. Re:OS2 failed for the same reason MacOS failed. by Alan+Partridge · · Score: 2

      Hanzosan's point is actually pretty well made. I personally feel that Mac OS9 is about 5 years ahead in terms of usability than anything else, but HOW does Apple sell it's OS? The truth is that it DOESN'T, it just comes pre-installed on the top 5% most glamourous computers on the market. An dpeople are ALWAYS gonna buy nice 'puters. Apple's REAL competitor isn't Microsoft, it's Sony - or anyone else who manages to design and build FABULOUS hardware. What's nicer? A VAIO running XP or a TiBook running OSX? TiBook right? WHY? Man, that's the most beautiful laptop EVER. If Ferrari's ran on a different type of fuel, we'd STILL want them.

      --
      That was classic intercourse!
    3. Re:OS2 failed for the same reason MacOS failed. by Anonymous Coward · · Score: 0

      While it might be true that some people buy Macs for the hardware (sexy workstation-class hardware in the 80s, sexy cases now), most Mac users I know buy Macs for one reason and one reason alone -- the OS and the associated software features.

    4. Re:OS2 failed for the same reason MacOS failed. by Anonymous Coward · · Score: 0

      ill still take win95 over OSX, but hell, id take OS/2 or win3.11 over OSX

      you can keep your candyland gui

    5. Re:OS2 failed for the same reason MacOS failed. by Anonymous Coward · · Score: 0

      "If Ferrari's ran on a different type of fuel, we'd STILL want them."

      and the rest of us would still think you were fools.

    6. Re:OS2 failed for the same reason MacOS failed. by Anonymous Coward · · Score: 0

      "Here's to the crazy ones..."

  42. Perception by Anonymous Coward · · Score: 0

    It's only a matter of perception.

    Let's forget about OS'es for now, and talk about people.

    Notice how sometimes very good people give very bad impression and other people won't give them their due? It can be at any level: professional or personal.

    Most of the time, it is those people's fault. They don't care about how others perceive them.

    Now back to OS'es. Microsoft has always been careful, before it became a monopoly, with its customer's. They'd give them what they wanted. Sure stability was not there, but people wanted ease of use + tons of fun ways of using your computer. Add to that the fact that its basis was the cheap PC and you've got a winner. Microsoft made it easy for developers to join its bandwagon. This is why you now have bazillions of apps for the Windows platform.

    Of course, as soon as you become a monopoly, the temptation is huge to say &*^* off to anyone who steps on you or competes with you.

    We can all bitch about Microsoft practices. In the end, a good initial (though maybe wrong) perception made the difference.

    The question for Linux, but really more for Linux companies is: How do you present yourself to give that good first impression of care, competence and professionalism?

  43. Win95 didnt kill OS2, Microsoft did. by HanzoSan · · Score: 3, Insightful

    If IBM had the exclusive OEM contracts, then Windows95 would have been destroyed.

    Why do people always ignore the illegal practices of Microsoft? IE is on top because it came with Windows.
    Windows is on top because it comes with every PC.

    Its IMPOSSIBLE to compete with a product which comes with the OS itself, and its IMPOSSIBLE to compete with a product which comes with the PC itself.

    A user is not going to spend money on something they already have. Thats why OS2 didnt sell, why buy OS2 when you already have Windows?

    Now, if Linux can manage to get OEM contracts, Linux can actually compete.

    Apple couldnt / cant get OEM contracts so they sell their own Machines, Linux may have to sell their own box's to be successful, Sun did it, SGI did it, Apple does it, Linux may have to do this if they cant get OEM contracts.

    The key is OEM contracts, thats the key.

    --
    If you use Linux, please help development of Autopac
    1. Re:Win95 didnt kill OS2, Microsoft did. by stubear · · Score: 3, Informative

      exclusive EM contracts aren't illegal until you're ruled a monopoly. When Microsoft established these contracts they were not a monopoly. Sure, over time they became one because of the exclusive contracts.

      Dell tried to sell Linux workstations. Their endeavors failed and they dropped the program altogether. They still sell servers with Linux preinstalled but that's it.

      Sun is failing as a hardware/os/software company due to Linux. SGI isn't in much better shape though they have one of the most lucrative industries in the world clammoring for their machines - Hollywood. Apple is doing well though they are having a tough time climbing out of their niche market. Be, well, be was, and won;t be anymore.

    2. 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
    3. Re:Win95 didnt kill OS2, Microsoft did. by Locutus · · Score: 3, Insightful

      Not a monopoly in 1994? You are right that the courts didn't RULE they were one but they did sign a consent decree in 1994 with the DOJ. The Justice overseeing the case looked it over and refused to sign it because it didn't do enough to stop Microsofts strong-arming tactics. Judge Sporkin was removed from the case and Judge Jackson was handed the case and told to sign it. He did.

      Judge Jackon is the same Judge Jackson who got the latest case and was he pissed to see what Microsoft did with the first decree.

      Not a monopoly? With billions in cash there seems to be no law you are accountable to. Or so it seems.

      Did you know that USAG Ashcroft received more money from Microsoft than from Enron?

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    4. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      Sun is failing as a hardware/os/software company due to Linux. SGI isn't in much better shape though they have one of the most lucrative industries in the world clammoring for their machines - Hollywood. Apple is doing well though they are having a tough time climbing out of their niche market. Be, well, be was, and won;t be anymore.

      You Intel weenies always crack me up.

    5. Re:Win95 didnt kill OS2, Microsoft did. by Arandir · · Score: 2

      what they did to make Windows 95 apps NOT run under OS/2 was anti-competitive and illegal.

      You mean upgrading a 16 bit API to a 32 bit API is now illegal?

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    6. Re:Win95 didnt kill OS2, Microsoft did. by gregorio · · Score: 1

      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.

      On a 32-bit platform that doesn't make any sense at all. If IBM wanted to run Windows 95 applications on their OS, they should have built an OS that can map 4GB of address space.

    7. Re:Win95 didnt kill OS2, Microsoft did. by snarfer · · Score: 1

      You mean upgrading a 16 bit API to a 32 bit API is now illegal?

      It would be helpful if people who posted had SOME idea of what they were talking about.

      What Microsoft did was keep many API calls secret. So programs like WordPerfect and Lotus 123 wouldn't work.

    8. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      This is not only wrong, but stupid. This kind of crap comes right out of an old Team OS/2 handbook.

      MS did have some minor hidden API's on Win16, but these weren't a major problem. Companies like Symantec and a host of other had no problems.

      The big problem was the Lotus and Wordperfect didn't want Microsoft to control the desktop. They thought that by withholding their apps, Windows would fail. They were wrong.

      You should have seen Wordperfect's first program for Windows. They refused to use Windows drivers for printers *they actually wrote their own*." Everything about the program was completely non-standard GUI wise.

      And how about Lotus? I bought their first version of 1-2-3 for Windows 3.x. It took literally 2 minutes to load on a 386 with 4M of RAM. Hell, the whole DOS/Win3.1 boot didn't take that long.

      These companies just SCREWED UP. Don't blame MS for their mistakes.

    9. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      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.

      And that IBM had full rights to Windows 3.1 and no rights to Windows 95.

      How'd IBM get Microsoft to hand over Windows 3 anyway? You could spin it as the tactics of an "anti-competitive monopoly".

    10. Re:Win95 didnt kill OS2, Microsoft did. by operagost · · Score: 1

      It could, the original poster was wrong. It's individual processes that are only allowed to address 512 MB. This limitation was extended in Warp Server SMP to 3 GB, and removed entirely in Warp Server for e-business and the latest OS/2 client called EComStation.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    11. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      Most of the important Democrat members of congress received more money from Microsoft than from Enron, too.

      That isn't to make the mistake of thinking that Democrats didn't receive a LOT of contributions from Enron. They got quite a bit.

    12. Re:Win95 didnt kill OS2, Microsoft did. by sheldon · · Score: 2

      I'm curious, but why exactly do you feel you have to stoop to lies to try to make a point?

    13. Re:Win95 didnt kill OS2, Microsoft did. by Locutus · · Score: 2

      From what I hear, IBM was a very bad monopoly and might have been just as bad as Microsoft. We'll never know because the choice was not given to us. You had to be a techie or REALLY want to install OS/2 in order to run it.

      How IBM got the source to Win16 but still had to pay Microsoft for every copy of WinOS2 sold in OS/2. I heard that many times from IBM people. I'm sure it was negotiated when Microsoft and IBM broke up their partnership. IBM monopolies had nothing to do with it since they had none.

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    14. Re:Win95 didnt kill OS2, Microsoft did. by Locutus · · Score: 2

      why didn't you state where you think I'm incorrect?

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    15. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      In the Microsoft Anti-Trust trial, an IBM executive testified under oath that they were licencing Windows 3.11 for $11 per copy, significantly below what competitors such as Dell and Compaq were paying. And that was without an exclusivity agreement (IBM was shipping OS/2 in dualboot configs at the time.)

      Presumably that $11 covers the difference between Windows 3.0 (which IBM owned, per the divorce agreement) and 3.11. Anyway, you can write off the siginificant price difference between the OS/2 Red Box and Blue Box to price discrimination against corporate customers, because it was much greater than $11 (more like $200, I recall).

    16. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      Ok - I really don't get this - how can Microsoft stop a program from running by keeping APIs secret? I could understand it if you were saying that Microsoft changed APIs, but what you're saying just doesn't make any sense.

    17. Re:Win95 didnt kill OS2, Microsoft did. by NeMon'ess · · Score: 1
      I coulda sworn even Windows 98 first and perhaps second edition can't address more than 768MB of RAM. What are you refering to when you talk about 1GB of memory?

    18. Re:Win95 didnt kill OS2, Microsoft did. by sql*kitten · · Score: 1, Flamebait

      Why do people always ignore the illegal practices of Microsoft?

      Probably for the same reason that they exaggerate these so-called illegal practices. When Microsoft signed the OEM contracts they weren't illegal. That's the funny thing about anti-trust law, it's retroactive: things that are perfectly legal for you to do if you're not a "trust" become illegal at the point at which you become one. But no-one knows for sure if you are or not until a court decides it. Hence the current situation.

      Its IMPOSSIBLE to compete with a product which comes with the OS itself, and its IMPOSSIBLE to compete with a product which comes with the PC itself.

      That's simply not true, and I challenge you to prove it. Why is WinAmp so popular when Windows Media Player can play MP3s? Why is Acrobat popular when WordViewer is free? Why is ICQ popular when MSN Messenger is bundled?

      A user is not going to spend money on something they already have. Thats why OS2 didnt sell, why buy OS2 when you already have Windows?

      See above.

      Now, if Linux can manage to get OEM contracts, Linux can actually compete.

      You clearly don't know what the OEM contracts were. The terms are, if a hardware vendor ships Windows on every PC, then they pay a vastly discounted license fee for each one. If they don't, then they need to pay MS full retail price for every one that they do ship with Windows on. How does Linux fit into this?

      Besides, didn't you just say that OEM contracts were illegal? Make up your mind!

      Apple couldnt / cant get OEM contracts so they sell their own Machines

      Apple don't even want OEM contracts, they are a hardware company, and use their OS as a loss-leader to sell hardware.

      Linux may have to do this if they cant get OEM contracts.

      By Linux I presume you mean VA Linux? Because Linux isn't an corporation or even an organization. And they tried selling their own kit... see any of a dozen other stories for how that went.

      The key is OEM contracts, thats the key.

      Do you even know what OEM means?

    19. Re:Win95 didnt kill OS2, Microsoft did. by j_w_d · · Score: 1

      From what I hear, IBM was a very bad monopoly and might have been just as bad as Microsoft. We'll never know because the choice was not given to us. You had to be a techie or REALLY want to install OS/2 in order to run it.

      Pure baloney. OS/2 was difficult to install because it is a powerful OS backed by a lot of code to enable things like multitasking. Installing linux was a techie job. Installing OS/2 was just tedious (24 floppies worth of tedium).

      How IBM got the source to Win16 but still had to pay Microsoft for every copy of WinOS2 sold in OS/2. I heard that many times from IBM people. I'm sure it was negotiated when Microsoft and IBM broke up their partnership. IBM monopolies had nothing to do with it since they had none.

      IBM had contractual rights to Windows 16 bit code. They helped pay for its development, since portions were originally destined for NT. When the rift happened, IBM went a head with OS/2 while MS went with the development of NT. But!!! If you examined the file names for the early NT OS, up through 3.51 I believe, many of the files and libraries had "OS2" in their names, since they were legacy from before IBM and MS went their separate ways. IBM had been investigated for monopoly pratices in the '80s and was extremely cautious about its competitive practices, since it did not want federal regulators tramping around Armonk. Win95 did not kill OS/2, IBM did.

      --
      ------ The only greater hazard to your liberty than n politicians is n+1 politicians.
    20. Re:Win95 didnt kill OS2, Microsoft did. by BlueBlade · · Score: 1
      Just a few comments about this line...

      That's simply not true, and I challenge you to prove it. Why is WinAmp so popular when Windows Media Player can play MP3s? Why is Acrobat popular when WordViewer is free? Why is ICQ popular when MSN Messenger is bundled?

      The reason that these programs are still popular today is rather simple : they came first. Winamp was an mp3 player long before Media Player was one, and it has 10% the memory footprint. The acrobat format is popular because it is portable and will print the same on any platform. Without this, it simply wouldn't exist. There is no WordViewer for UNIX or even Macs to my knowledge (you have to buy the full word). And for ICQ it's once again the came first thing. If 90% of your friends had been using ICQ for two years when MSN came out, well if you chose to use MSN you were simply left out. Between you and me, ICQ is probably one of the buggiest popular program floating around the 'net today. Totally shitty. But before it, there wasn't anything else, so it stuck. Notice that it's definitely losing ground to other IM clients. Especially MSN. Because it comes with IE, which comes with windows.

      --
      Religion is the best example of mass psychosis
    21. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      Netscape came first too. Give them time they get around to killing each and every one of the apps you listed.

    22. Re:Win95 didnt kill OS2, Microsoft did. by Anonymous Coward · · Score: 0

      It is not illegal to sign an OEM contract; it is however illegal to use the power that that contract gave you to extort an industry. Say fining a vendor if they install any other system but windows. In you comment you go so far as to site how Microsoft fines vendors if they ship machines without windows. You cannot do this if you do not own a monopoly, people would laugh you out of there office. However, with a monopoly, MS can say OK you get no windows therefore you are out of business, this means the vendors had to bow to any contract MS put in their face, that is illegal!! We therefore get back to OEM contracts not being illegal; the abuse that Microsoft did to vendors was illegal after those contracts gave them their monopoly. There is nothing being sighted retroactively about OEM contracts though you can bet future contracts will be modified to eliminate Microsoft from being able to extort the vendors again.

      Make no mistake Microsoft are bad people with Napoleonic complexes.

    23. Re:Win95 didnt kill OS2, Microsoft did. by Arandir · · Score: 2

      Having used OS/2 at that time, Microsoft did not change their API, they extended it in order to make their system, finally, a vague sort-of 32 bit OS. The Win16 API was no problem at all to OS/2. The Win32s API was only a slight problem. But the Win32 API wasn't available for OS/2.

      Even if the API's were open, it still wouldn't have made that big of a difference. You still couldn't run a 32bit Windows 95 program in a 32bit OS/2 virtual machine. At least not until VMWare came along.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  44. CP/M by Anonymous Coward · · Score: 0

    Had IBM chosen CP/M instead of PC-DOS (later MS-DOS) as their OS for the PC, the computing public may not have known Windows, and they would have become used to operating system names with slashes in them.

    Lesson learned... hopefully.

  45. A thousand cuts by Derek+S · · Score: 1

    OS/2 2.0 marked the first time I actually got excited about an operating system. I had worked with Macs in high school, but could never justify the high cost. I also worked on Unix workstations at Cal, but as a non-CS major I found them to be lacking in usefulness for most of my computing tasks (flashback to writing an English paper with jove). OS/2 offered a bit of everything: a flexible GUI, a decent multithreading kernel, and DOS/Windows compatibility. I joined the cult in the spring of '92 and was immediately hooked.

    Some problems were apparent immediately. The Workplace Shell had some really cool ideas, but it was pretty rough around the edges when 2.0 came out. Also, I could only afford 8MB RAM at the time, so I was constantly swapping to disk. I had done a little Windows 3.x programming, so the advantages of the OS/2 32-bit API were really obvious. Unfortunately, nobody bothered to write any software to it.

    Then there was the problem that most of the divisions of IBM itself were standing in the way of OS/2 deployment. And Microsoft was just starting to get the hang of its most predatory marketing tactics. During the '93-'95 period, they were masterful at manipulating the press into touting "Cairo" and "Chicago", while shrouding the already available OS/2 Warp with an SEP field. I remember when MS put out a whitepaper explaining that nobody actually needed preemptive multitasking and 32-bit addressing. A couple of years later they had the media giving them credit for inventing those capabilities (scene from one of the home shopping channels: "Preemptive multitasking...only with Windows 95!").

    In the meantime, Microsoft kept gradually improving their products until Windows was just good enough for the people using it (though with the preloads, it hardly mattered). OS/2 fell behind in the feature race, and never got out of the gate in application and driver support. Once PC games started coming out exclusively for Windows instead of DOS, OS/2 was completely eliminated from the consumer market. By '98, it couldn't claim any real advantages over NT except possibly a cleaner API.

    So now I'm mostly platform-agnostic, but I do try to support Linux and BSD where I can. The free Unix systems have the advantage of not being burdened by old-school IBM marketing, but I still fear that the free software community could make some of the same mistakes that sank OS/2. Open source licensing will keep free platforms from ever being completely lost, but they can fall behind to the point where they become largely irrelevant.

    Here's hoping that things go a little differently this time.

  46. You all act like people purchased Windows?! by HanzoSan · · Score: 3, Redundant



    No one went to a store and saw a box with OS2 on one side, and a box with Windows on the other.

    No, you went to buy a PC and Windows was on it, you had NO OPTION to buy OS2 at all.

    You had no option to buy BeOS.

    The only way to compete with Windows is from your own platform, because Microsoft has a monopoly on OEM contracts.

    How can any OS no matter how good it ever becomes, compete with an inferior OS thats packed in on every machine?

    Face it, if a person buys a computer and it works, theres no reason to ever buy a new OS.

    Sales of Windows95-98-2000 werent from people going to stores and buyingg boxes or the upgrades, most of the sales came from people buying PCs which came with Windows included.

    Perhaps there should be a law, no more OEM contracts period.

    Then let the user actually choose their OS, I guarentee that Windows95 wouldnt have beaten OS2.

    I didnt want Windows95 when i got a computer, I thought OS2 was cooler in every way, but when I got a computer, it already had Windows95, there was no reason to get OS2 because Windows95 worked.

    --
    If you use Linux, please help development of Autopac
    1. Re:You all act like people purchased Windows?! by Arandir · · Score: 3, Insightful

      How weird. I've had four computers in my life and none of them came with Windows.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:You all act like people purchased Windows?! by jallen02 · · Score: 1

      By and large consumer systems are shipped with Windows and your average consumer ends up with Windows installed. It is getting better, you can even have a Dell server shipped without an OS.

      Does not mean that it is does not happen because someone on /. did not encounter it. Purely anecdotal evidence :-)

      (None of my computers ever came with windows either)

      Jeremy

    3. Re:You all act like people purchased Windows?! by Anonymous Coward · · Score: 0

      I'm fairly certain he was inferring that he buys Apple instead.

    4. Re:You all act like people purchased Windows?! by Anonymous Coward · · Score: 0

      Whatever.

      Apple zealotry is so 1996 these days.

      I have had machines with no Windows on them, because there was never a Windows port to CP/M. Those machines had Microsoft Basic on the, though.

    5. Re:You all act like people purchased Windows?! by Arandir · · Score: 2

      Nope. Never owned on Apple. My computers have been an 8086, Pentium I, AMD K6-2, and AMD Athlon.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    6. Re:You all act like people purchased Windows?! by aarondyck · · Score: 1

      You know, in my experience Windows never worked. I have only ever bought one new PC with an OS installed, the system I currently own. It came with Windows ME and it crashes on average once every three hours. I've counted. That doesn't sound like a working OS. The worst part is that I can't even install Linux. The installers don't seem to want to work for me. (This is probably a problem on my end, though...I'm no Linux expert. My certs are all for Windows.) Regardless, when an OS can't run for more than three hours without a crash I see that as a problem. I've installed OS/2 on some of my other systems and it rarely crashed. I've also had Linux on a few of my systems and I don't recall it ever crashing on me. Windows seems to be prone to crashes and as a result I don't like to use it. It's most definitely not a working OS, every version of Windows that has masqueraded as an OS has been so buggy as to be unusable.

    7. Re:You all act like people purchased Windows?! by ChodaBoy · · Score: 1

      Yes, I remember when OS/2 came out I was working for a retailer that carried IBM's new (then) Aptiva line which recently replaced the PS/1's and 2's. We had asked the IBM rep who was visiting all the retailers (anyone remember Team OS/2?)if any of the Aptivas would be preinstalled with OS/2 and his answer was no.

      As much as they were touting OS/2 as the windows killer, they apparently didn't trust it enough to bundle with their own PCs. I think a couple models eventually showed up with the option of running OS/2 or Windows 95 but by then the lack of apps was already killing it.

      Interestingly enough, I have seen OS/2 in use in a couple businesses. Canadian Imperial Bank of Commerce (CIBC)uses OS/2 Warp 4 on their workstations and I think also Bank of Nova Scotia. I wonder if these banks are using OS/2 as a sort of Security through Obscurity thing.

      --
      ChodaBoy
      - The preceding statement is the product of a deranged mind and the sole property of the voices in my head.
    8. Re:You all act like people purchased Windows?! by Cro+Magnon · · Score: 1

      Then you must have specifically asked for no Doze. If you just walk into a CompUSA (like 95% of people do), all their non-Macs have Doze.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    9. Re:You all act like people purchased Windows?! by Anonymous Coward · · Score: 0

      WinME was the absolute worst of all the 9x-based OS's. If you can find a disk for 98 or 98SE (and don't want to get 2k or XP), you would be much happier.

    10. Re:You all act like people purchased Windows?! by fishbone42 · · Score: 1

      For me, OS/2 was the first real software I specifically went out and bought. At the time, I had tried to get a pc without windows, and I was todl that the price of the system with os/2 was $200 more. But then I asked ahy I had to pay $200 more for a $200 OS when I'm not taking the default OS. The dealer said that windows was included but the contract put a windows license fee into every machine sold, whether or not it actually had windows installed. So, thus began my dual boot years.

      However, with the dawn of affordable 10baseT, Warp never liked to play with my hardware any more.

      depressing really.

    11. Re:You all act like people purchased Windows?! by Anonymous Coward · · Score: 0
      As much as they were touting OS/2 as the windows killer, they apparently didn't trust it enough to bundle with their own PCs.


      IBM is a big company, a BIG company. Its left hand has no idea what its right is doing. Their hardware people have almost no connection to their software people. The individual parts of IBM almost operate in their own little vacuum. It wasn't a matter of trust, it was a lack of knowledge on the rep's part.

      The point is, if you had actually gone directly to a real IBM hardware rep, and made your point clear about wanting OS/2, you would have gotten it. We did with a big batch of 300GLs we special ordered. All OS/2, installed and configured correctly with the right drivers. But we had to put our foot down hard to get it...
  47. the Last Great OS until Mac OS X by deviator · · Score: 2, Insightful

    OS/2 was a truly great OS. The only other Truly Great OS I can think of is Mac OS X. "Linux+GNU utilities" is a very good OS for a number of reasons, but it's not particularly innovative.

    OS/2 2.0 (the first fully 32-bit version that also supported running more than one DOS session at one time) ran WELL on my 386sx-16 with 6 megs of RAM. Granted, it was slow as molasses, but I was able to run my BBS in one window and do other stuff without a problem. (I still remember my disgust when I tried to do this with Windows 3.0 on the same hardware - it didn't work well at ALL.) The environment was very graphically rich, and the jewel in the crown was the WorkPlace Shell, the likes of which I have yet to see on another OS (even BeOS didn't quite cut it).

    The workplace shell was completely object-oriented; it was so far ahead of its time that most people had a really tough time understanding it which may have helped lead to its demise. You could drag "things" or "attributes" from programs to collections of objects, etc. I could open up the paint or font panel and "drag" color & typefaces over to any part of any open folder or application, and they would stick. The links were stored *in* the filesystem with the objects they affected, instead of a monolithic pseudo-database or oodles of unwieldy text files. As long as programs were written to take advantage of the object-oriented aspect of the WPS, it was a thing of beauty to watch how seamlessly everything worked together. (I used to spend hours customizing colors & fonts on all of my folders & windows by dragging... no OS since then has really been quite as fun to do this with, as they all "feel" very rigid and inflexible in comparison.") WPS also had the concept of templates as stacks of paper that you would literally rip off the top and fill in, not worrying about what the underlying application is. And WPS brought us the first tabbed-divider interfaces, which were pervasive throughout the system.

    But OS/2 was released in a time when PC users were just starting to think graphically and Mac users were almost literally on another planet. Microsoft capitalized on this by releasing version after version of an OS that was essentially a menu-driven system overlaid on top of DOS. OS/2 was so advanced that people simply couldn't grasp its potential. And yes, people viewed IBM as "evil" at the time, and IBM sucked at marketing, etc...etc... there are really a ton of reasons why it didn't make it, but luckily I don't think most of them apply to Linux. No, Linux has a whole list of other problems that will hamper its adoption by the masses, but I digress. :)

    It is a small consolation that OS/2 is still in heavy use in banks, and in Germany (I believe some user groups still exist there). They like their finely engineered products over there. :)

    Like Mac OS X, (and unlike Windows or Linux) OS/2 wasn't simply a "list of features available in an OS" - it was designed from the ground up to deliver a complete & refined experience to the user. It disappeared into the background as you concentrated on the task at hand. It's what an OS should be. It's the last OS I ever used (until Mac OS X) that was truly a joy to use on a daily basis (and this includes several distributions of Linux).

    It's nice that at least Apple finally gets this. :)

    1. Re:the Last Great OS until Mac OS X by Anonymous Coward · · Score: 0
      The links were stored *in* the filesystem with the objects they affected, instead of a monolithic pseudo-database or oodles of unwieldy text files.


      As another ex-OS/2 fan, I hate to break this to you- Extended Attributes, like icons, and certain other qualities of a file- were stored with the file itself, in HPFS. However, those draggable properties- font sizes, window positions, etc- were stored in a "registry" little different than Win9x/NT's.

      See the first vaguely relevent hit on Google if you don't believe the claim. I had a small utility suite that could automatically clean useless cruft from the Registry- window opening positions for deleted folders (or positions I didn't really care about), and other such properties. 'Shadows' were also stored in the registry, which explains why you never saw them in the filesystem from the CLI. (Editing the registry was also the real way to remove a 'broken' shadow, though, not knowing of it at the time, I relied on a shredder replacement that did the trick for me- it probably worked through the WPS API, and only had to ignore a check on the properties of the object.)

      BTW, if there's one simple thing *NIX could take from OS/2, it would be the 'DELDIR' support- although the BOFH answer would be to mv things to a sticky-set /trash yourself. ;)
    2. Re:the Last Great OS until Mac OS X by deviator · · Score: 1

      I didn't know that - I *do* remember "EA DATA. SF" files (yes, with the spaces) on drives that weren't formatted with HPFS, so I assumed it was just a way of storing the extended attributes for the files/objects in that directory. I figured the "EA DATA" was just built into the HPFS filesystem. (HPFS seemed much faster and more resistant to fragmentation than NTFS is today...)

      I never had a problem though with those things getting corrupt, at least not like problems with the registry these days. :)

      Interestingly, my original post got modded up to a 3 last night, then back down to a 2. I suspect it's because I said something negative about Linux.

    3. Re:the Last Great OS until Mac OS X by deviator · · Score: 1

      I just took a look at that article-

      I think the "registry" stuff was installed by Netscape (in this case) just because it made it easier to port, no? I don't think it was anything that was a standard for the whole system.
      I still think attributes, shadows, etc. were stored in with the filesystem (or in the EA DATA files).

      Oh - and Unix has 'rm -rf' instead of DELDIR. :)

  48. OS/2: revolution, not evolution by steveha · · Score: 3, Interesting

    I read through the article, and it was full of weird conclusions. I am very familiar with what was going on in the computer industry during the time period discussed, and I disagree with much of the article.

    The story of OS/2 is what taught me that in the computer industry, revolution is not what the customers want; they want evolution. You can sometimes pull off a revolution (Macintosh) but it is much easier to offer a smooth upgrade path.

    OS/2 was not killed by some weird conspiracy by Microsoft. Some of the other causes of death listed were not doubt contributing factors, but the major cause of death was: incompatible APIs.

    It was not possible to take a Windows application and compile it for OS/2; you had to substantially re-write your app. It wouldn't be quite as much work as re-writing your app from scratch, but it was close. Microsoft didn't want this. Microsoft wanted to make OS/2's windowing API compatible with Windows, but IBM had some other API they thought was better, and they insisted it be used.

    This had the effect of forcing companies to decide whether they wanted to write for Windows, or write for OS/2. That was totally dumb of IBM. If people could have just recompiled for OS/2 and offered an OS/2 version of their app, they would have done so. IBM was asking developers for a revolution, not evolution.

    But let's go back to the first version of OS/2. Because it was written for the 286, its compatibility with DOS apps was poor. OS/2 1.x offered a "compatibility box" for running a single DOS app at a time; it worked poorly, and it was often called the "Chernobyl Box" because it would often crash (and it would take the whole OS down with it). So, any company that wanted to adopt OS/2 had to plan on getting new versions of all their applications.

    But in 1990, Windows 3.0 shipped. It sold like hotcakes. The article makes some bizarre statements about Win 3.0, but the reality was that it would multitask your DOS applications very well. DOS applications were preemptively multitasked, not cooperatively, and DOS apps could very well crash but usually Windows would not crash with them. In other words, Win 3.0 allowed companies an evolutionary upgrade path: they could keep running the same DOS apps they were using, and then phase in Windows apps over time. The same companies that were unwilling to commit to OS/2 were willing to commit to Win 3.0.

    Win 3.0 was what made Microsoft decide to walk away from OS/2. The customers were voting with their dollars, and what they were voting for was Windows. It didn't hurt that Microsoft had covered all bets: they had applications for DOS, Windows, OS/2, and Macintosh. (They even flirted with a few other platforms: my favorite word processor for the Atari ST was Microsoft Write.) When Win 3.0 took off, Microsoft was ready, and sold lots of Word and Excel.

    So, to review: IBM forced developers to choose whether to develop for OS/2 or Windows, and Windows became a runaway hit. That's it right there. That's what killed OS/2.

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
    1. Re:OS/2: revolution, not evolution by kawika · · Score: 2
      I subscribe to this version of history. IBM worked hard to make OS/2 fail, and only after they finally realized it did they try to fix it. By then it was too late.

      It was not possible to take a Windows application and compile it for OS/2; you had to substantially re-write your app. It wouldn't be quite as much work as re-writing your app from scratch, but it was close. Microsoft didn't want this. Microsoft wanted to make OS/2's windowing API compatible with Windows, but IBM had some other API they thought was better, and they insisted it be used.

      Yup. I was at a developer conference in late 1996 when Steve Ballmer said that all developers would have to do to run their existing apps on "Protected Mode Windows" was to recompile. It sounded like the reasonable course of action, and of course the developers loved it.

      By the time IBM announced OS/2 and the PS/2 in April 1997, they had hijacked the OS effort from Microsoft. There was no "just recompile" talk anymore, that was replaced by a reference to a "conversion tool" that never materialized. No wonder, because there were a lot of differences. There were even new UI standards and APIs for interoperability with character-mode 3278 terminals!

      Once Microsoft saw the success of Windows 3.0 they decided they didn't need IBM and broke off the relationship. (Shortly thereafter there was a quiet surrender ceremony where IBM handed over the "Evil Empire" moniker to Microsoft.)

    2. Re:OS/2: revolution, not evolution by s390 · · Score: 3, Interesting

      Shortly thereafter there was a quiet surrender ceremony where IBM handed over the "Evil Empire" moniker to Microsoft.

      ROFL! That's so funny because it's so incredibly true. IBM is quietly happy about this, and rightly so. Understandably, Microsoft isn't - but most of their employees probably don't even realize why they've become so widely hated in the computing industry, or why it's well deserved.

      IBM reached it's peak as an IT monopoly in the late '80s, then barely survived the backlash in the early '90s. But IBM had kickass hardware and software (still big money-makers), networking (since sold to AT&T and Cisco), and services (faltering, but still viable). IBM is also a very large multinational company (~$70 Billion annual revenue). IBM survived, but it's still a screwy company (I know, as I've worked there).

      Microsoft is a much smaller company (under $10 billion annual revenue), and doesn't have complementary lines of business (though they're trying, but not very successfully), so their fall will be faster and harder. The late '90s will be seen as the highwater mark for Microsoft's IT monopoly. Their crash will hurt the US stock market, at least mutual funds in Microsoft. They don't pay dividends, ever. It's a sub-$10 stock.

      The essence of the story of OS/2 is this: IBM gave away the PC Operating System to Bill Gates (Microsoft), then tried to recapture the PC platform with MicroChannel (implicating OS/2), but that didn't work out, so IBM tried partnering with Microsoft, which also didn't work, then finally IBM tried to build a real PC OS on it's own (OS/2 V3 and V4), but mis-handled it all horribly, and by then it was too late - Microsoft already had preloads, the political fix was in with the Courts, and the rest is history but still unfolding. But Microsoft's days are numbered....

      Yeah, I've still got an OS/2 partition on my system (Warp 4 at Fixpak 15, the last one). It works fine, but I use Linux (Mandrake 8.1) now and that works better. I did the 25+ floppy installs of OS/2, got it working well enough to use it as my normal desktop through several years, even kept it running Lotus Notes shared with Windows partitions on notebooks for work, but now I use Linux almost exclusively. Linux is better.

    3. Re:OS/2: revolution, not evolution by steveha · · Score: 3, Interesting

      I think you probably meant 1986 and 1987, not 1996 and 1997. Otherwise of course I agree with you (agreeing with me).

      There were even new UI standards and APIs for interoperability with character-mode 3278 terminals!

      Is that where IBM came up with their CUI stuff? I remember: F12 was save, Ctrl+Shift+F12 (or something like that) was Print, etc. etc.

      Originally, Microsoft apps used Ctrl+S for Save, Ctrl+P for Print, and so on. While Microsoft was trying to be friends with IBM, apps like Word adopted IBM's standard. Later, after the divorce, Microsoft went back to Ctrl+S and Ctrl+P.

      I always wondered where IBM got the idea that function key combinations were better than Ctrl+P.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    4. Re:OS/2: revolution, not evolution by ReinoutS · · Score: 1
      It was not possible to take a Windows application and compile it for OS/2; you had to substantially re-write your app. It wouldn't be quite as much work as re-writing your app from scratch, but it was close. Microsoft didn't want this.
      I do recall there was a "mirrors" lib that would ease porting from win16 to the OS/2 API. I'm not sure how good it was; but at any rate: porting GUI windows apps 1-on-1 to OS/2 is a real shame because of OS/2's OOUI Workplace Shell (see other comments). Real OS/2 apps take advantage of the WPS and integrate with it. One particularly good example of this approach was Seagate Backup, but there were others.
    5. Re:OS/2: revolution, not evolution by steveha · · Score: 2

      There were always compatibility libs. Microsoft never made a true OS/2 version of Word; they compiled Windows Word with a library called WLO (pronounced "willow", acronym for Windows Libraries for OS/2).

      But the 286 was marginal at best for a GUI, and memory was expensive in those days, and the added bloat and inefficiency of compatibility libs meant that they were a last resort.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    6. Re:OS/2: revolution, not evolution by spitzak · · Score: 2
      In the MSDOS days the numbered function keys were very popular as the way to do anything other than typing text to the computer. Ctrl and alt were often used to make there be 4 times as many function keys, but were not used with letters for anything.

      For a lot of people the only use of Alt was to type foreign letters (you held down Alt and typed the octal into the numeric keypad, and lots of people memorized all the ibm character set in this way).

      The one use for Ctrl+letters was to control the few programs that used DOS to read the keyboards (because these programs could not see any of the function keys). Ctrl+P was a DOS command.com standard to execute a print-screen function. Supposedly MSDOS needed this, while PCDOS could use the BIOS call and get the PrtSc key.

      When the Mac came out a lot of DOS programs copied it by using the Alt key, ie Alt+S to save, etc. NOT THE CTRL KEY though there seems to be a huge number of MicroSoft defenders who claim otherwise. Look at a contemporary Mac and PC keyboard and compare the locations of the "apple" and "Alt" keys and you will see why the Alt key was chosen.

      It is not clear why MicroSoft switched things to the Ctrl key. One is that IBM's CDE designs had the Alt key doing strange things to navigate menubars. Also some foreign keyboards used the Alt to type foreign letters, and that Alt+numeric keypad stuff was still in lots of use. They probably also confused menu bar items with local actions used by widgets, in fact we would be much better if Ctrl+x cut text and Alt+x cut the objects the program works with, right now you cannot put a text field into the main window, or selecting objects requires the focus to navigate to the selection area, both of which greatly hinder GUI design.

      In any case the use of Ctrl is more from windows 93 or so. It broke a lot of ported DOS applications, and made it hard to migrate between Mac and PC, it also made it impossible to do Emacs style ctrl keys in text fields, which made typing and editing text way slower. It also caused all the "Linux apps are inconsistent" because in fact Windows was inconsistent with general practice at that time and Linux tries to port apps from both Windows and Mac.

    7. Re:OS/2: revolution, not evolution by Anonymous Coward · · Score: 0

      Alt wasn't just for menu items -- the idea was that all UI controls would have a Alt+letter shortcut for keyboard access.

      So Ctrl+P = Print might conflict with the "Reverse _P_olarity" button. A lot of Windows apps don't implement these keyboard accelerators, but MS has Alt-key support in all their APIs -- even as a HTML extention in IE. (If /. implemented this, I could press Alt+P to Post Anonymously.)

    8. Re:OS/2: revolution, not evolution by spitzak · · Score: 2
      You are right that the Windows API interpreted &x in widget labels as meaning that Alt+x was the shortcut to activate that widget. However most logical people would take that to mean that MicroSoft wanted Alt+letter to mean "shortcuts" and that it should cause menu items to *execute*, to match the buttons. Instead the &x in menu items "navigated" to that menu item, completely different from what it did in buttons!

      I now believe they (and the CDE people who are just as guilty) screwed up with over-engineering. Every program up to then used Alt+letters as "shortcuts" whether that caused a menu item to be picked, a button to be pushed, or something to happen that you could not do with a GUI. This also matched the normal user's expectations. This screw up has greatly hurt the ability to have fast editing (with Emacs or similar control functions in text fields) and screwed up GUI design by requiring that the "focus" be able to move to non-text objects so that Ctrl+X can cut a non-text object (more practically it has required that all text entry fields be on pop-up windows so that average users are not confused by the need to move the focus).

      I am pretty certain that ctrl+P dates back to command.com. That program was incapable of detecting the PrtSc or any other function key if written in "portable MSDOS" that did not use the IBM PC Bios, thus all functions had to be on control keys.

    9. Re:OS/2: revolution, not evolution by steveha · · Score: 2

      Sorry, I can't agree with a lot of what you said.

      Apps expected to use ctrl keys to do stuff, and apps were not as complicated as they are these days, so you saw a lot of Ctrl+P for print and Ctrl+S for save. (And in those days they wrote them as ^P and ^S; it was only in the PC days, with Ctrl and Alt and Shift being used with wild abandon that the "Ctrl+" notation became common.)

      Microsoft's original Windows standard was mnemonic Ctrl keys. Microsoft went from Ctrl+S to Shift+F12 back to Ctrl+S. The Mac keyboard had nothing to do with this. As I said, IBM had their CUA (Common User Access, if memory serves) which called for weird shortcuts like F12 == Save As, Shift+F12 == Save, and Ctrl+Shift+F12 == Print (or whatever it was).

      The Mac was responsible for Microsoft adopting Ctrl+V for paste, and Ctrl+X for cut. Paste used to be the Insert key, and cut used to be Shift+Del.

      most logical people would take that to mean that MicroSoft wanted Alt+letter to mean "shortcuts" and that it should cause menu items to *execute*, to match the buttons. Instead the &x in menu items "navigated" to that menu item, completely different from what it did in buttons!

      No, Windows was always, always consistent about how this worked. Hitting Alt+ would always do the same thing as clicking with the mouse on the thing that showed underlined. If a menu item said "Save _A_s..." and you hit Alt+A, it would open the "Save As..." dialog. If a menu item said "_P_rint!" and you hit Alt+P, it would immediately print (items with a '!' would happen immediately without a menu... MS has walked away from that particular idiom though).

      Every program up to then used Alt+letters as "shortcuts" whether that caused a menu item to be picked, a button to be pushed, or something to happen that you could not do with a GUI.

      DOS apps also used Alt keys, and Ctrl+Alt, and so on. There was no standard. When Windows appeared, Microsoft put out a standard, and even DOS apps started following it (when they mimiced Windows in character mode): Ctrl+key does something immediately, Alt+key does something in a menu or dialog, and Alt+Fkey does window-related stuff. (Alt+F4 quits the app, Alt+spacebar brings up the "window menu", Alt+Tab jumps to next window, etc.)

      This screw up has greatly hurt the ability to have fast editing (with Emacs or similar control functions in text fields) and screwed up GUI design by requiring that the "focus" be able to move to non-text objects so that Ctrl+X can cut a non-text object (more practically it has required that all text entry fields be on pop-up windows so that average users are not confused by the need to move the focus).

      I really have no idea what you are talking about here. Text-entry fields are by no means always in pop-up windows. Text fields have always had Ctrl keys for editing: Ctrl+X cuts to clipboard, Ctrl+V pastes, etc. (Back in the IBM CUA days it was of course Shift+Del to cut to clipboard, Shift+Insert to copy to clipboard, and Insert to paste.) Ctrl+Tab jumps to the next field, Ctrl+Z undoes the editing, and so on. I'm sure you would love an emacs mode, and I would love a vi mode, but Windows will never offer either.

      I am pretty certain that ctrl+P dates back to command.com. That program was incapable of detecting the PrtSc or any other function key if written in "portable MSDOS" that did not use the IBM PC Bios, thus all functions had to be on control keys.

      Every app always used Ctrl keys since before PCs. If you were using a dumb terminal like an ADM3A, control keys were what you had, and there were some standards (under UNIX at least): Ctrl+S pauses the flow of text, Ctrl+Q restarts it, etc. The very first DOS apps used Ctrl keys as well as function keys. Yes, Ctrl+P special meaning in the DOS days, but that was mostly in the command shell; DOS apps would override it and there wasn't any real confusion. DOS apps also used Alt keys, and Ctrl+Alt, and so on. There really were no standards.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
    10. Re:OS/2: revolution, not evolution by UpnAtom · · Score: 1

      Microsoft has a revenue of around $25 billion now.

      OS/2 was competetive for a long time, despite Microsoft's monopoly power.

      Windows 3.x didn't cut it and Windows 95 was late (and native applications for it even later). That's when OS/2 got it's biggest opportunity with Warp and 10 million users. Before that, the cost of memory was a major factor.

      IBM blew the marketing badly with Warp. There was this phenomenon of TeamOS/2 which was a bunch of unpaid enthusiasts that were pushing OS/2 harder than IBM did!

      OS/2 v2.x required far more memory than Windows 3.x. In comparison, it looks like Bill Gates has been prescient about memory prices.

      So that and everything else that has been mentioned has led us to where we are now. Windows 2000 was the first (just about) usable OS from Microsoft since DOS 6, IMO.

      But users don't care about that. The vast majority will use what they've got rather than struggle with something else. They believe it's all operating systems that don't work rather than just Windows.

      Linux doesn't have a hope in hell (unfortunately).

      Dave.

    11. Re:OS/2: revolution, not evolution by spitzak · · Score: 2
      Although you said several times "there were no standards" you also said several times "Alt was used for something". I have programmed PCs for 20 years and I worked with Lotus and early MSWord and many other programs. Ctrl was rarely used for anything other than Emacs emulation, the average user knew that if they held down Ctrl they would get a card suit or something dangerous would happen, and stayed away from it.

      You also said Microsoft's standard was that "Alt+key" does something in a menu. That is exactly wrong, the problem is that for some reason they said "Ctrl+key" selects menu items, rather than "Alt+Key". And I can guarantee you that ONE HUNDRED PRECENT of the Mac-copying programs before that used "Alt" as replacement for the "Apple" key that exectued menu shortcuts. MicroSoft (and perhaps IBM) changed this well established standard for unknown reasons (though I don't think they were being evil, they were confused).

      I agree that Ctrl+letter should be a shortcut for cutting and pasting text. However the MicroSoft design means that these letters must also be used for cutting and pasting anything and this has seriously hurt GUI design because you cannot have a text field on the same window as any other selectable objects. For instance "illustrator" type programs usually make it quite difficult to modify the text, usually by having modes, which are very hard on users, because Ctrl+X may need to cut the letters or cut the text object depending on the mode.

      I challenge you to locate a popular Windows program where the main window has a text field and also has an area where the user can select objects. This very useful design (which would allow somebody to type in text commands or rename objects without any extra clicking) cannot be done due to MicroSoft's use of ctrl+letter for the menu shortcuts. (of course the Mac design where Alt+x did everything has the same problems, but at least they had another shift key (ctrl) free so they may have fixed it, try OS/X and you will see that Emacs control keys have reappeared!)

      Please take a look at the history. Yes there were many programs where neither ctrl+x or alt+x did menu shortcuts. But there were 3 or 4 years of alt+letter doing menu shortcuts before ctrl+letter was used for this.

      I also get disgusted with all the people complaining "Linux is inconsistent, do I use Alt+X or Ctrl+X to cut text" when this is entirely MicroSoft's fault for changing standards right in the middle.

    12. Re:OS/2: revolution, not evolution by steveha · · Score: 2

      Although you said several times "there were no standards" you also said several times "Alt was used for something". I have programmed PCs for 20 years and I worked with Lotus and early MSWord and many other programs. Ctrl was rarely used for anything other than Emacs emulation,

      I'm still not sure what you are talking about. Look at WordStar -- it did everything with Ctrl keys, didn't use Alt keys at all. PC Write used Ctrl keys and Alt keys and function keys, with only function keys used to bring up menus. Lotus 1-2-3 used its "slash key" system for bringing up menus. I can't remember any rhyme or reason anywhere to DOS apps and keys, but I definitely remember Ctrl keys being used all over the place.

      And emacs emulation!? I don't remember anything with emacs emulation. WordStar emulation was extremely common, but the average PC user didn't know what emacs was.

      By the way, I've programmed PCs for nearly 20 years. My first PC programming was with Borland Turbo Pascal 2.0.

      the problem is that for some reason they said "Ctrl+key" selects menu items, rather than "Alt+Key".

      Look, I never used Windows before 1989, so I suppose that this could have been true for Windows 1.x or something. But I have never, ever seen any windowed software from Microsoft that did not use Alt+key for choosing menus and dialog stuff. I include OS/2 PM, Windows 2.x and newer, and character-oriented Windows (COW) apps like Word for DOS 5.5 and 6.0.

      Are you talking about Windows 1.x?

      I agree that Ctrl+letter should be a shortcut for cutting and pasting text. However the MicroSoft design means that these letters must also be used for cutting and pasting anything and this has seriously hurt GUI design because you cannot have a text field on the same window as any other selectable objects.

      I will only make one comment: I do like having universal behaviors... if you can copy text to the clipboard, or copy an object, I like only having to remember one key to do it. But I'm sure that MS could make some improvments to their UI.

      Please take a look at the history. Yes there were many programs where neither ctrl+x or alt+x did menu shortcuts. But there were 3 or 4 years of alt+letter doing menu shortcuts before ctrl+letter was used for this.

      What do you mean "menu shortcuts"? In DOS apps, you never knew what Ctrl or Alt might do until you read the manual. Some apps used both keys. With Windows, Microsoft put forth a standard where Alt plus a letter or number would be used only for pulling down a menu or doing something in a dialog: Alt+S would only do something if there was a menu or dialog active that uses S as a shortcut, but Ctrl+S is outside the menu/dialog structure completely.

      Do you at least agree with me that Microsoft was consistent from Windows 2.x onward?

      I also get disgusted with all the people complaining "Linux is inconsistent, do I use Alt+X or Ctrl+X to cut text" when this is entirely MicroSoft's fault for changing standards right in the middle.

      As I said, I don't remember MS changing standards, but I won't rehash that here. I will point out that GNOME apps are all consistent, and KDE apps should all be consistent. It's only older apps (like Motif-based Netscape Navigator) that vary.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
  49. idSoftware killed OS/2 by TrAvELAr · · Score: 1

    I was an avid OS/2 user until Doom was released. I had nothing but troubles running id games under OS/2.

    On a side note, I still have 2 OS/2 1.2 servers running some kind of proprietary database that we can't live without. I just keep hoping that these pentium 120s don't die taking my database with it. It takes an average of 3-6 boots for OS/2 to even start right these days.

    I love being behind the times.

    1. Re:idSoftware killed OS/2 by SuiteSisterMary · · Score: 2

      Our cinphony ACD system ran on OS/2. It was great; boot to the desktop, bring up the task list, select 'acdmaster' and there it is. And this is current equipment, available for sale. Runs on a single-board P100, 32 megs RAM, and a hard drive. Wall mount.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    2. Re:idSoftware killed OS/2 by Locutus · · Score: 2

      get gtar and make a bootable floppy with it on it. put a backup hard disk in the system and just tar the entire OS/2 filesystem from / to your backup hard disk.

      If you ever have a crash, just fix the failure and then boot from the floppy, format the hard hard disk if needed and extract the tar file to it. I loved the fact that OS/2 could be restored completely from tape and run. I used to do this about every two years just to make sure my filesystem wasn't too fragmented.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    3. Re:idSoftware killed OS/2 by TrAvELAr · · Score: 1

      Thanks for the great idea. :)

      -TrAvELAr

    4. Re:idSoftware killed OS/2 by Richard+Steiner · · Score: 1

      Quake 1 ran fine under OS/2 in a VDM, but the production release of Doom (and other games that were based on the Doom engine) did not.

      Strangely enough, the initial Doom betas ran fine (with sound) under OS/2, but id Software changed the code before release in a way which broke its use (with sound) in VDMs. I remember having e-mail conversations with American McGee (who was understanding) and Jay Wilbur (who was kind of a dick) about it..

      Doom Legacy (a third-party version based on the code id Software released) has since fixed the problem, but I'm sure that the fact that Doom didn't work was one of the points that hurt OS/2 even when DOS was the main gaming platform...

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    5. Re:idSoftware killed OS/2 by walterbyrd · · Score: 1

      I had the same problem. Only real problem I had with OS/2 2.1.

  50. Install, oops, install, oops, install, oops.... by Harlow_B_Ashur · · Score: 1

    Twenty-one floppies, over and over. One bad click, one bad assumption, start over. I swear there was some sadistic dys-feature whereby the more rationally you behaved, the more inscrutable the behavior of the install program.

    Good riddance you patronizing sonzabiches! I don't care if they were all billable hours, they were hours of pure misery, and I will never, ever forgive IBM for putting me through them.

    At least not the old IBM. The new one is fine by me.

    1. Re:Install, oops, install, oops, install, oops.... by Anonymous Coward · · Score: 0
      ugh.

      "This CDROM drive is the exact make and model as the one found on the 'supported hardware' list, but the ID string says 4X instead of 4x so ill just cough and die now".

      OS/2 can rot in the same hell its developrs earned.

    2. Re:Install, oops, install, oops, install, oops.... by Locutus · · Score: 2

      I still think I have my 20-something Consensus UNIX floppies. That was a pain too but once installed on a 386, both OS/2 and UNIX did a nice job multi-tasking.

      Oh, how many nights I remember spent installing floppies...... Thanks for that memory. NOT. :)

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  51. Comment removed by account_deleted · · Score: 3, Insightful

    Comment removed based on user account deletion

  52. alive and well (for the moment) by .smoke · · Score: 3, Interesting

    I use OS/2 just about every day at work, and i can tell you it's very much still alive and kicking :) when the software that runs our equipment was first designed, windows 3.1 just wouldn't cut it, so the programmers decided to use OS/2. since then, each new version has been built on the last, and new equipments' software borrows elements from the previous generation's. so to this day, all our machines use OS/2 version 3 in their embedded computers, and all field engineers are given laptops that dual boot into Warp 4 to run simulations. (ironically, OS/2 is not supported on these IBM laptops, so it's sometimes hard to find drivers.) it looks like the big push to port everything to windows NT is finally on, though. but it will still be around on all our machines in the field for quite some time to come....

  53. Windows had no commercials by HanzoSan · · Score: 1, Redundant


    Thats because no one was even given a choice if they wanted to buy it or not. Why would they need commercials when everyone who buys a PC buys Windows automatically?

    How was IBM supposed to compete with a product which comes with every PC?

    --
    If you use Linux, please help development of Autopac
    1. Re:Windows had no commercials by mgkimsal2 · · Score: 2

      "Start me up"

      They had plenty of commercials for a short time.

      But true, no one can compete with something prebundled which locks out competitors.

    2. Re:Windows had no commercials by drank · · Score: 1
      How was IBM supposed to compete with a product which comes with every PC?


      In 1993 IBM reported revenues of $62.7B. Microsoft reported $3.8B that year. In other words, IBM was more than 16x Microsoft's size at the time in question. If IBM was serious about competing with them in the OS market, they might have:


      • Pre-installed OS/2 on their own computers
      • Payed for world-class branding, marketing & pr for their product
      • Given away OS/2 for 2 years to gain marketshare
      • Underbid MSFT for OEM contracts with Dell & Compaq and written off the loss

      The fact is that they chose to do none of these things. This seems more evidence of IBM's incompetence and lack of corporate direction than of Microsoft's monopoly powers at that point in time. It's one thing to say that Microsoft in 1993 could effectively block underfunded startups from entering some software markets. But it's laughable to claim that the largest IT company in the world couldn't compete with them, had they gotten their act together!


    3. Re:Windows had no commercials by mmusn · · Score: 1
      That's comparing apples and oranges. IBM couldn't have pulled money from, say, mainframes to support OS/2 even if they had wanted to--their customers would have crucified them. Effectively, Microsoft could dedicate their $3.8bn revenue to Windows, while IBM's resources in that area were almost zero in comparison.

      However, IBM could perhaps have given away OS/2 to gain marketshare, but there may have been legal obstacles to that.

    4. Re:Windows had no commercials by Anonymous Coward · · Score: 0

      The fact is that they chose to do none of these things. This seems more evidence of IBM's incompetence and lack of corporate direction than of Microsoft's monopoly powers at that point in time

      IBM has always been about selling very high margin proprietary stuff to a select group of customers worthy of their perfumed salesmen's effort. The fact that OS/2 was marketed as an expensive piece of software to go along with expensive proprietary lockin hardware shouldn't be a shock. The fact that they expected you to pay them to develop for their obscure platform was just insult upon injury.

      It's really too bad that the Windows-Hater Club latched onto a hunk-of-junk like OS/2 instead of pushing for something truely better (UnixWare, OpenStep, even Linux, etc etc).

    5. Re:Windows had no commercials by drank · · Score: 1
      That's comparing apples and oranges. IBM couldn't have pulled money from, say, mainframes to support OS/2 even if they had wanted to--their customers would have crucified them. Effectively, Microsoft could dedicate their $3.8bn revenue to Windows, while IBM's resources in that area were almost zero in comparison.


      Sorry, I don't agree. Resource allocation decisions aren't handed down on stone tables by some Diety. They are made by the corporation's executives! MSFT also had competing priorities in '93 (Win95, Office, NT, Backoffice, the future MSN, etc.), but their mgmt obviously saw the strategic importance of the desktop OS and put the appropriate $$ into development & sales.

      If IBM had decided that owning the default desktop OS was a corporate priority, they wouldn't have put "almost zero" resources on it. Had they decided otherwise, they could have dwarfed Microsoft's investment in the area. Although, as you say, they'd have had to take it out of some projects they deemed a lower priority.

      I do agree with you that legacy of their antitrust troubles in the 70s & 80s probably held them back. It's hard to be a nimble competitor when your every move is scrutinized by lawyers, the courts and an unfriendly press. It's certainly ironic that Microsoft a decade later finds itself in almost the same position.
    6. Re:Windows had no commercials by Anonymous Coward · · Score: 0

      The only reason that they couldn't have pulled money away from mainframes was for internal political reasons. One of the points of OS/2 was to improve mainframe-to-desktop connectivity, so if it had sold, it might have increased mainframe sales (in steep decline at the time).

      Windows was the loss-leader for MS Office for a long time. IBM never quite got that shipping good applications was a good way to sell your OS.

  54. Selective History by angryargus · · Score: 1

    This author for this article, even for September 1997, seems a bit biased. He doesn't have much regard for the IBM/MS agreements (the companies did try to make the relationship work, at least initially), and doesn't even point out that MS did release software to customers call "Microsoft OS/2" (which I have a copy of).

    His timeline also ignores NT--many people don't see to be aware of (or ignore) the fact that NT 3.1 came out in 1993, and he doesn't make any mention of NT until the timeline reaches 1996. NT factored a lot more into people's decisions than Windows 3.1 did.

  55. So you are saying by HanzoSan · · Score: 2

    IF IBMs OS2 was packed with every PC sold Windows would have beat OS2?

    You are saying every PC owner would burn their OS2 backup CD, format their harddrive, and run to the store to spend $200 extra to buy Microsoft Windows?

    if the tables were turned, the result would be OS2 is the winner.

    It was the OEM contracts.

    --
    If you use Linux, please help development of Autopac
    1. Re:So you are saying by OSgod · · Score: 1

      Microsoft out-marketed IBM... No one can say with a straight face that at the time OS/2 was released that it was locked out of the market by MS.

      Was it locked out of the market by IBM? As usual MS's competition couldn't market themselves out of a wet paper bag.

      How does this apply to Linux today? Have we learned anything? Are the Linux companies winning due to not only technical merit but also marketing prowess?

      No.

    2. Re:So you are saying by SuiteSisterMary · · Score: 2

      Yes. Remember, this was back when the phrase 'IBM-PC or compatible' meant something, and if you DIDN'T own an IBM, you ran the very serious risk of software just not running correctly. This was back when the gov't was seriously considering breaking up IBM, exactly the same way they're thinking of breaking up MS. And where as MS tried to lock in OEMs, IBM tried to lock OUT OEMs. Remember MCA? No? There's a reason.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    3. Re:So you are saying by scrytch · · Score: 2

      Yunno, simply asserting something over and over doesn't make it magically come true -- even if you hold your breath til you turn blue (hey that rhymes). The world still ran on DOS back then, Windows was a launchpad for DOS, PC-DOS was perfectly compatible and many people ran it, and IBM was the 800 lb gorilla, by dint of the fact that IBM was one of the biggest OEM's out there.

      if the tables were turned, the result would be OS2 is the winner.

      So if OS/2 were the winner, then the result would be that OS/2 is the winner... Stunning insight.

      Sig:All who want games in linux will sign up to Transgaming,All who dont sign up to Transgaming dont want games

      Yep, this seems to be the sort of prevailing logical rigor around here...

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    4. Re:So you are saying by HanzoSan · · Score: 2



      No, OS2 would be the guarenteed winner if
      A IBM were the only PC maker on the market
      B IBM actually packed OS2 in with their own machines

      Even IBM was packing windows with their machines.

      --
      If you use Linux, please help development of Autopac
  56. -3 Offensive by borgboy · · Score: 1

    In the beginning, there was a collaborative project between IBM and MS to produce a 32-bit, client server OS. Client server in the sense that it would support the concept of a "native" API, and adapter/wrapper APIs that resembled standards, such as POSIX, that brokered requests to the native API. It featured an advanced (for the time) filesystem with metadata features and a binary tree implementation of the file lookup table/cluster map. Eventually, IBM and MS parted ways. IBM sold the product as OS/2; Microsoft as Windows NT.
    Yes, there are a TON of differences between the 2. But they began life as one.

    --
    meh.
  57. I used to write device drivers for OS/2 by CoffeeNowDammit · · Score: 1

    No kidding. My first job was with Le Grand Bleu here in the Research Triangle Park, NC area. There I was, fresh out of school , and I found myself writing very-close-to-kernel code. (Remember, this was back in the days when Linux barely existed if at all, during the last spastic twitchings of the reign of Bush the Elder.)

    The OS internals themselves were pretty slick (multi-threading, flat memory model), and the driver interface was decent, even in the 2.0 days, but Christ, IBM couldn't market lemonade in the desert. No TCP stack, no developer tools without mortgaging your soul, and as far guaranteeing compatibility on other manufacturer's 386 boxes, well, you were on your own.

    Having said that, it was a great OS to cut my driver-writing teeth on, even if the APIs were butt-ugly to behold (definitely MSFT's influence there; IBM preferred things to be more Unixy IIRC).

    If you wonder what it was like watching a product being made and poorly poorly marketed, I'll say this much: I was getting totally fscking tired of watching great developers get screwed. IBM recruited, and got, a wide array of very talented technical people, only to have their efforts (as developers and evangelists) stifled by suits. Yes, the same kinds of suits who gave MS-DOS to MS in the eighties, and who never had a clue about the PC software market until it was too late. Despite the developers' best efforts, IBM management and marketing always managed to find a way to lose to Microsoft. Really snatching defeat from the jaws of victory. They had either no will to win, or not enough brains to do it. Quite a few of us just ended up leaving in disgust.

    Again, that was another life. My main dev platform these days is the Penguin, and I'm using MacOS X at home. I still don't have much of a tolerance for x86-based machines, let alone their corporation-generated OSes. And I'll never return to a large mega-monolithic corporation for a job if I can help it..

    --

    ".sig, .sig a .sog, .sig out loud,
  58. Why OS/2 failed by rseuhs · · Score: 2
    OS/2 failed because IBM is a PC-maker and other PC-makers don't like to be dependent on the competition.

    It's that simple.

  59. OS/2 is dead by Anonymous Coward · · Score: 0

    Nuff said..

    OS/2: Half an OS

  60. AmiPro Debacle by saihung · · Score: 2, Insightful

    Remember AmiPro? Now it's called WordPro, and it's a part of the IBM/Lotus office suite that comes with a lot of computers for free but never, ever gets installed or used. Ever. There was a time, however, when AmiPro was a serious, bona-fide competitor for MS Word. I used to use it on my 286 with Windows 3.0, and it was fantastic. It did everything, it gave me real WYSIWYG (something that I associated with seriously high-end apps like Ventura, but not Word), it was just great. IBM had been promising a native OS/2 version of AmiPro for ages, and this was it - the last hope, the last light for OS/2. This was still a viable product, people were still using it and paying actual MONEY for it, and this was the suite that could (maybe) save OS/2. The release was pushed back time and time again, and when AmiPro for OS/2 finally saw the light of day, everyone wanted to put it back in the ground. It was awful, buggy, evil stuff, didn't install properly, crashed non-stop, ate files, and just plain didn't work. That was when even the faithful started jumping ship. A working version of AmiPro could have made OS/2 an operating system that you could actually accomplish normal office tasks with, but instead gave MS-boosters yet another thing to point to when they dismissed it. Ahh well.

    1. Re:AmiPro Debacle by rudy_wayne · · Score: 1

      I used AmiPro for a long time and loved it. The AmiPro story is just one example of how companies screw themselves without any need for Microsoft to do anything evil.

      In the fall of '95, *AFTER* Windows 95 had already come out, Lotus releases a new version of AmiPro, re-named to WordPro. Holy Mother..... what a load of crap!! Slow, buggy, crashes constantly .... and it's not even a Win95 app ... it's still designed for Windows 3.1

      Oh yeah, and just for good measure, they completely re-designed all the menus so that all of your favorite AmiPro functions were now located somewhere different .... if you could find them at all. PC Magazine gave WordPro glowing reviews, raving about all sorts of wonderful new features. Unfortunately, figuring out how to use these wonderful new features was nearly impossible since WordPro came with an "instruction manual" that was nothing more than a small, thin pamphlet that contained only the most basic of information.

    2. Re:AmiPro Debacle by Anonymous Coward · · Score: 0

      I actually liked the later versions of WordPro alot (and I'm pretty much a Word Bigot from the old days).

      In particular, the formatting 'pallettes' was much nicer than the modal dialogs that Word still has on Windows. The downside was shitty DOC file support. (I do note that the OS X version has gone to pallettes, but I guess MS is scared of anything that might require retraining on the PC side.)

    3. Re:AmiPro Debacle by BoneFlower · · Score: 2

      I liked AmiPro- The whole Lotus Smart Suite was a good package, it was the standard office package for the US Marine Corps until late 98 when orders came down to switch to MS Office. Even then, alot of units and individual departments still used Ami/Word pro. By the time I got out though(last october) it was dead... A few copies kept around in the event you needed to work with old data, but effectively dead. In fact, at my last unit, you just about needed a written request from an officer to get a copy installed.

  61. Microsoft has fooled most people by HanzoSan · · Score: 2

    Most people think Microsoft Windows comes "FREE" with their PC.

    Microsofts tricky Marketing has made Windows as free as Linux.

    --
    If you use Linux, please help development of Autopac
    1. Re:Microsoft has fooled most people by ObitMan · · Score: 1

      By your reasoning...
      Linux is not free?

      --
      Who run Barter Town?
    2. Re:Microsoft has fooled most people by HanzoSan · · Score: 2



      Whats Linux have to do with this?

      No, Linux is actually free, you can download it for free. Try downloading Windows.

      --
      If you use Linux, please help development of Autopac
  62. Fact Check by Anonymous Coward · · Score: 0

    Windows 2000 came out in February 2000.

  63. Kinda like... by OSgod · · Score: 1

    Linux isn't it?

    I.e.: an OS that is great as a server but has a rudimentary UI at best and a horrendous one at worst.

  64. What lessons are to be learned? by Anonymous Coward · · Score: 0

    Simple: don't partner with Microsoft! A lesson that has been learned over and over?

  65. Better than anything else ? by q-soe · · Score: 2

    I was selling this stuff on launch and the better than anything else tag is hilarious.

    OS2 1 was a disaster

    What about the steepest resource requirements around ? (you didnt have 24mb of ram forget it - in those days the standard systems i sold with 3.1 had 8mb)
    What about random crashes for no reason?
    buggy software ?
    unpredictable performance?
    Installations that wouldnt work for no apparent reason?
    Issues with Vesa equipment ?
    Cryix processor issues ?
    IBM's legendary lack of support?
    price of the OS - well above windows 3.1? ($50-90 more from memory)
    Applications that didnt work properly ?

    and thats just off the top of my head

    I mean come on OS2 Warp was getting there sort of but V1 was a big steaming heap. OS2 never got to the point where it could compete on stability with win3.1 and IBM's half hearted on again off again support and marketing for it didnt help.

    --
    I refuse to argue with Anonymous Cowards - if you want a discussion get an account....
    1. Re:Better than anything else ? by BoneFlower · · Score: 2


      Counterpoints to your agument:)

      >What about random crashes for no reason?

      Windows.

      >buggy software ?

      Windows.

      >unpredictable performance?

      Windows.

      >Installations that wouldnt work for no apparent >reason?

      Mandrake Linux 8.0.

      >Cryix processor issues ?

      Cyrix processors.

      >Applications that didnt work properly ?

      Windows.

    2. Re:Better than anything else ? by q-soe · · Score: 2

      The era we are discussing was PRE mandrake and the competiton was windows 3.1

      It was stable, easy to install and worked (as does XP)

      The Mandrake comment is true though - i have a computer and a notebook here that mandrake wont detect things on (Video Card in One (neomagic 128) and sound (Crystal in the other) yet Debian and Lycoris and Red hat all work perfectly.

      Adn the less said about cyrix processors the better (stil the only processor i have ever seen that needed a software patch)

      We all forget that Windows 3.1 was a stable and well developed OS at the time - attempting to make out that modern OSes have any relation to OS2 V1 is a laugh as standard machine build was 386 with 8mb ram and a 512k video card(1mb if you had money to burn)

      And we are'nt discussing Warp VS Windows 95 BUT if you do a bit of reading you will find that on NON ibm hardware 95 with all of its problems still outperformed OS2 in most cases and was more stable (Note the bit about embedded OS2 in ATMS is true but its very very customised and stripped down and doesnt have all of the problem casuing bits (the Graphics subsystem, memory management (what a joke) and the other tripe that made OS2 such a dog. The kernel in this mode is apparently very stable but were only talking i believe IBM ATM machines and some older NCR's so it could hardly be called an industry standard.

      In closing the /. attitude that windows is the root of all evil got old a long rime ago and with XP its now incorrect as well.

      (i know you may be joking but im sick of it - lets move on with Linux and forget about windows and MS - its not as bad as most people on here make out and it alienates people)

      --
      I refuse to argue with Anonymous Cowards - if you want a discussion get an account....
  66. It's all in the perception by Eric+Damron · · Score: 1
    I remember when OS/2 came out. I was working at a large computer center. We ran mostly main frames and a few mini-computers. This was back in the DOS days and it had just become obvious that PCs were going to become big. Really big. Microsoft had come out with it's awful Windows 1.0 and then Windows for workgroups.

    We evaluated OS/2, it was much closer to true multi-tasking then WFW and superior in a lot of other ways. I couldn't understand why, given the superiority of OS/2, management wanted WFW. I think that management just wanted to "go with the flow" because Microsoft pretty much controlled the desktop already with MS DOS. The fact that OS/2 was superior was irrelevant.

    Did management make the right choice? One could argue that they did being that OS/2 languished. But one could also argue that it was a self-fullfilling prophesy.

    I think that it is human nature to try to back the company with the advantage rather than take a chance and back the company with the better product.

    The advantage that Microsoft had was that their name was already associated with PC operating systems. IBM was (and is) a big name too but it was associated with mainframes.

    --
    The race isn't always to the swift... but that's the way to bet!
  67. Sad indeed by Anonymous Coward · · Score: 0

    Compared to what else was out there, OS/2 was way ahead. It was stable, an elegant api, etc. But, it needed more memory than anyone could afford at the time (remember memory at 100 /mb). Win3.0 could run on a machine that os/2 couldn't. Microsoft has been very lucky, although you could say they made their luck.

    Developers couldn't get a realisticly complete api for the workplace shell. Everytime you wanted to do something, you ran into an undocumented interface. IBM was loosing money right around then, and had to refocus. The real death of OS/2 wasn't win95, but NT. IBM ported all their middleware and db's to NT, and OS/2 died.

    I think within IBM that OS2 came to signify the bad old days. Too much MS and mainframe infighting. Think of OS2 as windows ME. Microsoft had the sense to realize they were in the same hole.

    Interestingly, within IBM, linux is selling the big iron. IBM will never support/push another desktop.

    The lessons to learn for the open/free software movement is not to count on compatibility with MS software for any measure of success. They will change the api/ interfaces to break it. Remember Windows 3.11? No? Anybody who used OS/2 does.

    Mono and other initiative to hook into some kind of MS software will eventually fail. Same with any attempt to reverse engineer the office data. And Samba, as successful as it has been, will increasingly run into walls.

    Free software will succeed on it's own merits. As it already has. I await the day when I read reviews of software that say this app is good for a microsoft shop, but otherwise choose this one.

    Derek

  68. MS did NOT kill OS/2. IBM DID. by thammoud · · Score: 0

    The stupid IBM decision to release an OS that did not take advantage of the 386 multiple DOS boxes is what doomed OS/2 against Windows 3.0.

    During those days, people were looking for a solution to allow them to run multiple DOS boxes. Windows did not have any serious apps and was not a threat. 3.0 allowed people to finally run multiple DOS boxes under a cute little GUI.

    I made a lot of money from OS/2 consulting and was an avid fan. As much as I detest Microsoft, IBM did the OS in. They had no clue and they truley cared about thier stupid PS/2 line (mostly 286's) at that time. What a bunch of goofballs.

  69. "Findings of Facts" DOJ :VS: Microsoft by joeler · · Score: 1

    It was in there, IBM was forced to drop supporting OS/2 on the desktop if they didn't want to pay a big penalty for Windows licenses. IBM fought a good fight, but was not ruthless enough. Hopefully linux will fair better, but don't count on it as long as people refuse to learn about history, they will be forced to repeat it.

    --
    >>>please remove "nospam" from email address
  70. IBM shares blame with MS for the demise of OS/2 by Brett+Glass · · Score: 2, Insightful
    I was an OS/2 developer and aficionado from Day -1.... That's right, I had OS/2 0.9 running (under NDA) before it was available to the general public. And I can tell you with certainty that it was not just Microsoft that killed OS/2 (though it certainly played a role); it was IBM itself. Many bugs that I discovered in the OS were never fixed, even though I and others reported them many times. Speed and memory issues weren't adequately addressed. IBM shifted its OS/2 operation from Boca Raton to Austin, causing key developers to quit. Support was terrible. And hardware evangelism was even worse.... There were painfully few drivers available.

    IBM's biggest mistake, though, was implementing Windows compatibility. This killed the application market. Why write for OS/2 when you could write for Windows (and OS/2 could then run your product under emulation)? Because of this, OS/2 could never, ever have had a "killer app."

    RIP, OS/2. I wasted a lot of brain cells, time, and money on you. If IBM were smart, it would release all of your code under a BSD license, thus giving every one of Microsoft's competitors -- commercial or not -- a leg up. But, alas, I don't think it's that smart.

    --Brett Glass

  71. Where IBM went wrong by NewtonsLaw · · Score: 3, Insightful

    There's absolutely no doubt that OS/2 was a vastly superior product to Windows (and probably still is).

    The only problem was that IBM really didn't have a very clever strategy for dealing with the competition from Microsoft.

    Their single biggest mistake was to treat developers as a cash-cow rather than a valuable resource.

    I did some development work for OS/2 and it cost me a fortune to tool up with all the necessary compilers, libraries, tools and documentation.

    Most developers at the time already had the tools I needed to develop Windows 3 programs so it made little sense for IBM to raise a barrier to developers by charging like a wounded bull for its tools -- but they did.

    IBM mistakenly thought that they could just spend $50 million on advertising the product to the end-user and ignore the needs, complaints and hearts of the developer community.

    They paid dearly for this neglect -- simply because it resulted in a dearth of good quality "off the shelf" OS/2 applications to rival those offered for Windows.

    Even worse, IBM kept touting its great ability to run Windows 3 programs alongside native OS/2 apps.

    How smart was that? Not very!

    Faced with IBM demanding outrageous prices for new tools (and even more outrageous upgrade fees for the same tools) -- or simply writing Windows code that OS/2 users could run anyway -- the choice was obvious.

    Mainstream programmers kept pumping out Windows applications while almost completely ignoring OS/2. Oh sure, there were small groups of devout OS/2 developers who cherished the technical superiority of the operating system -- but that old catch-22 soon popped up.

    Despite all that expensive advertising, consumers said "why buy OS/2 just to run Windows 3 software when you can buy Windows 3 for less?" Don't forget that OS/2 really needed about twice as much (expensive in 1992) RAM to properly run a Win3 program than did Win3 itself.

    All in all, the public weren't about to pay extra without some real benefits -- and there wouldn't be any such benefits until there were enough native OS/2 apps to rival Windows apps.

    And (here it comes) there wouldn't be enough native OS/2 apps until there were more OS/2 developers -- who were not about to fork out the price of a good used car just to write code for the tiny community of OS/2 users.

    If IBM had half a brain they would have realised that the hurdle to the acceptance of any new OS is the availability of applications.

    In stead of trying to screw big profits out of developers they should have given away their tools, SDKs, etc. This would have endeared them to the developer community (rather than alienate them as they did) and the result would likely have been some damned fine apps that matched Win3 versions for functionality and blew them away from a reliability perspective.

    Of course this is what's happening now with Linux but I fear that it's simply too late to overtake the beast. Ten years ago there were many more large software companies and competing with Microsoft was hard but not impossible. These days you're sunk before you get your boat to the water.

    Maybe 20-20 hindsight is a wonderful thing -- but I was telling them this ten years ago -- except they were so arrogant that they felt they didn't need to go out of their way to help developers and that end-users were far more important.

    1. Re:Where IBM went wrong by eAndroid · · Score: 2

      I think you're right. I just wanted to point out that Apple appears to have learned the same lesson since they give out all the OS X development tools as well, including a nice GUI IDE.

      --

      I can't spell or type, but that doesn't mean I'm unusually stupid.
  72. Some history & facts and OS/2 relation to Linu by xt · · Score: 2, Interesting

    Well, OS/2 3.0 Warp was great, I used it for a year and a half and it was really stable and powerful.

    It did have its share of bugs, the keyboard queue could hang for example, leaving the system running but non responsive to user input, or it didn't protect the swap file (one could hang the system, if I recall correctly, by writing into the swap file!).

    Despite, it was clearly better than Windows 3.x and Windows 95. It run almost everything DOS related, even games (Mortal Kombat 2 in a window anyone? ) and most Windows apps, sometimes faster than Windows itself and surely more stable.

    Pricing for personal users was also right, I recall I bought it for less than the equivalent of $50.

    It had a number of powerful commercial apps, a lot of shareware/freeware good ones, a very active user/developer community...

    But it didn't have proper support from IBM itself. Period. What killed OS/2 was IBM as a company, since it never showed faith that it could succeed and never had a consistent plan as to what it should achieve.

    Was it a big company OS? A personal computer one? Was it a Windows replacement? Something entirely different? IBM used to shift positions and the result was that the killer big name app never came.

    The result is that now OS/2 is a niche product, used mostly in financial institutions and getting replaced slowly but steadily by alternatives.

    Is OS/2 related to Linux? In a way. But OS/2 started as the next big thing and became a niche product, while Linux was not even a niche product and now is the next big thing.

    Applications are here, support is here, publicity is here, only one thing can reverse Linux's course; inconsistency.

    Diversity is a good thing, but some well chosen standards are better. Give the choice to those who need it, but have a common set of choices defined for those who don't.

    If Linux is to succeed in all these different markets it targets (server, desktop, embedded), there a must be a clearly defined path and set of options for each. One size fits all was never the answer in computing.

    OS/2 was killed because IBM didn't have a consistent vision as to what it should have been, while Windows was everywhere and good enough for most.

    Linux could succeed, by not repeating this mistake.

  73. Good story, but here's the short version by ajp · · Score: 1

    Without digressing as to who actually wrote the crappy 1.0 version, IBM made OS/2 for businesses. It was a business-class OS from a business-class company. Years later, it's failed in the consumer market but is still being used by its core customer base: businesses.

    Similarly, Linux is a geeky OS, written by geeks for geeks. Years later it will fail in the consumer market but will still be used by its core customer base: geeks.

    OS/2 was a better DOS than DOS and a better Windows than Windows. When I ran it, it was a better kernel for the GNU toolset and X-Window system than Linux. (Linux has improved, thank god.) The sole advantage that Linux has is that IBM can't pull it off the market.

  74. RAM Prices by Anonymous Coward · · Score: 0
    What killed OS2's market opportunity was that, at the time, RAM cost an arm and a leg.
    There was a real drought. And OS2 definitely needed much more RAM than did Microsoft's dreck.

    I'm 45, I remember quite clearly wondering at the time: Why couldn't OS2 get market, how could that lame Microsoft stuff capture market share?? ... but the RAM drought was the reason ... IMHO.

    A couple of the top-level posters danced around this issue but didn't quite hit it.

    fred@welho.com

  75. OS/2 Far From "Dead" - Just renamed by Angry+Black+Man · · Score: 2

    Much (most) of the first versions of the Windows NT operating system was just OS/2 code repackaged.

    OS/2 is far from being dead - its just called Windows XP.

    --
    the byproduct of years of oppression by the white man
    1. Re:OS/2 Far From "Dead" - Just renamed by crawling_chaos · · Score: 2
      I don't think this is correct. They hired a new team of old DEC guys to write NT. I would guess that XP has more legacy VMS code in it than OS/2 code.

      And they left out a lot of the stuff that made VMS cool, too. What ever happened to version as part of the file name anyway?

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    2. Re:OS/2 Far From "Dead" - Just renamed by Osty · · Score: 1

      I would guess that XP has more legacy VMS code in it than OS/2 code.

      Only if by "legacy code" you mean "guys that worked on VMS also worked on NT, and thus may have had tendencies towards doing things in a VMS way", rather than "old VMS code", since NT was a completely new OS. Also, while NT did for a while have an OS/2 subsystem, that's no longer in XP, and it was along the lines of the POSIX subsystem -- it was not part of the OS, other than that it added a layer to NT to allow POSIX or OS/2 apps to run. Other than the fact that NTFS was originally loosely based on HPFS from OS/2, that's the only OS/2 code you'll find in NT.

    3. Re:OS/2 Far From "Dead" - Just renamed by Anonymous Coward · · Score: 0

      NTFS -- Updated HPFS
      Networking -- Even called "LanMan Server" in the NT 3.x days. Straight out of OS/2.
      CMD.EXE -- Looks familiar?
      Win32 -- Planned 32-bit OS/2 API with names changed to protect the innocent.

      It's true that the kernel was rewritten by the DEC guys, and they put some VMS ideas in there. That's only because the OS/2 kernel was a pile of buggy non-portable i286 crap.

      Think about it -- We know that MS had full rights to the OS/2 code. AFAWK, they didn't have any rights to VMS. Which codebase would they have used?

    4. Re:OS/2 Far From "Dead" - Just renamed by roseanne · · Score: 1
      Actually, if you're interested in the history of NT, Showstopper! by Pascal Zachary might be a good book to read. It touches upon some of the OS/2 related tensions, too.
      Think about it -- We know that MS had full rights to the OS/2 code. AFAWK, they didn't have any rights to VMS. Which codebase would they have used?
      Can't find a link for this now, but afaik msft and digital had an agreement to cross-license technologies. Also, msft apparently paid digital for the right to own some patents they had (not sure of this, though).
    5. Re:OS/2 Far From "Dead" - Just renamed by mirabilos · · Score: 1

      Erm, the POSIX and OS/2v1 subsystems were on the
      same layer as the Win32 subsystem over the NT
      kernel.
      You can even code NT native applications under,
      e.g. W2k. Just google for "NT native API"

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
    6. Re:OS/2 Far From "Dead" - Just renamed by Anonymous Coward · · Score: 0
      OS/2 is far from being dead - its just called Windows XP.
      There's nothing in XP equivalent to the WPS.
  76. OS/2 subsystem for NT by user32.ExitWindowsEx · · Score: 1

    Did the OS/2 subsystem for Windows NT/2000/XP have any role in killing OS/2?

    --
    "Evil will always triumph because good is dumb." -- Dark Helmet
    1. Re:OS/2 subsystem for NT by Hyped01 · · Score: 1
      No... it was OS/2 1.X compliant only (16 bit OS/2 command line apps).

      Robert

      (Happily running this year's release of OS/2)

      --

      WebMaster:
      BinFeeds
      XXX Thumbnailed Image Newsgroups but

    2. Re:OS/2 subsystem for NT by Locutus · · Score: 1, Troll

      No, it was mainly to give NT it's networking back in the rev 1.0 (3.1) days. Microsoft owned Lan Manager and it was a 16bit OS/2 server process. They eventually wrote native NT networking into NT but it was probably not until v4.0 that the OS/2 subsystem wasn't used much.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    3. Re:OS/2 subsystem for NT by BakaMark · · Score: 1
      I have seen developers trying to port an application originally written for OS/2 to the Windows NT Platform, but running it under "Presentation Manager for NT" (or something like that). It was a programming environment that simulated parts of OS/2 within a Windows environment, which Micorosft left out.

      It was expensive from a software licencing perspective, and it required the developers to redevelop the code anyway. The result was that they spent just as much time on the porting to this environment, as it would have been to port the application to a Native Win32 binary.

    4. Re:OS/2 subsystem for NT by Anonymous Coward · · Score: 0

      Yes -- All seven people running MS-SQL on LAN Manager switched to NT. That was about 50% of OS/2 installed base.

  77. A bit erroneous... by Lethyos · · Score: 2

    WinG huh? It wasn't until IBM showed ID's Doom running in a window on OS/2 that Microsoft got off their ars and build WinG. IBM build DIVE with IDs help but something happened in the process and ID dropped out of the partnership. I think it had to do with culture clashes. Just a guess. From what I remember, there were huge groups of people around the OS/2, Doom-in-a-window demos at COMDEX.

    You're talking about apples and goats here. Running DooM in a DOS window is only a demonstration of, well, DOS. WinG and DirectX after it are API's for writing Win32 programs that can access the hardware by more sophisticated means. If IBM had demonstrated DooM ported to OpenGL, that would have been something impressive. But it wasn't. Running a DOS window is not impressive.

    Gesh, OS/2 v3.0 had OpenGL support builtin too, though it never got hardware OGL support.

    Saying an operating system has OpenGL support built in just does not make sense. What you mean is that OS/2 came bundled with native libraries that provided OpenGL routines. If you want to "add" OpenGL support to an operating system, you just port (devil of details here) it and recompile. Windows 9x had support for OpenGL if you went to SGI's web site and downloaded their runtime libs. However, Microsoft just bundled them eventually. Big deal. As for never getting hardware support... well, case in point.

    There is very little, if anything, Microsoft ever did first in the computer industry. Most was just copied and they dominated by the anti-competitive leveraging of their monopoly. IMHO.

    This is the only point on which I'd say you're absolutely correct.

    --
    Why bother.
    1. Re:A bit erroneous... by Anonymous Coward · · Score: 0

      IIRC, the DIVE version was native OS/2 and shipped before there was WinG/DirectX etc, but after the Macintosh port of Doom-in-a-window. So not that impressive.

    2. Re:A bit erroneous... by Anonymous Coward · · Score: 0

      >You're talking about apples and goats here. Running DooM in
      a DOS window is only a demonstration of, well, DOS. WinG
      > and DirectX after it are API's for writing Win32 programs that can access the hardware by more sophisticated means.

      Bullshit. There is an OS/2 native Version of Doom; I am not
      absoluteley sure whether it uses DIVE or not, but it was
      certainly not an DOS Application; You can find it on one of the old Hobbes Mirror CDs.

      murphee

    3. Re:A bit erroneous... by Anonymous Coward · · Score: 0
      You're talking about apples and goats here. Running DooM in a DOS window is only a demonstration of, well, DOS. WinG and DirectX after it are API's for writing Win32 programs that can access the hardware by more sophisticated means. If IBM had demonstrated DooM ported to OpenGL, that would have been something impressive. But it wasn't. Running a DOS window is not impressive.

      He wasn't referring to running Doom in a DOS box. IBM actually contracted out for Doom to be ported to OS/2 as a native application. This was, in part an excercise in improving DIVE to make it capable of handling such games. One "improvement" that came out of the effort was Full Screen DIVE (improvement is in quotes because this mode never particularily worked very well).

      I have a copy of the object code for Doom for OS/2 somewhere. It ran rather well, but by the time it was mostly ready for end-user use, Doom had long gone by the wayside.

  78. Did you people really use OS/2? by ToasterTester · · Score: 2, Insightful

    I was involved with the development and support of OS/2 products since its first release and I read all this praise and wonder what product did you people actually use. Okay interfase is a personal thing, I hated it if you liked it fine. But did you really look at the architecture it wasn't that robust as many would like to think. One misbehaving application could crash the entire system. As for Warp what a mess, I had to work with the IBM developers because our product that IBM used was crashing. Bottom line don't believe the OS/2 API things don't work as documented. Then Warp was a performance dog. IBM tried to hide it by speeding up all the interface code. but test timings on non-interface code and pre-Warp versions were faster. Even IBM wanted to kill OS/2 off years before they did, but for political reasons they couldn't. OS/2 was a nice idea, but bad implementation. No tears in the end.

    1. Re:Did you people really use OS/2? by Anonymous Coward · · Score: 1, Interesting

      You must have used a different OS/2 than me or any of the people I knew at the time then. Both OS/2 3.1 and Warp ran faster and were much more stable than either DOS/Win31 or Windows 95 on my Gateway 4DX266V (486/66, w 8MB ram). It wasn't until I finally installed Slackware on that beast that I discovered an operating system that was more fun and useful.

  79. Unbelievably Annoying Thread Renamings by Anonymous Coward · · Score: 0

    1. If you had anything that interesting to say, you wouldn't have to start FIFTY FUCKING THREADS in every story you comment on.

    2. If you'd pause for a minute you'd realize that you aren't saying anything that hasn't been said 800 FUCKING TIMES on slashdot already.

    3. But you don't, and apparently you haven't, so my only advice to you is to either STFU, or learn to troll more creatively. Also, you might want to work on your communication skills, if you're actually interested in communicating with post-adolescents.

    4. Not that you'll find a lot of those here anyway.

    5. There must be something better you could be doing with your time. Homework, possibly?

    Oh well, I tried

  80. Been there... by Anonymous Coward · · Score: 0

    used OS/2 since 2.0 to Warp. The base was
    pretty robust but the pm with it's extended
    attributes was not so pretty. especially the
    version for FAT. Otherwise, the integration was
    pretty neat and GNOME or KDE aren't
    really there...
    but they will!

  81. Linux has better marketing than WindowsXP by HanzoSan · · Score: 2



    Linux ads were all over cars, sidewalks, billboards, all around the city, People who dont even know what linux is know about the pengiun

    Linux's problem isnt marketing at this point, not only is there a league of linux users willing to market it via word of month, theres also hackers who market it, IBM Markets it, Sun, etc etc, Marketing is not the issue with Linux.

    Maybe IBM didnt market itself, that is true, but Linux has very good marketin

    --
    If you use Linux, please help development of Autopac
  82. Re:Paid based on K-LOCs by wiresquire · · Score: 2, Interesting

    It fascinated me that in the revenge of the nerds, it was pointed out that IBM was paying Microsoft based on K-LOCs (thousands of lines of code). I think it was Ballmer who pointed out that it was hardly an incentive to code something tight and efficiently...

    Also, IBM got wind that MS was developing Windows in parallel. That's when that 'partnership' started to unravel. I believe there was meant to be a fundamental difference about supporting older DOS applications. With earlier incarnations of OS/2, you had to be lucky to have a program work in the DOS box. With Windows, you had to be a lot more unlucky...

    --

    So does Anonymous Coward have good karma?

  83. os/2 was prebundled... for some time by dunkelfalke · · Score: 1

    for some time two of the biggest german computer computer market chains - vobis and escom - had os/2 bundled with their computer. they did it because microsoft wanted dos/windows license fees for EVERY computer, not only for those with dos/windows preinstalled. of course vobis and escom were pissed so they bundled their pcs with os/2. it wouldn't last long tho... too much power on microsoft side.

    --
    "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
  84. Macs werent the same price by HanzoSan · · Score: 2



    Back when i got my first PC, a Mac was over $2000 and the PC was hundreds of dollars less.
    Still even now, Macs are more expensive. Sure theres some cheap Macs now, but its too late, the Imac should have been around in 1996, not 1999.

    --
    If you use Linux, please help development of Autopac
  85. OS/2 isnt dead...is IS windows by ghack · · Score: 1

    This is something most people dont know or understand: OS/2 isnt dead, it just lives on in a different form.

    Windows NT 3.1, 3.51, 4.0
    Windows 2000
    Windows XP

    are ALL based off of some OS/2 kernel code!!

    I run nt 4, and therefore, I also run a portion of early OS/2 releases!!

    Microsoft didnt kill OS/2, they helped it to SURVIVE

    1. Re:OS/2 isnt dead...is IS windows by jallen02 · · Score: 1

      Do you have any proof of such extraordinary claims?

      This sounds like a /. conspiracy theory in the making.

      Jeremy

    2. Re:OS/2 isnt dead...is IS windows by danielrose · · Score: 1

      proof? This is slashdot! We don't need no stinking proof!

      --
      i hate pansy republicans
    3. Re:OS/2 isnt dead...is IS windows by ghack · · Score: 1

      did you VISIT the links on the parent? if you dont know os/2 history, dont comment on the story. you just made a fool of yourself.

    4. Re:OS/2 isnt dead...is IS windows by jallen02 · · Score: 1

      No comment.. :-P

    5. Re:OS/2 isnt dead...is IS windows by jallen02 · · Score: 1

      I certainly did read the links.

      "Shortly after this split, Microsoft renamed OS/2 V3 to Windows NT."

      Ok, Ill buy that. Now show me some EVIDENCE that is true.

      That is what I wanted to see, the /. conspiracy theory was just a snide remark. I will admit the links lend more credence to the claim, but I still would like to see some definite way to verify this claim, verification beyond "they did it".

    6. Re:OS/2 isnt dead...is IS windows by ghack · · Score: 1

      the stability of NT? I havent had a crash in months. seems like evidence enough to me...

      The fact that NT can run [very early] OS/2 programs?

      The fact that NT has finicky dos emulation that is practically identical to OS/2.

      I suppose searching the ntos kernel code for "IBM" or something would be even better proof...

    7. Re:OS/2 isnt dead...is IS windows by Bishop · · Score: 2

      Do a search for *os2* on NT or 2k and you will find os2.exe on 2k. I think you will find os2api.dll on NT. It is part of the OS2 compatibility layer. The claims aren't that extraordinary. MS and IBM really were working together on the next generation OS to replace DOS. There was a falling out for many reasons. One that comes to mind it that OS2 was taking too long for MS's tastes. (OS2 was taking too long for everyone's tastes.) If you look through the API functions for OS2 and old the Win32 api you will find many similarities from names right down to parameters. If you can program for OS2 you could switch to Win32 easily. As MS had access to much of the OS2 code large chunks of it ended up in NT 3.51.

      You are making me feel old. This only happened 10 years ago.

    8. Re:OS/2 isnt dead...is IS windows by Anonymous Coward · · Score: 0

      Old versions of NT would sometimes produce a OS/2-style SYS boot error.

      Try this book if you are curious: Show-Stopper! : The Breakneck Race to Create Windows Nt and the Next Generation

    9. Re:OS/2 isnt dead...is IS windows by fataugie · · Score: 1
      Acutally, if you want conspiricy theory, read some MS whitepapers on how to secure NT4 and W2K. High on the list is to remove any referance to OS/2 in the registry and in the system32 folder.

      I used to run OS/2 for years, until it gave up on me

      --

      WTF? Over?

    10. Re:OS/2 isnt dead...is IS windows by toriver · · Score: 1
      Um, it's well-documented that NT has an OS/2 subsystem. From an MSDN article:

      The first design layered the POSIX API set over a slightly extended OS/2 API set. (Originally, the operating system was to have an OS/ 2-style user interface and was to provide the OS/2 API as its primary programming interface. However, due largely to the greater popularity of Microsoft Windows®, Microsoft refocused its strategy and developed the Microsoft Win32® API, a 32-bit programming interface for the development of next-generation applications.) As the design progressed, it became clear that it would result in a system that would not be robust, easily maintained, or extensible. A similar attempt during the development of OS/2 led to considerable change in the base system capabilities, which further strengthened the team's conclusion that this was a poor alternative.

      The next design implemented both OS/2 and POSIX API sets directly in the Windows NT executive. This was an improvement on the previous design, but the large number of oddly structured and tricky interfaces required by this design threatened the goals of extensibility and maintainability.

      The third design implemented OS/2 and POSIX as protected subsystems outside the Windows NT executive. This type of client/server architecture had been successful in the academic community and at other research sites, largely because it decoupled the more volatile services from the operating-system kernel--thus preserving the integrity of the operating system while allowing system services to grow and change as necessary. After analysis and an extended mock up and test cycle, it became clear that this design would provide the robustness, extensibility, maintainability, portability, and performance that the new operating system required.

  86. it failed, because it sucked by jmcnamera · · Score: 1

    this will be mod'ed down for troll bait, but sheesh, I used OS/2 and it sucked.

    It wasn't stable when you ran many apps, it was too easy to write code that locked the system up, and it was gawd awful to install.

    Yeah, I saw the speech rec software for OS/2 ver 4(?). It barely worked.

    Yes OS/2 was cool next to DOS and CPM. But it was way behind the Mac and also behind Windows once Win 95 came out.

    --
    this is not a sig
    1. Re:it failed, because it sucked by Anonymous Coward · · Score: 0

      The only way an application could "hang" os/2 was if it stopped responding to GUI messages when it had focus. IBM fixed this problem in Warp, where you just pressed control-escape and you could kill the offending process (much like Windows XP where you bring up the task manager and kill the process that is hanging up the GUI).

  87. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  88. The lesson with OS/2: make it work ! by stain+ain · · Score: 2

    I bought WARP as a Christmas present, the first time I paid for retail software instead of copying it, so you can imagine I really had faith in OS/2, I wanted to get rid of Windows forever.
    But, it never worked for me, I had some strange BIOS/HD combination that made it impossible to install.
    After many failures and talks with support, I gave up.

    I bought a new computer after some months, but I was so bored with OS/2 that I never tried again and of course, now I regret having spent money and time in something that I never used.

    If Linux is ever to succeed, the first time experience will have to be completely painless, that is, easy to install, easy to run, visually appealing, no troubles with that new device just bought...

    I run Windows and everything works fine for me, if I change, I want to be able to read my documents, play my music, use my LAN adapter, my new digital camera, my webcam, my printer at its full capabilities, I want the energy settings to work, I want to connect my cellphone to my address book... everything that works now has to work in Linux and then, provide something extra so that switching to Linux is worth it.

    I'm affraid right now, I cannot change, (and I have tried!), but my LAN doesn't work, no drivers for my digital camera, the same for my cellphone, the sound is crappy... I know it's getting better, but Linux, still, is not good enough for me and many, many other people. I hope it changes...

  89. IBM execs aren't smarter today. by Futurepower(tm) · · Score: 2


    In my opinion, IBM top executives with little technical education killed OS/2. They called OS/2 "Warp", a term for something so bent that it is useless.

    They aren't any smarter today. They have contracted with their ad agency for those stupid DB2 ads which show dorky guys in space suits. The ads show the lack of knowledge and interest of the ad agency writers in IBM's products. The IBM execs are not smart enough to know they're horrible.

    Only technically educated people can manage a technically educated company.

    --
    Bush's education improvements were
  90. Hear hear! by xtal · · Score: 2

    Excellent comment and I agree completely. OS/2, like MacOS X, has that polished, finished, and well thought out feel to it that I was missing in a OS for a long time. Lack of applications and hardware support is what killed off OS/2, but with the pile of open source applications being rapidly ported to Cocoa/Carbon on OSX, and apple's excellent hardware compatibility - e.g. what's there, works - will help it to overcome the historic stumbling blocks of a new OS.

    --
    ..don't panic
  91. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  92. There was plenty wrong with OS/2 2.x by lseltzer · · Score: 2, Informative

    OS/2 2.x was a great piece of software in many ways, but IBM missed the mark on several important points, some of which the linked story gets.

    For example, it should be perfectly obvious by now, and was to many even at the time, that preloads were a critical factor. Microsoft appreciated this much earlier than IBM, who couldn't even convince their own PC company to preload OS/2. Remember that OS/2 2.0 came out long before Windows 95 - If OS/2 really was a better Windows than Windows, like IBM claimed, no threat Microsoft could make should matter. The IBM PC Co should have been happy to preload OS/2 2.0 and dump Windows 3.x. (Remember IBM even had their own DOS on the same code base, they didn't need Microsoft at all.) The fact that IBM PC Co could never be convinced to preload OS/2 is damnimg evidence that it was never all it was cracked up to be.

    There were dozens of important problems. Among which:

    • 32-bit OS/2 driver support lagged badly behind Windows driver support, which was a far higher priority for every device vendor out there. For the first year or so there were maybe two graphics cards with OS/2 drivers shipping, which meant that you were stuck with standard VGA on any other system (I don't think they had a standard SVGA 8x6 then).
    • The minimum RAM requirement for OS/2 was 4MB, a high-end requirement at the time. By the time Windows 95 came out in 8/95 4MB was mainstream, but it was a real problem for IBM, especially since they were trying to sell into the existing installed base.
    • The OS/2 Netware driver shipped very late and was a steaming turd when it did ship. Good Netware support was about as critical as can be, so it's hard to see how IBM didn't place a higher priority on this. IBM's own LAN Manager networking was rock solid once you had it set up properly, but as others have pointed out, it was a bitch to set up.
    • This is a matter of taste, but I always thought the Workplace Shell was an awful user interface. The context menus were crowded with complicated and irrelevant distractions. You really needed to use HPFS for your file system because the disconnect between the naming system in OS/2's FAT and the WPS was complete. Fortunately, HPFS was a good file system for its time (invented at Microsoft by the great Gordon Letwin), but if you wanted to dual-boot from OS/2 to DOS/Windows you were screwed.

    Microsoft was hardly friendly to OS/2 after it washed its hands of it in the 1.3 days, but all the big reasons for its failure in the market have IBM's fingerprints all over it. Them and a gang of fanatics that make the worse Linux advocated look downright boring.

    1. Re:There was plenty wrong with OS/2 2.x by NutscrapeSucks · · Score: 2

      IBM's own LAN Manager networking was rock solid once you had it set up properly, but as others have pointed out, it was a bitch to set up.

      Just for the outsiders, IBM's networking was the faimilar NetBEUI or SMB-over-TCP/IP. Except they had some Dynamic DNS thing in addition to NBNS (WINS). As pointed out by the Samba guys, "SMB sucks, it really really sucks". Still, I'd take the NT implementation of this over the OS/2 version any day, where it's pretty much plug-n-play.

      I lived through the pain of the NetWare drivers -- they didn't even use the standard NDIS hardware drivers, but instead required a seperate ODI card driver and some sort of bitchy NDIS-ODI shim. They also liked to forget where the NDS tree was and crash the system.

      Not only was IBM's networking a bitch to setup, it was even a bitch to order. You had to understand a mess of TLAs and ETLAs and FRU numbers to even get right software. Little things like TCP/IP support cost more than the entire OS. The administrative tools were some of the fuglist things I ever pushed a mouse pointer at.

      It was so bad that I'm convinced that they actively were discouraging you from putting OS/2 on a LAN -- Just run your 3270 client and be happy.

      Too little, too late, IBM fixed these issues with the Warp Connect Edition. By then, we'd converted our OS/2 boxes to NT.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
  93. 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.
    1. Re:and Windows in an Elevator is a scary thing! by LadyLucky · · Score: 2
      Heh, the elevators in our university keep breaking down. After II enquired, i was told that the valves in the computer needed to be replaced quite frequently.

      Oh my

      --
      dominionrd.blogspot.com - Restaurants on
  94. So why are KDE and GNOME so bent on being Windows? by dpilot · · Score: 2

    It still bugs me that KDE and GNOME still seem to be aspiring to be Win-clones. IMHO, the OS/2 WPS is still way better than Win-anything. But even if I want to accept that something better than the WPS can be done, it simply isn't. The "advanced" desktops of Linux are just chasing Windows.

    At least in the desktop arena, Microsoft has nearly completely destroyed innovation, unless you want to call minor variations in colors, icons, and product bundling innovation.

    I run DFM, and have played a little with the ROX filer.

    --
    The living have better things to do than to continue hating the dead.
  95. 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?

    1. Re:Crap by NutscrapeSucks · · Score: 2

      OS/2 always did talk to the mainframes very well.

      I always saw this as the core flaw in IBM's marketing that killed OS/2 and almost killed the entire company. While the world was going ga-ga over Client-Server computing, IBM was slogging forward with this this mainframe-centric (SNA) view of computing that nobody outside of a few Big Blue shops was buying into.

      Consequentally, OS/2 would come with various terminal emulators and such, but a LAN client or a TCP/IP stack cost extra $$$ and wasn't easy to order. Meanwhile MS was pushing out products based on TCP/IP, RPC, ODBC, and agressively marketing into the small server space, and UNIX ("the network is the computer") use was exploding.

      IBM acted like the PC was nothing more than a glorified dumb terminal and seemed to want to 'keep it it's place' in order to protect their fat midrange profit margins. That probably explains their completely half-hearted software development for the platform, and their unwillingness to offer anything that looked like 'server' hardware in PC space.

      When IBM finally figured out they were getting slaughtered by UNIX on the high-end and Windows on the low-end, they moved quickly. But by then it was too late for OS/2.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    2. Re:Crap by Reziac · · Score: 2

      I understand that a lot of ATMs run on a stripped-down embedded OS/2 kernel.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    3. Re:Crap by sheldon · · Score: 2

      "2.1 was the ultimate in stability and performance for OS/2. "

      That's not true at all. I worked for a Fortune 500 company at one time with OS/2 deployed everywhere. We had much more success both in terms of performance and stability when upgrading client desktops to OS/2 3.0.

      And these were "official" IBM machines. Lot's of Model 77's, PC-750, etc. All of these machines came shipped pre-installed with OS/2, so I don't understand this other point of yours.

      You are correct on the Win95 thing, as well as native application support. OS/2 had it's day in the sun, failed to take advantage of that and ultimately lost.

    4. Re:Crap by roseanne · · Score: 1
      Yes. One HSBC ATM rebooted in front of me, and I got a chance to take a *good* look at the screen. In fact, it was running OS/2 1.3. And, interestingly, it had *no* IBM copyright notice, just a (C) Copyright Microsoft notice. That's what took me by surprise. In fact, IIRC, the screen looked just like this.

      Anybody know who gets paid every time one of these is sold? MS? Would be kind of ironic, if so.

    5. Re:Crap by Reziac · · Score: 2

      Well, I'll be dipped. That's a most interesting discovery!

      And thanks for the screenshot link.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  96. More companies are advertising linux by HanzoSan · · Score: 2


    Which means more advertising dollars, and more ads. Sure they arent as organized or as planned, but everyone has heard of linux even if they dont know exactly what it is yet. Thats all you really need.

    --
    If you use Linux, please help development of Autopac
  97. Europe rocks. by nougatmachine · · Score: 3, Funny
    I think I might just have to move to Europe. My favorite part of that article was when it quoted John Dvorak saying he didn't like Europe because they always did their own things and bought Amigas, Ataris, and OS/2s. You know, the cool stuff that the rest of the world is too timid to use.

    So if I got this right, Europe actually gives a shit about their computers. My plane leaves in five hours ; )

  98. LIES OS/2 March 1897 = manuals and OS for sale by Anonymous Coward · · Score: 0, Troll

    LIES OS/2 March 1997 = manuals and OS for sale to developers.

    March 1987

    Check Wallstreet Journal and other magazines if you dounbt this fact.

    The Mac II (supporting multiple montitors, ability to use multiple simultaneous keyboards and mice and much more) shipped two months after OS/2.

    But this crappy liea bout OS/2 shipping in March 1992 is crap.

    Its buggy slow as hell history goes way back to 1987.

    Slow ? OS/2 could only transfer SCSI data in commands packets of 4Kilobytes per gulp!!!! The Mac II could hanfle 16 megabyte transfers and was over 6 times faster.

    Buggy? OS/2 could only support interrupts from serial protocols in little packets of minimum of one interrupt per two bytes safely without losing data. The Mac II and its full color OS in that year could handle interrupts for serial a few different ways but could handle Zmodem out one port and in the other serial port on the same machine at 38400 baud.

    The OS/2 was a command line oriented pile of swill in 1987 and the Mac supported 8 meg of RAM for a single program, and had digital sound, animation grade video calls, and much more.

    OS/2 programming manuals in 1987 cost 5000 dollars and came with free video tapes of lectures on OS/2 that IBM had no time to put into paper notation.

    The Mac had Inside Mac volumes 1 through 4 already on store shelves.

    But this crap about OS/2 coming out in 1992 is a lie.. they just want to forget the half-born bastardized lame versions for the first 5 years that actually SHIPPED.

  99. History by Eric+Green · · Score: 3, Insightful
    I was there, I was not doing homework, I was operating off of 15 year old memories. The fact that 15 year old memories are not 100% accurate is not surprising. I do remember the long boot times though, at least on the PS/2 Model 50's. Your notion that they booted as fast as DOS is more probably historical revisionism than a 1 year slippage in date in 15-year-old memories.

    The ISA machines in the PS/2 lineup came after some of IBM's major customers refused to buy a MCA version of the computer, I remember them later being re-named as PS/1 computers in an attempt to flog the PS/2. The MCA-based PS2 line did NOT survive until the mid 90's -- it was long dead by that time -- by the mid 90's IBM had migrated to PCI like everybody else, and had computers named "PS/2" but they were just generic clone machines.

    I see no reason to do research about something I lived through when you're the only anal twit on Slashdot who cares. I'm sure that nobody else here cares that the PS/2 was released in 1987 rather than 1986. The point is that IBM was trying to hijack the personal computer market -- not that it was 1987 rather than 1986.

    -E

    --
    Send mail here if you want to reach me.
    1. Re:History by tkrotchko · · Score: 2

      "PS/2 Model 50's"

      Just to remind people, PS/2 Model 50's were 10mhz 286 machines and usually shipped with just 1M of memory.

      They weren't particular speedy even when released, and I remember them primarily as being too slow to even run Windows 3.0 very quickly.

      I remember the boot time on a PS/2 50 for OS/2 was in the order of 2-5 minutes, whereas DOS could probably boot up in 30-45 seconds.

      My memories are old, but I do remember it as being a well-engineered, but slow machine.

      --
      You were mistaken. Which is odd, since memory shouldn't be a problem for you
    2. Re:History by Anonymous Coward · · Score: 0

      The MCA-based PS2 line did NOT survive until the mid 90's -- it was long dead by that time -- by the mid 90's IBM had migrated to PCI like everybody else

      IBM relaunched their PC lineup in 1994 or so with the "PC 300". Those machines shipped with ISA and a PCI riser card but had the option of replacing that with an MCA risercard. IIRC, those were the first IBM machines to support PCI -- everything before was MCA or ISA.

  100. The Sad Parable of OS/2 by britton · · Score: 1

    Comments to the final paragraph....

    >Post Script: In the years since this article was >written, independent developers have kept OS/2 on >life support,

    Not to mention a plethorial of regular fixpaks since 1996 from IBM... latest Jan'02... and IBM has stated support thro'2008.... so OS/2 will take another 10 years to actually... looks like I will be dead before OS/2....

    >with projects such as eComStation, which seeks to >produce updated versions of the operating system >and applications that run under it,

    Hardly 'seeks'... they are doing it, it is real, and it works....

    >and Project Odin, which works to provide a way to >run 32-bit Windows applications under OS/2. But >claims that OS/2 is alive and well are mostly of >the sort of claim that imparts such characteristics >to Elvis Presley.

    Wasn't he one og the Beatles...?
    Running fine on SMP, with JFS, and blows Linux and windozes out of the water in terms of high volume multitasking...and running winbloze apps under Odin quite necely thank you....

    >The ironies abound: A hopeful community waits in >hope that a federal judge will slap down Microsoft >and level the playing field. Quality even now does >not govern the success of operating systems or >application software.

    It is of no interest to me what US psuedojustice system attempts to do to mickeysoft.... the point is I do not, will not, and never have done business with mickey soft.... because I have chosen to use a better alternative.....

    >IBM, which failed with its Microkernel project, now >offers a single operating system with all of its >computers except the consumer desktop models. A >better desktop operating system exists -- John C. >Dvorak mentiuoned it, and this site is devoted to >it -- and already the talk is that it's only good >for businesses and less of a desktop operating >system than even OS/2 was. What was it about "those >who fail to learn from the lessons of history . . >."?

    Singularly appropriate last sentence....
    why indeed should so many continue to pander to the greatest organised crime in commercial history, and continue to buy mickeysoft overpriced abandonware...
    (Buy XP today, and get your incompatible upgrade same time next year...LOL)

    An otherwise very informative article was ruined by the authors laziness in being unable to do even one hours research into the current state of OS/2... if you are going to comment on something at least have the courtesy to your readership to actual know something about what you are attempting to pontificate upon....

    Bloody amateurs...

    1. Re:The Sad Parable of OS/2 by Anonymous Coward · · Score: 0
      i wrote the article in question. and i have ecomstation running on a machine next to me right now. even dealt with the long and insane registration code. have the latest smartsuite for OS/2 -- done through a translation layer oodles better than the miserable micrografx mirrors that shipped with 2.0 and everything since. the original story was written on describe as shipped on the describe voyager cd. and believe me, it was no pleasure to me when i interviewed soyring and the others in 1997 and was told that desktop OS/2 users should pretty much go shit in our hats.


      but the fact is, OS/2 is dead except in embedded systems, and has been for close to five years. i take no joy in saying that, but i take no joy, either, in the fact that it's true. i agree with posters who aver that there is not to this day a UI that approaches the wps. i wish that ibm would turn it loose, even as i wish that jim lennane would release the code to describe. but OS/2 today is, sadly, a look back, and looking back in the computer field for anything other than lessons is to give up entirely.

      dep

  101. OS/2 came out in 1987 and was crap. by Anonymous Coward · · Score: 0

    You said OS/2 was cool or had features better than a Mac"

    LIES !

    OS/2 March 1997 had manuals and OS for sale to developers.

    March 1987

    Check Wallstreet Journal and other magazines if you doubt this fact.

    The Mac II (supporting multiple montitors, ability to use multiple simultaneous keyboards and mice and much more) shipped two months after OS/2.

    But this crappy lie about OS/2 shipping in March 1992 is crap.

    Its buggy slow as hell history goes way back to 1987.

    Slow ? OS/2 could only transfer SCSI data in commands packets of 4 Kilobytes per gulp!!!! The Mac II could hanfle 16 megabyte transfers and was over 6 times faster.

    Buggy? OS/2 could only support interrupts from serial protocols in little packets of minimum of one interrupt per two bytes safely without losing data. The Mac II and its full color OS in that year could handle interrupts for serial a few different ways but could handle Zmodem out one port and in the other serial port on the same machine at 38400 baud.

    The OS/2 was a command line oriented pile of swill in 1987 and the Mac supported 8 meg of RAM for a single program, and had digital sound, animation grade video calls, and much more.

    OS/2 programming manuals in 1987 cost 5000 dollars and came with free video tapes of lectures on OS/2 that IBM had no time to put into paper notation.

    The Mac had "Inside Mac" volumes 1 through 4 already on store shelves.

    But this crap about OS/2 coming out in 1992 is a lie.. they just want to forget the half-born bastardized lame versions for the first 5 years that actually SHIPPED.

    And saying OS/2 EVER was better than a mac for a single moment in history is a sick joke.

    Cite a feature and date : and do not discount MPW from Apple.

    1. Re:OS/2 came out in 1987 and was crap. by deviator · · Score: 1

      were you replying to my post??

      I never said the Mac sucked; I just said it and its users were on a different planet from PCs. :) And the first several versions of OS/2 really did suck (and they were 16-bit) - OS/2 1.3 was the first *good* version. I was lucky enough to use it a couple of times - that thing was solid.

      Macs had dual-monitor, dual-keyboard, better I/O, better sound, better graphics for years... the list goes on and on. But the OS did kinda suck until Mac OS X - it was kinda toylike.

  102. 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.
    1. Re:1.0 vs. 2.0 by Anonymous Coward · · Score: 0

      One story I read somewhere was that Microsoft attempted to sell Windows to IBM many times in the 1980s, but IBM was too struck with it's TopView thing. Also, before IBM and Microsoft divorced, there were negotations to sell the whole company to IBM.

      One of the sore points with OS/2 was that Microsoft had full rights and control of DOS, but was just a contractor on OS/2, and IBM called all the shots.

      The history would be very different if OS/2 1.x would have sold worth a damn. As the article pointed out, by 1991 or so, the "stench of death" was already pretty heavy.

  103. No, it wasn't by smoondog · · Score: 2

    The interface could be plugged in much like a Unix interface. I remember they had a win 3.1 interface that made OS/2 look exactly like windows 3.1!(?) Also, the default interface, being totally object oriented, was infinitely configurable. True oo is really cool for an interface, things can be put anywhere and configured anyway you like!

    -Sean

  104. Have you heard the 3 R's of Windows? by os2fan · · Score: 2
    Reboot - Reinstall - Rebuild.

    Gee, I installed Windoze way more times than OS/2. It's given out as a "standard fix for anything."

    And you obviously have not seen NT install :)

    --
    OS/2 - because choice is a terrible thing to waste.
  105. Article and posts are wrong... by rufusdufus · · Score: 2

    As an employee at MS at the time, working on DOS and Windows, with many friends on OS/2 I can only say everyone is just wrong. I had written a big article about it, but decided it was too big a pain to set everyone straight; just know this, what you think you know about OS/2 and its relationship to Microsoft are almost certanly wrong.

    1. Re:Article and posts are wrong... by Anonymous Coward · · Score: 0

      I find the stories posted to this thread facinating, so I'd be interested in hearing yours. What's the point in standing in the corner and saying "You're Wrong. Wrong I tell you!"? Make your case.

  106. OS/2.... by Anonymous Coward · · Score: 0

    Just wasn't that good. It's about time someone said it. Yea. it had some nice features but it was a pain to install, in fact, I only got OS/2 Warp to install correctly *once* in my life, which covers about 10-20 attempts on various hardware.

    Driver support was dreadful, the GUI was good conceptually but was often too cluttered to really be effective.

    It was also pretty slow, not any slower than Windows but, as this article does point out, most people stuck with DOS apps because of speed issues, and even if OS/2 had been really popular I think a lot of people would have kept using DOS anyway.

    So there it is. OS/2 was just never very good. It had potential and a lot of people confused that with quality. Not all together unsimilar to what killed linux's chances of making an impact on the desktop. Progress and potential are NOT the same thing as a usable product.

  107. os/2 still gets two thumbs up by Anonymous Coward · · Score: 1, Interesting

    This is one of the poorer "why os/2 is dead" articles constantly being rehashed. Got Ecs running on my file, mail, http and ftp servers, and all is good. Why not xp - i don't waiste money on things i don't need. Why not Linux - i have a life and i want to keep it that way

  108. Not really, no. by Anonymous Coward · · Score: 0

    "Ten years ago IBM was considered the big monopolist threat in both hardware and software. "

    Not really. Maybe 20-30 years ago, but by 10 years ago, it was pretty clear that Microsoft had beat the snot out of IBM on the low end.

    The funny part is that when the Apple ][ was the most popular computer, everybody said "ooooh, just wait until IBM releases their minicomputer (that's what we called them), they'll own the market!". Never happened.

    IBM was a big player in the PC market for about 3 years. Their day is past.

  109. EComStation by Anonymous Coward · · Score: 1, Informative

    The latest release of OS/2 is by Serenity Systems.

    Take a look at www.ecomstation.com.

  110. OS/2 - Win3.x - Win95 Gui by BakaMark · · Score: 1
    It still bugs me that KDE and GNOME still seem to be aspiring to be Win-clones. IMHO, the OS/2 WPS is still way better than Win-anything.

    The desire to try and emulate the Windows GUI way of doing things is so people who are used to the Windows GUI don't have a harder time in picking it up.

    The Gui that OS/2 originally used, and Windows 3.0 were so alike that it was not that hard to move from one to the other.

    Both were expanded to include extra features, but I reckon that both Microsoft and IBM did not want a product that looked and felt like each others.

    So there was a redevelopment effort of the GUI on both sides. The changes in the OS/2 GUI were small between versions (I have not had a good look at OS/2 Warp though).

    However Microsoft had their "Chicago" project, which was eventually called Windows 95. This was a complete redevelopment of many aspects of the GUI interface, in the pursuit of being more "user friendly". Nowdays the GUIs of Windows 2000, et al, are still referred by some people as the Win95 GUI.

    At the time that Windows 95 was released, followed by NT 4.0 later. The GUI was .. a problem for organisations that already had a large number of staff trained on, and using the existing Windows 3.x GUI interface. This meant the use of "Program Manager" and "File Manager" which OS/2 also had, etc. Win95 had the start button, and task bar.

    The Windows 95 interface was supposedly easier to get around for a joe bloggs, who knew nothing about computers, and was just dragged off the street. I remember a promotional video shown years ago that showed two complete idiots trying to find and open notepad on a Widnows 3.x and a Windows 95 GUI. It still required prompting for both of these people, but it appeared blatantly obvious at the time that the person helping the idiot #2 using the Windows 95 interface, was being a little more helpful.

    However this video meant nothing to the corporate managers out there who had to completely retrain their staff on using the new GUI system. After that Microsoft have made no real effort to try and change away from the start button, and task bar. Besides it makes the GUI look more like an Apple Mac anyway.

  111. From a shallow perspective by wytcld · · Score: 2

    I read the press, ran out and bought an early version of OS/2 (at that point in life I ran CP/M with ZCPR, DR-DOS, PC-DOS, MS-DOS, Win 3.1 with Norton Desktop, NDOS). The friggin OS/2 desktop was ugly. Now, at that time I did most of my work without a GUI, and DR-DOS + NDOS was just fine for that. But when I went into a GUI it was to do something that really needed it - graphic design work - and why would I do that in a GUI that was ugly? It's a different part of the brain, and it wants to be happy in its workspace.

    Then I grew up to Solaris and Linux, and spend most of my working hours in xterm - but will still boot into Win 95 if I really need Pagemaker or Freehand or whatever. But I'll never believe OS/2 was a superior GUI - may have been a superior underlying OS, but the market momentum was about the GUI then. It lost to Windows because IBM actually managed to present something uglier. It's like a really fertile woman who never bathes - great if you're just rating fertility, but do you want her to have your kids?
    ___

    --
    "with their freedom lost all virtue lose" - Milton
  112. Kind of pretty in a psychodelic way. by Pope · · Score: 1

    Ah, so the Apple execs REALLY loved it, eh?

    --
    It doesn't mean much now, it's built for the future.
    1. Re:Kind of pretty in a psychodelic way. by Anonymous Coward · · Score: 0

      Apple was really scared of OS/2 PM (partially due to things like PageMaker support) and completely missed the fact that Windows was getting pre-installed on a gazillon boxes.

      No offense to the parent, but I tried PageMaker on OS/2 (IBM dumped a bunch of free PS/2s on my Uni) and it was offensively bad relative to the Mac version.

    2. Re:Kind of pretty in a psychodelic way. by Pope · · Score: 1

      I was implying that the Apple execs were all stoned hippie types.
      Lame, yes. Whatcha gonna do...

      --
      It doesn't mean much now, it's built for the future.
  113. Re:So what? Only versions 1.3, which stunk anyway by EMIce · · Score: 3, Interesting

    "OS/2 1.30 (SE and EE) was the first version which was written entirely by IBM. There was still some Microsoft code in it - that would not go away for a couple years yet - but all of the new code and a good portion of the existing code for OS/2 1.30 was written by IBM. As a result, OS/2 1.30 was smaller and faster than previous versions, more stable, and there were far more device drivers available, though still not nearly enough."

    This is from your own link #2. Many users agree that the quality of OS/2 peaked around version 2.1. At this point there was very little Microsoft code left in there. Reading the original article that \. linked to, these early releases weren't very good at all. Only after IBM re-wrote it and brought it beyond the simple *text-mode* support of 1.0, did it gain a following. If Microsoft was able to create a system as good as the OS/2 written by IBM, it wouldn't have tripped and stumbled through NT 3.51 and 4.0 before releasing something decent like 2000. This comment sounds real juicy at first glance but is highly misleading. Sheesh, if only I had some moderator points.

  114. Re: I mean only versions less than 1.3 by EMIce · · Score: 1

    Correction -
    The slash engine took out the less than sign before the 1.3 in the subject line, since it can be interpreted as an html tag. I meant to say "So what?, Only versions (less_than_sign)1.3, which stunk anyway."

  115. Give Wine a chance by marm · · Score: 3, Informative

    Wine is considerably more, err, byzantine.

    Hardly surprising given what the OS/2 Win16 compatibility layer was: Windows 3.1 run in a virtual 286 (thus in standard, not enhanced mode, which is why some apps wouldn't run), without the Program Manager. IIRC there were two versions of OS/2 you could buy at one point, one with a cut-down copy of Win3.1 included (that Microsoft let them include it was a legacy from agreements signed during the Microsoft/IBM co-operation days, although Microsoft was still getting a licence fee from it) and a cheaper version which asked you for your Win3.1 disks during installation.

    A much more fair comparison would be with Win4Lin, which attempts to do much the same thing with Windows 98, i.e. run it in a virtual machine without Explorer, and display the application windows on an X desktop.

    Win4Lin is actually a more impressive achievement, as in order to run Win98 it has to virtualize a 386 in protected mode, which is hard, as opposed to virtualizing a 286, which is really really easy (the 386 and above has hardware especially designed to do this).

    Either way, whether you run Win16 apps in OS/2 or anything Win98 can run in Win4Lin, you have paid the Microsoft tax and are running Microsoft code.

    The other approach to running Windows software on other systems is to reimplement the Windows API. Some projects that do this are basically ports of Microsoft code (like Mainsoft's MainWin, which is used in the HP-UX and Solaris versions of IE). Just two projects have ever done this without using any Microsoft code: Wabi and Wine.

    Wabi was very successful in its time, providing a complete Win16 layer on lots of UNIXes, and something that even Wine doesn't do: an i386 emulator for people who want to run Windows apps on non-IA32 architectures. Unfortunately it never got much Win32 support and, being a proprietary product, died a death a few years ago.

    So we're left with Wine, the most ambitious Windows emulation project of them all: efficiently reimplementing all of the Win16 and Win32 APIs and ABIs, without any Microsoft code, and all as free software.

    it seems like the developers are more interested in using the code for proprietary emulation for running specific programs (games, plugins) or porting (corel stuff, etc.) than producing a general, Free, universal windows emulator.

    They are effectively rewriting about 30% of Windows, with only Microsoft's published documentation and reverse engineering as references. They have to be bug-for-bug compatible (this is the real killer). The core team is absolutely tiny compared to Microsoft's Windows development group.

    Is it any surprise that they are trying to do what they can as they get things working? They are doing stuff that people would have thought near-impossible just a couple of years ago, even by an extremely well-funded corporate behemoth like Sun or IBM.

    It would seem that Wine is the most underappreciated of all the major free software projects out there, which is such a shame given its promise.

    Give Wine some time. I know it's been a long wait already, but the pieces are falling into place right now, and it shouldn't be too long (measured in Wine time, of course ;) before Wine gets to version 1.0. When that happens, expect repercussions for years to come.

  116. Why buy OS/2? by Chris+Colohan · · Score: 2, Interesting
    When I bought my first PC (I was a former Amiga addict) I had decided I wanted to run OS/2 on it. Being a poor high school student, I went comparison shopping on prices. Here is what I found in the stores in Toronto:
    • OS/2 2.1: $199
    • Windows 3.1 OEM edition: $45
    • OS/2 upgrade from Windows: $50

    At the time I didn't want Windows, but the pricing scheme forced me to buy it anyways. Rediculous. Once I got it I discovered that the memory requirement of 8MB was a joke -- OS/2 was never happy doing any real work with less than 32MB, and as a student I could never afford to buy that much RAM...

  117. I regret selling my copy by idiotnot · · Score: 1

    I bought a copy of OS/2 Warp 3.0 in 1994, shortly after it came out. I liked it quite a bit, then.

    It did take me awhile to get it running.

    - Sound Card/CD gremlins. I had an Ensoniq sound card, which was pretty damn nice at the time. It supported a standard Panasonic 2x CDROM. All of this stuff came in a package by the now-defunct company Reveal (anyone remember those guys?). The card didn't really do anything via hardware; you'd have to boot DOS, initialize the card, then do a quick three-finger salute to get OS/2 to recognize the drive (had to do this with Linux, too). I finally gave up and bought a SB16.

    - HPFS. It was very, very cool at the time. No, it wasn't considerably faster than FAT (as so trumpted by IBM...and I did benchmarks on this to test). Of course, if you didn't buy the expensive version with a second copy of Windoze, you had to have a FAT partition somewhere. And that none of the existing Windoze applications could use long filenames....

    - REXX. I enjoyed messing around with it quite a bit. I'd like to see a nice version of it for Linux.

    Once I got things working with OS/2, I used it for several months, until MS decided it liked me and started giving me free software (I beta-tested MSN.....so shoot me). I also started running Linux about this time, ran short on disk space, and OS/2 went away.

    A couple of years later, with more RAM and more disk space, I re-installed OS/2 on my old machine. On a P-66 with 24MB, it absolutely flew....totally blew Win95 away. Netscape 2.something ran fine, as did the 16-bit Win apps I was still running.

    I ran short on cash one day and decided to auction my copy off. I think I sold it for fifteen bucks. Now, that old P-66 is sitting in the corner. I wish I had a copy to install on it. Instead, I think it'll probably become a diskless workstation running Linux.

    Advertising.....Anyone remember the "IBM OS/2 Warp Fiesta Bowl?"

  118. Judge Thomas Penfield Jackson by untulis · · Score: 1

    It's an interesting reversal (and one not noted in the article since it was written in 1997) that the "freshly inked rubber stamp"ing Jackson, who's made out to be in MS' pocket compared to the quixotic Judge Sporkin ends up in pretty much the same straits as his predecessor: exposing Microsoft for who they are, but then being marginalized by an eager Justice Department and Administration. I wonder what Judge Kollar-Kotelly's opinion will be in a few years.

  119. VMS +1 = WNT, alphabetically by jelle · · Score: 2

    V+1=W
    M+1=N
    S+1=T

    take the VMS people, make another OS: WNT, Windows NT

    Of course everybody already knew that, so I'll probably burn some karma for getting 'redundant' rating here...

    --
    --- Hindsight is 20/20, but walking backwards is not the answer.
  120. such fond memories of nostalgia by Anonymous Coward · · Score: 0

    can we try to revive CP/M, just for a little while? Oh, when 16k was so much more RAM than anyone needed.

    Get over it.

  121. It's funny. by Decimal · · Score: 2

    IBM's OS/2 commercials just showed a bunch of guys crowded around a monitor going "Wow! I can't beleive it can do that! Wow that's amazing!" but the Camera view was from behind the monitor so you didn't see anything they were doing. Then it had some catchy IBM slogan and that was it."

    Looking back, I find it laughable how computer-illiterate I was when those came out. I don't think I even knew what an OS back then. When I all of those people huddling around the screen going "Ooh! Ah!" I remember thinking: "What the hell are they looking at? Porn?"

    --

    Remember "Bring 'em on"? *sigh
  122. Judge Jackson by humblecoder · · Score: 1

    Here is an interesting tidbit that I gleaned from the article. In the first anti-trust investigation of Microsoft (circa 1995), the original judge disapproved the weak settlement that had been reached between Microsoft and the DoJ. However, the appeals court removed the original judge and replaced him with none other than Judge Thomas Penfield Jackson!

    From the article:

    "The following June, a federal appeals court ruled that Judge Sporkin had overstepped his authority and assigned the case to a different judge, Thomas Penfield Jackson, who had a freshly inked rubber stamp."

    It is ironic that in the second anti-trust trial, it was this same Judge Jackson who was removed from the case on appeal.

  123. Hi, MS shill by operagost · · Score: 1

    I don't care what you think IBM 'told the world', it didn't happen. Just because PS/2 and OS/2 share 75% of their characters doesn't mean they're tied together. OS/2 from version 1.0 ran perfectly fine on non-IBM machines, and MS-DOS ran on PS/2 machines, if you were stupid enough to choose it over the superior DR-DOS or PC-DOS.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
    1. Re:Hi, MS shill by Anonymous Coward · · Score: 0

      Hmmm -- the general OS2er argument is that IBM blew the marketing big time. But you seem to be implying that was not the case and OS/2 failed on it's merits.

    2. Re:Hi, MS shill by Zeinfeld · · Score: 2
      I don't care what you think IBM 'told the world', it didn't happen. Just because PS/2 and OS/2 share 75% of their characters doesn't mean they're tied together.

      The IBM VP in charge of the PC product line served notice that OS/2 would only support Microchannel in future releases, that IBM would 'eliminate' the clone manufacturers.

      I am sorry, but calling people shills does not support your case. The fact is that when the industry decided to go down the Microsoft route it did so for tactical reasons. We knew we could not trust IBM, they had shafted the computing industry for thirty years. IBM only got out of the anti-trust case in the end for the same reason Microsoft got off - the case was dismissed by an incomming Republican president as a campaign pay off.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
  124. Linux VS OS/2 Warp -- A survivors tale. by StormyWeather · · Score: 2, Interesting

    The year was 1994. I was still kind of newbish about operating systems, but had a real burning desire to learn. My little Packard Bell 486 DX2-66 with 4 megs of memory came preloaded with Windows 3.1. I was working at Babbages at the time, and we had just recieved a shipment of OS/2 Warp, including a couple free(beer) versions for employees to take home with them so we would know more about the product to sell it. A friend of mine had just gotten in his 85+ boxed set of linux slackware floppies in the mail (kernel version 1.1.18 if I remember correctly but it could have been prior). We sat down side by side that night, him on his 386 with 2 megs of memory, and me on my 486. OS/2 took me a good 4 hours to install, mainly due to the fact that I was so limited on memory, however he had linux up and running within what seemed to be minutes. I was aghast at how blazingly fast he was able to start doing things while I was still watching the stupid install screen. I had used the HPUX system at school and remembered all the neat stuff I learned I could do just from a telnet session, and that was all she wrote. That evening I was running slackware on my little POS Packard Hell, and the OS/2 box was in the trash can.

    What killed OS/2 more than anything was the people like me with 4 megs of ram, back when an 8MB stick would cost you around 400(us) dollars. The timing of 95 hit perfectly with manufacturers(coincidence?) rolling out systems with 8 megs or more memory.

    On a side note I trashed my linux install the day after I installed it with a recursive delete and had to reinstall windows to have an operating system. It didn't detour me from using Linux, just made me accountable for my actions from then on out. I never made that mistake again (just one very similar; ).

  125. Windows 3.x I/O by operagost · · Score: 1

    Windows 3.x couldn't even run serial communications over 19200 bps reliably without a third-party driver. I've seen it in my modem manuals from the time. I used one written by some Joe Programmer and distributed for free that worked great up to 57600.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  126. IMPORTANT message for all OS/2 programmers by marat · · Score: 1

    The work is going on for porting OS/2 to ReactOS (Freeware NT clone). For me this seems to be the most promising project. There're already a lot of developers for OS/2 subsystem as well as horde of them for the OS itself. Site is under construction but mailing list is >20 messages a day.

    For all who wonder - there's still life in OS/2 though not too much of it. OS/2 links:

  127. 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.

    1. Re:OS/2 Screenshots by Anonymous Coward · · Score: 0

      The part about WLO (Windows Library for OS/2) was interesting. I'm assuming this became NT's WOW, which I always thought was a less flakey (and less compatible) way to run Win16 apps than WinOS2.

    2. Re:OS/2 Screenshots by praedor · · Score: 2

      Those are really REALLY old screenshots. They look NOTHING like OS/2 Warp, Warp Connect, or Warp 4 (the last real release). Those screenshots gives one the incorrect impression that the GUI was crude and ugly. It was most assuredly not. The GUI on OS/2 was fantastic, with features that are still unmatched by any other GUI on Macs, windoze, or linux. Pity, that.

      --
      In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
    3. Re:OS/2 Screenshots by Anonymous Coward · · Score: 0

      Eh, that's an ancient version. OS/2 3.0 and 4.0 looked much nicer.

  128. It didn't fail... by SparafucileMan · · Score: 1

    ...it just wasn't popular. There's a big difference, what with corporations dictating mass appeal. OS/2 just didn't have the $$$.

  129. DIVE = WinG aka DirectDraw by operagost · · Score: 3, Informative

    DIVE stands for DIrect Video Extensions. It's not running DOS games in a window. What IBM had done was allow OS/2 programmers quick access to the display adapter instead of having to use the slow GDI, just like WinG would do later. You see, when you don't want your programs to crash your spiffy protected-mode OS, you have to virtualize your hardware.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  130. OS/2 Warp ads chased me away by CactusCritter · · Score: 1
    The article only mentioned the Belgian nuns TV ad, but there were several others, all of high production quality, but of no interest to an end user.


    I was weaning myself away from the Amiga at the time by buying a Windows laptop. I was aware of OS/2 Warp and wondering if I should buy it. (I recognize now that the laptop couldn't have hacked it!) However, IBM ran an OS/2 Warp TV ad that totally turned me off.


    The ad showed a goup of youthful folks clustered around a computer, oohing and ahing and generally making sounds of enthusiasm and approbation. It never showed a hint of what was supposedly on the computer display to generate such excitment.


    I assume that some high-level marketdroid thought the ad would make the viewer eager to see what the excitements was all about.


    I don't know how other folks reacted, but my conclusion was that OS/2 Warp had nothing special worth showing or else they would have shown the computer display. Therefore, why should I even give a thought to OS/2 Warp.


    My loss? I think not. I didn't invest any money in OS/2 Warp and it remained a non-factor in my life.

  131. An OS/2 Warp ad chased me away by CactusCritter · · Score: 1
    There were other foreign-sited ads besides the Belgain nuns. All were very professionally done, but were designed solely for international corporate business. Nothing there for the end user.

    During that period, I was phasing out of the Amiga market and had purchased a Windows laptop. I wondered if I should consider OS/2 Warp to replace Win95. (I recognize now that the laptop could not have hacked it with OS/2 Warp!) Then, an ad appeared for OS/2 Warp that showed a group of youngish folks gathered around a computer, oohing and ahing about what they were supposedly seeing on the screen. No hint of what was supposely displayed on the screen was shown.

    Evidently, some high-level marketdroid thought that viewers would be motivated to go post haste to a nearby computer store to see what the excitement was about.

    My take was that something exciting would have been shown if there was anything like that to show. I concluded that OS/2 Warp was an empty promotion and I never chose to even look at it.

    My loss? I think not. It cost me nothing and I have survived.

  132. Comparissons to Be by The+OPTiCIAN · · Score: 1

    I used to be a fantaical os2 user. Reading this brought back lots of sadness, and even more at Be, because Be wasn't fucked up in all the ways the IBM was, and the BeOS wasn't as crappy as os2 (said in retrospect - it was never that stable, and the browsers were a disaster). Be did everything within their power right, and Microsoft still swallowed them.

    --


    Believe with me, my saplings.
  133. What about the OS/2 being ported to linux article? by Mustang+Matt · · Score: 2

    http://www-1.ibm.com/servers/esdd/articles/linux_c .html?t=gr,l=805,p=OS2toLinux

    This was posted on slashdot not so long ago.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  134. Trying to post link again.. by Mustang+Matt · · Score: 2
    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  135. A couple of pedantic corrections... by Hugonz · · Score: 1
    I read several years ago, Dvorak's column "Inside Track" He said that OS/2 never succeeded because it was supposed to be optimized for Microchannel (the bus used in the PS/2) and for the PS/2 itself. People feared IBM would go proprietary again...

    Paul Allen and Bill Gates named their company Micro-Soft, not Microsoft.

  136. Linux is not a person, real or artificial by Arker · · Score: 2

    Will Linux learn the lessons of OS/2?

    Linux is not a person or a corporation. Linux is a kernel.

    Does a kernel ever really learn lessons?

    I don't think so.

    This is what you have to understand about Free Software. It's not a business. There may be businesses that use it, but it's not a business and it's not dependent on any particular threshold of "business" to survive. Unlike OS/2, or Windows, or Macintosh, Linux is not going to be a "failure" and die if it doesn't attract the unwashed masses.

    Anyway, Free GUI systems, which seems to be what you want to see, are getting quite usable. Admittedly, initial setup can be a bit confusing, and they require occasional routine administration that the average home user isn't going to ever understand. The same is true of every version of Windows around too, though, so what's the point?

    Whether Microsoft will switch sides on time to stay on top or not remains to be seen, but short of making Free Software illegal they simply cannot kill it.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  137. Re:OS/2 - no it was not by Anonymous Coward · · Score: 0

    The interface was not locked in, it was trivial to change and not only that it was really easy to just boot to a prompt if you so desired.

  138. Floppies! by ciryon · · Score: 1

    It had too many damn floppies. Took all evening to install on my 386 computer. Has it really been 10 (!) years?!?

    OS/2 was my first "alternative" OS to use. The multitasking was really impressive, and overall much better than DOS/Win3.1

    1. Re:Floppies! by MImeKillEr · · Score: 1

      Having worked for IBM in the OS/2 support center in Austin,TX, I can say you're sadly mistaken. OS/2 had less floppies that 2000 or XP use to install the OS -- OS/2 had 3 diskettes and a CD. XP uses ** 6 **

      --
      Cruising the internet on my TI-99/4A @ a whopping 300 baud!
  139. No Eye candy killed OS/2 by SlashDread · · Score: 1

    Ever say the striking difference in colordepth, and in 3d (raised buttons) between OS/2 and Win 3.1/95?

    OS/2 was UGLY.

    Seriously, lack of IBM marketing killed it.

    Gr /Dread

  140. Those screenshots are quite old, however. by Richard+Steiner · · Score: 1
    A more modern OS/2 setup (in my case Warp 4) can look somewhat different:

    Click here to see some Warp 4 Example Screens

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  141. A simple reason by forgoil · · Score: 3, Insightful

    There is one very simple reason to why OS/2 failed and Windows did not. Microsoft gave their all to make Windows win, they didn't have hardware sales to worry about as well. Just as Sun today are not willing to put all their eggs in one basket with Java but also wants to push slow expensive hardware and an outdated OS.

    To win you have to want to win, bad. For this is what Bill and Steve wants to, they want to give people what they want (that is normal people, they don't want to pay extra for a bunch of stuff, they want one package, and have all they need. I want that too, and I consider myself a computer geek after all) and they want to win. Though I personally don't think they try to be some "evil empire" and gets accused of a lot of things they haven't done. Anyone dealing with software on that scale knows how hard it is, and interfaces etc are bound to change. Heck, free software is even worse.

    So, this turned into a rant again. So for all you linuxnerds out there. If "Linux" is going to succeed, Mandrake/SuSE/RedHat/etc better join forces and put all their eggs in one basket. Produce one OS that looks and works the same all the time (you won't get away with several desktops, Apple and Microsoft is going to tear you to shreds, with good reasons) with a good set of applications and tools to go with it. Yes, to integrate and bundle *IS* good for the consumer. Anyone who says anything else must be mad. I buy a car, not a bunch of parts to build a car with (we all know the cost for that).

  142. Wonderfull by fabiolrs · · Score: 0

    I used to play around with OS/2 a long time ago. It was wonderfull, fast, reliable, etc. I could even compile some basic unix softwares written in C on it! I used to had 2 servers running OS/2 and average uptime was far higher than windows NT on the same machine (dual boot).

    --
    Fabio - Sumare/Sao Paulo/Brazil/South America/Earth/Solar System/Milky Way/Universe
    http://www.morroida.com.br
  143. I'm not dead yet! by bryanp · · Score: 1

    OS/2 is still being used for some things. It's still used to run the Octel 0100 voicemail system and it's just plain solid. It runs. I have *never* had an 0100 crash.

    Bryan
    (who came very close to running Warp on his home system but never quite took the plunge)

    --
    "An unarmed man can only flee from evil, and evil is not overcome by fleeing from it." Col. Jeff Cooper
    1. Re:I'm not dead yet! by forgeeks · · Score: 0

      I ran warp on my home system for awhile. I had a 2 line BBS! Oh the memories...I have not seen OS/2 in many years...but from what I remember, it was rock solid!

      --
      -- Powered By Linux
  144. Why didn't IBM put OS/2 on their own computers? by walterbyrd · · Score: 1

    I could never figure out why IBM PCs didn't have OS/2 pre-installed. Instead, they had Windows pre-installed. To get OS/2 you have to pay an additonal $120.

    It seems to me IBM should had OS/2 pre-installed on their PCs, and sold OS/2 for about $10 a copy until OS/2 caught on.

    I could never understand the marketing.

    1. Re:Why didn't IBM put OS/2 on their own computers? by d-e-w · · Score: 1

      IBM did put OS/2 warp on their computers (at least, at the end). I bought a Aptiva in early 1995 that dual-booted into Win 3.1 and OS/2. I liked OS/2 but we could never get the Enternet card working properly (so I couldn't get it onto the network under OS/2.)

      But, as I recall, you could not run OS/2 and Win95 on the same system (or both IBM and Microsoft claimed.) When I was forced to upgrade Windows, I had to totally wipe OS/2 off the system.

    2. Re:Why didn't IBM put OS/2 on their own computers? by Cro+Magnon · · Score: 1

      I heard vague rumors of IBM installing OS/2 in 1995. Soon after, I heard official announcements that IBM would be supporting W95 - before W95 was even out. That was what finally killed OS/2 for me! They couldn't preload their OS in 3 years, but promised W95 support before it even shipped.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    3. Re:Why didn't IBM put OS/2 on their own computers? by kmankmankman2001 · · Score: 1

      For the same reason it was so hard to get OS/2 on other mainstream computers - Windows licensing. That was in the day when MS required that the manufacturer install Windows on EVERY PC if they wanted to secure the favorable license pricing. If they didn't pre-install Windows on every PC their per-copy cost of Windows to MS went up dramatically. This was, of course, before MS was officially a monopoly according to the US DOJ (who now wants to settle the current monopoly lawsuit by awarding MS another monopoly in the education market). Brilliant marketing and clout by MS again beating pretty good technology and lousy marketing by IBM. This is the model that EMC adopted quite succesfully in the storage market.

      --
      "The bigger the lie, the more they believe." - Det. Bunk
  145. hardly by Anonymous Coward · · Score: 0

    "It was better than anything around, yet it failed."

    bs, it was WORSE than EVERYTHING around. no wonder it failed!

  146. Selective memory? by igiveup · · Score: 1

    I remember being exposed to OS/2 on a project I was on circa 1994. Our machines were configured to dual boot between OS/2 and DOS/WFW. My experience was that it was sluggish, non-intuitive, and did not come with a TCP/IP stack. I preferred WFW then, and Windows 95 completely blew it out of the water. The only people I remember using it were people with a serious anti-Microsoft jones.

    I surprised some postings were wishing OS/2 would have won the "desktop" wars. Even if it was superior (and I don't think it was), would you really want to trade one monopoly (Microsoft) for another (IBM). Their seems to be some feeling in the Linux community that IBM is some benevolent sugar daddy. These same people obviously don't remember the IBM of the '80s and earlier. Nasty bunch. Just because Microsoft got the better of them doesn't make IBM a tragic hero. More likley just desserts.

    --
    --- igiveup ---
  147. "OS/2 for PS/2" by Anonymous Coward · · Score: 0
    half an operating system for half a computer.

    And no, I'm not talking about the Sony box.

  148. Those Bastards! by Anonymous Coward · · Score: 0

    OS/2: another case of M$ stepping on the little guy!

  149. Linux knocked OS/2 off my desktop by Dragoness+Eclectic · · Score: 3

    Actually, I started with OS/2 2.0 back when the alternative was Windows 3.1. OS/2 2.0 was a bitch to install, and the WPS was a bit on the unstable side--patch o' the week from IBM was the norm---

    --but in 1992 it could multi-task a GUI and input from multiple serial ports at once, without dropping characters on the floor or forgetting to draw on the screen, which was just what certain applications needed that I was writing for the company I then worked for. Windows 3.1 couldn't do that, and DOS sure the hell couldn't.

    A lot of that was fixed with OS/2 2.1, and OS/2 3.0 (Warp) cleaned up the remainder. OS/2 Warp was a dream compared to Windoze 3.11 or 95. Much more stable, and could multi-task cleanly.

    I learned GUI programming with OS/2 (ignoring some early dabbling with X/Motif), and got my first exposure to multi-threading with OS/2. Later, I applied what I had learned from OS/2 to learning Windows programming (that and Petzold's book), and have been stuck programming Windows ever since. (Professionally only).

    I had OS/2 at home, and even wrote some command-line and GUI utilties for my Traveller (RPG) stuff. Some of them are still on my website, but not maintained for obvious reasons.

    <digression>
    (No, I'm not going to link it from here. I pay for bandwidth; it ain't no free Geocities site! Especially since that Altavista spider went amok and tried to download every eBook and zip-file on my site several hundred times every three hours for a month. Had to deny access to the av.com netblock to stop it. Word of advice: if you pay for your bandwidth, check it now and then; something might be eating it up for you.)
    </digression>

    At one time, my home machine dual-booted Win95 and OS/2. One day I found out that this Linux thing I had heard about in college (back in '91) was now available on CDs for a reasonable price. (I had only a 2400bps modem back in the days of Linux 0.96 and the SoftLanding distribution, so downloading all those packages was Right Out). So, I ordered my first Linux distribution, Slackware '96 (or was that my second?)

    It was cool; I fell in love with it right off. It was no worse to install than OS/2 2.0, and in some ways easier: I had fewer hardware incompatibilities. There was no KDE or GNOME in those days; I used FVWM as my window manager. Worked fine. But the greatest thing was the feeling of sheer power I had compiling my own, custom-tailored kernel. You can't do THAT with OS/2, Windows, or DOS!

    <digression>
    Do you know that kernel compiling hasn't changed much since the days of 1.x kernels? Sure, there's new menu options, and they introduced those new-fangled "module" things, and "make zImage" is now "make bzImage", but it's still "make mrproper; make config/make menuconfig; make dep; make bzImage; cp arch/i386/boot/bzImage <somewhere>/vmlinuz; vi /etc/lilo.conf; lilo -v" (and nowdays add "make modules; make modules_install" before the "cp").
    </digression>

    For a brief time, my home computer multi-booted OS/2, Windows 95, and Linux; but eventually I noticed that I never booted OS/2 anymore. I had moved most of my hobby-programming to Linux, and had decided that local web pages were an even better way than OS/2 help files to organize my vast amounts of data, writings, and RPG info. My games were all Windows games, so I didn't use OS/2 for that. Finally, Linux came with lots of free networking stuff, which worked better than the early OS/2 2.x TCP/IP packages, so I didn't need OS/2 for telnet or FTP, anymore. Besides, as I mentioned, the Linux TCP/IP implementation worked better and didn't bog down CPU and memory as much. Frankly, the only reason I still used OS/2 was for the PMTAPE tape backup program, and I eventually moved to LS120 super-floppies. (Now I burn CDs for data backup).

    There finally came a day when I was re-installing my OSs on a new hard disk that I decided there was no point in re-installing OS/2 Warp, because I never used it. In my house, Linux killed OS/2. It's been gone for several years now, but I still have fond memories of it.

    I love Linux!

    --
    ---dragoness
  150. OS/@ -- no one killed OS/2, IBM let it die. by wsandman · · Score: 1

    The one thing that no one (that I see) is addressing is

    MARKETING MARKETING MARKETING

    WinBlows does just that. But it's successful. Why? Your mother and your boss think it's the best thing since sliced cheese -- even if it sucks.

    IBM NEVER did any marketing to let your boss or your mom know what OS/2 was. Consequently they followed the path of lease resistence and bought Microsoft.

    I believe the LINUX project has nothing to learn from the demise of OS/2 because since the marketing of LINUX by the LINUX community has been phenominal.

    --
    W. Sandman III
  151. CDs! by lseltzer · · Score: 1

    Two problems with this argument: In the era of 2000 and XP almost every system boots off the CD, so the floppies are now irrelevant; and Windows is usually preloaded anyway.

  152. IBM even dropping it from Mainframe console by kmankmankman2001 · · Score: 1

    I was a long-time user of OS/2, through every version after V1. Great OS, but the battles of living in a corporate desktop world where the admins only acknowledged Windows and MS made the apps increasingly OS/2-unfriendly eventually wore me and my (all mainframe folks) out. Today the only OS/2 application we have running is the HMC (hardware management console) that is the central point of control for the mainframe. It's a good choice for the function as you really don't want a box like that taking GPF's and BSOD's and the apps that run on it are written strictly for those functions - it's not a MS Word/Excel/etc kind of workstation. What I find interesting, and very telling, is that IBM recently shared with us that a future version of the HMC will be Linux based. I can't think of anything that signals the death knell of OS/2 more resoundingly (or IBM's commitment to Linux) than IBM saying that the mainframe will be managed from a Linux console. I still miss some of those OS/2 apps. Comm Mgr was hands down the best emulator package for my uses. Obviously, as a mainframer, I have specific needs and biases, but neither Reflections nor Exceed are at the same level of what I got from OS/2 Comm Mgr (ESPECIALLY support for my 122 key, 24 PFKey, weighs ~3 lbs, keyboard that nobody will ever take away from me!).

    --
    "The bigger the lie, the more they believe." - Det. Bunk
  153. Multithreading browser by wardk · · Score: 1
    All these years later and netscape and ie still don't multithread their image downloads, the FIRST release of the OS/2 Web Explorer allowed you do specify how many separate download threads to use (up to 8), and you'd get a seperate counter for all the threads, and they would all MIRACULOUSLY be spinning CONCURRENTLY. Such feats of computing still appear to be beyond the software wizards of today.


    But alas it didn't do the gotta-have javascript, and IBM decided that it would be better to drop the Web Explorer and port Netscape, which was so far behind it's non-os2 counterparts that it was discouraging to users.


    Of course when Microsoft PROHIBITED the IBM PC Company from pre-installing OS/2 EVEN ON THEIR OWN PC's, OS/2's death was certain.


    I don't see a single desktop system in use today that multithreaded like OS/2. (Amiga perhaps?). Personally I find that pretty pathetic. But not suprising in an industry that locked itself into the Operating System equivilent to the Ford Pinto, exploding gastank and all, when a Mercedes was available for the same damn price.


    rant over...next one due at 20 year anniversary of OS/2...when I suspect I'll be able to just cut and paste this one and have it be relevent. Innovation my ass, ms.

  154. Open source by mrfiddlehead · · Score: 1
    Why the heck doesn't anyone ever talk about getting the source code for OS/2 out and about?

    What's the buzz?

    --
    :wq
    1. Re:Open source by Anonymous Coward · · Score: 0

      There are two projects that are intended to build a Open Source clone of OS/2. One of they has released a Preview and is fantastic. OS/2 is more alive now.

  155. Painful memories by The+Fun+Guy · · Score: 1

    I used OS/2 3.0, waited impatiently for OS/2 Warp, and used it for years, with WordPerfect 5.1 for DOS and QuattroPro 4.0 for DOS and ProComm and, greatest of all, Galactic Civilizations for OS/2. Difficult to set up and keep running, but more stable than Windows, and besides, I could always reboot to run Win apps that wouldn't run under OS/2.

    Finally, though, I needed to run Windows more and more, and more and more, the software that I need to work with wouldn't run under OS/2. Eventually, the only thing I used OS/2 for was GalCiv.

    OS/2 was picky about hardware, and drivers for OS/2 were rare and rarely good. When I bought a motherboard and associated parts to build a new machine, I gave up and never quite got around to installing OS/2. I was pro-OS/2, certainly, and it hurt to finally admit defeat.

    I still have the 3.0 and Warp disks in the back of the closet. A friend called me up last year and wanted to install OS/2 on his laptop, and knew that I had experience with it. I suggested Linux as an alternative to Win98, but he said he wasn't technical enough and didn't want something that complex. It hurt more than I expected to tell him that he was wasting his time looking at OS/2, and that he should install Win98.

    This article was painful to read.

    --
    The man who does not read good books has no advantage over the man who cannot read them. - Mark Twain
  156. UPS runs OS/2 by limejuice · · Score: 0

    UPS is still running OS/2 in most of their major hubs, and it runs some of their most critical systems.

    --
    Daniel J. Kelly
  157. The "death threat" thing by Anonymous Coward · · Score: 0

    Speaking of which, there was this guy who founded OS/2 Professional magazine and edited it for the longest time. His name was Edwin Black. When Big Blue pulled the plug, he started writing what would eventually become IBM and the Holocaust", in which he accused IBM of being complicit with and profiting from Nazi Germany.

  158. If it's dead, why am I here? by Atomic+Frog · · Score: 1

    Funny, since OS/2 is dead, how come IBM mailed me (and many other users) a brand new copy of OS/2 a couple of weeks ago? Hmmmm....

    I've used OS/2 and Linux extensively. How many of you whiners have actually used a recent version of OS/2?

    OS/2 provides one of the most consistent interfaces around. It's more configurable than Windows, and easier to configure for Joe Average than anything on Linux.

    Linux GUI's, even the latest KDE or GNOME have a long, long way to go to catchup to OS/2's PM + WPS. I only wish those people working on Linux would take a good look at OS/2 and see what's been done already and take some good ideas from it.

    1. Re:If it's dead, why am I here? by ReinoutS · · Score: 1
      even the latest KDE or GNOME have a long, long way to go to catchup to OS/2's PM + WPS. I only wish those people working on Linux would take a good look at OS/2 and see what's been done already and take some good ideas from it.

      As a participant in the GNOME usability project I can assure you this is not as easy to achieve as you suggest. But please join the mailinglist/irc channel and voice your opinions. You have a better chance to be heard by the right people there than here on /.

  159. Better than anything around? by Anonymous Coward · · Score: 1, Interesting
    [OS/2] was better than anything around

    Uhh, wasn't NeXTStep around at the time? If I'm not mistaken, it was introduced with the NeXT Cube in 1988 (four years before OS/2). It had UNIX stability, display postscript, was great for multimedia applications...

    NT tries hard to emulate UNIX (and does a pretty good job, I suppose), but UNIX has been UNIX for thirty years...

  160. I Have 21,000 OS/2 Desktops Out There.... by CrazyLegs · · Score: 2
    ....and I need to replace them. I work for a large financial institution and, like many (many!) other banks worldwide, we run a lot of OS/2, have used it for a decade (ie. since version 1.3), and are now forced to move. This is not trivial.

    All you closet OS/2-lovers are right, this o/s is rock-solid and needs very little active systems management to run. As well, we run all of our OS/2 desktops in RIPL-mode - which is akin to treating them all a 'network stations' sucking their o/s off a server at boot time. These desktops only have hard disk for swapping. And I could go on ad nauseaum about the PM API, file system, etc. etc.

    As to OS/2 murky history, it's the stuff of legend. MS was there to handle the desktop interface while IBM was bringing it's mainframe skills to bear (swapping, pre-emptive multitasking, etc.). When things went sour, IBM had the OS/2 kernal and MS had some pretty desktop icons and a vague notion of what a real o/s might be. The rest, unfortunately, is history.

    So, dear friends, where to go? What real choices do I have? MS with their obscene pricing and inferior technology (next to what I have today)? Otherwise, it's Linux with its low cost-of-ownership and less-than-clear (but getting clearer) support from mainstream vendors?

    Fact is, nothing today comes close to matching OS/2's combination of solid technology and ease of support. Regardless, I have to choose.

    Anyone got any bright ideas?

    --

    CrazyLegs

    "Pork!!" said the Fish, and we all laughed.

    1. Re:I Have 21,000 OS/2 Desktops Out There.... by Os2man4 · · Score: 1

      If I were you I would seriously consider contactig Serenity Systems for information about staying with Os/2 in its newest form eComStation. They have done a lot of work to it and added many features speccifically to help in simplifying the administration and upgrade of RIPL booted os/2 machines. You could check out www.serenity-systems.com or email Info@Serenity-Systems.com I am sure that they would be able to help you stay with Os/2 and solve the problems your currently having with it. The amount of work they've managed to do is really amazing and I think it would be worth your while.

    2. Re:I Have 21,000 OS/2 Desktops Out There.... by Anonymous Coward · · Score: 0

      The problem is that Serenity doesn't really 'own' OS/2. So they might be a short term solution, but they won't be of much help if OS/2 doesn't boot on fancy new Pentium 5 machines or whatever. The fact that they are around doesn't counter the weight of IBM telling everyone to Migrate Now.

      I imagine moving 21K desktops and all the associated apps is a monsterous 5 year task. Since he's probably got a very controlled environment, I'd recommend looking into something centrally managed like Citrix Winframe or X-terminals as replacements.

    3. Re:I Have 21,000 OS/2 Desktops Out There.... by Anonymous Coward · · Score: 0

      If you will change to Citrix, you don't must change out from OS/2. There is an OS/2 client for citrix metaframe. I use it today and I can run remotly WinNT software at the same time that OS/2 local software.

    4. Re:I Have 21,000 OS/2 Desktops Out There.... by Os2man4 · · Score: 1

      I disagree with this because IBM said that they were stopping fixes for Warp 4 and Warp3 yet they just realeased fix packages for both. THe youngest of which is more than 5 years old. So the conveniance pack has a huge amount of support behind it. IBM has committed itself to Os/2 until at least the year 2006 and if they continue like there have been you can look forward to things after that. Also the os/2 setup he currently uses if I read it correctly was already a central managed and booted system which in order to upgrade I would imagine to be a simple task.

  161. Take a lesson from Netscape by Anonymous Coward · · Score: 1, Interesting

    It can't be denied that IBM let OS/2 wither on the vine. Whether that's a good or bad thing seems to be a matter of personal preference and is definitely a moot point anyway. But has anyone noticed that IBM has developed a web browser for OS/2 that is based on Mozilla? At least someone cares enough about OS/2 that they bothered. It's funny that people always used to count out Moz/Netscape, but lately they've been roaring back. Maybe if IBM open-sourced OS/2, it might be put to good use by more people. However, I suspect they may not be able to because of some ancient licensing agreement with MS (especially because of the fact that some old code is still put to use in NT/2000/XP). Maybe someone out there knows for sure.

  162. 2.0 didn't run on ours by metamatic · · Score: 1

    We tried OS/2. We really wanted to use it. I tried installing it on three different machines from three different PC manufacturers. On the first, there was no video driver to go beyond 640x480. On the second, there was no compatible hard disk driver, so it wouldn't boot. On the third, the BIOS was incompatible, and it wouldn't install at all.

    Tried again with Warp. Same problems. Gave up at that point.

    OS/2 may have run on machines other than PS/2s, but it was very very picky about which ones.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  163. No, OS/2 *was* ported to the PowerPC. by Richard+Steiner · · Score: 1

    Unfortunately, the product was effectively hidden from view. IBM didn't make any effort to publicize its existence becayse Apple was already in the process of killing the CHRP platform.

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  164. Ironic by chiph · · Score: 0

    It's ironic that when I viewed this story, there was an IBM banner ad present trumpeting how their DB2 database runs on operating systems like Linux, Windows, AIX, and OS/2.

    I do miss OS/2. All it really needs is a re-write for 64-bits.

    Chip H.

  165. Actually, I bet he used OS/2 1.x by Anonymous Coward · · Score: 0

    Version 1.x of OS/2 was, indeed "half" an operating system. It was a completely different beast from OS/2 2.x, which was a fully-featured pre-emptively multitasking operating system with strong memory protection, kernel-mode device drivers, and other features you would expect from a modern OS.

  166. Anybody want a copy of the Microsoft 286DOS manual by Anonymous Coward · · Score: 0

    I suppose I'm not violating the NDA or the detailed legal notice that's stamped on the back of every page in it: I still have my copy of the original manual for Microsoft's 286DOS operating system... the working name for OS/2. Got it along with an *early* alpha release a very long time ago when I worked for the company that invented the chipset market. It was as revolutionary at the time as it was when I worked on the first multi-processing version of 1.2, and as Warp was a few yeas later. To bad it couldn't keep up with Windows, and indeed a good lesson to the Linux writers and users out there.

  167. Full on IBM... by Trracer · · Score: 1

    At work (banking industry) we run 3000+ IBM PCs with OS/2 on token-ring against IBM servers with MCA, talk about being in IBMs lap!

    --
    English is not my first language, so cut me some slack -: Om du kan lasa det har sa kan du Svenska :-
  168. The Book by mirabilos · · Score: 1

    Okay, more down the threads I found the name
    of the book and felt remembered.
    It was called "Showstoppers!" and describes
    the evolution of NT from EA F0 FF 00 F0 to
    start of the sales.

    --
    My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
  169. Revisionist history was:1.0 vs. 2.0 by Anonymous Coward · · Score: 0
    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.
    No, it was not true in the begiing. From 1.0 OS/2 was running on non-IBM hardware.
  170. Bah by G00F · · Score: 1

    Dude, on a 486/66 with 12 ram, I coudl run doom2 in one dos box right next to heritic. You could see the whole thing but smaller, and it was real time, not paused when you was playign the other window.

    This was on os/2 warp 3. Damn, I loved that OS. I could run anything, anyway I wanted too. Well, until DirectX came out. (32bit windows dlls put a damper on things for a while too)

    But I had an easier time running dos games back then, remember the two major memory usages for games and having to reboot dependiong on the game or application playing? OS/2 didn't need any of that.

    OS/2 problem was that IBM should have sold it to someone who could leagle push a major os w/o litigation about monopoly praticies.

    --
    The spirit of resistance to government is so valuable on certain occasions that I wish it to be always kept alive
  171. Re:OS/2 isnt dead...is IS windows - NOT! by Anonymous Coward · · Score: 0
    This is something most people dont know or understand: OS/2 isnt dead, it just lives on in a different form.

    Windows NT 3.1, 3.51, 4.0
    Windows 2000
    Windows XP

    They don't know it because it isn't true. What is true is that:
    1. The kernel of NT was intended to be the kernel of the portable version of OS/2
    2. The was an OS/2 personality for NT
  172. Greatest OS since what? by Janax · · Score: 1

    OK, so I know that not enough people bought the Amiga and also that it's long "dead", but I am still sometimes amazed by the compactness and flexibility that was provided by the Amiga OS. I programmed on it for 3 years for the Prevue Guide (actually Sneak Prevue, for those who ever saw that), and the OS seemed simple yet powerful. I haven't done too much programming on Linux, and only a small amount on Win32, but even the user features of the Amiga OS still had things that LInux is starting to get (thinking of modularized filesystems, for example), and that Windows never will have.

    AutoConfig was something that worked great, and allowed drivers to be installed from the devices themselves at boottime instead of having a separate disk/CD for them. Of course you could do it the other way too...

    Of course the preemptive multitasking was great, and you could have your system up and running multiple programs with the basic 512kB memory. I remember Microsoft was commissioned to write BASIC for the Amiga, but it was buggy, crashed often, and was dumped later for incompatibility reasons with the 68020 (go figure).

    Naturally the AmigaOS wasn't perfect either. Its prototypes were developed in BCPL (did I remember this right? - I know it was some kind of off-base BASIC-like language), and had a kind of glue layer for C compatibility. And yes, I hated the .info files for "Workbench" cluttering up my file structure, but the idea of a compact, small yet flexible OS was adhered to rather well.

    Many of the design philosophies from the Amiga team have made it into other OSs... the fact that it's survived so long in spite of terrible management and business gaffes proves that its ideas were founded on solid ground.

    ...just wanted to point out that other OSs should be given their due for what they brought to the table.

    1. Re:Greatest OS since what? by deviator · · Score: 1

      OK - I'll give you that. :)

      You know they've resuscitated Amiga, and are now developing it as a portable virutal machine... check the archives for info on that.

  173. No one will read this by NortonDC · · Score: 1

    PC bus history:

    ISA
    MicroChannel Architecture (MCA, the PS/2 bus)
    EISA
    VESA Local Bus (VLB)
    PCI

    Everbody's so freaking eager to forget VESA. It was FASTER than PCI (32 bits X 40(!) MHz), which it coexisted with later on as PCI appeared.

    MS did not pioneer the "reset the CPU" method for enabling preemptive multitasking on the 286, Novell did.

    And, to my recollection, OS/2 was not fully 32-bit until 2.1 GA.

    And OS/2 Warp crashed all the damn time if you were doing something so outrageous as to trying to play an AVI file it didn't like. Fall down, go boom, either the whole damn thing or whatever had control of the single input queue, another single point of failure in the system that would completely lock you out of your 'puter.

  174. Yeah .... by Taco+Cowboy · · Score: 1



    You said:

    "How weird. I've had four computers in my
    life and none of them came with Windows."

    Yeah ......

    Computer #1: Commodore PET

    Computer #2: TRS-80

    Computer #3: Original IBM-PC, with ROM-BASIC.

    Computer #4: Apple III.

    --
    Muchas Gracias, Señor Edward Snowden !
    1. Re:Yeah .... by Arandir · · Score: 1

      Computer #1: 8086
      Computer #2: Pentium 100
      Computer #3: AMD K6-2
      Computer #4: AMD Athlon

      The only one that came with an OS at all was #1, which had a MSDOS-3.3 floppy in the box.

      Honestly, if you guys don't know how to buy a computer without Windows, then you just don't know how to buy computers.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Yeah .... by Cro+Magnon · · Score: 1

      Most people DON'T know how to buy a computer without Doze, or even know that there IS such a thing. Sure, YOU have the savy to buy a bare machine and install a real OS, but what about the 99% of the population that doesn't read /.?

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  175. Who is the revisionalist??? by os2fan · · Score: 2
    Microsoft did not "simply give up on it". NT really is OS/2 running a legacy shell, just as Win9x is DOS running the legacy shell.

    The decline in RISC operating systems (such as the PPC), came more as a result of that these chips never took the market by storm. Yes, there was a OS/2 for PPC in the pipeline.

    The reason more often pushed forward is, that MS was quite happy with OS/2 when it was a console session, and even alright when it had the PM layer. But the moment it grew WPS, MS was not keen on it because, were it to succeed in the market place, MSFT would not control it.

    Microsoft essentially forked OS/2 (and all its bits), just as they forked HTML, Kerebos, etc, etc.

    --
    OS/2 - because choice is a terrible thing to waste.
  176. Where do these myths come from? by Geezle2 · · Score: 1

    And you are Dumb as Ass. Clearly your disfunctional mind is comparing OS/2 1.2 with Windows XP or something. . .Comparing Warp3 with Windows 3.1 is a little more appropriate and Warp 4 with Win9x. OS/2 1.3 looks almost identical to NT 3.5. The icons were a problem for you? More adventuresome or competent users changed the ones they didn't like. . .Really pretty easy on OS/2. How long was it before Windows supported transparent backgrounds for icon text? Having an opaque text background was butt-ugly. Howabout bitmaps for folder backgrounds. . .I assume that M$ implemented that at some point after the challenge of keeping suckers like yourself convinced of the superiority of their desktop became too expensive. I like your final thought. . .you had that one some years ago and have not had another since, right? With a little imagination (very little. . .but you aparently lack even that much) the drives objects combined with Launchpad objects make a remarkable file management system. In fact, Microsoft's latest offerings STILL lack desktop tools as powerful yet simple to configure as Launchpads (Warp 3 and later) or the WarpCenter (Warp 4 and later). The cheezy Taskbar/System Tray isn't even in the running. And then there are Workspaces. . .Windows thralls don't know what they are missing without Workspaces. . . More about ugly. . .let me see if I can visualize your Windows desktop. . .dozens upon dozens of icons crowding each other. . .sitting pretty much where the application's installer dropped them or if you are neat, aligned in row after row. Like most Windows users you are probably afraid to move the icons off the desktop to their own folder because Windows might forget what the icons are for. . .Don't tell me about ugly. . .I have yet to see a windows desktop that someone actually works with that isn't ugly.

  177. It's not as sad as it seems... by Phil2 · · Score: 1

    Since I'm writing this using an OS/2 Warp machine, Warp cannot be as dead as the majority expects it to be.
    So much for that.
    I must agree that rather sad things happen at IBM's. But in spite of their favour for Linux in all flavours I have to remind the kind reader that OS/2 resembles that good old Phoenix lately by being burned (by it's inventors) and rising up again with some new feathers and appearance. Since IBM doesn't want this bird to be recognized they chose to let someone else sell it as eComStation (eCS). This thing looks much more like a consumer OS (but still not like something Xtremely Problematic my kids smuggled into the trolley at toys'r'us) while featuring a journalling filesystem (when MS kept brushing up their 'good' old FAT filesystem to something with 32 in it) and much more.
    We indeed have our problem zones, but at the moment there's the situation that eCS can almost do anything Linux can concerning hardware and driver support. Well, eCS still is a single user OS and would never run on an IBM z/series machine, but for everyday work it does it's tricks (and you're always sure your data gets stored instead of going up in (blue) smoke.

    MS had enough time to work on their mediocre stuff, so we finally have XP. If somebody had invested the same sums into OS/2 (plus the advantage that it surely wouldn't have been MS), who knows what we (or better, they) would be able to do with their PCs today...

    I'd say, let OS/2 live, let Linux live, and don't let them put gates all around us. Maybe we should join forces and kick them out! Linux and OS/2 make a much better combination than Windows and... well, Windows.

    --
    ...still flying with OS/2...