Slashdot Mirror


The Software That Failed To Compete With Windows

harrymcc writes "When Microsoft shipped Windows 1.0 back in November 1985 — it turned 25 on Saturday — it wasn't clear that its much-delayed windowing add-on for DOS was going to succeed. After all, it was a late arrival to a market that was already teeming with ambitious competitors. A quarter-century later, it's worth remembering the early Windows rivals that didn't make it: Visi On, Top View, GEM, DESQview, and more."

347 comments

  1. OS/2 by Wonko+the+Sane · · Score: 5, Insightful

    They left out the most viable competitor.

    1. Re:OS/2 by VGPowerlord · · Score: 4, Insightful

      They left out the most viable competitor.

      Given that this is a list of "Windows' Failed Rivals", OS/2 rightfully isn't on that list... IBM continued to release new OS/2 versions for nearly a decade after its initial release.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    2. Re:OS/2 by RDW · · Score: 2, Informative

      This site is generally more comprehensive, and has lots of screenshots (though can't see TopView, which is maybe just as well):

      http://toastytech.com/guis/

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

      They left out the most viable competitor.

      I don't believe OS/2 was ever a competitor to the Windows 1.0 that the article is about. Maybe windows 3.x, but I believe Windows 1.0 predates OS/2 by a bit.

      TFA indicate that IBM's Top View would have been around at the same time though.

      --
      Lost at C:>. Found at C.
    4. Re:OS/2 by eln · · Score: 1, Redundant

      They seem to be referring to competitors of Windows 1.0 specifically, not just any old Windows. OS/2 wasn't a competitor of Windows 1.0, if was supposed to be the successor to Windows, developed by IBM and Microsoft jointly. OS/2 didn't really become a competitor to Windows until around Windows 3.0/3.11 after IBM and Microsoft parted ways on the project.

    5. Re:OS/2 by gstoddart · · Score: 2, Informative

      I'm amazed that OS/2 isn't mentioned in the article since it was the other OS option at the time.

      Both the summary and the article are discussing the 25th anniversary of Windows 1.0 which shipped in 1985.

      OS/2 was not available "at the time" in question, which was 1985, and wasn't an "option" to Windows 1.0.

      --
      Lost at C:>. Found at C.
    6. Re:OS/2 by VGPowerlord · · Score: 2, Informative

      As someone who in 1991 ordered his 386/SX (4MB RAM, 80MB hard drive and 256k VGA card) with MS DOS 5.0 and Windows 3.0, I'm amazed that OS/2 isn't mentioned in the article since it was the other OS option at the time.

      OS/2 being a failure would be news to IBM, who sold it for a combined total of 19 years (1987-2006) across all versions.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    7. Re:OS/2 by commodore64_love · · Score: 5, Informative

      From the article: "I considered only environments which were designed to run on IBM-compatible PCs, and which (like pre-1995 versions of Windows) ran on top of DOS rather than replaced it. (That's why the Mac OS and OS/2, for instance, aren't here.)"

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    8. Re:OS/2 by SnarfQuest · · Score: 2

      My memory may be dim, but I don't think that OS/2 even existed in the Windows 1.0 time frame. It wasn't until much later that OS/2 was even started as a project. You cannot compete if you don't exist. This article was about pre-existing projects that existed before Windows was dumped on the market.

      --
      Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    9. Re:OS/2 by Wonko+the+Sane · · Score: 1, Insightful

      IBM continued to release new OS/2 versions for nearly a decade after its initial release.

      That just means it took longer to fail than the other competitors.

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

      DESQviewX was pretty elite back in the day...

    11. Re:OS/2 by aardwolf64 · · Score: 1

      Actually the last PC in the article compared PC/GEOS to Windows 3.0.

    12. Re:OS/2 by Binestar · · Score: 1

      Perhaps you should read the article... OS/2 was mentioned, along with MacOS.

      --
      Do you Gentoo!?
    13. Re:OS/2 by interval1066 · · Score: 3, Insightful

      "I believe Windows 1.0 predates OS/2 by a bit."

      You're right, but OS/2 is worth mentioning anyway. I tried it back in the day, and really liked it. It was a 32 bit os when Windows was still only 16 bit and REXX was a really powerful shell language, much more so than Batch. I'm really sorry it couldn't survive. Although it gave it quite a go. I think I've read comments from /. readers who still use it.

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
    14. Re:OS/2 by Jugalator · · Score: 1

      They left out the most viable competitor.

      Even later than Windows though. They're mentioning competing desktop managers at the time of Windows' inception.

      --
      Beware: In C++, your friends can see your privates!
    15. Re:OS/2 by confused+one · · Score: 2, Interesting

      One legacy of OS/2 is NT 3.5. After the IBM/Microsoft split, the Microsoft team turned out the first NT versions... So, in a somewhat obtuse way, if you want to map out the code legacy, OS/2 lives on.

    16. Re:OS/2 by BrokenHalo · · Score: 5, Funny

      OS/2 rightfully isn't on that list...

      ...but then, of course, OS/2 was 1/2 of an operating system.

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

      This article makes me feel old.

      Why? Because I remember when none of these OSes exist. When the world of computers was "open" and anyone could win. It was time of uncertainty AND excitement. In fact the #1 selling computers upto 1985 were the TRS-80 (70s), Atari 400/800(early 80s), and Commodore 64 (1983-). The Apple Macs and IBM PCs were not yet the dominant platforms they eventually became.

      Aside:

      PC/GEOS mentioned in the article originated on the Commodore 64 as a Mac-like clone OS. Apparently it's still being sold: http://www.breadbox.com/

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    18. Re:OS/2 by BrokenHalo · · Score: 1

      DESQviewX was pretty elite back in the day...

      [shudder]. The only thing I hated more then DESQView was Gem. That was truly awful.

      Back then, there were lots of approaches to getting applications started (given that DOS was/is a single-tasking OS, so stopping programs wasn't an issue). Many went down the path of using LeMenu and similar menu systems. I recall setting up a lot of machines with suites of menus constructed using Norton's extensions for batch files, which allowed us to create menus similar to the kind of thing we can do with ncurses. I can't remember what the collection was called offhand, but those menus survived even through the advent of the 386 machines, simply because they were totally bombproof and had zero overhead. Perfect for commercial environments where the emphasis is on getting work done...

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

      Windows didn't kill OS/2. OS/2 killed itself.

      OS/2 was wonderful until 2.11. When IBM released OS/2 Warp, at least half the users went looking for something else.

      --
      morcego
    20. Re:OS/2 by ArhcAngel · · Score: 2, Insightful

      Depends on what you call a failure. Considering government and banks depended on it heavily for almost 20 years sounds like somewhat of a success to me.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    21. Re:OS/2 by bennomatic · · Score: 1

      PC/GEOS? My fave was GEOS for the C64.

      --
      The CB App. What's your 20?
    22. Re:OS/2 by perpenso · · Score: 1

      My memory may be dim, but I don't think that OS/2 even existed in the Windows 1.0 time frame. It wasn't until much later that OS/2 was even started as a project.

      OS/2 1.0 (16-bit text) followed Windows 1.0 by 2 years (less?), a graphical option called Presentation Manager soon followed. Perhaps you are thinking of OS/2 2.0 (32-bit w/ GUI)?

      To avoid a redundant post I'll just offer a link to another response:
      http://slashdot.org/comments.pl?sid=1878948&cid=34308386

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

      I still use OS/2 whenever I need to format 2 floppy disks at once while compiling C-Kermit and browsing the web.

    24. Re:OS/2 by rcamans · · Score: 1

      Actually, Windows 0.9 and OS/2 0.9 were simultaneous.

      --
      wake up and hold your nose
    25. Re:OS/2 by TRS80NT · · Score: 1

      It was fun on the C64 but I didn't really get into it until I got my C128 and a second floppy drive. Program in one drive, data in the other. 80-column screen! Whoo boy that was fun.

      --
      Lorem ipsum dolor sit amet.
    26. Re:OS/2 by Anonymous Coward · · Score: 0

      By that logic, I can say that Windows failed against Mac OS X. But we just need to wait a decade.

    27. Re:OS/2 by Cwix · · Score: 1

      So..

      Win NT 3.5/OS/2 -> Win NT 4 -> Win XP -> Win Vista -> Win 7

      So I don't have to feel guilty about using 7 anymore?

      --
      You are entitled to your own opinions, not your own facts.
    28. Re:OS/2 by Capt.DrumkenBum · · Score: 1

      I loved OS/2. I especially loved how I could start a 14.4 modem download and switch over and play Doom. Windows users could play Solitaire while their download completed in the background, and I was playing doom. :) Those were the days.

      --
      If I were God, wouldn't I protect my churches from acts of me?
    29. Re:OS/2 by Anonymous Coward · · Score: 0

      They left out the most viable competitor.

      No you are mistaken, OS/2 did not run on top of DOS.

    30. Re:OS/2 by cbhacking · · Score: 1

      That's mostly true. However, OS/2 was 16-bit until LONG after 32-bit chips were available. From Wikipedia (http://en.wikipedia.org/wiki/OS/2):

      OS/2 1.x targeted the 80286 processor: IBM insisted on supporting the Intel 80286 processor, with its 16-bit segmented memory mode, due to commitments made to customers who had purchased many 80286-based PS/2's because of IBM's promises surrounding OS/2.[15] Until release 2.0 in April 1992, OS/2 ran in 16-bit protected mode and therefore could not benefit from the Intel 80386's much simpler 32-bit flat memory model and virtual 8086 mode features. This was especially painful in providing support for DOS applications. While, in 1988, Windows/386 2.1 could run several cooperatively multitasked DOS applications, including expanded memory (EMS) emulation, OS/2 1.3, released in 1991, was still limited to one 640KB "DOS box".

      By comparison, Windows 3.0 (came out in 1990) supported the 386's "Enhanced" Protected Mode and Virtual 8086 Mode. On the other hand, NT came out in 1993, so there was a one year gap where OS/2 was 32-bit and Windows wasn't.

      --
      There's no place I could be, since I've found Serenity...
    31. Re:OS/2 by Anonymous Coward · · Score: 0

      it did survive, NT was 80% OS/2 code in the kernel, a lot of that code still lives today in Windows 7 I am sure.

    32. Re:OS/2 by vux984 · · Score: 3, Funny

      I still use OS/2 whenever I need to format 2 floppy disks at once while compiling C-Kermit and browsing the web.

      That "need" come up often?

    33. Re:OS/2 by falconwolf · · Score: 1

      Given that this is a list of "Windows' Failed Rivals", OS/2 rightfully isn't on that list... IBM continued to release new OS/2 versions for nearly a decade after its initial release.

      I'm not GP but I thought the same thing. DESQview was a gui that ran multiple DOS programs to run at the same tyme allowing task switching. The only place it is at the end of IBM's TopView's section: "TopView wasn’t officially discontinued until mid-1990, but by that point just about everyone who found the idea intriguing had switched to Quarterdeck’s DESQview." A few article comments mention it though.

      Falcon

    34. Re:OS/2 by KingMotley · · Score: 1

      It was a re licensed copy of 4Dos.

    35. Re:OS/2 by Creepy · · Score: 1

      True, but it ran like the original mac, which is to say it ran one program at a time in different windows and could application switch between them. Macs didn't have multitasking until 1987 (as I recall the Lisa had cooperative multitasking - the mac hardware couldn't handle it). I don't think Windows had any OS that did true multitasking until Windows 95 (but I'm not sure about PC/GEOS - they entered the market when MS was offering massive discounts on anti-competitive exclusivity and bundling agreements and were more-or-less forced out of the market that way).

    36. Re:OS/2 by jbolden · · Score: 1

      I used it. DESQVIEW normal was pretty standard among techies. X wasn't nearly as popular.

    37. Re:OS/2 by MonTemplar · · Score: 1

      Well, in one sense 7 carries the software DNA of both NT and OS/2 - unfortunately, there was some less than intelligent design applied to the transitional versions, in terms of security and reliability.

      (I think I have probably managed to offend multiple sets of geeks plus proponents of both Evolution and Creationism. My work here is done. ;-D )

      -MT.

      --
      -MT.
    38. Re:OS/2 by wumpus188 · · Score: 1

      Actually, the first release of NT was 3.0, but it only existed for a few months before 3.5 came out. I remeber running 32 bit version of Visual C++ 1.52 on it.

    39. Re:OS/2 by Tablizer · · Score: 2, Informative

      They left out the most viable competitor [OS/2].

      TFA: "For the purposes of this roundup of Windows rivals, I considered only environments which were designed to run on IBM-compatible PCs, and which (like pre-1995 versions of Windows) ran on top of DOS rather than replaced it. (That’s why the Mac OS and OS/2, for instance, aren’t here.) I also cover only products released in 1990 or before..."

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

      Actually, the opposite was true. I suppose you are basing your statement on anecdotal evidence. What do you think was wrong with OS/2 Warp? It had full PCMCIA support, internet access (full LAN access with the Connect edition), full multimedia support, lower memory demands, and better bootup recovery options.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    41. Re:OS/2 by operagost · · Score: 1

      I don't know if I'd even dare to play Solitaire under Win 3.x during a download unless I had one of the third-party COM driver replacements.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    42. Re:OS/2 by Creepy · · Score: 1

      Warp failed less because of its own merits or demerits than because of Microsoft having every major PC supplier in the US (and probably elsewhere) tied to exclusive Microsoft only product deals in the early 1990s (you know, pretty much exactly like the Comcast TV, internet, and phone service which should be illegal, but the US is a terrible regulator of "regulated" monopolies).

        In 1994, when Warp came out, if you wanted a computer it came with Microsoft Windows 3.11, and the only exception I know of that shipped with PC's was Compaq's in-house window manager (but they still had to ship Windows 3.11 with it, and it was an easy switch). Server PCs had to include Microsoft SQL Server, as well, and by the time PCs started to encroach in the server market Microsoft was forced to abandon exclusivity deals in order to not be broken up as a monopoly. I worked for a major computer manufacturer in 1994 and while I didn't see the exclusivity agreement, it was widely publicized that if Microsoft had a product for it, we had to sell their product and no other (applying to software only - I'm not sure if MS even had a hardware division at that time, but most manufacturers had their own brand of mice and supplied 3rd party modems).

      I actually bought my first mac (and replaced it in 1999 with a B&W G3 haven't bought one since) in 1994 because I was disgusted with this industry practice and my inability to find a PC that shipped with PC/GEOS (my preferred PC OS after GEM), or Slackware (my preferred OS at the time). The only bad was lack of a UNIX-like, but I got that with Yellow Dog Linux and SuSE a few years later (I got SuSE in early beta and YDL in release). For a long time I ran Linux and macOS concurrently (mac-on-Linux), but switched to full mac with MacOS X.0 (or what should have been called MacOS X beta).

    43. Re:OS/2 by froggymana · · Score: 1

      Well isn't that a given since since it is divided by 2?

      --
      "To prevent this day from getting any worse, I'll just read ERROR as GOOD THING" 1GJU8xLuDKDxEs4KLf8fAGyptoDsqvEsBT
    44. Re:OS/2 by Anonymous Coward · · Score: 0

      whoosh

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

      I ran a lab on NT 3.1 for ages, then 3.51. The biggest difference was the HAL, IIRC.

    46. Re:OS/2 by confused+one · · Score: 1

      I kind of suspected there was a 3.0 but never saw it in real life myself. Seemed strange to start with version 3.5; but, it was the first version I came across.

    47. Re:OS/2 by morcego · · Score: 1

      Warp was completely unappealing for OS/2 users. In other words, IBM decided not to dance with the person that took her to the ball.

      I was working at IBM when Warp was released, although on a non-related area. But I did have friend on the OS/2 PCP division of my country, and their statements corroborated what I experienced, and what I've seen from other people I knew.

      As for the people who were not OS/2 users yet ? Maybe they would have liked Warp. But they had no incentive to try it, not even from their friends.

      --
      morcego
    48. Re:OS/2 by hairyfeet · · Score: 2, Interesting

      Actually OS/2 isn't "dead" in that it STILL has a niche and is selling to this very day, whereas good luck actually buying a new copy of any on the list. You can go to eComstation and still buy a copy of OS/2 (because that is what eComstation IS...OS/2 with continued upgrades and support) and have someone there to support you. In my mind that makes it a non dead OS since you can still buy it plus support. From what I understand eComstation is still used in the financial district to some extent, hence the continued sales and support.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    49. Re:OS/2 by RobertM1968 · · Score: 1

      I still use OS/2 whenever I need to format 2 floppy disks at once while compiling C-Kermit and browsing the web.

      That "need" come up often?

      Hmmm.... dunno about that need, but I know I still use OS/2 when I want to serve high volume websites such as Star Trek New Voyages: Phase 2 on very minimalist hardware (Quad 550MHz), alongside 2 dozen other sites and an FTP server that handles a few terabytes each direction a month - while being able to format two floppies at once.

      I can't do that on any version of Windows Server (the site USED to run on it (when hosted by someone else) when it had 1/10th of the traffic... not a pretty scene). And while Linux is an alternative, even it doesn't perform as well on slower hardware (or take as great advantage of faster hardware). It performs far better than Windows - but still not quite as good. Oh, and I am in love with a full featured, integrated REXX - amazing what REXX and PHP can do together.

      OK... all but the floppy formatting part is true.

    50. Re:OS/2 by gnapster · · Score: 1

      By that logic, I can say that Windows failed against Linux. But we just need to wait until the year of the Linux Desktop.

      Fixed that for you.

    51. Re:OS/2 by exomondo · · Score: 1

      Well isn't that a given since since it is divided by 2?

      Well done, you got the joke.

    52. Re:OS/2 by HermMunster · · Score: 1

      You all seem to think this was an even playing field. It wasn't. DOS was being pre-installed in a way that violated anti-trust laws. That sealed the deal for most of these alternative. It wasn't so much a failure, rather it was a monopolist exercising it's muscle.

      If you think about it most of their technology was designed to lock in vendors. Everyone developing for any given OS had to make decisions because they couldn't afford to develop for multiples. And in designing it the way the did they effectively made the costs too high. There was no hope for development on other platforms and with the DOS pre-installs it made it prohibitive when Win 3.x came out.

      As far as Windows 1 goes it had no impact on the industry whatsoever, none. It was actually quite creepy that they'd try to foist that on the public.

      Most of the products listed in this thread didn't even come into existence till several years after 1.x was released.

      --
      You can lead a man with reason but you can't make him think.
    53. Re:OS/2 by aibrahim · · Score: 1

      I guess you never know who you'll run into on the Internets

      --

      Don't post innacurate information
      If you do, I swear by my pretty floral bonnet I will end you.
    54. Re:OS/2 by Anonymous Coward · · Score: 0

      They left out the most viable competitor.

      They also forgot Mac OS which was a failure by the fact that people were forever astroturfing it being better yet it had no useful programmes for the mass of computer buyers who ignored it and only joined the 20th Century in the 21st when OS X was released. Sales subsequently increased.

    55. Re:OS/2 by froggymana · · Score: 1

      Do I get a prize for that?

      --
      "To prevent this day from getting any worse, I'll just read ERROR as GOOD THING" 1GJU8xLuDKDxEs4KLf8fAGyptoDsqvEsBT
    56. Re:OS/2 by RobertM1968 · · Score: 2, Funny

      I guess you never know who you'll run into on the Internets

      LoL Alex, I run into you all the time online... :-)

    57. Re:OS/2 by jrumney · · Score: 1

      It also seems to be a list of graphical shells that were around in the same timeframe as Windows 1.0. I'm pretty sure OS/2 came later, around the Windows 3.0 timeframe.

    58. Re:OS/2 by Pherlin · · Score: 1

      McBain.jpg

    59. Re:OS/2 by toddestan · · Score: 1

      Did it really fail though? A lot of the work put into OS/2 made it into Windows NT 3.1, which Windows 7 is a direct descendant of. You might even consider OS/2 a winner over Windows 1.0, in the sense that the line started with Windows 1.0 ended with Windows ME over 10 years ago.

    60. Re:OS/2 by XCondE · · Score: 1

      Given that this is a list of "Windows' Failed Rivals", OS/2 rightfully isn't on that list... IBM continued to release new OS/2 versions for nearly a decade after its initial release.

      Did they ever manage to get it to print?

    61. Re:OS/2 by ebbe11 · · Score: 1

      I used OS/2 for a while. When I set up shop as an independent contractor in early 1995, I needed an OS that was:

      • Multitasking
      • Capable of running Windows and DOS programs
      • Capable of running on hardware I could afford
      • Available

      At that time there was exactly one candidate.

      --

      My opinion? See above.
    62. Re:OS/2 by Anonymous Coward · · Score: 0

      That's why the Mac OS and OS/2, for instance, aren't here.)"

      Or GS/OS

    63. Re:OS/2 by drsmithy · · Score: 2, Insightful

      So, in a somewhat obtuse way, if you want to map out the code legacy, OS/2 lives on.

      No it doesn't. NT was not developed from OS/2.

    64. Re:OS/2 by RobertM1968 · · Score: 1

      Ummm, thanks for the Funny mod, but really, Alex and I have known each other for years now. We've worked together on Star Trek Phase 2. Check out his work... pretty talented guy.

    65. Re:OS/2 by hazydave · · Score: 1

      OS/2 2.0 was 32-bit... kinda-sorta. You still had to write PDDs (physical device drivers) in 16-bit protected mode. Trust me on this... it was nothing like 32-bit deep down. But for applications, sure, they supported 32-bit before Microsoft did.

      --
      -Dave Haynie
    66. Re:OS/2 by hazydave · · Score: 1

      The big problem with OS/2 was IBM. There was roughly half of IBM backing OS/2. But the other half, as well as the bulk of the rest of the computer industry, was behind Windows. And that pretty much included IBM's own PC division.

      But hey... it lived on in ATMs for another decade or more.

      --
      -Dave Haynie
    67. Re:OS/2 by bhtooefr · · Score: 1

      The list actually points out that you can still buy Breadbox Ensemble (the latest version of PC/GEOS,) and here's where you can buy it at: http://www.breadbox.com/ensemble/geosdetails.asp?id=45&category=Purchase%20Ensemble

    68. Re:OS/2 by bhtooefr · · Score: 1

      3.1 was the first, and it was named that to maintain version parity with regular Windows 3.1.

    69. Re:OS/2 by hairyfeet · · Score: 1

      Actually there is one BIG difference between your link and mine...support. The eCom guys are busy right now writing and adding new drivers for things like SATA, new networking stacks, better USB support, etc. The Breadbox guys on the other hand (which is why the GEOS community hates their guts, check out GEOS forums and see the hate) are letting it rot and haven't written a SINGLE BIT of code for it since picking it up, and it had rotted before that.

      That is why it says on their website "good for older hardware" because it can NOT run on anything newer, whereas I have actually tried an eComstation machine running on a circa 2005 P4 at a financial services corp in the state capital I was hired to add some desktops to and it was actually a damned nice OS. Reminded me of the good old days running OS/2 Warp while everyone else was "enjoying" the BSODs in win9x. While I remember using GEOS for a little while in the 80s (I think it was an Atari) they just never updated past the stage of DOS shells, so I would argue that the crazy price Breadbox wants ($99? For an OS they haven't updated in over a decade and a half?) just shows they really don't care and don't mind if it does die. OS/2 is still used in banking and finance and is still being updated for modern equipment. BIG difference.

      --
      ACs don't waste your time replying, your posts are never seen by me.
  2. So ... by WrongSizeGlass · · Score: 1

    So, is this supposed to be a story of victory for MS or a tale of woe for the rest of us?

    1. Re:So ... by bolthole · · Score: 1, Insightful

      Both.
      The "woe" part being, that no replacement for microsoft will succeed, unless it has the same blinding ambition and greed that microsoft had, and the others lacked. This was proven by the fact that the other competitors were "nice", but did not have those qualities, so were dominated.

    2. Re:So ... by erroneus · · Score: 1, Insightful

      A windows replacement can succeed if it's pushed out by Microsoft. The factors at play were nothing to do with quality of the product. Microsoft "skillfully" pushed its stuff out in such a way that no one else could play in the same market for long. And yeah, OS/2 was effectively stolen by Microsoft and made into Windows NT. I miss OS/2... it was way too good. I wonder what it would be like today if they continued to develop it.

    3. Re:So ... by commodore64_love · · Score: 1

      >>>a tale of woe for the rest of us

      Yes. Woe. Windows was complete crap prior to 95, which is why I mostly used Mac OS and Amiga OS. Hell even the lowly Commodore=64 had a better "windowing" system called GEOS. I only moved to windows 98 because atari died, commodore died, and apple looked like it was heading the same direction.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    4. Re:So ... by mikael · · Score: 5, Informative

      Thought it was more the "lock-in" provided by the Window API. Microsoft didn't conquer the workstation market until around 1995 with Windows NT/95. One by one they got the workstation vendors to replace their UNIX OS's with Windows NT using a "UNIX is LEGACY" advertising campaign; DEC, Digital, then HP and SGI caved in, as application developers could really only support the three most popular OS's that their customers use. As Windows NT took over one vendor after another, they gradually reached No.1 position and forced customers and vendors to use Windows.

      UNIX competitors didn't help themselves by charging "UNIX" prices for components like monitors and RS232 cables as well as having totally different API's for everything - remnants of this can be seen when reading Linux man pages - there will be references to POSIX behavior, parameters or result codes.

      At this time, Microsoft Mail was the dominant E-mail server software, but even they had to adopt "sockets" in order to connect to web servers. Sun came out with this little PC on a board solution that ran a Windows desktop in a window in order to allow users to use Microsoft Office, before buying up StarOffice (renamed to OpenOffice) and released it to break the Microsoft stranglehold, then went on to provide JAVA as a rival to MFC, .NET and C#

      You can stand up to Microsoft, but only through co-operation, quality and reliability. Make sure that whatever you develop is to an internationally agreed standard that literally leaves no bit unspecified (even in an API function call). Otherwise, Microsoft will just find a way of embracing, extending and extinguishing that specification through a patent on the use of that single bit. Similarly with "extension" based API's and formats.
      Tie down every single bit and avoid any sort of "extension format"

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    5. Re:So ... by Anonymous Coward · · Score: 0

      Man pages are supposed to have references to POSIX behavior, parameters, and return values. Not sure what that has to do with overpriced cables.

    6. Re:So ... by Teun · · Score: 3, Funny

      You deserve your three digit /. ID :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    7. Re:So ... by Anonymous Coward · · Score: 0

      Actually, OS/2 goes by the name of eComStation these days.
      It's being developed by Serenity Systems and eCS v2.0 was released April 29 2010.
      It runs a pretty recent FireFox (v3.5.3), QT Apps and lot's more ported Linux stuff.

      See http://www.ecomstation.com

    8. Re:So ... by armanox · · Score: 3, Informative

      I would point out that StarOffice never ceased to exist (and never was quite the same as OpenOffice), and that .Net and C# came about to push Java out of the market, not the other way around.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    9. Re:So ... by Anonymous Coward · · Score: 0

      Sun [...] then went on to provide JAVA as a rival to MFC, .NET and C#

      Rubbish. C# and .NET came out many years after Java (I'll give you MFC, though).

    10. Re:So ... by Anonymous Coward · · Score: 0

      It was a hard thing to cough up the price of a Workstation (Indigo, DECStation, SPARCStation, etc) around the time that Windows was starting out. X was lightyears ahead, (ooooh wallpaper! 3D objects!), but the simple cost really did it.

      I managed a lab that was largely used for DEC Stations, AlphaStations, Indigos and Indys and Windows 3.11 was pretty much the end of it. First we had an NT 3.1 server, then Windows for Workgroups started popping up, then sooner or later it was mostly "Clones" (non-IBM PCs).

      Though ironically, people for the most part wanted it that way. The students *hated* the DECStations and the Indigos.

    11. Re:So ... by MichaelKristopeit165 · · Score: 0
      it's supposed to be a record of facts... your inability to see self proclaimed "news" outlets as providers of such information is very telling.

      who is "us"?

      you are NOTHING.

      marketeers have invaded this internet web site chat message board and rendered it a useless wasteland for nothing but "tales of woe".

      slashdot = stagnated.

    12. Re:So ... by Anonymous Coward · · Score: 0

      A lot of what turned the workstation market from UNIX was hardware-based not software, it just happened that the new hardware ran Win NT. I'm talking about things like Pentium Pro, Intergraph's 3D graphics etc which made the PC into a viable workstation platform that wiped the floor with UNIX workstations on a price/performance basis, and in some cases was competitive on raw performance. If there had been a viable PC UNIX with broad application support for things like word processing, spreadsheets, corporate email etc (say LINUX as it is today, not as it was in '96) then it might have stood a chance against NT, but there wasn't so NT won by default.

    13. Re:So ... by mikael · · Score: 1

      Thanks - I kindof forgot about the exact sequence of events.Microsoft came out with MFC in 1992
      Java came out around 1995, as a solution to improve security and speed up application development by eliminating the use of pointers and delete memory operators. .Net and C# came out in 2002.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    14. Re:So ... by KingMotley · · Score: 1

      I thought it was because AT&T/SCO unix came on like 80 3.5" disks, and had a shelf and a half of reference manuals so you could get the thing configured, and the unix base was fractured between competing implementations making it extremely difficult for 3rd parties to write software that would run on any of them.

      Add in that the majority of terminals were text-only, and most systems were limited to vt100/vt220/ansi escape sequences (or similiar), and even different manufacturers of those terminals couldn't get the sequence for sending F1-F10 (and other) keys correctly making it a PITA.

      On the other hand windows came on few disks, installed quickly (and no manual needed to do so), and the only reference manual was 1 book, and you really didn't even need that.

    15. Re:So ... by Anonymous Coward · · Score: 0

      having totally different API's for everything - remnants of this can be seen when reading Linux man pages - there will be references to POSIX behavior, parameters or result codes

      Actually, the whole point of POSIX was to provide a unified API. POSIX is mentioned in the Linux documents precisely because the $documented_thing conforms to the POSIX standard - evidence of modern standards-convergence. Whether POSIX succeeded sufficiently in its first decade is debatable of course. But mention of POSIX in modern linux documents is irrelevant to early 90s UNIX competitors having different APIs.

    16. Re:So ... by mikael · · Score: 1

      Because at the time, every UNIX vendor (SGI,HP,Sun,Dec) implemented API's like pthreads, sockets, and GUI systems+widgets such as X-windows/Motif) with different features. It became a headache for application developers to support multiple API's on multiple systems.
      To support an application, they would have to purchase workstations from each vendor. On top of that they would have to pay extra for as end-user licences as well as the compilers.

      POSIX was an attempt to standardize UNIX to make life simple for developers. It came out in 1997, just after Microsoft brought out MFC. Even then some vendors would have official "RS232" cables with extra pins and internal wiring that made sure that regular RS232 cables wouldn't work.

      For a start-up like a new animation studio, it was all too much. Why pay extra for all these licenses, when they could just go down to a hardware store, buy some generic PC hardware, slap on Windows NT + Studio Max , and have a hardware party at the same time?

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    17. Re:So ... by westlake · · Score: 0, Troll

      You can stand up to Microsoft, but only through co-operation, quality and reliability. Make sure that whatever you develop is to an internationally agreed standard that literally leaves no bit unspecified (even in an API function call).

      That standards committee takes eternity and a day to come to a decision.

      Which will, most likely - in the end - ratify existing practices, while tossing a bone or two to every significant faction. The Engineer. The Corporation. The Nationalist. The Ideologue, and so on.

      The Kinect controller hits retail shelves just weeks before Christmas. 20% of prime time Internet traffic becomes a Netflix stream. Dwarfing YouTube, BitTorrent. Everything. 500 million people sign on to Facebook - before the geek is aware he has taken a punch to the gut.

             

    18. Re:So ... by steelfood · · Score: 1

      More likely, they released Java to compete with MS's Visual products like Visual Basic. They made their language platform-independent to try to level the playing field so that companies wouldn't become increasingly dependent on MS APIs--and the latest version at that.

      MS did try to kill Java with their own JVM implementation. Fortunately, the market and consumers were wising up to MS's business practices and Sun sued.

      From one perspective, Java did its job. A lot of (new) enterprise code is written is Java nowadays, whereas it would've otherwise had to have been written in C or a C-derivative, most likely against a Windows-based compiler and using Windows libraries. It pretty much removed Visual Studio as a threat to the server application development environment, and it quite possibly single-handedly stopped MS from further penetrating into the entreprise server market.

      On the other hand, all Java really did in the end was swap one dictator for another. Sun may have been benevolent, but Oracle certainly isn't. And with the threat of patents against alternative-VM implementations, it's quite possible Oracle is now going to get where Microsoft would have been fifteen years ago, and where IBM was 40 years ago.

      Interesting times we're living in... interesting times...

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    19. Re:So ... by vegiVamp · · Score: 1

      Umm... I seem to recall Java predating .net and C# by quite a bit, actually.

      --
      What a depressingly stupid machine.
  3. DVX by ehrichweiss · · Score: 1

    I still have a copy of DesqView/X which I know came afterward but was a much better alternative. I remember a friend showing me it running on top of DOS and Windows 3.1(or maybe it was '95) running on DVX. That was better multitasking than Windoze ever brought.

    --
    0x09F911029D74E35BD84156C5635688C0
    1. Re:DVX by Rifter13 · · Score: 1

      RIP Desqview/X. I remember running it, and loving it. I was able to get a few other friends to try it, too. I agree with you on this.

    2. Re:DVX by commodore64_love · · Score: 1

      DesqView is listed in the article as arriving in 1985: "DESQview sold only a tiny fraction as many copies as Windows did, but it was one of the few packages here that qualified, for a while, as a success. At some point, though, sticking with DOS apps and running them in DESQview went from a perfectly understandable decision to a weird affectation."

      I dislike windows. Now I have Puppy Linux (based on Ubuntu 10.0) which fit inside just 96 MB of memory, but I still need windows for some apps. Like my Netscape ISP and Accelerator software.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    3. Re:DVX by Safety+Cap · · Score: 2, Informative

      Windows 3.1(or maybe it was '95) running on DVX.

      It would've been Win 3.1. DV/X was released in the early 90s, well before Win95.

      --
      Yeah, right.
  4. OS/2 by Markvs · · Score: 2, Insightful

    As someone who in 1991 ordered his 386/SX (4MB RAM, 80MB hard drive and 256k VGA card) with MS DOS 5.0 and Windows 3.0, I'm amazed that OS/2 isn't mentioned in the article since it was the other OS option at the time.

    --
    46. The Hobo smiles, his eyes glaze over, and he burps. "Beware the man who has lived longer than the Wasteland."
  5. I used to use GEM / Ventura by DrSkwid · · Score: 1

    GEM was pretty good but Ventura was the only app I ever came across for it.

    DesqVIEW was useful but really just as a fancy menu / full screen task switcher.

    For a while were were an OS/2 shop, it really was better than Windows but Windows did the dirty with Word and here we are.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:I used to use GEM / Ventura by MrEricSir · · Score: 2, Interesting

      I remember that when you ran DOS apps when GEM, it would open a dialog asking how much RAM you wanted to allocate for the program. Hardly a user-friendly desktop.

      --
      There's no -1 for "I don't get it."
    2. Re:I used to use GEM / Ventura by Anonymous Coward · · Score: 1, Informative

      It may be true that DesqView was just a task switcher; but DesqView/X -- X meaning X11 -- was much more.

    3. Re:I used to use GEM / Ventura by Malc · · Score: 2, Interesting

      GEM Desktop was great (I had it on an Amstrad 1512, with dual 360K 5.25" floppy drives!), but crippled compared with the version running on Atari STs because they removed the "trash can" thanks Apple being predatory.

    4. Re:I used to use GEM / Ventura by HBI · · Score: 3, Interesting

      You didn't use Desqview appropriately, then.

      With QEMM loaded on a 386 platform and lots of available memory, Desqview was a superior multitasker that would run raw DOS applications simultaneously. No special coding required, though if you did code to TopView/DV then more applications could be run simultaneously.

      I ran 4 nodes of a DOS multinode BBS, along with door applications, on a single 386-20 DV box with 4MB of RAM. Searchlight, then Wildcat, if you are interested.

      Easily kept up with the modems. In fact, the lack of a multiport serial board was more the reason why I didn't run more nodes than any inherent limitation of DV. There was plenty of CPU to spare.

      The only limitation DV really had was that it didn't arbitrate hardware misconfigurations. Therefore, if you tried to use the same ports/IRQ lines from different windows, you could lock the system hard. Assuming you weren't doing anything stupid, though, it was great stuff. Also, doing BIOS video output made it easier for DV to control the output. Most applications did direct screen writes, so you were kind of stuck with the overhead unless you wrote your own code. I did, so using BIOS output was an option for me.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    5. Re:I used to use GEM / Ventura by SCPaPaJoe · · Score: 1

      Wow, I had the very same computer. I upgraded it with a 20MB hard drive and used it as a retail store POS system until 1997. The computer's power supply was in the monitor! Didn't it also require 2AA batteries to maintain bios settings?

    6. Re:I used to use GEM / Ventura by rongage · · Score: 1

      DesqVIEW was useful but really just as a fancy menu / full screen task switcher.

      As someone who ran a 4 node BBS on a single 386-40 with 4 high speed nodes (USR Sportsters and Dual Standards) using DesqView and PCBoard, I think your description of "fancy menu / full screen task switcher" is a touch off. DesqView could easily handle running all 4 nodes at once plus an operators console. It was always interesting watching all 4 nodes in operation at once (windowed mode - in text).

      Ron

      --
      Ron Gage - Westland, MI
    7. Re:I used to use GEM / Ventura by elrous0 · · Score: 1

      I agree, GEM was truly, truly, truly outrageous.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    8. Re:I used to use GEM / Ventura by JoeWalsh · · Score: 1

      I miss DesqView. Like you, I ran a multinode BBS on pretty plain hardware (386SX-16 w/ 4 MB RAM in my case) thanks to DesqView and QEMM386. Those were the days! As you said, DV was great stuff, as long as you knew what you were doing.

    9. Re:I used to use GEM / Ventura by smchris · · Score: 1

      "and lots of available memory"

      Ding! Ding! You said the magic word. Like I said on this thread (last week?), most of us who _weren't_ sys admins, or whatever, who were droning away using the programs of the time on typical hardware didn't have ram to spare to play with stuff. Sure, I "evaluated" a copy of DESQview. Conclusion? I couldn't do my work with it installed.

    10. Re:I used to use GEM / Ventura by DadLeopard · · Score: 1

      Your right the version for PC was pretty much Neutered after Apple Sued over the "Look and Feel" two fixed windows, no trash can and not much in the way of software for it! The version on the Atari ST was superior in every way! I still think that if not for Apple, Gem would have ended up as the default OS for PCs today!

    11. Re:I used to use GEM / Ventura by HBI · · Score: 1

      I remember at the time that someone thought I was nuts for loading my 2 machines with 4 and 5mb of RAM, respectively. It wasn't all that expensive - at the time RAM was about $70 a megabyte, down far from the $500/meg heights it had hit in 1987 or so.

      The memory served me well then, and having more RAM will serve just about anyone well even today.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    12. Re:I used to use GEM / Ventura by Purity+Of+Essence · · Score: 1

      Atari's version of GEM was great. I really miss those machines. Of course, any OS that includes J. R. "Bob" Dobb's in the character set wins by default.

      --
      +0 Meh
    13. Re:I used to use GEM / Ventura by drcheap · · Score: 1

      The fact that the parent post has gone over 3 hours without a single +1 Funny moderation really shows how many /. members weren't even alive in the 80s.

      Age...sigh.

    14. Re:I used to use GEM / Ventura by gl4ss · · Score: 1

      we had a single 360k and a 20mbyte hd. gem was simple enough for us kids to use and also the ability to give parameters to dos progams you were launching was a good feature, that's how I understood what such parameters were. ..those amstrad mouses weren't the best around though, didn't work with all games(worked with most games, but in some the rmb didn't work).

      --
      world was created 5 seconds before this post as it is.
    15. Re:I used to use GEM / Ventura by Malc · · Score: 1

      Actually the biggest problem I had with the Amstrad 1512 were the graphics. Although it could do well enough for GEM, it wasn't a standard PC video mode. The common standard it supported was CGA (four colours, two palettes). It's elder brother (which we didn't have at home), the 1640, did much better as it supported EGA (and added some extra RAM).

    16. Re:I used to use GEM / Ventura by Malc · · Score: 1

      Ahhh, I just looked over the Wiki page, which is bringing back memories. I'd forgotten my trials with the mouse and joystick. Certainly a lesson in standards.

    17. Re:I used to use GEM / Ventura by Malc · · Score: 1

      Rings a bell. I remember fiddling around with the NVRAM. Have you seen the Wiki page?

    18. Re:I used to use GEM / Ventura by elrous0 · · Score: 1

      Well, there goes my plans for a Sgt. Slaughter joke.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    19. Re:I used to use GEM / Ventura by DrSkwid · · Score: 1

      Nah, I guess I just didn't have enough DOS apps I wanted to run simultaneously.

      Also perhaps I mis-remember its awesomeness :)

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  6. Don't Forget: by Anonymous Coward · · Score: 1, Informative

    DR-DOS.

    Yours In Novosibirsk,
    K. Trout

    1. Re:Don't Forget: by KingAlanI · · Score: 1

      TFA does mention it obliquely in the section for fellow Digital Research product GEM.

      --
      I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
  7. X-Windows? by mozumder · · Score: 2, Funny

    Half the audience here is still running it.

    1. Re:X-Windows? by Beelzebud · · Score: 2, Insightful

      Well then I guess it wasn't a failed one, was it?

    2. Re:X-Windows? by Anonymous Coward · · Score: 0

      It came out in 1984, so why are we talking about this MS Windows thing again?

    3. Re:X-Windows? by Anonymous Coward · · Score: 0

      Because you're all failures...

      In some ways, one could say that MacOS failed against Windows (especially 7), and Linux failed against MacOS. Even Ubuntu is dumping X!

    4. Re:X-Windows? by mozumder · · Score: 5, Funny

      This is slashdot.

      If slashdot users are using it, then it failed in the real world.

    5. Re:X-Windows? by Anonymous Coward · · Score: 0

      OTOH, INGIALOPLI (it's no good if a lot of people like it)

    6. Re:X-Windows? by Ginger+Unicorn · · Score: 1

      your mom failed in the real world?

      --
      (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
    7. Re:X-Windows? by Anonymous Coward · · Score: 0

      This is slashdot.

      If slashdot users are using it, then it failed in the real world.

      Slashdot is where I come with my MiniDisc questions.

  8. SideKick (by Intuit) by Anonymous Coward · · Score: 2, Insightful

    This was perhaps the Enabler for Windows. It addressed the primary multi-tasking via
    a terminate-and-stay-resident pop-up that had a calculator, todo list, and the like.
    By solving this problem for Word Perfect, Lotus and DB3 users, it delayed the
    adoption of windowing environments for another 2-3 years till Windows 3.0

    1. Re:SideKick (by Intuit) by confused+one · · Score: 1

      DESQview gave you some of the same capability by making entire user environments swappable. I used both, SideKick and DESQview.

  9. One more... by Compaqt · · Score: 1
    --
    I'm not a lawyer, but I play one on the Internet. Blog
    1. Re:One more... by Anonymous Coward · · Score: 0

      Yup...figures that AmigaOS wouldn't get mentioned. It's OS and hardware package continued to put Mac and Windows to shame for at least 10 years after it's release.

  10. Hard to forget hell. by pugugly · · Score: 4, Insightful

    "Twenty-five years and two days later, it’s not just hard to remember an era in which Windows wasn’t everywhere"

    Bullshit - As a C64 and Atari ST veteran, twenty-five years later it's painful to remember the extraordinary effort it took to lose to windows. I had better graphics playing Neuromancer on the C64 than windows managed for a decade, and let's not even talk about comparing Star Flight on the ST vs the DOS version.

    Jack Tramiel should be strung up for crimes against computing.

    {sigh} - Pug

    --
    An Invisible Entity of Vast Power whose existence must be taken on faith alone: Liberal Media
    1. Re:Hard to forget hell. by Tuan121 · · Score: 3, Funny

      Your solid and detailed argument of "Neuromancer on C64 had better graphics than on Windows" is such a solid argument I'm just not sure where to start attacking it...

    2. Re:Hard to forget hell. by Mike+Buddha · · Score: 3, Insightful

      So many people have posted that what you need to succeed against Microsoft is simply greed. I think Jack Tramiel is evidence that this is not true. Greed != Business Acumen.

      --
      by Mike Buddha -- Someday the mountain might get him, but the law never will.
    3. Re:Hard to forget hell. by Angst+Badger · · Score: 3, Insightful

      Bullshit - As a C64 and Atari ST veteran, twenty-five years later it's painful to remember the extraordinary effort it took to lose to windows. I had better graphics playing Neuromancer on the C64 than windows managed for a decade, and let's not even talk about comparing Star Flight on the ST vs the DOS version.

      Seriously. I never had one -- I was an Apple II fanatic for reasons (obviously) unrelated to its graphics capabilities -- but the Atari ST was an amazing piece of hardware, way ahead of its time, and in retrospect, I can see that it was clearly the best of the 8-bit era. This was a machine with three microprocessors: one general purpose CPU and separate processors for both sound and video. And it was cheaper than most of its competitors. It probably would have been vastly successful if the Atari name hadn't been so firmly associated with games.

      I wonder how old the author of TFA is. It's not hard to remember life before Windows at all. I remember life before DOS, back when the first pull-down menus were implemented in WordStar -- a text editor by today's standards -- solely as an aid to learning the key commands.

      Hardware and software have come a long way since then, but it came at the expense of losing the rich variety of the early personal computer era, to the point that people now have passionate arguments about the barely perceptible differences between Mac and PC GUIs.

      Hm, if I'm not mistaken, this is where I should tell someone to get off my lawn. ;)

      --
      Proud member of the Weirdo-American community.
    4. Re:Hard to forget hell. by H0p313ss · · Score: 2, Interesting

      "Twenty-five years and two days later, it’s not just hard to remember an era in which Windows wasn’t everywhere"

      Bullshit

      My thoughts exactly, it makes me wonder how old this kid was (and will he stay off my lawn?)

      Given just how retarded Windows 1 was compared the original Mac we should be more surprised just how successful they've been. Even Win 3.1 only competed with Apple on price. If nothing else Microsoft has my respect for putting lipstick on that pig and finally delivering XP and Win 7 which are pretty damn good.

      (Disclaimer: my personal machines run OSX, iOS, Win7, Vista, XP and Linux ... as an oldschool Linux junkie who has version 0.9 on floppy disk I'm almost ashamed to admit that my OS of choice these days is Win 7)

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    5. Re:Hard to forget hell. by UnknownSoldier · · Score: 3, Informative

      The GP had a point. You remember what they jokingly referred to the CGA as? Crappy Graphics Adapater, because it had 4 colors: black, white, cyan, and magenta.
      http://en.wikipedia.org/wiki/Color_Graphics_Adapter

      Hell, even my Apple ][ had (graphics) Page Flipping plus 6 colors: black, white, green, violet, orange, blue
      http://www.codinghorror.com/blog/2006/01/i-heart-cheatsheets.html

    6. Re:Hard to forget hell. by radish · · Score: 3, Informative

      Agreed, except that the ST was 16-bit (actually parts were 32-bit). There's a rumor (not sure how true it is) that the letters "ST" came from "Sixteen/Thirtytwo".

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    7. Re:Hard to forget hell. by WeatherServo9 · · Score: 1

      and let's not even talk about comparing Star Flight on the ST vs the DOS version.

      Up until the late 80's the ST did have some nice advantages over PC, but I'm not sure this is a great example: the ST version of Starflight came out 4 years after the PC version and was improved quite a bit over the 1986 PC original (which did not really push the platform to its limits to begin with). By 1990 a PC version could easily have been much better than the ST release.

    8. Re:Hard to forget hell. by jandrese · · Score: 1

      I've often thought it was odd that CGA went white instead of yellow for that fourth color. At least with Yellow you could have pretended to be kinda sorta colorful, instead of just having basically two highlight colors like it did. Granted, people might not like reading yellow text all of the time, but a lot of computers throughout history have used alternate default colors (blue backgrounds, yellow text, who doesn't remember the old days?).

      --

      I read the internet for the articles.
    9. Re:Hard to forget hell. by dannys42 · · Score: 1

      Actually, CGA did have a separate palette that had yellow instead of white. And I think cyan and magenta were more green and red in that mode as well. I personally never really liked that mode, and fortunately it didn't appear to be used all that often.

    10. Re:Hard to forget hell. by Anonymous Coward · · Score: 0

      There was an alternate CGA palette with black, brownish-orange, red, and purple ...

    11. Re:Hard to forget hell. by Anonymous Coward · · Score: 0

      Sorry, yellow not purple.

    12. Re:Hard to forget hell. by SGDarkKnight · · Score: 1

      Atari ST... thats bringing back memories, i still remember my first computer which was a Atari 800-XL -- ah the good old days.

      --

      ...A no smoking section in a restaurant is like having a no peeing section in a swimming pool...
    13. Re:Hard to forget hell. by WeatherServo9 · · Score: 1

      Page flipping was probably the biggest advantage Apple II had over CGA, and CGA wasn't the greatest possible, but the comparison isn't quite so simple as Apple II had more colors (which isn't always true).

      First, do you have the CGA card connected to a composite or RGB monitor?

      If a composite monitor, CGA wins big time in number of colors. You could get 16 at a time (even more with some programming trickery, though I've never seen anyone really take advantage of this). Also, there were quite a few different palettes available, you didn't have to always have the same set of 16 colors. Resolution is slightly lower (160x200 vs 280x190) though. A couple years later Apple introduced the double hi-res mode which would bring 16 colors to the Apple II.

      If an RGB monitor, you can get 16 colors in 40 or 80 col text modes (compare to black and white on Apple, plus 80 col text was much sharper on CGA), but only get 4 colors at a time in 320x200 graphics or 2 colors in 640x200 graphics. Resolution is higher (320x200 vs 280x190) than Apple II. Also you can make each pixel whatever color you want without affecting other pixels, something not possible on the Apple IIe due to the oddities of using a composite display and the manner in which Apple II created some of the colors. While some clever programmers made this an advantage to apparently gain two more colors (yellow and pink if I recall) there were certain pixel combinations that just weren't possible without some bizarre unintended consequences. You were not limited to just cyan/magenta/white/black as you implied, this was the default, but other combinations were possible; background color could be any of the 16 colors, and 6 foreground color palettes were available.

    14. Re:Hard to forget hell. by operagost · · Score: 1

      Since we're talking about circa 1985 here, the PC had a 16 color EGA adapter at the time.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    15. Re:Hard to forget hell. by Anonymous Coward · · Score: 1, Interesting

      the Atari ST was an amazing piece of hardware, way ahead of its time, and in retrospect, I can see that it was clearly the best of the 8-bit era.

      It was a 16/32 bit machine, not 8.

      This was a machine with three microprocessors: one general purpose CPU and separate processors for both sound and video.

      It had exactly one microprocessor, the CPU. The sound chip was an off the shelf Yamaha sound chip, a decent (by 1980s standards) tone generator chip. It was strictly a peripheral chip (i.e. incapable of doing anything complex without CPU control). As for video, most STs had just a dumb framebuffer. Later models added a blitter, which is basically a memory copy/modify/fill engine. Once again, strictly a slave to the CPU, no real intelligence of its own.

      The coolest thing about the ST's hardware design was that it was the fastest of the main 3 mid-80s ~8 MHz 68000 personal computers (Macintosh, Amiga, ST). It had a DRAM controller which (IIRC) ran 2x as fast as the CPU needed it to, so that even cycles serviced the CPU and odd serviced DRAM refresh and DMA peripherals like the blitter, floppy controller, and ACSI disk interface. This meant that its CPU always ran flat out with minimal wait states, and it also had fast disk I/O. (ACSI note: it was a bit like 8-bit parallel SCSI, but without quite enough smarts to actually be SCSI. Atari STs used SCSI host adapters which attached to the ST via ACSI.)

      It probably would have been vastly successful if the Atari name hadn't been so firmly associated with games.

      It would have been much more successful if Atari management knew how to be a successful computer company. The ST just kind of sat there for years without any significant evolution of the platform, hardware or software.

      It also didn't help that the launch hardware firmly associated itself with games by being a non-expandable keyboard wedge form factor. It wasn't until the Mega ST that they had a design suited for non-home use (and even the Mega wasn't very expandable).

    16. Re:Hard to forget hell. by KingMotley · · Score: 1

      Yes, ST meant sixteen/thirty-two. The later versions of the atari were named TT for thirty-two/thirty-two.

    17. Re:Hard to forget hell. by Purity+Of+Essence · · Score: 2, Informative

      Sorry, green not brownish-orange. You were so close.

      Actually CGA had two palettes, each with a dark and light version:

      black - dark cyan - dark magenta - gray (dark white)
      black - cyan - magenta - white
      black - dark green - dark red - brown (dark yellow (sort of))
      black - green - red - yellow

      Brown has actually encoded as dark yellow, but RGBI monitor hardware intercepted an altered the color to a "more pleasing" brown. On a composite monitor, the color remains dark yellow.

      --
      +0 Meh
    18. Re:Hard to forget hell. by westlake · · Score: 1

      I had better graphics playing Neuromancer on the C64 than windows managed for a decade

      What you didn't have - until the C-128 - was a decent keyboard and an 80 column display. What you didn't have was an upgrade path for C-64 video and sound.

    19. Re:Hard to forget hell. by Stuntmonkey · · Score: 2, Interesting

      Jack Tramiel should be strung up for crimes against computing.

      I wouldn't call them crimes necessarily. Tramiel was just misguided: He thought of computers as an extension of the calculators he made before, which were an extension of the typewriters before that. In this mindset the computer is a widget that is undifferentiated from any other, where price and distribution are all-important and the engineering details don't matter. This fundamental mistake spelled doom for Commodore, but on the other hand it made computing accessible to a huge number of people. Most people who got started with computing in the early-to-mid 1980s got their start on a Commodore computer that was probably 1/5 to 1/3 the price of anything Apple sold.

      It is shocking though how little Tramiel actually understood. As when he finally realized he needed a floppy disk drive, then told his team to have the software done in a weekend! No wonder the stock 1541 was so lame.

    20. Re:Hard to forget hell. by Anonymous Coward · · Score: 0

      It was used half decently in early Sierra titles like kings quest & space quest. With a blue background you had R,G,B and Y, and with dithering you got decent approximations of purples, oranges etc. It was far from ideal but looked better than the CMW mode.

    21. Re:Hard to forget hell. by vegiVamp · · Score: 1

      I think you need both, actually. The business acumen lets you see how to beat competitors, but the greed makes you actually perform the necessary evils.

      --
      What a depressingly stupid machine.
    22. Re:Hard to forget hell. by master_p · · Score: 2, Informative
      You are wrong on most of your accounts. It's amazing that memory has faded so fast. 25 years is not that of a big period of time to forget all those things.

      but the Atari ST was an amazing piece of hardware,

      It wasn't. It was a shitty piece of hardware, bolted on the superior cpu of the time (the MC68000). The sound chip of the ST as an FM modulator with 3 channels and only one hardware channel, and there was no graphical acceleration. Graphics were limited to 320x200 with 16 colors, 640x200 with 4 colors and 640x400 with 2 colors. It had MIDI ports, but the joystick ports were 'reversed' so you could only buy Atari joysticks to connect to it.

      I can see that it was clearly the best of the 8-bit era.

      Having a 32-bit CPU with a 24-bit address space, the Atari ST was a 32-bit computer, with 24-bit memory, confined in the limitations of a 16-bit machine. It was not 8-bit. 8-bit computers included the machines with the Z80 and 6502 CPUs (ZX Spectrum, Amstrad CPC, BBC Acorn Electron, Apple I/II, Commodore 64 and their offsprings).

      and separate processors for both sound and video

      No, it did not. It had minimal support for hardware sound and graphics. Most Atari ST games were really bad when compared to Amiga, which had real custom chips.
      The Atari ST got a Blitter chip with STE, and a DSP with Atari Falcon.

      And it was cheaper than most of its competitors.

      It wasn't. It cost a little bit less than the Amiga, but it was way inferior to the Amiga in all things that mattered. The Atari ST was much more expensive than the 8-bit micros of the time.

      I wonder how old the author of TFA is. It's not hard to remember life before Windows at all. I remember life before DOS, back when the first pull-down menus were implemented in WordStar -- a text editor by today's standards -- solely as an aid to learning the key commands.

      I wonder if you really had an Atari ST. I had a friend who was a fanatical Atari supporter, while I had an Amiga. We had epic "battles" regarding which computer was superior, and the Amiga always came on top. This is understandable though, because the Atari ST lacked any sort of hardware support for graphics and sound.

      Hardware and software have come a long way since then, but it came at the expense of losing the rich variety of the early personal computer era, to the point that people now have passionate arguments about the barely perceptible differences between Mac and PC GUIs.

      The rich variety you mention was a setback, actually. It meant wildly different codebases for game companies for the same games, wildly different graphics, wildly different music. GUI applications had to deal with totally different UI concepts and capabilities. Software companies back then had to actually choose one of the platforms to develop on, as they were wildly different. Creating the same game for different platforms meant that you had to give all your data to a third party that was specialized in developing programs for the other platform. Writing code meant assembly. There were no fancy IDEs, C compilers, garbage collection and all that jazz and hand holding we have today.

    23. Re:Hard to forget hell. by Anonymous Coward · · Score: 0

      Star Flight. I remember having to put the computer in 16 MHz on my PC because it ran too fast on 32. On my C64, it was perfect.

    24. Re:Hard to forget hell. by Angst+Badger · · Score: 1

      I stand corrected, but...

      I wonder if you really had an Atari ST.

      ...if you had read the very first sentence of my post as carefully as the rest that you so carefully dissected...

      Seriously. I never had one --

      ...you'd have noted that I didn't have one, so my knowledge was second-hand. Again, I stand corrected.

      The rich variety you mention was a setback, actually. It meant wildly different codebases for game companies for the same games, wildly different graphics, wildly different music. GUI applications had to deal with totally different UI concepts and capabilities. Software companies back then had to actually choose one of the platforms to develop on, as they were wildly different. Creating the same game for different platforms meant that you had to give all your data to a third party that was specialized in developing programs for the other platform. Writing code meant assembly. There were no fancy IDEs, C compilers, garbage collection and all that jazz and hand holding we have today.

      This is typical of a programmer-centric view of things. I'm not without sympathy to that view, having spent the last twenty years as a programmer, but it entirely misses the point of computers, which do not exist for the benefit of programmers. Computers exist for the benefit of users, as do programmers. During the 8-bit era, there was a lot of competition and lots of choices for users, and that was a good thing... for users. Now, we have only one major PC hardware platform -- Intel and its clones -- and three major operating systems -- Windows, Mac OS, and Linux and its derivatives -- that really don't differ much from the POV of the average user. There aren't enough competitors at any level to give users real choices or to prevent abusive behavior from vendors, and what could have been a compensating factor, the open source "movement", is dominated by self-serving narcissists who think that the point of hardware advances is to allow them to be ever less efficient.

      And yes, some of it is just the simple nostalgia effect, but there are some very real respects in which things turned out for the worse.

      --
      Proud member of the Weirdo-American community.
    25. Re:Hard to forget hell. by Mike+Buddha · · Score: 1

      True dat. Take Steve Jobs, for instance. He's always been greedier even than Bill Gates, he just didn't have the business acumen part until the third generation (the Windows-compatible one) came out. Once he stumbled into the fact that he can't sell computers, Apple flourished.

      --
      by Mike Buddha -- Someday the mountain might get him, but the law never will.
  11. What about GEOS/GeoWorks? by Anonymous Coward · · Score: 0

    Exactly as stated. What about GeoWorks, and its Ensemble upgrade? If I recall (which may be incorrect), GeoWorks was another competitor about that time. And it also was one of the (if not THE) first to run AOL, back when it was one of the more easily-used online systems before the Internet became the behemoth it is today.

    Once Win95 with 32-bit computing came out for desktops (even with all its bumps and bruises), it seems Geos wasn't able to keep up, unfortunately.

    1. Re:What about GEOS/GeoWorks? by abigor · · Score: 2, Informative

      GEOS is mentioned on page 2. I remember using a version of it on my old C64! Remarkable software.

  12. I used GeoWorks by David+Gerard · · Score: 2, Interesting

    I was working as a paperwork generator for a school funding appeal in 1994. They wouldn't pay the bucks for Windows 3 (why spend $45 when you're only trying to make $3 million), but I did get GeoWorks to run on my 386SX (which I had only because when my 286 died, they couldn't get a replacement 286 motherboard; they were very annoyed). It was very nicely designed, ridiculously usable and very fast. Fatal problem? It was ridiculously unstable and would crash if you looked at it funny. Windows with Wordpad would have beaten it as a productivity tool. Oh well.

    --
    http://rocknerd.co.uk
  13. Desqview by TheDarkener · · Score: 4, Interesting

    was awesome. I used it to run multiple nodes on my Renegade BBS. Of course, back then nothing was truly multitasking, but this was pretty darn stable for its time. We moved to Windows '95 when we were told that it would provide better multitasking abilities.

    It was at that point I started truly despising Windows/Microsoft. "What are all of these files in my root directory?" I remember exclaiming. I always kept a very organized filesystem, and now my operating system was telling me I couldn't do that anymore.

    It was all pretty much downhill from there.

    --
    It is pitch black. You are likely to be eaten by a grue.
    1. Re:Desqview by gstoddart · · Score: 5, Informative

      Of course, back then nothing was truly multitasking, but this was pretty darn stable for its time.

      Well, except for UNIX and a couple of others. There was real multi-tasking in 1985, don't let anybody tell you that Windows '95 was first with it.

      MS was actually late to the game when it came to multi-tasking.

      --
      Lost at C:>. Found at C.
    2. Re:Desqview by elbobo · · Score: 3, Insightful

      Same experience here. Nothing at the time other than DESQview was offering decent multitasking for tasks like BBSes. Windows was a joke in comparison.

      Eventually I gave up DESQview, but it was a painful transition and I bitterly resented Microsoft for winning in the market with their inferior product.

    3. Re:Desqview by TheDarkener · · Score: 1

      Well, except for UNIX and a couple of others.

      Sure - I should have clarified, no real multitasking in MS-based operating systems =)

      --
      It is pitch black. You are likely to be eaten by a grue.
    4. Re:Desqview by dada21 · · Score: 3, Interesting

      Lord I miss those days. I ran Renegard multinode until I bought MajorBBS (which was really efficient, but proprietary).

      Remember the Extended versus Expanded memory hub-bub way back when? 640K is enough for anyone!

    5. Re:DESQview by Tanktalus · · Score: 4, Interesting

      I started running my BBS under DESQview. However, I then wanted to learn to program C++, and went out and bought Borland C++ for Windows. Silly me. At least it was the student edition (read: cheap). So I thought, well, Windows 3.1 claims to multitask DOS apps, so why not try it? Well, just running the single DOS app under Windows, not even having anything else loaded, on a 486dx2/66 w/16MB RAM, resulted in users complaining about speed - on their 2400 baud modems. So I knew that was a no-go.

      Then, someone at work (I was a co-op student at the time) suggested OS/2. After buying a student copy of that, too, I installed it. I could run two nodes of the BBS at 33.6kbps PLUS compile under Windows, or I could run one node AND use the other modem to connect to the internet via the university, and load up a web browser and do all of that stuff while the DOS BBS continued to run just fine.

      Later I switched from Renegade to Maximus which had a native OS/2 version. Used a lot less resource that way, but even then, Renegade for DOS still *worked* under OS/2, which is more than I could say for the same machine running DOS 5.0 / Windows 3.1.

      I continued with OS/2 for years, and avoid Windows still, just because it has never, in my estimation, been able to handle what I threw at OS/2, or now throw at Linux. I still miss the OO desktop OS/2 had, that and the Extended Attributes. They were really really useful things - metadata attached to a file that when you removed the file, the metadata automatically went away. Brilliance. Copy the file, the metadata copies along. Move the file, the metadata moves with it. Absolute brilliance. The 64KB limit might have been a bit low to continue on into today, but the idea was still awesome.

    6. Re:Desqview by Khashishi · · Score: 1

      What is the difference between real multitasking and fake multitasking? I don't think processors with multiple cores existed back then.

    7. Re:DESQview by elbobo · · Score: 2, Interesting

      Well, just running the single DOS app under Windows, not even having anything else loaded, on a 486dx2/66 w/16MB RAM, resulted in users complaining about speed - on their 2400 baud modems.

      Yep. Same here. I gave it a try, and wow was it ever bad - completely unworkable.

      I never got into OS/2, having no copy available to me (I just couldn't afford it). I did my C in Borland's DOS based Turbo C++ inside DESQview and was blissfully ignorant of what life under OS/2 might be like.

      By all accounts I heard soon after that time, OS/2 was a glorious thing, so I'm always mildly disappointed I missed out on it. I think I held out in DESQview land (and then Linux without X) until almost Windows 98 times.

    8. Re:DESQview by Anonymous Coward · · Score: 0

      Desqview didn't fail either.

      It did what it was supposed to do. And the first versions worked perfectly. And amazingly... the company would actually support the thing you bought! (gasp) A real live human would help you!

      I've STILL go an ancient little machine sitting somewhere running desqview.. And it still works perfectly 20 years later and barring hardware failure. I imagine it will sit there doing it's jobs for another 20 years.

    9. Re:DESQview by 0123456 · · Score: 1

      By all accounts I heard soon after that time, OS/2 was a glorious thing, so I'm always mildly disappointed I missed out on it. I think I held out in DESQview land (and then Linux without X) until almost Windows 98 times.

      I used both in the 3.0 days: OS/2 was architecturally superior, but Windows was cheaper and had more software and hardware support so it was pretty much a no-brainer for home users.

    10. Re:Desqview by 0123456 · · Score: 1

      What is the difference between real multitasking and fake multitasking? I don't think processors with multiple cores existed back then.

      Real multitasking doesn't depend on applications to decide when to switch, the OS does it transparently for you. As far as I remember Windows 3.x performed task switching during message processing, so an application which looped forever after receiving a message could hang the entire OS.

      I'm sure someone will correct me if my memory is wrong.

    11. Re:DESQview by elbobo · · Score: 1

      It's hard for me to describe how much appreciation and affection I had for DESQview. It was such a joy, with really no negatives. Every dabbling I had with Windows in comparison just further cemented my love of DESQview and hatred for the unacceptably substandard tripe Microsoft were pushing.

      DESQview -> Linux without X -> Linux with X -> OS X (10.2) -> today.

    12. Re:Desqview by radish · · Score: 4, Informative

      Preemptive vs co-operative. In early multitasking setups (Win 3, MacOS, etc) each task had to cede control of the CPU itself so that the OS could schedule the next process - a badly behaved app could fail to do so and thus take over the whole system. Preemptive multitasking puts the OS in control so that it can decide how much CPU time each process gets.

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    13. Re:DESQview by John3 · · Score: 1

      I too ran a multi-node BBS (PCBoard) for many years under DESQView with QEMM. It ran reliably and on pretty basic hardware. By the time the hardware improved the Internet was replacing BBS setups so I just moved the BBS message boards into the web and newsgroups.

      --
      "We make our world significant by the courage of our questions and by the depth of our answers." Carl Sagan
    14. Re:Desqview by squizzar · · Score: 1

      I'm guessing preemption. From what I remember earlier versions of windows relied on 'co-operative' multi tasking: one bad program would never release the CPU and everything hung up.

    15. Re:Desqview by gstoddart · · Score: 1

      What is the difference between real multitasking and fake multitasking? I don't think processors with multiple cores existed back then.

      Windows 3.1 used to use time slicing ... if you had three apps running, they each got around 1/3 of the CPU time, even if they were idle. (You could tweak it, but that's the gist of it.) It essentially meant that performance of multiple tasks in Windows 3.x degraded and was wasteful since apps you weren't using at the moment still got their chunk of the CPU time..

      Pre-emptive multi-tasking allows the task schedule to interrupt a program at an arbitrary point, and swap it for another running program. It uses some hardware features introduced in the 286 but shored up in the 386 that allowed for memory to be segmented and kept separate, as well as support for hardware context-switches.

      Apples used to run in a model where it was considered good form for the apps to offer to relinquish the CPU regularly, so that they could all cooperate and give the user a better experience.

      --
      Lost at C:>. Found at C.
    16. Re:Desqview by Clueless+Moron · · Score: 1

      "Fake" multitasking is what early Macs and MSWindows did. It was also known as "cooperative multitasking". With that, when your process makes a system call, the OS might take the opportunity to switch to another task instead of immediately finishing the call. The fundamental problem with this is that if some code is stuck in a lengthy loop where it doesn't make system calls, no other tasks can run. A trivial infinite loop would effectively lock up your system. Anyway, the end result to the user was very "jerky" interaction with the GUI since the taskswitching was so coarse and unpredictable.

      "Real" multitasking is transparent to each process. Every now and then the CPU will just save the state of a given process and switch to running another process. Eventually it'll restore the state of the original process and pick up where it left off. This is normally done off a timed interrupt. So an infinite loop won't effectively hang the system, plus the scheduler can (for example) allocate fewer timeslices to processes that do not require user interaction.

    17. Re:Desqview by rwbaskette · · Score: 1

      I still remember reading covetously about the old DESQview/X system. Much later than Windows 1.0, but the X windowing system plus ability to run DOS and Windows 3.1 in boxes blew me away.

      I'd still like to install it on something just to play with it.

    18. Re:DESQview by kwalker · · Score: 1

      I used DESQview as well, and I ran a little 2-node BBS under it. I was solidly in the "love it" crowd. It ran on my 486dx33 w/4MB RAM and I was able to do up to four things at once, but typically would limit myself to 2 to save RAM.

      I tried DesqView/X when it came out, but it wanted like 8MB RAM and didn't run very well, and I didn't have X Windows deployed elsewhere for it to make any real difference. I still have a DesqView/X book around somewhere.

      --
      ... And so it comes to this.
    19. Re:DESQview by bill_mcgonigle · · Score: 2, Informative

      Then, someone at work (I was a co-op student at the time) suggested OS/2. After buying a student copy of that, too, I installed it. I could run two nodes of the BBS at 33.6kbps PLUS compile under Windows, or I could run one node AND use the other modem to connect to the internet via the university, and load up a web browser and do all of that stuff while the DOS BBS continued to run just fine.

      My OS/2 moment was formatting a floppy in one DOS box while playing Wing Commander in another. Windows would effectively halt on floppy disk access at that point.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    20. Re:DESQview by Safety+Cap · · Score: 1

      DESQview was a "must-have" for anyone running a multi-line DOS-based BBS. Windows/286 /386 were horrible at multi-tasking, whereas DV did it quite well.

      QEMM386 (which came with DV), was a slam-dunk for getting much more usable RAM under DOS. MemMaker was a weak attempt, and it wasn't until Win95 that people stopped caring (even though Win95–ME were nothing more than a windows environment running on top of DOS).

      --
      Yeah, right.
    21. Re:DESQview by carton · · Score: 1

      DESQview was more like VMware than it was like present-day Windows NT/XP/... It had some hypervisor memory management syscalls that were standardized, and could be called by programs running within it. The standard was called LIM EMS or something, lotus/intel/microsoft expanded memory specification, and it was implemented by QEMM386.SYS using the 80386 vm instructions, but it was also implemented by hardware ISA memory expansion cards with MMU's on them---I don't think many people bought these, but you could use >1MB on 286, and it was compatible with the DESQview API. This API was later absorbed by microsoft (DRIVER=EMM386.EXE). People forget how important this API was: for many years it was common to have a computer with 2 - 16MB of RAM, but no reasonable way to get programs to actually use that RAM. One way was to use programs like DESQview to run several API-less programs at once, sort of like how we can now virtualize many 4GB 32-bit guests on a 128GB 64-bit host. aanother way to get at the extra ram was through these ad-hoc-MMU bank-swapping PAE-like API's. The most common way was to burn it on useless things like TSR disk caches and pop-up PIM's.

      The forgotten part of the story here is how much *intel* sucked. The intel suckage and the microsoft suckage were complimentary, and fed off and enhanced and prolonged each other. The whole platform was like a hardware-only game console, with no API toolkit available after signing onerous NDA's and royalties, just bare hardware.

    22. Re:DESQview by dannys42 · · Score: 1

      Around the time of DesqView, there was also this great little known program called (I think) Concurrent PC. Does anyone remember that?

      It was the first real "virtual machine" I'd seen for the DOS environment. It only supported 2 VMs, but it was really awesome. It could run lots of stuff in parallel that DesqView couldn't.

      Maybe we need another article on DOS multitaskers. =)

    23. Re:Desqview by smbell · · Score: 1

      I would really struggle to find an example of something MS hasn't been late to the game at. They have a long proven track record of getting into the game after the market looks promising, and then crushing anybody else in the market by whatever means is available to them. Not just competing with a product, but actively working to kill off their competition.

    24. Re:DESQview by dunkelfalke · · Score: 1

      Mine was playing Dark Forces on a PC with only 4 megabytes of RAM. Yes, it was slow, but it worked.
      OS/2 really was great.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    25. Re:DESQview by Eristone · · Score: 2, Interesting

      For those of us who were on the support side of things - we missed DV and DV/X too. Lots of good memories - and it's lead to me being able to explain all the VMWare stuff to coworkers and friends in a fashion that clicks a lot easier. In addition, the same problems that would cause DESQview issues are invariably the same type of stuff that showed up in VMs. The more it changes, the more it stays the same...

        (formerly bryant@qdeck.com)

    26. Re:Desqview by cbhacking · · Score: 2, Informative

      NT came out in 1993 and was true 32-bit with full pre-emptive multitasking. It wasn't the first OS with those features, but it handily beat Win95.

      --
      There's no place I could be, since I've found Serenity...
    27. Re:Desqview by TheDarkener · · Score: 1

      NT came out in 1993 and was true 32-bit with full pre-emptive multitasking

      K, how about the first MS operating system with multitasking that could run Renegade BBS ;) Man I'm getting hammered by this one =p

      --
      It is pitch black. You are likely to be eaten by a grue.
    28. Re:Desqview by Nefarious+Wheel · · Score: 1

      From 1981 to about 1990 I ran a series of Vax/VMS nodes. They all had true multitasking, in fact were rather good at it. Not just from the operating system; around mid-80's their symmetric multiprocessor systems (e.g. 6340's etc.) were rather popular. And I think IBM had a clunkier version earlier than that, and of course the CDC 6000 series back in their Cray heyday all ran multiple processors with pipelined instruction queues. Intel was fairly late to the party.

      --
      Do not mock my vision of impractical footwear
    29. Re:Desqview by Anonymous Coward · · Score: 0

      No, pre-emptive multitasking was around in full force in the 80's. AmigaOS, Unix, and others all were doing it. AmigaOS since around 85, Unix since the 70's.

      It's amazing how history is rewritten...

    30. Re:Desqview by martin-boundary · · Score: 1

      MS was actually late to the game when it came to multi-tasking.

      Unlikely. Technically, MS actually sold Xenix, which was some kind of Unix clone. I've never used it, so I don't know if it was truly multi-tasking or not, but I would think so.

    31. Re:Desqview by KingMotley · · Score: 1

      Actually the ability to task switch was detected in many places, one of which was the "idle" message. There were many other places that also triggered it, file IO being one, checking for keyboard activity, etc etc. However, if windows was in the middle of a DOS call, in many cases it was unsafe to switch to another task (DOS was not fully re-entrant) so often the task switch would/could be delayed, and if the system crashed while DOS was in the middle of one of it's calls, it brought down the entire system.

      In later versions 3.11/3.12 (maybe 3.1 as well), the timer interrupt was also used as a possible trigger to task switch, and since many dos functions had been moved to a true 32-bit protected mode code, there chance that DOS was in the middle of one of these important functions that could not/should be pre-empted dropped significantly.

      This being the reason that Microsoft Windows refused to run on non MS-DOS regardless of what other people say. DOS wasn't really designed to be fully re-entrant, and it was tricky enough to get it to work on the version they controlled, and DR-DOS/FreeDos had a different set of rules of when it was safe to be interrupted and when it wasn't. It wasn't totally about 3rd party lockout.

    32. Re:Desqview by Anonymous Coward · · Score: 0

      Of course, back then nothing was truly multitasking,

      Except the fairly commonplace, 64-bit massively multitasking VMS VAXclusters I was using at the time, of course.

      POSIX compliant, cheaper than mainframes, capable of running seven networking protocols on the same wire, able to support 400 end users on a single CPU... if you'd told me back then that unix was the hope for the future, I'd have slit my throat. VMS was the bomb compared to anything else at the time (as long as you spoke English as a milk tongue, that is - DCL was very heavily influenced by the English language).

      But unfortunately DEC's marketing and sales group staged a palace coup, deposed Olsen, and ran DEC straight out of business. Thank all the odd gods of the galaxy for Linus Torvalds and Theo deRaadt... and for Microsoft, for making an OS so lame that even unix, that ancient dog, could compete with it.

    33. Re:DESQview by Xtifr · · Score: 1

      Windows/286 /386 were horrible at multi-tasking, whereas DV did it quite well.

      That's why I continued to use it as a software developer--when my apps blew up, they would often take down the VM, but my desktop, editor, and build environment would all remain running, which was much less likely to be true when I ran them under Windows. I think the only time I ever managed to trash DV completely was when I was trying to run a program that had its own built-in protected-mode multitasking, and even that one normally worked just fine.

      This was just before I switched to Unix (the transition aided by DV/X); I've never actually used Windows or Mac for much of anything. :)

    34. Re:Desqview by sourcerror · · Score: 1

      And with OS/2 you didn't had to reboot to switch between memory modes.

    35. Re:Desqview by adonoman · · Score: 1

      Windows 3.1 used to use time slicing

      Ummm... No. Windows 3.1 and older Macs (up to OS 8.0) used pretty much comparable cooperative multitasking models. Time-slicing generally can't happen under these models. It's the more modern preemptive schedulers that use time slices. They avoid the issues of giving time to idle threads by keeping track of the running status of processes, and only giving time to threads that are ready to do work, and ignoring those that are idle/waiting on the kernel/of lower priority.

    36. Re:Desqview by Anonymous Coward · · Score: 0

      I'm sure someone will correct me if my memory is wrong.

      It is. Windows 3.1 was not an operating system.

    37. Re:Desqview by gstoddart · · Score: 1

      Unlikely. Technically, MS actually sold Xenix, which was some kind of Unix clone.

      Microsoft may have re-sold Xenix ... but, as so often happens with Microsoft and technology, they bought it, they didn't build it.

      Like I said, UNIX had proper multi-tasking ... Microsoft licensed a variant of UNIX from AT&T, and the porting was done by SCO (the real one that used to do technology, not the one that just sues people now).

      Please, don't go around either believing or spreading the notion that Microsoft developed Xenix. They didn't. Not by a freakin' long shot. Someone else wrote it.

      I stand by my assertion, Microsoft was way behind the curve in real multi-tasking. Arguably, it wasn't until at least Windows '98 where Windows had any meaningful multi-tasking -- almost 20 years after they licensed the technology from someone else.

      --
      Lost at C:>. Found at C.
    38. Re:Desqview by Anonymous Coward · · Score: 0

      Of course, back then nothing was truly multitasking, but this was pretty darn stable for its time.

      Well, except for UNIX and a couple of others. There was real multi-tasking in 1985, don't let anybody tell you that Windows '95 was first with it.

      MS was actually late to the game when it came to multi-tasking.

      Not as late as Apple though! They only got pre-emptive multi-tasking in 2001.

    39. Re:DESQview by Pikoro · · Score: 1

      THIS. I ran a 4 node bbs back in the 386 days and it would have been impossible to do that under DOS without having multiple computers.

      Each session got it's own COM port and I still had enough resources left over to play X-Wing while the BBS was running.

      --
      "Freedom in the USA is not the ability to do what you want. It is the ability to stop others from doing what THEY want"
    40. Re:Desqview by Anonymous Coward · · Score: 0

      > back then nothing was truly multitasking

      Do you think that's air your're breathing now?

      Ok, I could leave it at this but my techie won over my artist and I'll step down from the coolness monolith I raised myself to with that snarky quote to reply that I felt just the same as you the first few times I used WinCrap 95 (let's also use the expressions of the time, shall we?). The OS was taking away all the fun I'd had in university with Unix, or before at home with an Amstrad CPC or my mind-boggling ST: Windows spewed thousands of ridiculous files everywhere you looked, no documentation, incredibly patronizing PR bullshit, was butt ugly, needed lots of megabytes just to display a couple of windows... mediocre no matter how you look at it. It sucked the fun out of computing for me and today I'm a professional only because Linux came along somewhere in between windows 3.11 and NT and restored the fun. These days I'm moving to even better FOSS alternatives.

    41. Re:Desqview by master_p · · Score: 1

      Not only UNIXes, but the Amiga as well had preemptive multitasking.

    42. Re:Desqview by drsmithy · · Score: 2, Insightful

      I stand by my assertion, Microsoft was way behind the curve in real multi-tasking. Arguably, it wasn't until at least Windows '98 where Windows had any meaningful multi-tasking -- almost 20 years after they licensed the technology from someone else.

      Windows 98 had the same pre-emptive (for 32-bit processes) multitasking capabilities as Windows 95, NT had fully pre-emptive multitasking two years before that.

      DOS, Windows 3.x and OS/2 1.x did not, due to a combination of hardware constraints and legacy support.

  14. DESQview by elbobo · · Score: 4, Informative

    DESQview was brilliant. It was completely workable on the hardware of the time, functional, did what the box said, fast... It was the right solution for the time. It just happened that hardware moved on and left the phase in time that DESQview occupied behind.

    I was running multinode BBSes under DESQview back in the day and getting fantastic performance. None of the graphical competitors were in any way workable alternatives for that sort of performance on the hardware available.

  15. Amiga had a real shot, but dropped the ball by Anonymous Coward · · Score: 0

    http://technologizer.com/2010/07/23/amiga/

    It was ahead of pretty much everything at its début. But they managed to cock it up something fierce - it was amazing to see a decade of PC technology leadership go "poof" with bad management at the helm.

  16. GEM by blind+biker · · Score: 3, Interesting

    GEM was a damn good piece of software. It was actually multiplatform (CP/M on 8088 and 68000, DOS (any CPU), and I think I saw floppies of GEM for the Commodore 64.

    Incredibly powerful considering the tiny resources it needed. One of the first DTP softwares, Ventura, was based on GEM for its user interface.

    Like X, GEM isn't quite an operating system. It's a graphical shell. Well... more or less what Windows 1.0 was!

    --
    "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    1. Re:GEM by Anonymous Coward · · Score: 0

      GEM was clearly better than Windows 1.0. I used it on a TI Professional, which was the best PC in 1983. They didn't waste the 128k of lower memory on a limited version of basic, and gave it to the main memory. I had GEM for the TI, and could run Ventura Publisher on the full version of GEM, rather than the limited version that was needed to run Ventura on the IBM PC, because I had 768k of lower memory rather that the IBM's 640k.

      The thing that I haven't seen mention is the fact that Windows didn't get to its position of power by playing fair. (They were found guilty in their trial vs the DOJ, and they settled in Comes vs. Microsoft in Iowa because they didn't want all their dirt aired.)

    2. Re:GEM by spitzak · · Score: 1

      GEM however did have some really stupid design decisions. In particular the method they chose to allow "double click" to be an event was to delay reporting of *all* clicks to the program until the double-click time had passed. Thus all clicks had a built-in delay before the program could respond.

      Any programmer with an IQ over 80 would have instead had it report the single click immediatly, then report a second double click event later when it was detected. Windows and mac and X and every other system I have heard of did this, so it is pretty obvious.

      I think GEM also had some hard-coded limits of 4 apps and 8 windows in the api.

  17. Windows did fail... Totally. by LWATCDR · · Score: 5, Insightful

    Windows 1.0 was a total failure. Nobody used it. I worked at a computer store at the time and people would ask us to take it off the drives of the compter because they had no use for it.
    Windows 2.0 was also a total failure.
    Only when Windows 386 and WIndows 3.0 came out was Windows usable. Even then most people didn't use it. It just slowed down their dos programs.
    Only when Windows 3.11 came out did WIndows become popular. Mostly to run DOS apps. Windows won because Microsoft just gave it away for the longest time. Almost nobody would have paid for it. That is why all the others failed. Most people wouldn't pay for a program to run programs!
    Microsoft used the drug dealer method to win market share. But to call any version of Windows before 3.0 as not a failure is just not valid.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:Windows did fail... Totally. by sconeu · · Score: 2, Informative

      Windows 1.0 was a total failure. Nobody used it. I worked at a computer store at the time and people would ask us to take it off the drives of the compter because they had no use for it.

      I call bullshit. Microsoft didn't get into the pre-installed Windows until 3.0. Hell, in 1985, PCs didn't even come with DOS pre-installed -- you had to FDISK, FORMAT/S, and copy the DOS floppy onto the hard drive yourself.

      Some machines came bundled with Windows 1.0x (I owned one), but they came with a box of 6 360K floppies that, once again, you had to install by yourself.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    2. Re:Windows did fail... Totally. by Reziac · · Score: 1

      Win 3.1x cost all of $70 at MSRP, $35 in the Real World, or $5/lic. in bulk. That was definitely a pricing sweet spot, sufficient to suck in everyone.

      Apparently the pricing of today's Windows is proportional to the number of lines of code, rather than being tied to the inflation index. ;)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    3. Re:Windows did fail... Totally. by fermion · · Score: 1
      Absolutely. The purpose of Windows 1.0 was to keep people from ditching MS DOS. Most still ran MS DOS. By supplying MS Windows, and showing how bad it was, which was mostly due to the screwed up architecture of the machine, people could be convinced to stay with MS DOS. Most people did not know of these other products. Most people had no overwhelming need to go WIMP. Such a move was costly in term of training, and the current solutions worked.

      It was fortunate that Window 3.11 came along, as at that time a failed MS Windows product might have cost MS market share. People were seeing how the WIMP interface could produce value. Of course innovative small bussiness saw this pretty early on, but the vertical market applications were not there.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    4. Re:Windows did fail... Totally. by pastyM · · Score: 1

      Most people wouldn't pay for a program to run programs! Microsoft used the drug dealer method to win market share.

      And this is why I run Linux.

    5. Re:Windows did fail... Totally. by Markvs · · Score: 2, Insightful

      Windows 1.0 was a total failure. Nobody used it. I worked at a computer store at the time and people would ask us to take it off the drives of the compter because they had no use for it. Windows 2.0 was also a total failure. Only when Windows 386 and WIndows 3.0 came out was Windows usable. Even then most people didn't use it. It just slowed down their dos programs. Only when Windows 3.11 came out did WIndows become popular. Mostly to run DOS apps. Windows won because Microsoft just gave it away for the longest time. Almost nobody would have paid for it. That is why all the others failed. Most people wouldn't pay for a program to run programs! Microsoft used the drug dealer method to win market share. But to call any version of Windows before 3.0 as not a failure is just not valid.

      I call shenanigans!
      * Windows 1.0 was MS-DOS EXEC. It didn't have an installation. Also, what drives are you referring to? As I recall hard drives were pretty scarce in 1985 (heck, even into 1988 when IDE really got going), as most XTs (and early ATs) were dual floppy systems!
      * Yet Windows 2.0 manged to be successful enough that Apple sued Microsoft (in a 189 point lawsuit) over the same look & feel they "borrowed" from Xerox.
      * Also, Windows/386 was a version of Windows 2.1. So much for it being a failure.
      * Exactly how did running Windows 3.0 slow down DOS programs when you had to shell into Windows from DOS? Unless you put Win (or Win: to avoid the spashscreen) into your autoexec.bat, it was a manual process to load Windows!
      * For that matter, why run DOS programs on Windows 3.11? You still had to shell to it from DOS, though by this time some companies had begun changing the autoexec.bat on their machines (Blackship, Fast Data and Dell come to mind).
      BUT! By the time it was released (31 December 1993), Microsoft Office for Windows was already on version 3, and 4 was out a few months later. Nevermind the competing products like Lotus Smartsuite 1994, cc:Mail/Microsoft Mail or even AutoCAD . Or a little thing called Mosaic, which of course led to Internet Explorer... which also ran on Windows 3.11... as did Netscape. Have you ever heard of Novell Netware or Windows NT 3.51? WfW was the corporate client du jour for *years* (they bought it, mostly) and it's success paved the way for Windows 95.

      As opposed to what... using bright, shiny polychromatic plastic cases?

      --
      46. The Hobo smiles, his eyes glaze over, and he burps. "Beware the man who has lived longer than the Wasteland."
    6. Re:Windows did fail... Totally. by LWATCDR · · Score: 2, Informative

      Kaypro and Zeniths did.
      Kaypro didn't come with Windows but it come with a lot of preinstalled software.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    7. Re:Windows did fail... Totally. by LWATCDR · · Score: 2, Informative

      Actually we sold a lot of machines in 85/86 with Hardrives Kaypro 16s, Z-151's Z-158s. We also did a lot of business adding hard drives. 30 mb RLL was very popular.
      Windows 386 was 2.1 but it was sold as Windows 386 and only ran on 386. Again very few people bought it.

      Why run DOS apps under Windows 3.11? Really simple. So you could run more than one at a time. That was Windows 386 and Windows 3.0's big feature.
      You could actually run a something like ACT! and your application at the same time!
      Formatting a floppy would still bring a system to it's knees but that is why they sold preformated floppies!

      Netscape? You better get a copy of Trumpet Winsock first!
      Yes the browser plus 3.11 and Microsoft Office really helped.
      Truth is that only one part of Office really carried the day. That was Excel. Word was also a major also ran until Excel came out. And yes I had a copy of Word 1.0 back in the day. They also came bundled with the Zeniths. Nobody wanted it. They all wanted Wordstar, PFS:Write, QnA, and later WordPerfect.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:Windows did fail... Totally. by Markvs · · Score: 1

      Actually we sold a lot of machines in 85/86 with Hardrives Kaypro 16s, Z-151's Z-158s. We also did a lot of business adding hard drives. 30 mb RLL was very popular. Windows 386 was 2.1 but it was sold as Windows 386 and only ran on 386. Again very few people bought it.

      Why run DOS apps under Windows 3.11? Really simple. So you could run more than one at a time. That was Windows 386 and Windows 3.0's big feature. You could actually run a something like ACT! and your application at the same time! Formatting a floppy would still bring a system to it's knees but that is why they sold preformated floppies!

      Netscape? You better get a copy of Trumpet Winsock first! Yes the browser plus 3.11 and Microsoft Office really helped. Truth is that only one part of Office really carried the day. That was Excel. Word was also a major also ran until Excel came out. And yes I had a copy of Word 1.0 back in the day. They also came bundled with the Zeniths. Nobody wanted it. They all wanted Wordstar, PFS:Write, QnA, and later WordPerfect.

      Oh, I'm not saying that there were NO HDs back in 85/86/87, but I think you'd agree that the number of machines that were floppy only probably outnumbered HD systems by a pretty wide margin -- maybe three to one (or more).
      Ah! That's clearer now. Okay, I agree re: Windows 386 then.
      Yes, of course you could, but my point was more that you could be running Windows apps. (Or you just formatted the discs in DOS of course...)
      I agree Excel helped to carry the day but a big piece of that was because it was so interoperable with Word. There were a LOT of holdouts from 1-2-3. When Word finally vanquished WordPerfect 5.1/6.1 that was as big a deal IMO.

      --
      46. The Hobo smiles, his eyes glaze over, and he burps. "Beware the man who has lived longer than the Wasteland."
    9. Re:Windows did fail... Totally. by ThreeGigs · · Score: 2, Insightful

      Windows won because Microsoft just gave it away for the longest time.

      I'll disagree with you there. MS kinda had to give away Windows 3.0, but one change from 3.0 to 3.1 made all the difference in the world: TrueType fonts with WYSIWYG printer output. That was truly the birth of the desktop publishing revolution. The new simplicity of being able to create good looking documents, handouts and brochures *without* having to know any arcane printer commands meant you no longer needed the WordPerfect Guru secretary who knew all the ins and outs of the printer command codes.

    10. Re:Windows did fail... Totally. by LWATCDR · · Score: 1

      Actually once the 30MB RLLs came out I would say it was about two HD systems for each none. And we sold very few 286 machines. The 8088s where dropping in price we sold a ton of them.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    11. Re:Windows did fail... Totally. by LWATCDR · · Score: 1

      Wow you drank the deep of the Microsoft kool-aid.
      The birth of desktop publishing was on the Mac years before Windows 3.1 You had real desktop publishing on the Mac, Amiga, Atari ST, and even the PC with Ventrua publish running on GEM long before Windows 3.1. Hell you even had GeoPublisher for the Commodore 64! Considering the limitations of the platform it did some amazing work. I will not even go into Next with it's use of Display Postscript.

      "The new simplicity of being able to create good looking documents, handouts and brochures *without* having to know any arcane printer commands meant you no longer needed the WordPerfect Guru secretary who knew all the ins and outs of the printer command codes."

      Wow you do know that at that time Only PC users where forced to deal with that crap. Really everybody else on the planet had already moved past that point.
      What a great example of how the PC held back a huge section of the population until Microsoft got around to catching up to Apple, Commodore, and Atari.
      What a victory of marketing over reality.

      Windows 3.1 was when the PC was no longer a festering dung heap of a platform for desktop publishing not the birth of the desktop publishing revolution.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    12. Re:Windows did fail... Totally. by drsmithy · · Score: 2, Insightful

      Only when Windows 386 and WIndows 3.0 came out was Windows usable. Even then most people didn't use it. It just slowed down their dos programs.
      Only when Windows 3.11 came out did WIndows become popular. Mostly to run DOS apps. Windows won because Microsoft just gave it away for the longest time. Almost nobody would have paid for it. That is why all the others failed. Most people wouldn't pay for a program to run programs!

      Actually, Windows 3.0 was the (surprising to everyone, including Microsoft) turning point, and largely the reason that today we have Windows NT and not OS/2 NT.

      Also, people were more than happy to pay for a "program to run programs" when it gave them things like multitasking, WYSIWYG and consistent printer support (then later, TT fonts and networking).

    13. Re:Windows did fail... Totally. by drsmithy · · Score: 1

      For that matter, why run DOS programs on Windows 3.11?

      So you could multitask multiple DOS sessions at the same time, along with your Windows applications, and not have to keep restarting everything.

    14. Re:Windows did fail... Totally. by LWATCDR · · Score: 1

      Actually people started to use Windows in big numbers only when new computers started to bundle it. A few users bought it but most got it bundled. But it was a while before A lot of major apps moved to Windows.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  18. Microsoft's business model ... by PPH · · Score: 2, Insightful

    ... is to own everything from the application down to (and in some cases including) the hardware. It was inevitable that add-ons to DOS were not going to be allowed to survive. The only viable UIs have been those on top of other (non Microsoft controlled) O/Ss. And they have been viable only because Microsoft hasn't been able to kill them off. Yet.

    Captcha: penguin

    --
    Have gnu, will travel.
  19. Revisionist history by Stumbles · · Score: 3, Informative

    What a load of shit. It is pretty hard to compete when PC vendors were tied by jackbooted licensing deals with Microsoft and they sabotage their own software so competing software won't or runs "poorly" compared to their own. What's that? Oh yeah, Microsoft was sued just for that; sabotaging their own software.

    --
    My karma is not a Chameleon.
    1. Re:Revisionist history by brian0918 · · Score: 1

      At most, Microsoft only has a responsibility to their vendors to make clear any sort of handicapping that they've implemented in their OS. So long as the vendor is aware of that, and still voluntarily chooses to enter into a licensing agreement with Microsoft, there is no fraud occurring.

      Yes, that does mean I am saying that the sort of anti-trust laws that are used against software companies with claimed "monopolies" are unjust and should not exist. So long as no force is involved, and no purposeful deception is used (fraud), then the government should stay out of it.

    2. Re:Revisionist history by St.Creed · · Score: 2, Informative

      Yes, however, that wasn't the case here. Microsoft was sued and convicted for including code in Windows to crash the kernel when they detected competing software. And they sure didn't tell anyone.

      --
      Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
    3. Re:Revisionist history by bhtooefr · · Score: 1

      AARD? That was only in the BETA.

  20. Wayfarer by Gallenod · · Score: 2, Interesting

    My favorite Windows alternative back in the early 1990's was Wayfarer, a freeware replacement for the Windows v3.x Program Manager. Long before Microsoft figured out how to do tabbed and nested windowing, Wayfarer did both.

    My favorite trick as to post a screenshot of the Windows Program Manager as the screen background and then turn off Progam Manager completely and replace it with Wayfarer, which would minimize to a single desktop icon. People would click on what looked like Program Manager icons with no result.

    (Including the tech support guy who showed up unannounced at my desk one day to install software while I was out and was five minutes away from wiping and reinstalling my entire PC because he couldn't figure out why it wasn't working. I told him the next time he wanted to hijack my PC during the work day he needed to schedule an appointment so he didn't interfere with my work day.)

    Ah, those were the days when we could still have some fun with customization. Now it's all "safe choices" or lock-downs, depending on how you look at it.

    --

    TLR

    A man no more knows his destiny than a tea leaf knows the history of the East India Company
    1. Re:Wayfarer by MonTemplar · · Score: 1

      Don't recall that one, but I used Norton Desktop for Windows back in the Windows 3.x days. Multiple desktops, nested groups of programs, program icons directly on the desktop as well as icons for printers, it was a really neat system shell. Sadly, it was already dead by the time Windows 95 arrived.

      -MT.

      --
      -MT.
  21. The real question is: why just one big incumbant ? by Alain+Williams · · Score: 2, Insightful

    There are plenty of motor car manufacturers, and most people don't just drive a Ford (or whatever). So why is the computing market so different ? I don't believe that it is down to manufacturing capacity, ie s/ware is so much easier to make many of once you have the first copy; if that was so then the many smaller manufacturers, the list is huge.

    I think that the key is standards, everyone wants the same - especially file formats. The way that MS got to where it is was by taking everyone else's standards and keeping its own as secret as it could. Whatever reasons: it is something that we should learn from and stop from happening again.

    Disclaimer: my desktop has always been Unix based since 1986, Linux for the last 15 years.

  22. Deskmate by coolmoose25 · · Score: 3, Interesting

    I had a Tandy 1000 (still do actually) and ran Deskmate during the Windows 1.0 days... It is hard for people to understand just how messy things were in those days... printer drivers were essentially non-existent and you had to embed printer commands in documents if you were doing anything fancy (meaning different fonts or sizes). There were a plethora of TSR programs (Terminate-Stay Resident) like Sidekick. There were all kinds of hacks to make your machine use memory above 640k. Deskmate was basically something more similar to the Office suite than a real Windows replacement. There were all kinds of menuing programs at the time, many of them shareware, that would essentially allow you to build a simple application launch screen. Deskmate did a pretty fair job of documents and rudimentary spreadsheets... It was the MS Works of its day. Other applications like Lotus 123 and dBase (or Clipper) were the norm - and you ran one of them at a time. (No multitasking) So Windows 1.0 was basically a fancy menu program and as TFA points out, it had many competitors... It wasn't until Windows 2.1 came out that it advanced any farther than that...

    --
    Brawndo: It's what plants crave!
    1. Re:Deskmate by St.Creed · · Score: 1

      I remember using Wordperfect 5.1 and Lotus 1-2-3. Very good spreadsheet and small database program. I used a combination of Wordperfect and Pagemaker on Windows 3.11 for ages to create publications: Wordperfect was very good at editing, and Pagemaker was very good at lay-out. The combination still works better than MS Office 2007, when it comes to dealing with layout. Every time I get frustrated with the way in which MS Word just has its own mind about where to put images in text, I yearn for the days when I could tell my software where to set the picture and it actually went and stayed there.

      --
      Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
    2. Re:Deskmate by uncle+slacky · · Score: 2, Informative

      Sounds like you need a proper DTP package in that case: http://www.scribus.net/

      --
      Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it.
    3. Re:Deskmate by St.Creed · · Score: 1

      That actually looks very good - I'll give it a try. Thanks!

      --
      Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
    4. Re:Deskmate by Anonymous Coward · · Score: 3, Insightful

      " TSR...hacks to make your machine use memory above 640k..."
      " It is hard for people to understand just how messy things were in those days..."

      No, things were NOT that messy in those days. They were that messy in the DOS/Windows world.

      Other systems of the time had device drivers that abstracted printing details from apps. They had no 640K barriers. They had preemptive multitasking. They had device independent APIs, and abstracted container file formats.

      Don't confuse the mess that was DOS and early Windows with the state of the industry as a whole. It was not that bad, it's just that for whatever reason, everyone chose to support the system that was an architectural clusterfuck.

  23. Anonymous Coward by Anonymous Coward · · Score: 1, Informative

    DESQview rocked back in the day!

    Ran several PCBoard BBS nodes off of one machine with DESQview.
    Would not even think of doing that with the old versions of Windows.

  24. OK. I'll speak the truth and take the hit. by Zero__Kelvin · · Score: 5, Insightful

    These are not examples of technologies that Windows beat. They are example of companies, many of whom had superior products, that never made it due to Gates' underhanded business practices.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  25. Did anyone else try out the version of GEOS for the Commodore 64?

    1. Re:GEOS by StuartHankins · · Score: 1

      Yes, I remember it was a big deal to me and I loved it. I used it for (admittedly simple) desktop publishing tasks. Memories of it are a bit vague since I was still a child, but I seem to recall having lots of fonts and how cool that was.

    2. Re:GEOS by TRS80NT · · Score: 1

      Me too. It's good to get the ransom letter phase out of the way early ;)

      --
      Lorem ipsum dolor sit amet.
    3. Re:GEOS by St.Creed · · Score: 2, Interesting

      Yes, i found it horrible. Ofcourse, I only had a joystick and games, so I wasn't really the target audience :) But in general it was excruciatingly slow, took ages to load and the interface was visually underwhelming - especially when compared to the BBC Archimedes computer you already had then.

      Ofcourse, the Amiga arrived not long after :)

      Brilliant computer, it wasn't until I bought a 80486DX@50 Mhz that the speed of the CPU + graphics in Windows began to match the 7.8 Mhz 86000 CPU + coprocessors from the Amiga...

      --
      Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
    4. Re:GEOS by tekrat · · Score: 2, Interesting

      GEOS was a brilliant hack and probably one of the tightest pieces of code ever created. The fact that it provided a true GUI on a "toy" computer was jaw-dropping. The fact that it could do that AND even run applications (Word processing, spreadsheets, Desktop Publishing) gave it Macintosh-like functionality at 1/10th the price -- well, that was simply beyond astounding.

      What a lot of people don't know is that the folks that created GEOS, Berkely Softworks, went on to recreate GEOS for the APPLE II, and then later for the PC. Retitled "Geoworks Ensemble", it gave the GUI and related apps to "low end" PC that had been abandoned by Microsoft in their bid to make Windows rule the world.

      MS started to make Windows "real" by Version 3 -- but, in order to run it, you needed a 386 or better. GEOWORKS could operate on much lower-end equipment (I believe all you needed was a hard-drive, so even the 8088 CPU was possible). So, you could have the equivalent of Windows without having to buy new hardware.

      And remember that a lot of people have already invested $2000 in a 286 and didn't want to give it up right away -- so GEOS got more traction than you'd think. There was also a large contingent of people with early laptops that found GEOS to be just the ticket for a black-and-white only screen and a 20mb HD with maybe 1 MB of RAM (much too small for Windows).

      While aiming for the low-end gets you initial sales, aiming for the high-end turned out to be MS's path to the future, and it's been that way ever since. What MS guessed right was that the hardware would catch up with the software, and get cheap enough that you could afford to upgrade every few years.

      --
      If telephones are outlawed, then only outlaws will have telephones.
    5. Re:GEOS by bhtooefr · · Score: 1

      Amiga came in 1985, GEOS came in 1986, Archimedes came in 1987.

      (The BBC Micro came in 1981, but did it ever have a GUI environment of any kind? It was certainly within the realm of possibility, but...)

  26. XTree? by bughunter · · Score: 2, Interesting

    Given the particulars of the DOS environment, and the capabilities of the displays at the time, I found XTREE much superior to anything prior to Win95.

    (Excluding the Macintosh and Amiga GUIs, of course.)

    --
    I can see the fnords!
    1. Re:XTree? by zmollusc · · Score: 1

      Yoink! Xtree gold flashback!
      Yeah, xtree was a must for dos.

      --
      They whose government reduces their essential liberties for temporary security, receive neither liberty nor security.
    2. Re:XTree? by Anonymous Coward · · Score: 0

      yah, xtree made the early xt/at machines useable. without it, i couldn't have founded an empire.

      uh, wait..

      seriously, xtree was pretty cool. but when i got to use an A1000 for a few weeks in 1985, I knew the game was up..

      Unfortunately (and several hundred dollars of CBM stock later), I realized that not everyone playing was playing the same game (and some people at CBM weren't playing with full decks..)

      Win/Lin/Ami/Morph

      Workstations are Win.
      Our Servers are Lin.
      Ami and Morph just showed up with some gin!

      gurgl

  27. DESQview on a 386 was incredible for its time! by Anonymous Coward · · Score: 1, Informative

    IMO, for a year or two DESQview was a real marvel compared to anything else out there, it even had early cut and paste of ASCII text between applications. I once visited their small office not too far from the Santa Monica pier. (I think it was on Pico)

    - TWR

  28. CP/M by formfeed · · Score: 2, Informative

    CP/M? Features almost like *nix but could run on a 32kB computer
    Ah, now you remember!
    No? Anybody?

    1. Re:CP/M by Spectre · · Score: 1

      Eh, I remember CP/M.

      I was doing application development at the time, for the state of Kansas.

      We used Kermit and a null-serial cable to transfer the source code from the IBM PC-DOS computers over to the Zenith CP/M machines, so we could compile and build "install" diskettes for each environment.

      Yes, I'm that old (barely).

      --
      "Flame away, I wear asbestos underwear"
    2. Re:CP/M by Anonymous Coward · · Score: 0

      CP/M? Features almost like *nix but could run on a 32kB computer

      Ah, now you remember!

      No? Anybody?

      "Almost" is a stretch, how many layers of directories was supported? Two-three?. And no pipes.

      In school (1986?), we had to start up CP/M inside a virtual machine in our ABC 806 to be able to use Turbo Pascal (a.k.a. PolyPascal). Natively, ABC 806 had support for BASIC (not the MS flavour) and assembler programming, both which was frowned up on by our Datalogy teachers. Then when Turbo Pascal became good enough on the DOS/IBM PC platform, my school switched over to PC. MS DOS at that time had actually less features then C/PM, but at least they had added pipes just when my school started to use DOS. Still, DR DOS (an upgraded version of C/PM that was compatible with MS/IBM DOS), was a hell of a lot better. DR DOS is one of those products that would have won by merit if Microsoft ever had played fair.

    3. Re:CP/M by Just+Some+Guy · · Score: 1

      I took a sick day last week and spend part of the morning installing VICE's Commodore 128 emulator and playing around with the CP/M boot disks I found on the Internet. It was fun, but I was reminded why I never actually used it.

      --
      Dewey, what part of this looks like authorities should be involved?
  29. The lessons of "just okay" by mpapet · · Score: 2, Insightful

    I think sometimes the geeks forget the Marketing adage that most enduring products are functionally "just okay." Typically a successful product uses lots of cash to drown their competitors. Might makes right.

    Someone somewhere said "Early to bed. Early to rise. Advertise Advertise Advertise"

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  30. I see dead people by Anonymous Coward · · Score: 0

    One of the things I like to think about is that out there, somewhere, is someone still using 1.0 as their daily computer.

    "The horror."

    1. Re:I see dead people by Teun · · Score: 3, Interesting
      Yep very likely, it's only a few years ago a Public Notary in Louisiana asked me to have a look at her 'puter and it was running Windows 1.0.

      Although I'm since 1979 in IT I had never before seen this stuff...

      But knowing DOS and Win3.11 I managed to get it working again :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    2. Re:I see dead people by sconeu · · Score: 1

      I still have my Windows 1.03 floppy disks lying around somewhere.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    3. Re:I see dead people by tqk · · Score: 0, Flamebait

      But knowing DOS and Win3.11 I managed to get it working again :)

      "A few years ago...", you upgraded them to 3.11?!?

      I hope they sue you.

      --
      "Tongue tied and twisted, just an Earth bound misfit ..." -- Pink Floyd.
  31. And Symphony didn't make this list? by rickb928 · · Score: 2, Interesting

    A spectacular opportunity, dommed to failure for all the same reasons as the others.

    Nice trip down memory lane... I used DeskMate at home for a while, got into configuring DesqView for clients, and talked clients out of most of the rest.

    I used DR-DOS for a long time to generate bootable floppies for stuff like patches and Norton Ghost, avoiding some of the unpleasentness of the various MSDOS problems. Ultimately, didn't DR-DOS go to Caldera? I have some of those disks still.

    But Windows was pretty much unstoppable. My old buddies from then still lament that Apple never wrote Mac OS for Intel processors, but that would have gotten Apple into DLL and driver hell, trying to support even the worst drivers from the worst writers, and then getting tarnished with the reputation of unreliablility.

    Still, Windows seems to have come out of that ok.

    Did anyone else get a MACH board for Christmas, and drool over that awful mouse?

    Anyone else ever play Balance Of Power? Damn, I miss that.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:And Symphony didn't make this list? by Anonymous Coward · · Score: 0

      My old buddies from then still lament that Apple never wrote Mac OS for Intel processors,

      In 1985 an Apple executive suggested porting the OS to the Intel platform. The idea was rejected. In 1991 Novell wanted to put a GUI on the Intel platform and not be sued by Apple. They teamed up in 1992 and engineers were given from February until Halloween to get the port done. They succeeded but Apple executives were horrified because they saw this as a threat to Apple hardware sales and the project went into abeyance as management concentrated on Pink, Taligent, and other notorious Apple failures.

      For further information Owen Linzmayer's Apple Confidential 2.0

  32. Desqview rocked by hoggoth · · Score: 1

    Man I loved Desqview. It had true preemptive multitasking and separate virtual desktops for processes years before Windows.

    --
    - For the complete works of Shakespeare: cat /dev/random (may take some time)
    1. Re:Desqview rocked by Radical+Moderate · · Score: 1

      I wasn't a user, but I used to do support for the annual users' conference they put on in Santa Monica. They were a fun company to work with, good people, I was sorry to see Windows steal their thunder.

      --
      Never let a lack of data get in the way of a good rant.
  33. According to MS, Win temporary, OS/2 + PM future by perpenso · · Score: 5, Informative

    "I believe Windows 1.0 predates OS/2 by a bit."

    You're right, but OS/2 is worth mentioning anyway. I tried it back in the day, and really liked it. It was a 32 bit os when Windows was still only 16 bit ...

    OS/2 2.0 was 32 bit but OS/2 1.0 was a 16-bit protected mode text based replacement for DOS. OS/2 1 eventually had a GUI called Presentation Manager, the API was very similar to MS Windows. I think OS/2 1 + PM is the actual first competitor to WIndows, not OS/2 2.

    In the early MS Windows 3 era MS told developers that Windows was just a temporary GUI for DOS to satisfy existing installations that will eventually be migrated to OS/2 1 + Presentation Manager. They emphasized how source compatible WIndows and Presentation Manager were and that porting would not be a major issue.

    IBM and MS were partners in OS/2. IBM was developing OS/2 2.0 while MS was developing OS/2 NT in parallel. While both were 32-bit and GUI based, OS/2 2 was the more expedient reworking of OS/2 1 and ran only on x86 CPUs. OS/2 NT was to be to the complete rewrite that would run on various CPUs. At some point MS decided to ditch IBM and renamed OS/2 NT to Windows NT. Its interesting to note that Windows NT offered OS/2 1 support.

  34. desqview had windows by hildi · · Score: 0

    i ran desqview on an old IBM PC, dos circa 2.1 or 3.3 i had wordstar open in two windows at once. the point was you could copy/paste between them. it was awesome. you could have several windows if you wanted. this was years before DOS 5 and it's "shell" thing. It was a close as you could get to task-switching on an 8088 with MS DOS.

  35. DESQview/X by lophophore · · Score: 2, Interesting

    DESQview/X was even cooler than DESQview, which was a remarkable piece of software.

    This could display MS-DOS character cell and Windows 3.0 apps onto an X-Terminal, could run X apps locally, could display X apps from Unix onto your pc.

    It was too late to market. Windows 3.11 came out soon after, with reasonable networking, and that was the end... Sadly, even the X window system is now a niche player...

    --
    there are 3 kinds of people:
    * those who can count
    * those who can't
  36. Re:The real question is: why just one big incumban by 0123456 · · Score: 1

    There are plenty of motor car manufacturers, and most people don't just drive a Ford (or whatever). So why is the computing market so different ?

    Windows programs run on Windows. Some of them run on Linux through Wine, but that's still a crapshoot.

    So if you have thousands of dollars of Windows software, you can't just switch to a different OS and continue to use it.

  37. OS/2 NT or was it OS/2 3.0? by perpenso · · Score: 1

    Now that I think about it I'm not sure whether MS's OS/2 development project was called OS/2 NT or OS/2 3.0.

    1. Re:OS/2 NT or was it OS/2 3.0? by 0123456 · · Score: 1

      Now that I think about it I'm not sure whether MS's OS/2 development project was called OS/2 NT or OS/2 3.0.

      It was certainly referred to in the media as OS/2 NT for some time before it vanished and Windows NT suddenly appeared out of nowhere.

  38. Re:OK. I'll speak the truth and take the hit. by ArhcAngel · · Score: 2, Informative

    This is an extremely insightful comment. I would add his ability to market vaporware. Remember...He didn't even have DOS when he sold it to IBM.

    --
    "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
  39. its hard to true-multitask on 8088 by hildi · · Score: 0

    since it is lacking a lot of the CPU code for task switching... i.e. there was no memory protection, any program could write to anywhere in memory. (which spawned a million keyboard-hook malwares) i really wonder how desqview accomplished what it did. did it rewrite the machine code of the programs it loaded into memory?

    1. Re:its hard to true-multitask on 8088 by Clueless+Moron · · Score: 1

      since it is lacking a lot of the CPU code for task switching... i.e. there was no memory protection, any program could write to anywhere in memory. (which spawned a million keyboard-hook malwares)

      Memory protection is completely separate from multitasking. For example, Microware OS-9 (from the 1980's, not to be confused with the much-later Mac OS9) ran on plain old 6809's and did true multitasking but without memory protection.

  40. Ahh DESQview... by steppin_razor_LA · · Score: 1

    It's been a long time, but my recollection is that Windows used to multi-task anything that wasn't actually a Windows application *terribly*. I ran DESQview for a long time with plenty of fond memories. In fact, I want to think that a later version of DESQview was my first X-Server on my PC....

    --
    Evolution: love it or leave it
    1. Re:Ahh DESQview... by NetServices · · Score: 1

      DESQview rocked. It was far more friendly, compatible and stable than DoubleDOS. Especially with serial communications drivers.

  41. Mondrian by russryan · · Score: 2, Interesting

    Mondrian was a TopView clone created by Dynamical Systems Research, a company formed by Nathan Myhrvold and Chuck Whitmer. Microsoft bought them because Mondrian was arguabley smaller and faster than the IBM product. The team of engineers went to work in the WIndows team and were a good part of the reason that Windows 3.0 emereged as the "good enough" GUI to dominate the industry efver since.

  42. DoubleDos by ShavedOrangutan · · Score: 2, Informative

    For running a BBS on an 8MHz PC/XT, DoubleDos was great.

    No windows or GUI, but you'd get two functioning DOS environments. Even better, you could run a CGA adapter and a Monochrome adapter at the same time. Each would be like its own functioning computer. It was extremely simple and lightweight.

    Desqview was cool, but with 640K ram, more than 2 programs at once was unrealistic so DoubleDos was still better.

    Windows was a pig. I tried it once and threw it out. A windowed GUI was pointless at 640x200 black and white.

    --
    Godaddy is a scam and a ripoff.
  43. Re:The real question is: why just one big incumban by Ephemeriis · · Score: 1

    There are plenty of motor car manufacturers, and most people don't just drive a Ford (or whatever). So why is the computing market so different ?
    I don't believe that it is down to manufacturing capacity, ie s/ware is so much easier to make many of once you have the first copy; if that was so then the
    many smaller manufacturers, the list is huge.

    I think that the key is standards, everyone wants the same - especially file formats. The way that MS got to where it is was by taking everyone else's standards and keeping its own as secret as it could.
    Whatever reasons: it is something that we should learn from and stop from happening again.

    Disclaimer: my desktop has always been Unix based since 1986, Linux for the last 15 years.

    The issue certainly is standards.

    I can drive whatever car I want on basically any road I want because the interface is standard. You've got some kind of more-or-less flat surface that my tire roll on.

    Similarly, I can get behind the wheel of virtually any car and do OK because the interface is pretty standard. Ignition, gas pedal, brake pedal, steering wheel, spedometer, etc.

    The problem, when it comes to computers, is that there's precious little standardization.

    A specific piece of software will run on one OS, but not another. Or it'll run with a specific service pack installed, but not without.

    A specific OS will only run on certain types of hardware.

    A specific piece of software will draw its UI one way... Another piece of software will have a completely different UI... Maybe you can hit CTRL+Z in one app, but not in another... Maybe the middle-mouse button works one way here, and another way there...

    So people just pick what's going to behave the way they're used to. They pick the OS and the software that they're familiar with. Which is why everyone yelled and screamed when Microsoft rolled out the whole "ribbon" thing - it was too different.

    --
    "Work is the curse of the drinking classes." -Oscar Wilde
  44. Re:OK. I'll speak the truth and take the hit. by Anonymous Coward · · Score: 0

    [citation needed]

  45. that and WfW and trumpet winsock by hildi · · Score: 0

    if it hadn't been for trumpet winsock i would have moved to linux in 1994.

    1. Re:that and WfW and trumpet winsock by dbIII · · Score: 1

      Same with me using trumpet, but I did move to linux in 1995 when Win95 didn't match the hype (and even initially had a crappier TCP/IP stack than what only two guys at trumpet did with windsock).

  46. Re:OK. I'll speak the truth and take the hit. by Zero__Kelvin · · Score: 1

    You could check this, or you could talk to some other people who watched it all happen.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  47. Re:OK. I'll speak the truth and take the hit. by Anonymous Coward · · Score: 0

    Business practices, marketing, distribution channles, partnerships, good ol'fashioned sales glad-handing are just as important to product sucesses in that real world outside of the computer geek's narrow view. To me, it's as legitimate a way to win as product capability. If you want a technically superior product to suceed ( or a technically inferior product, come to that), get a management team who can win in the real world, not one who complains about how the other side isn't playing fair.

  48. I bet none of these had Solitaire. by ip_free · · Score: 1

    I bet none of these had Solitaire. If they included some free time waiting games they would have been a success.

  49. WordPerfect by istartedi · · Score: 1

    I was working tech support in the late 90s. This stuff was not common, but it was still "in the wild". Somebody fielded a call from a woman who, when asked what here OS was, replied "WordPerfect". The wise tech realized that WordPerfect was one of these companies that had written their own shell. From the Layman's PoV, it was easy to regard the shell as the OS. The woman was not nearly the idiot that some techs had made her out to be.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  50. Re:OK. I'll speak the truth and take the hit. by bluefoxlucid · · Score: 1, Redundant

    Actually he marketed a concept. When he sold DOS to IBM, IBM already had Commodore... who was delaying their IBMPCOS project heavily. Lots of promises, lots of nothing to show for it. Gates convinced IBM that Commodore's PC operating system was ages-off vaporware and that he could do it faster.

  51. Re:The real question is: why just one big incumban by UnknownSoldier · · Score: 1

    > The problem, when it comes to computers, is that there's precious little standardization.

    Yes, that is definitely one BIG problem with computers. /me *glares* at Excel for STILL having non-standard cut/copypaste.
    e.g. Copy cell, type into another cell, Paste ... does NOTHING ?! Seriously, WTF, its 2010 and MS can't even implement this right in Excel 2007 ....

  52. Re:OK. I'll speak the truth and take the hit. by Zero__Kelvin · · Score: 1

    Apparently you don't know what the word underhanded means.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  53. AmigaOS by zr-rifle · · Score: 1

    AmigaOS had true multitasking, a windowing UI called Intuition, multiple screen of varying resolution on top of each other and a hardware mouse cursor (via custom graphics chips such as Denise). It also had scripting languages such as Amiga Basic (by MS) and an ARexx interpreter.

    In 1986.

    --
    Hack your mind out of its sandbox.
    1. Re:AmigaOS by anss123 · · Score: 1

      Actually, that was in 1985 but while had all that it lacked worthwhile copy & paste and printer support. Also I have to question the "true multitasking" bit as even the last version (OS 3.9) freeze animations while accessing menus.

      I've seen others note that though Amiga OS has preemptive multitasking, it's effectively cooperative since one regularly has to "call a routine" so that other apps can run UI workloads.

    2. Re:AmigaOS by MonTemplar · · Score: 2, Interesting

      You raise some good points - both the ability to cosistently copy and paste information between different applications and unified support for a wide range of printers and other devices were the Achilles Heal of a lot of alternative operating systems back in the day.

      -MT.

      --
      -MT.
    3. Re:AmigaOS by anss123 · · Score: 1

      And here I was thinking I'd get flamed by a hardcore Amiga Zulu. :-)

  54. Re:OK. I'll speak the truth and take the hit. by Hatta · · Score: 1

    Yeah! Preach it brother! Speak truth to power!

    --
    Give me Classic Slashdot or give me death!
  55. Re:OK. I'll speak the truth and take the hit. by BLKMGK · · Score: 1

    He also didn't have a working Windows for quite some time but instead an artful screen show. He spotted GEMS at one of the big tech conferences in 'Vegas, sent his minions over to take copious notes, killed it by announcing something "better" was coming, and then got to work building something to show. GEMS died on the vine because everyone ASSumed Microsoft would build something to kill it and GEMS couldn't get enough developer support to continue. Microsoft had a HUGE marketing campaign for their vaporware back then - and it worked. When Windows 1.0 was released it was pretty compared to say Desqview but it didn't multitask and background apps were halted for foreground tasks - I hated it. In the end I managed to stay away from Windows until Win95 at home but had to suffer with it at work. I wish I'd known about Linux back then and grown up with it :-(

    --
    Build it, Drive it, Improve it! Hybridz.org
  56. 1985 Fidonet tagline by Anonymous Coward · · Score: 0

    "Windows multitasks (in a Desqview window)."

  57. Visi On by linebackn · · Score: 2, Interesting

    In my opinion, there was an additional reason why Visi On failed (As if there weren't enough reasons already)

    Visi On used copy protection. You either had to have your original floppy disk in the drive at boot or have a genuine Visi On mouse attached (the software would check the mouse for a serial number). Now, tell me you don't see the problem with disks or mice wearing out quickly!

    From a historical preservation perspective, the worst part was since few people want to preserve old software besides games, it almost "protected" itself out of existence!

  58. Linux by dragin33 · · Score: 1

    ..Que flame bait...

    1. Re:Linux by mcgrew · · Score: 2, Interesting

      You're mixing Spanish with English? "What (que) flame bait"? Yes, your comment is, and is incorrect as well. Linux is on everything from wristwatches to supercomputers. The only place Linux isn't dominant is the desktop.

      And the only reason is that Windows comes preinstalled on almost ever PC sold. No normal user is going to install an alternative OS. Hell, most people have never heard of Linux.

    2. Re:Linux by MonTemplar · · Score: 1

      He might have typed his comment on a touch device like an iPhone or iPad, hence the typo. (I am typing this on an iPad, but I am also a fairly decent typist after all these years, in spite of the extra hoops required by the on-screen keyboard to get some characters. Needless to say, trying to write code on this thing would be a nightmare. D: )

      -MT.

      --
      -MT.
  59. DesQview ewas sweet by Anonymous Coward · · Score: 0

    I always loved it. Basically let you have unix's "screen" program. Short and sweet.

  60. Re:The real question is: why just one big incumban by Anonymous Coward · · Score: 2, Insightful

    *WE* made it happen that way. We as software devs for the longest time would make 3 different versions and then maybe sell a Mac ver and a Sun/HP Unix ver. We got tired of the 5+ different software configurations *ON TOP OF* the zillions of hardware configurations. Just for our sanity we picked windows. Love em or hate em MS was everywhere. Eventually the only software that was everywhere was windows. But we didnt care. We were too busy selling tons of software...

  61. Have a look at a few of them.... by rwbaskette · · Score: 2, Interesting

    This is a site I've enjoyed browsing for quite some time that gives small walk-throughs of the UI on many versions of different operating systems.

    http://toastytech.com/guis/

  62. Failed To Compete With Windows by Anonymous Coward · · Score: 1, Interesting

    Depends on your definition of 'compete` and apparently ingesting too many chemicals at the time that has caused you long term amnesia. In this case MS definition of 'compete' is to engulf the competing product and suck every last morsel of real innovation out of it, similarly to how a squid eviscerates its next dinner. The below extract is just one of many beautifully illustrating how they do 'business' out of Redmond:
    --

    "Geoview is a gui that runs on top of MS-DOS for low end systems. It is more of a competitive issue for Windows (and Works) than DOS .. I suggested that someone on the technical side call Robert Smith at Phoenix in Norwood who has in depth technical knowledge of this product and is willing to share it"

    "We need data on this product ASAP, it is about to scoop Works on a major deal, in going through the mass merch channel this fall if we do not kill it have we gotten a copy of it and done any evaluation?" link

    " It would great if we could get our hands on Jaguar. Joachim and Jeremy are harassing Atari and Amstrad respectively to get them to send us a copy" link

    "the way to shut out novell in the base is to either ship a full client or make it so there is no network connectivity " link

    "I an reading about the Gateway adoption of the Corel software. I am interested to understand what this means better and how it relates to any contracts we have with them link

    1. Re:Failed To Compete With Windows by MonTemplar · · Score: 1

      s/do "business"/did "business"/

      Nowadays they cannot do that thanks to continuing oversight imposed as part of the US antitrust settlement. So now they have to try other methods to attempt to impede competitors, with "attempt" being the operative word, thankfully - people are a lot wiser now.

      -MT.

      --
      -MT.
  63. .Net / C# Java by Safety+Cap · · Score: 1

    .Net and C# came about to push Java out of the market, not the other way around.

    Yep! .Net is about as close to Java as one can get without violating Sun’s^H^H^H^H Oracle’s copyright.

    --
    Yeah, right.
  64. linux killed os/2 as much as windows did. by Anonymous Coward · · Score: 0

    Maybe not in sales, but in usage.

    I think the reason we don't have OS/2 servers today is because of how popular linux was becoming amongst nerdy college students.

    I used OS/2 for a while but the licenses were as expensive or more expensive than windows for workgroups. As a broke college kid linux was very interesting to me. I could do anything I was willing to invest my time into learning how to do with it.

    All those nerdy college kids became employees at some point and eventually management.

  65. It should also be noted by Sycraft-fu · · Score: 2, Insightful

    That one isn't inherently better than the other. At first glance, it sounds like preemptive multi-tasking is the way to go since that is what all our desktops use now and since it is far more stable. However that is only true in an environment flush with resources, as our computers are. It incurs a good deal of overhead, which is why it was more problematic on older hardware. You could do it, but you paid a performance price. That's part of the reason you saw CMT not just on Windows but on things like MacOS as well. If programs behave themselves, it can be a much lower amount of overhead, and that mattered on those slower processors.

    For just an idea of how slow they were consider that it took almost all of a 486 to play a stereo 128k MP3. I remember when I first started playing with them and in Windows 95, it wasn't possible. Even running nothing but an MP3 player the overhead from the OS (which wasn't fully preemptive itself) was too much, I had to turn it down to mono or reduce quality to play. To get full stereo I had to drop to DOS and play it with Cubic Player. Now of course we can play them in the background with less than 1% CPU time on a single core.

    Just something for people to consider with regards to cooperative vs preemptive. Preemptive works great and is really what you want on a desktop computer where arbitrary code can be executed because it keeps problematic code from running away with resources, and also just makes programming a bit easier (you have to be careful when programming something for a co-op system that will be expected to use as much resources as it can get, yet still cede control properly). However it does incur overhead to make happen, and when you talk a slow enough system, it is a non-trivial amount.

    1. Re:It should also be noted by Anonymous Coward · · Score: 1, Insightful

      > At first glance, it sounds like preemptive multi-tasking is the way to go ...
      > However that is only true in an environment flush with resources,

      It's probably more accurate to say that it's only true on a system with an MMU.

      PMT isn't inherently more resource-hungry than CMT; most of the perceived difference comes from that fact that CMT systems typically switch tasks far less frequently than PMT systems. You could get the same effect with a PMT system simply by using longer time-slices.

      The problem with trying to implement PMT on a system without an MMU is that the OS cannot reallocate memory as it sees fit. Once it gives RAM to a task, it can't take it away it until the task says so, because there's no mechanism (i.e. page fault) by which it can return the memory when the task needs it.

      With CMT, tasks are supposed to acquire temporary buffers and release them before yielding the CPU. With PMT and an MMU, the OS just confiscates the memory as it sees fit and gives it back when needed.

      Also, reliability tends to suck if you implement PMT without an MMU (I'm looking at you, Amiga). Programmers access shared data without bothering to lock it, which works most of the time but results in obscure bugs when the data changes at just the wrong time. With CMT, data only changes when it's expected to change, i.e. either when the program modifies it, or when it yields the CPU. With an MMT, the OS can force the application to go through the proper channels.

    2. Re:It should also be noted by jrumney · · Score: 1

      Co-operative multitasking might perform better in a special purpose device, where all the software running is designed to work as a cohesive system towards a common design goal. But for a general purpose computer that is going to be running software from various third parties that have no interest in working with each other, preemptive multitasking is the only sensible way.

  66. Re:The real question is: why just one big incumban by MaWeiTao · · Score: 1

    That would be nice, but cars and operating systems are a totally different dynamic. The interface for all cars is virtually identical: two or three pedals, a shift lever and a steering wheel. Virtually car will run on public roads, regardless engine size, number of doors and even wheel count. Even something more exotic, like a tank or construction equipment will run on the road, even if it does damage pavement in the process.

    Operating systems, however, are a totally different animal. First, you've got user interface which has an impact on user-friendliness and functionality. Second, you've got the applications available on each system. Then you've got a host of other factors, like software lock-in, marketing prowess, established user base, etc. All these factors contribute to a particular platform being popular.

    I suppose, in theory, various companies could developed their own OS and then follow certain standards. That already exists to some extent. But you're still dependent on software developers offering a version of their application that runs in your OS. That's not a trivial undertaking in the least, even selecting which operating systems to support is daunting.

    But building the OS itself is a massive undertaking, and everyone's got their own vision about what it should do, so this inevitably breeds incompatibility. What you're suggesting almost sounds like everyone should go with a single base OS and then do nothing more than skin their version.

  67. After reading the title... by larppaxyz · · Score: 1, Flamebait

    .. i was sure we are talking about Linux desktop.

  68. Re:OK. I'll speak the truth and take the hit. by Anonymous Coward · · Score: 0

    IBM already had Commodore

    I'm pretty sure you mean Digital Research and their CP/M-86 operating system. Which already existed, but which Digital was raising roadblocks over on account of IBM's insistence on NDA terms.

    -AC

  69. quick review to the past... by Anonymous Coward · · Score: 0

    There is a quick review to the past...
    http://www.webdesignerdepot.com/2009/03/operating-system-interface-design-between-1981-2009/

  70. Re:The real question is: why just one big incumban by Smauler · · Score: 1

    So why is the computing market so different ?

    The only reason I run Windows is because I play games on my PC. It's just vendor lock-in, and I realise I'm rewarding them for it by buying their product, but I'm a little short-sighted. The first thing I'd do if I was in power would be to mandate open standards.... The software market is _completely_ fucked at the moment. DirectX is the major problem for games.

    I would dual boot Linux (that was my original intention when I got this computer), but at the time the fakeraid implementation on Linux was tenuous at best - my first attempt at a linux installation on this system helpfully told me that the best thing to do would be to format my primary drives seperately before continuing. I have bought another HD to stick Linux on, but I haven't got around to it yet... I haven't checked to see if their fakeraid implementation is working better, either.

  71. Why they failed by 28.stick · · Score: 1
    a Visi On window on TFA says:

    Multiple Apps are ruining at the same time.

  72. Re:The real question is: why just one big incumban by bolthole · · Score: 1

    There are plenty of motor car manufacturers, and most people don't just drive a Ford (or whatever). So why is the computing market so different ?

    because what you do with them is completely different.
    With a car, you are doing something that is fairly primitive: travelling from one point to another.
    You are taking yourself. possibly passengers.
    But the operation is trivial, and it does not need to be repeatable, or recreatable by others.

    In contrast, what most people want to do with computers (at least in the business world) MUST be
    repeatable
    recreatable by others
    and sharable with others.
    and the complexity of what you are sharing, is way, way higher.
    You arent just moving a handful of words/numbers around. you are moving them around, preserving a particular place on a page, with a particular font, with a particular relationships to other words/numbers. and if you are sharing spreadsheets/etc. then you need to ensure that if some of them are altered, then [this other set of numbers] change, in a guaranteed predictable way.... and so on, and so on.

  73. Re:OK. I'll speak the truth and take the hit. by blarkon · · Score: 1

    Yeah - that's the reason we didn't get the year of Linux Desktop - wasn't because Linux wasn't awesome enough... it was because Microsoft Cheated!!!!!!!

  74. Re:The real question is: why just one big incumban by jonbryce · · Score: 1

    Excel 2010 isn't any better.

  75. Re:OK. I'll speak the truth and take the hit. by Zero__Kelvin · · Score: 3, Insightful

    First of all, your post erroneously assumes that the answer to the question: "When will Linux be ready for the desktop?" is not "It has been ready for years.". You also are overlooking all the lies told, the FUD sold, the standards committee tampering, and the Halloween Documents that prove that Microsoft indeed cheated, even though it still didn't win (though their customers have certainly lost.)

    The question I want answered is "When will Windows be ready for the desktop?", because I guarantee you my Linux box blows the doors of of any Windows machine hands down, and does it all without being a Malware fest.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  76. Re:OK. I'll speak the truth and take the hit. by JohnBailey · · Score: 1

    Apparently you don't know what the word underhanded means.

    Come on.. They guy is in marketing. You need to use more meaningless buzz words..

    --
    It is difficult to get a man to understand something when his job depends on not understanding it.
  77. Re:OK. I'll speak the truth and take the hit. by westlake · · Score: 0, Troll

    Remember...He didn't even have DOS when he sold it to IBM.

    What Gates had was a full suite of programming languages ready to port to the new micro.

    What Gates had was the guts to promise delivery of a serviceable 16 bit CP/M clone in time for the scheduled launch of the IBM PC.

    These were the words IBM needed to hear.

    What Gates had was the smarts to negotiate a non-exclusive license for DOS -

    which would sell for $200 less than CP/M 86.

    $467 less, adjusted for inflation. The Inflation Calculator

    MS-DOS would be the commodity OS.

    That alone permanently altered the landscape.

    The MS-DOS PC was an unquestionably viable commercial product before the cloning of the PC BIOS.

  78. Q-DOS by Kittenman · · Score: 1

    Before they branched out to the "tips" business. Snappy file manager, but that was about it, really.

    --
    "The greatest lesson in life is to know that even fools are right sometimes" - Winston Churchill
  79. the other side of the prison bars by epine · · Score: 1

    The short history of windowed operating systems:

    Memory Prices (1957-2010)
    1985 $300/MB
    1990 $100/MB
    1995 $32/MB -- cartel warning !!!
    1996 $5/MB -- and the wall came crumbling down
    1998 $1/MB

    Even uglier if you correct for inflation.

    I couldn't stand *any* of the early Windowing products. Too cramped. My "fat" Mac was no better than anything else. Spent more time dragging Windows around on that small screen to see what I was working on than getting anything useful accomplished.

    Had two floppy drives, but Jobs had instilled a miraculous ability into the OS to pop out the wrong floppy when it needed a file on a different diskette, the one you knew you'd have to put back in two seconds later. There was no way to override or preempt this. Jobs knows best. Burned into my amygdala so deeply it will twitch on the autopsy table at the sound of automatic floppy disk eject.

    If I had been willing to upgrade with a hard disk, that system might have become borderline usable. I priced the drive upgrade at roughly on par with buying a turbo XT with a hard drive and monitor from scratch.

    From that day forward, I learned to tolerate MSDOS, and had a work flow that got enough done. What I realized in retrospect is that my work flow discouraged experimentation. No Carmack for me. New ideas were added straight into the production code base. Just to keep the number of contexts to a minimum, with no multitasking to help out. I was shaped by my tool, and not in a good way.

    At one point we had a spare machine and I tried out Coherent. That experiment ended immediately when I discovered that the bundled C compiler supported K&R, but not ANSI. All of my own code was portable ANSI. Game over. I didn't have access to the internet yet, so it wasn't easy to download Linux, which was still pretty green.

    My long sentence under DOS ended when I jumped to Windows NT 4 circa 1996 on a brand new Pentium Pro. Had my first cable modem within the year. Good times.

    By 1999 I had several large monitors, a KVM, OpenSSH, and *finally* enough system memory. I was no longer shackled to picking one primary work environment. I could use whichever system best matched the requirements. Divorce rocks!

    For me 1999 was an inflection point in the merit debate. It was like the sexual liberation of the late 1960s. Choosing your system environment in 1985 was like watching a movie made in the 1950s about communicating emotion. You weren't operating in a regime of easy choices. Much consumer loyalty in the PC space 1985-1999 was born of cognitive dissonance. After you married the damn thing, you couldn't bear not to defend it.

    Most people think of getting a driver's licence as a milestone of independence. For me, a decade of suck ended the day in December 1995 when I discovered AltaVista through my crappy dial-up service. "Damn, this rocks!" I thought to myself. I've never give ten brain cells to a press release for the rest of my natural days! Finally a liberation worth having.

    For my desktop, I wanted a window that opened outward, not a set of prison bars to tile a display that was too small to begin with. This was largely driven by the limitations of the CRT and the cost of memory. Pricey to have a desk full of bit-mapped workstations prior to 1996.

    After my sour Mac experience, had it been available in 1986 for a competitive price, I sure would have enjoyed a 24" text mode video panel (say 80 rows by 200 columns, and a couple of grey levels). My window manager could have been a frame enhanced Emacs running under MSDOS, and I would have been happy as a pig in poo.

    I never found much use for micro-managed gun turrets with more screen area devoted to window cruft than document content.

  80. Re:OK. I'll speak the truth and take the hit. by Anonymous Coward · · Score: 0

    Who the fuck marked this insightful? It's fucking well known IBM asked Gates to find a DOS when Microsoft told IBM they didnt have one. Oh boohoo QDOS writers werent told who Microsoft were buying for. So MS got a DOS for IBM, this doesnt make it vapurware

  81. On Jack Tramiel by Tablizer · · Score: 1

    I'm not sure why you blame Jack Tramiel. The PC was bound to succeed against existing computers because the architecture was more open. And the Amiga was after Jack's era. Microsoft won because it controlled the OS on top of the open hardware. Commodore was not an OS company even if it had been given a magic envelope from the future, and it was too late in the game to turn it into an OS company.

    Commodore perhaps could have survived by marketing the Amiga as a desktop publishing (DP) computer, a "cheaper Mac". But back then nobody knew what DP was or how big it would get. DP was the only thing that saved Apple.

    Many good software and hardware companies died off in that era. The few combination of behaviors that worked were hard to fathom at the time, and much of it came down to luck.

  82. The best technology does not always win by plopez · · Score: 1

    This is heresy to many "Conservative" economists. MS prevailed due to their unholy alliances with IBM and Intel; and anti-competitive practices. They also had a slick marketing campaign in the begining. It's not just about the technology.

    --
    putting the 'B' in LGBTQ+
  83. LCARS by dnafrequency · · Score: 1

    DESQview looks like it.

  84. Jack Tramiel should be strung up by nurb432 · · Score: 0, Troll

    No, his sons should be.

    And forgetting games, GEM on the ST ( even in its original form ) was still more functional then MSwindows has ever been.

    --
    ---- Booth was a patriot ----
  85. Failed? by nurb432 · · Score: 1

    Or pushed out due to unfair/illegal business practices?

    I vote the 2nd.

    --
    ---- Booth was a patriot ----
  86. Windows 1.0 was junk, in my experience. by Futurepower(R) · · Score: 1

    TopView was unusable junk, in my experience.

    Windows 1.0 was also junk in my experience. It was only released to show that Microsoft would soon have a usable windowing operating system.

    Books written about that time indicate that Windows 1.0 was released to try to buy time until Microsoft could release a product that was better than GEM. It was dishonest marketing, the books indicate. People at that time had so little knowledge about computers that they did not detect the lie.

    1. Re:Windows 1.0 was junk, in my experience. by falconwolf · · Score: 1

      TopView was unusable junk, in my experience.

      Until I read this article I don't think I ever heard of TopView. By then I was using Macs most of the tyme. I only used PCs and DOS for programming. For papers, desktop publishing, and drawing it was all Mac.

      Falcon

  87. Re:OK. I'll speak the truth and take the hit. by HermMunster · · Score: 2, Informative

    http://www.roughlydrafted.com/RD/RDM.Tech.Q1.07/5F0C866C-6DDF-4A9A-9515-531B0CA0C29C.html

    The above article is very demonstrative of the truth of the insightful GP comment.

    Very interesting article even for someone that lived through it. I can remember reading articles and thinking that Microsoft is just doing it better or doing what's best for us consumers, when all along they were out to kill superior products and were trying to take over certain technological advances (such as streaming video or authoring media). Very interesting article.

    --
    You can lead a man with reason but you can't make him think.
  88. Re:The real question is: why just one big incumban by petit_robert · · Score: 1

    It doesn't take that many dollars to use some kind of virtualization tool, and run your windows application inside a virtual machine.

  89. Re:OK. I'll speak the truth and take the hit. by thejynxed · · Score: 0

    Except when it comes to games.

    Or audio/video/photo editing. Or commercial publishing.

    Essentially, anything that doesn't involve databases, email, webservers, specialized machine control (routers, cnc machines, etc), or number crunching.

    I think by now everyone knows that answer to "When will Linux be ready for the desktop?", is never. It's not an insult, it's just a fact. Linux just works better for certain workstations, embedded systems, and most servers. It falls down flat when it attempts to disguise itself as a desktop OS. The developers would be better off forgetting things like laptops and desktop systems and pour their resources into mobile versions of the operating system and the back-end that would serve and control those mobile systems. This includes future control/communications platforms that are starting to appear in mass-market transportation. It's missed the boat for being ready for the desktop by a longshot when so much of computing is already moving away from it.

    BSD is a better desktop OS than Linux for that matter anyhow (just look at MacOSX for a prime example), and isn't in a state of fractured chaos like Linux (Too many flavors: great for choice, bottom-barrel for support and quality control).

    --
    @Mindless Drivel: 100% of Twitter posts ever Tweeted.
  90. Re:OK. I'll speak the truth and take the hit. by BraksDad · · Score: 1

    ...due to Gates' underhanded business practices.

    You mean successful business practices, right?

    --
    Slowly waving my hand - "This is not the sig you are looking for."
  91. Re:The real question is: why just one big incumban by sznupi · · Score: 1

    Similarly, I can get behind the wheel of virtually any car and do OK because the interface is pretty standard. Ignition, gas pedal, brake pedal, steering wheel, spedometer, etc.

    Well, since most of the cars on the planet have also clutch pedal, you might be in for a little surprise... ;p

    --
    One that hath name thou can not otter
  92. Windows succeeded because it was better. by master_p · · Score: 1

    It may be that DesqView, GEM etc were better than Windows 1.0, but when PCs became a viable platform (i.e. when 80386 was a viable choice), Windows 3.0 was the only O/S choice, vastly superior than anything else on the PC.

    When the 386 CPU came out, some of the people that were into computers understood that it was time for a true 32-bit operating system for the PC. Most magazine articles of the time talked repeatedly about how 32-bit operating systems is the future of the PC and the IT industry.

    Microsoft got it, and they made Windows NT. The others didn't(*), and they faded into oblivion.

    (*)Except Apple, that is: MacOS was superior than Windows, but Windows run on PC compatibles.

    1. Re:Windows succeeded because it was better. by bhtooefr · · Score: 1

      OS/2 2.0 beat NT 3.1 out of the gate (and got it out in 1992, causing Steve Ballmer to lose a bet that would've required him to eat a floppy disk, had he actually honored the terms of the bet,) by releasing a beta version and calling it a "limited availability" edition.

  93. In 1982 by Phoghat · · Score: 1
    I had bought a Commodore 64 and it was used with the Contiki GUI. Humph!

    Nothig to see here, move along

    --
    Think of how stupid the average person is, and realize half of them are stupider than that.
    1. Re:In 1982 by bhtooefr · · Score: 1

      You may have bought it in 1982, and you may have used it with Contiki, but those were separate events.

      Contiki came out around 2003 or so.

  94. Re:OK. I'll speak the truth and take the hit. by Zero__Kelvin · · Score: 1

    "Except when it comes to games"

    You have confused a computer with a gaming console. Color me surprised.

    "Or audio/video/photo editing. Or commercial publishing."

    If only I could use Ardour with a realtime kernel to not only have a superior Digital Audio Workstation, but also do live signal processing while on stage :-( Oh wait, that's right, I've been doing that for years! You also evidently don't know what is available for the other applications you identified. Unix/Linux are where the real tools are at to be found.

    You are confusing your ignorance of the available tools with actual unavailability of tools, I'm afraid.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  95. Re:OK. I'll speak the truth and take the hit. by Zero__Kelvin · · Score: 1

    Yes, that is exactly what I mean, much in the same way that Charles Manson was a successful murderer. Give my condolences to Brak.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  96. Re:OK. I'll speak the truth and take the hit. by Anonymous Coward · · Score: 0

    Obviously you have a narrow understanding of what happened. IBM technically never asked them to find anything. They asked if Microsoft had something to offer that would work. Microsoft stated they did. Then Microsoft's Paul Allen went and negotiated with the Seattle company that cloned CP/M (called QDOS (for quick and dirty operating system)).

    At that point in time there was nothing wrong with what they did other than it was very deceptive, and it forewarned of their future practices, which were very destructive to innovation and to the market as a whole.

    The insightful nature of his post was that he pointed out with clarity that the road was not lined with rose petals, instead it was lined with artillery aimed at technologies that would have certainly been better choices had the industry been allowed to advance unfettered by the threats and criminal actions of Microsoft over its first 20 years.

    In other words it wasn't through competition that these alternative products lost but through deceptive and criminal acts. Those criminal acts that resulted in a criminal trial (the Justice Department doesn't pursue civil claims) and Microsoft's conviction which resulted in a Judge's initial order to break Microsoft up. Though the order was overturned when Microsoft got the judge thrown out (after the trial) the criminal conviction stood. It was only a question of remedy at that point. The individual states were still suing Microsoft.

    So, let's not make it seem like Microsoft was just better at what they did and that they came up with DOS in some purely innocent manner, and let's not be convinced that their criminal conviction means nothing.

  97. Re:According to MS, Win temporary, OS/2 + PM futur by Elbowgeek · · Score: 1

    If I'm not much mistaken I believe some vestiges of an OS/2 subsystem survived in Windows until very recently. In fact I do often wonder if there's more OS/2 in Windows than they let on...

    --
    Who is this delectable creature with an insatiable love of the dead?
  98. GeoWorks Ensemble FTW! by mlosh · · Score: 1

    Back around 1991 I had a PC-clone 386SX. For you youngsters, thats a 32-bit CPU with a 16-bit (i.e. slow) data bus. I didn't have the coin to put Windows/386 or Windows 3.0 on it, but I could afford GeoWorks. It worked very well on that old machine. I kept using it after I moved on to a used 486. GeoWorks word processor was quite good for it's time. I was sad it never got much market share.

  99. Re:OK. I'll speak the truth and take the hit. by Raenex · · Score: 1

    OK. I'll speak the truth and take the hit.

    No, you didn't "take the hit" (post currently modded at +5). You're a mod whore making such statements and bashing Bill Gates. If you have something to say, just say it.

  100. Re:OK. I'll speak the truth and take the hit. by Anonymous Coward · · Score: 0

    Well good luck playing games chump.

    Cause my gaming WINDOWS box owns yourz.

  101. Re:According to MS, Win temporary, OS/2 + PM futur by IntlHarvester · · Score: 1

    In the early MS Windows 3 era MS told developers that Windows was just a temporary GUI for DOS to satisfy existing installations that will eventually be migrated to OS/2 1 + Presentation Manager. They emphasized how source compatible WIndows and Presentation Manager were and that porting would not be a major issue.
     

    That was the plan, but IBM was not interested in making software easy to port, and made a bunch of gratuitous changes to OS/2 PM (the famous one being moving the screen coordinate zero-point to the bottom left.)

    The "source compatibility" issue was one of the major reasons Microsoft started on Win32 and eventually broke from IBM.

    --
    Business. Numbers. Money. People. Computer World.
  102. Perspective from the CAD / DTP viewpoint by MasterOfGoingFaster · · Score: 2, Insightful

    I've owned and used Top View, GEM, DESQview and Windows 1.0 and all later editions. And I think the real reason Windows won was simple - Drivers.

    I was running Lotus 123, Word Perfect, Ventura Publisher, and AutoCAD. I had expensive ($3000+) graphics cards, a 21" monitor and a laser printer (when they were $5000 beasts). Every time a new software release came out, I had to wait months for drivers to appear for the graphics card and printer. Sometimes they never arrived.

    When Windows appeared, it wasn't very useful. But they always seemed to have drivers. I switched to Ami Pro, Excel and PageMaker because they all ran on a system (Windows) that had drivers for all my equipment. It was wonderful to be out of the waiting-for-drivers quandary. When Windows 386 appeared, I could run my DOS apps in a Window and not have to switch back-and-forth to DOS.

    I'm pretty sure the younger crowd would have no idea what we went through. Every single app either ran at 640x480 (pretty bad on a 21" monitor) or had to have custom drivers. And you only had text printing - no graphics - without drivers. And you only had text printing if your printer emulated the IBM Graphics Printer.

    Pretty soon, the hardware vendors started noticing that the availability of Windows driver became a binary decision for consumers - graphics boards with just Windows drivers would sell, while devices without became hard to sell. Companies that focused on Windows-only got the jump on those that had to write dozens of drivers.

    Stop and think about the effort of keeping track of drivers for graphics, printer, mouse, modem, keyboard, sound card for EVERY app. And then do it again for each new release of every app. This is why Windows won - at least in my opinion.

    --
    Place nail here >+
  103. Re:OK. I'll speak the truth and take the hit. by BraksDad · · Score: 1

    I miss Brak, but I miss Dad more.

    --
    Slowly waving my hand - "This is not the sig you are looking for."