Slashdot Mirror


Petition To Get OS/2 Open Source

Landreth writes "There is currently an ongoing petition taking place at OS2 World to get IBM to open source either the whole part or parts of OS/2 to the community. I would highly encourage the Linux community to take part of this open source petition as well due to the fact there are lots of interesting code base the they could benefit from. To sign the petition: http://www.os2world.com/petition/" Despite the jokes about it, there was some good stuff in OS/2; however, I'd rank the ability to open it up fairly low, since I suspect there's a fair amount of legal restrictions on elements of the code.

503 comments

  1. I'm In (293) - Many More Needed. by Allen+Zadr · · Score: 5, Interesting
    The total number of registrants for this OS2 petition: 293

    Thank you
    real name, your registration was successful.

    I've got to say - even if 40% of OS2 is opened up, the benefits to many, many projects could be wide-spread. Further, history shows that IBM is likely to use a GNU compatible license if they open the source at all.

    They obviously need more names. Posting it here though will make a nightmare for those who need to clean up the petition.

    --
    Kinetic stupidity has a new brand leader: Allen Zadr.
    1. Re:I'm In (293) - Many More Needed. by lilmouse · · Score: 2, Funny

      Hey, now we know how many signatures there are at the beginning of the slashdotting! Now, if someone will dupe the story in 3-4 days, we can see how many signatures got added :-D

      --LWM

    2. Re:I'm In (293) - Many More Needed. by Allen+Zadr · · Score: 1

      Good point ... I got in about four minutes before the story was open for comments (gotta love that subscription). I'm also curious to see if the counter actually works.

      --
      Kinetic stupidity has a new brand leader: Allen Zadr.
    3. Re:I'm In (293) - Many More Needed. by pavon · · Score: 5, Insightful

      Further, history shows that IBM is likely to use a GNU compatible license if they open the source at all.

      Sort of. When they release code added to an existing project, it is released under that projects licence. But most of the code that they have released on their own is under the Common Public License (previously IBM Public License). The CPL is a very nice license, simular to the LGPL in what rights it gives to the user, and the FSF has no philosophical objections with it. However it is not compatable with the GPL for technical legal reasons. That means that you cannot compile GPL(or LGPL) code and CPL code together, although you can link CPL code against LGPL.

      I also agree that it would be very difficult to open source OS/2 because of cross licensing. Just one example - OS/2 is posix compliant. I would be very suprised if IBM did not have some license agreement with the holders of the SVR4 when making the posix layer. Also because they were not planning on releasing the code, they may not have kept track of every location of licensed code. This could become a bigger nightmare then the SCO lawsuit if they tried to open it up.

    4. Re:I'm In (293) - Many More Needed. by digismack · · Score: 1

      The total number of registrants for this OS2 petition: 713

      (as of 12:34pm Monday)

      --
      http://www.hollowdepth.com
    5. Re:I'm In (293) - Many More Needed. by maotx · · Score: 1

      It works. I was number 283.

      --
      I'm a virgo and on Slashdot. Coincidence? Yes.
    6. Re:I'm In (293) - Many More Needed. by Cat_Byte · · Score: 1

      It works. I was number 283. That was at 11:38 my time. The total number of registrants for this OS2 petition: 1063 This was at 11:55 my time. So it went up to 5 times the signatures in less than 20 minutes ;)

      --
      Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
    7. Re:I'm In (293) - Many More Needed. by superskippy · · Score: 1
      That means that you cannot compile GPL(or LGPL) code and CPL code together, although you can link CPL code against LGPL.


      No it doesn't. It just means that you can't distribute the results. This is a common GPL misconception. GPL only has any effect when you distribute your binaries. "You" in this case can mean your company or organisation.

    8. Re:I'm In (293) - Many More Needed. by ClosedSource · · Score: 1

      "I've got to say - even if 40% of OS2 is opened up, the benefits to many, many projects could be wide-spread."

      I've got to wonder if there's really any generic information in OS2 that OSS programmers (as a group) don't already know.

      It seems to me that source code for cancelled software products is most useful for those who were already using it and need to upgrade it so they can continue using it in the future.

      I'd like to see Rational Visual Test opened because many people are still using it. As soon as IBM bought Rational, they discontinued selling it to help prop-up sales of the more expensive Rational Robot.

      That's why I don't buy in to the idea of IBM as the OSS poster child.

    9. Re:I'm In (293) - Many More Needed. by Mantorp · · Score: 1

      1496

    10. Re:I'm In (293) - Many More Needed. by MisterTut · · Score: 1

      #1432 at 1:15 EST. Wee-hoo!

      -Tut

      Health-Hack.com

      --


      -Tut

      Health-Hack.com
    11. Re:I'm In (293) - Many More Needed. by pavon · · Score: 1

      You are correct. I was simplifying.

    12. Re:I'm In (293) - Many More Needed. by jbolden · · Score: 1

      I'm having trouble following the whole line of reasoniong here. IBM kills a closed source product and thus shouldn't be given credit for their extensive open source work.

      IBM has had a policy for decades of trying to avoid undercutting their own products. The only major company I know of that didn't have this policy was the old HP (basically make every product as good as you can for the cost target). While I don't know any details of them killing Rational Visual Test it sounds like its essentially them doing what they openly admit is their strategy. Incidentally a strategy that Rational also held to when they were independent. So I can't see anything unethical about this at all. I also don't see what this has to do with open source at all.

    13. Re:I'm In (293) - Many More Needed. by jemfinch · · Score: 4, Informative
      That means that you cannot compile GPL(or LGPL) code and CPL code together

      No, that means you can't compile GPLed code with CPLed code and distribute the resulting binary.

      Repeat after me: copyright affects distribution, not use.

      Jeremy
    14. Re:I'm In (293) - Many More Needed. by ClosedSource · · Score: 2, Interesting

      Isn't avoiding undercutting your own products exactly the same policy that MS has?

      If someday IBM decides it can't release any OSS products without undercutting it's money-making products, will they still qualify as an OSS poster-child?

      If IBM really believed in openness, as they claim they do, they would open all their products up and offer a free license to all their patents.

      I don't blame them if they don't (because I believe it's bad for their business), but I can tell the difference betwee principle and PR.

    15. Re:I'm In (293) - Many More Needed. by afd8856 · · Score: 1

      1965

      --
      I'll do the stupid thing first and then you shy people follow...
    16. Re:I'm In (293) - Many More Needed. by xanadu-xtroot.com · · Score: 1

      #1981 @ 2:00 PM, EST

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    17. Re:I'm In (293) - Many More Needed. by tolan-b · · Score: 3, Funny

      2001..

      Do I get a prize for it being a geeky film reference? :)

    18. Re:I'm In (293) - Many More Needed. by Chandon+Seldon · · Score: 1

      The thing to remember is: Being an "OSS poster-child" is worth a bunch of money.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    19. Re:I'm In (293) - Many More Needed. by drinkypoo · · Score: 1
      Linux is also posix compliant - or as close as you can get without paying for POSIX anyway. However, when you pay for POSIX, what you get is a specification, not a rubber stamp. That should have no bearing on this whatsoever. POSIX is not a layer if you design with it in mind, it's a methodology, an interface, and a set of functions which must be present.

      More importantly, what will stand in the way is agreements with Microsoft. Win32 and OS/2's paths are crossed and are probably inseperable at this point.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    20. Re:I'm In (293) - Many More Needed. by drinkypoo · · Score: 1

      By "really" believing in openness, you're saying that IBM should open everything. Your use of the phrase is improper. You're saying that if IBM really bought into your understanding of open systems, which is to say that they're good for everyone and everything in all situations (or so you imply) then they'd open everything. However, it is clear that IBM "gets" Open Source. They also understand that there are some advantages to closed source. Since no one has ever successfully proven that one system is better than the other, IBM is currently in the process of making that determination. They'll get back to you in a decade or so - IBM doesn't have to make snap decisions very often, due to sheer inertia.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    21. Re:I'm In (293) - Many More Needed. by pavon · · Score: 1

      Absolutely, you can create a posix complient implementation on your own. It has just been common practice for commercial companies who are creating "UNIX" functionality to license SVR5 code to speed things up and just to be safe. Especially after the BSD lawsuit.

    22. Re:I'm In (293) - Many More Needed. by jbolden · · Score: 1

      Isn't avoiding undercutting your own products exactly the same policy that MS has?

      Yes, as I indicated in my post the only major computer company I know of that hasn't continuously had this policy is HP. I should mention actually that MS is far better about this issue than most and has often undercut their more expensive products with cheaper products/ So if anything the comparison is unfair to Microsoft.

      If someday IBM decides it can't release any OSS products without undercutting it's money-making products, will they still qualify as an OSS poster-child?

      I assume you mean some. And the answer is IBM they has already made this choice and said so. I still disagree with the OSS-poster child comment. IBM is a powerful ally of opensource. RedHat, VA-Linux (several years ago), MySQL I think are better poster boys.

      If IBM really believed in openness, as they claim they do, they would open all their products up and offer a free license to all their patents.

      Which specific claim have they made that would apply to all their products? They've indicated they think open source software provides a great consulting opportunity. They've indicated that open source is a good way to get out of non proftable software construction projects. They've never indicated that open sourcing software is a good way to enhance profits for products where the majority of money comes from software sales (as is the case with Rational).

      I don't blame them if they don't (because I believe it's bad for their business), but I can tell the difference betwee principle and PR.

      Except that it seems like you are attacking them for things they've never actually said they believed in. Its sort of like attack George Bush for being a bad Buddhist.

    23. Re:I'm In (293) - Many More Needed. by rAiNsT0rm · · Score: 1
      The total number of registrants for this OS2 petition: 293

      Thank you real name, your registration was successful.
      Boy, it sure is a good thing you edited out the "Real Name" part, it's not like your Slashdot User ID or email address would have given you away or anything.
      --
      http://teasphere.wordpress.com - A little spot of tea
    24. Re:I'm In (293) - Many More Needed. by HybridJeff · · Score: 1

      2989

    25. Re:I'm In (293) - Many More Needed. by Mortanius · · Score: 1

      And then the even more interesting number, how many of those 'signatures' are actually real, living people. :-P

    26. Re:I'm In (293) - Many More Needed. by TexasDex · · Score: 1
      Repeat after me: copyright affects distribution, not use.
      A remark about DRM just writes itself right here.
      --
      The Cheese Stands Alone.
    27. Re:I'm In (293) - Many More Needed. by Anonymous Coward · · Score: 0

      Yes! Your tickets to 'Star Wars Episode III:Revenge of the Sith' are on their way. Hope you enjoy the movie! ;-]

    28. Re:I'm In (293) - Many More Needed. by oxygene2k2 · · Score: 0

      interesting, how CPL is a "very nice license", while its brother, the CDDL is usually regarded pure evil over here..

      I know, /. isn't hive mind - but hey, you weren't even modded as troll for that praise of the CPL!

    29. Re:I'm In (293) - Many More Needed. by DJCater · · Score: 1

      Just signed it as #3188.

      --
      Sig Appended to the end of comments you post. 120 chars.
    30. Re:I'm In (293) - Many More Needed. by ClosedSource · · Score: 1

      I don't have anything against IBM doing any level of closed vs. open source. But I do have an objection to IBM talking as if they have "seen the light" on open source and giving advice to other companies like Sun when they are holding back the most profitable products from the open source model.

      Perhaps "getting" open source for IBM means throwing a few crumbs to OSS community with the knowledge that it will get them a free pass in the future.

    31. Re:I'm In (293) - Many More Needed. by Allen+Zadr · · Score: 1

      Yeah, but Allan Zadr isn't my real name.

      --
      Kinetic stupidity has a new brand leader: Allen Zadr.
    32. Re:I'm In (293) - Many More Needed. by Anonymous Coward · · Score: 0

      DB/2 running on OS/2 on a PS/2 Half of a database running on half an operating system, running on half of a PC.

    33. Re:I'm In (293) - Many More Needed. by drsmithy · · Score: 1
      I've got to wonder if there's really any generic information in OS2 that OSS programmers (as a group) don't already know.

      The Workplace Shell is probably the only thing in OS/2 that's still worth worrying about. Everything else it had was surpassed by the competition a decade ago (if not longer).

    34. Re:I'm In (293) - Many More Needed. by dryeo · · Score: 1

      Yesterday at 09:55:52 I was number 115. Glad to see it soaring today.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    35. Re:I'm In (293) - Many More Needed. by NutscrapeSucks · · Score: 1

      My understanding is that OS/2 POSIX support is not "native", but implemented with a cygwin-like DLL. It's probably Berkeley code.

      If IBM licenced SVR5 code for OS/2, they really should have used more of it (like the portable multiuser kernel).

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    36. Re:I'm In (293) - Many More Needed. by Anonymous Coward · · Score: 0

      #4078, 11pm cst

    37. Re:I'm In (293) - Many More Needed. by Anonymous Coward · · Score: 0

      Well doesn't it make sense to hold back the most profitable products and release the products that everyone already has and try to help to improve on the easy to obtain and not very profitible software. Why would you release something that is making you millions of dollars. Should they starve themselves and their families. Sure its not there only source of income but it sure is nice to have.

      IBM can help the community by providing support and helping improve available open technology. Thats a good thing. They can also make money off of selling special and very good software that they have patients and copyrights on. Thats also a good thing. Combine these two things and you have a company that improves the comunity, makes products that work with open source and makes money. All of it is good. The Open Source community claims to be able to do everything and yet we are begging for IBM to release their software. What happened to us being so god damn good. I guess we arn't. In fact I know we arn't that good. I've worked on a few open surce projects and half the programers where slow and made dumb mistakes. I see it happen all the time. So IBM has better stuff then we have thats all this prooves. IBM has done quite alot so don't knock them for making money because the FOSS community isn't the end all be all like many of them think.

    38. Re:I'm In (293) - Many More Needed. by Ilgaz · · Score: 1

      I was os2 3.x user and I know IBM's philosophy in general. Also, as you wrote the 40% part, I better say more openly, half of OS 2 was coded by microsoft.

      Thats why I wouldn't sign it. Also, OS 2 is still used at very critical places, what about their concerns about opensource valid or not? They are "customer" you know and customer is always right. Especially customers having M16 part of their job :)

    39. Re:I'm In (293) - Many More Needed. by ClosedSource · · Score: 1

      I guess you didn't notice my Nickname; I'm not a FOSS advocate.

      As I said before, I have no problem with IBM holding back any technology they wish to. My problem is with their hypocritical attitude over FOSS. If they simply want to quietly support FOSS in a limited way, fine. But if they are going to preach to others about it, then they should be willing to go all the way.

      I also have a problem with FOSS advocates that while preaching purity to everyone (note the extreme arguments about the use of BitKeeper), are willing to give IBM a pass despite that fact IBM hasn't released source code for any of its core technologies.

      I suspect that many believe that the practical value of an endorsement of FOSS by IBM outweighs IBM's "sins".

    40. Re:I'm In (293) - Many More Needed. by Anonymous Coward · · Score: 0

      The total number of registrants for this OS2 petition: 4946
      2:58pm EST.

    41. Re:I'm In (293) - Many More Needed. by mink · · Score: 1

      You havent used OS/2 since about a decade ago have you?
      AFAIK it had LVM before Linux or any other desktop OS.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  2. The instant the source is released by mferrier · · Score: 5, Insightful

    ... you know IBM is going to have ten more lawsuits on their hands as various software copyright holders magically find bits of "their code" in the OS/2 source.

    1. Re:The instant the source is released by Anonymous Coward · · Score: 0

      IBM is quite anal about ensuring that code contamination doesn't happen.

      If they could, I would say they probably would open it. But IBM don't just click thier fingers, they move quite slow and in minute detail. I would expect every line of code would be reviewed as well as numerous visits by legal department and studies to see if it is cost effective to open source it.

  3. Microsoft owns a lot of the code by SocietyoftheFist · · Score: 5, Funny

    It taint gonna happen.

    1. Re:Microsoft owns a lot of the code by SocietyoftheFist · · Score: 1

      Weirdest moderation I've seen... I wrote this before somebody else pointed out that Microsoft owned a lot of the code in OS/2 and they were modded +5 and for some reason I was modded... funny??? Remind me to not use improper english anymore.

    2. Re:Microsoft owns a lot of the code by NextGaurd · · Score: 1

      I dont know if it's funny but it's true.... OS2 was more or less written by Microsoft for IBM.

    3. Re:Microsoft owns a lot of the code by mink · · Score: 1

      WEll I trust the guy who worked as an OS/2 Developer who said that what you say is true is wrong.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  4. MSFT will say no by DaHat · · Score: 5, Interesting

    Lets not forget that OS/2 was jointly developed by IBM and Microsoft and no doubt Microsoft still has significant rights to large portions of the code base. I find it very unlikely that they would let IBM release the code even if IBM wanted to.

    1. Re:MSFT will say no by Anonymous Coward · · Score: 0

      Also keep in mind that a significant amount of the code in Windows 2000, XP and likely Longhorn too, will have had its origins in OS/2.

    2. Re:MSFT will say no by Gopal.V · · Score: 0, Flamebait

      Shared sores.... maybe open too..

    3. Re:MSFT will say no by Anonymous Coward · · Score: 0
      Microsoft may say yes if it's a non-GPL-compatable patenty-encumbered "Open Source" (or OSI approved, at least) license.

      Remember, they have no problem with that "Open OS" from the other member of "The Unholly Alliance".

      Their war is against the GPL (they like BSD & CDDL because they need to "borrow" code from these projects to stay competitive, and like it that they can keep this "borrowed" code proprietary).

      Theh more they can divide and conquer the open source community the better for them.

    4. Re:MSFT will say no by BrookHarty · · Score: 2, Insightful

      Exactly, you can run Windows 16bit and (Win32) software on OS/2. I doubt microsoft will allow that code to be GPL'ed.

      I rathed liked OS/2, stable and had the best VGA Font I used. Ya, die hard terminal user. :P

    5. Re:MSFT will say no by marat · · Score: 2

      Exactly, and more than that, parts added (ported from AIX to be precise) solely by IBM, like JFS or modern TCP/IP stack, were already released for Linux, so I think IBM did whatever it could.

      In fact this question is almost as old os OS/2 itself and the answer is well known, so very strange it reappeared again.

    6. Re:MSFT will say no by astrojetsonjr · · Score: 1

      MSFT voting no would be my guess also. It was really amazing how OS/2 could run the Win16 and Win32 apps better than Windows could. I was an OS/2 user for a few years after Warp came out. I would have kept it up but the new applications were starting to have a tough time with the Windows bridge software.

    7. Re:MSFT will say no by DrXym · · Score: 4, Insightful
      With that said, anything from red books to technical documentation would be useful. Even header files. Or the CSet++ / VisualAge classes. Aside from SOM / WPS, OS/2 is like a primitive NT (flame proof clothes on but it's true) - it has limited plug and play, limited registry, limited games support (DIVE), less APIs, it's not a moving target and its API very closely resembles Win16 / Win32.

      Someone could produce something akin to WINE but for OS2/ apps. What use would this be? I have no idea, but I suppose there might be a lot of file servers, EPOS & banking code out there written to OS/2. It might be a big win to someone if that could be moved over to Linux.

    8. Re:MSFT will say no by Locutus · · Score: 1

      Microsoft only like the BSD and CDDL when it's somebody elses code being used. I think there are two examples of MSFT open source code but one is an installation tool, IIRC, and the other is a 'forms' framework. Hardly cutting edge and both have no chance of helping out any non-Windows projects.

      Do you really think Microsoft would want competition from it's own code? And it doesn't matter how old it is. If it'll help the competition, they'll say no.

      To that, I say release the non-Microsoft code and provide the API's and docs for the Microsoft parts. That is, unless IBM let Microsoft dictate the contract/license in the breakup. I've heard that even Serenity Systems( eCS ) has had a very difficult time getting access to OS/2 sources with or without NDA's.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    9. Re:MSFT will say no by AKAImBatman · · Score: 2, Interesting

      Remember, they have no problem with that "Open OS" from the other member of "The Unholly Alliance".

      That makes no bloody sense. What does Microsoft have to do with an OS that Sun has been developing for over two decades? It's none of their business, and Sun would likely sue if Microsoft got in the way.

      OS/2, OTOH, was a joint development project between Microsoft and IBM. They set about developing an ultra-advanced version of Windows that was supposed to be the next in line after Win3.1. However, Microsoft was secretly developing Windows NT and was planning to use OS/2 as a stop-gap measure while they built their true "next OS". Then a couple of MS engineers managed to get protected mode working for the Win3.1 code, and Microsoft shifted development to Win95, thus leaving OS/2 in the dustbin of Microsoft history.

    10. Re:MSFT will say no by squiggleslash · · Score: 2, Informative
      Kinda. You could run Microsoft Windows code if you had a copy of Microsoft Windows or bought the "full" version of OS/2 that, essentially, came with Microsoft Windows. But a Microsoft Windows-less OS/2 was also sold, which contained no Microsoft Windows code.

      At one point, IBM distributed OS/2 2.x on a computer magazine coverdisk (I forget which one) in the UK sans Microsoft Windows. That was, needless to say, before sales started to take off with OS/2 Warp (3.0.) IBM wouldn't have been able to do this had the code included anything from Microsoft Windows.

      (Apologies for the need to spell out "Microsoft Windows" each time, but I know the very first OS/2s came without any type of GUI, and know there's potential for confusion here with people assuming I mean "GUIless" - the Microsoft Windows-less OS/2 had a full GUI, it just couldn't run apps for Microsoft Windows.)

      --
      You are not alone. This is not normal. None of this is normal.
    11. Re:MSFT will say no by Locutus · · Score: 5, Interesting

      The ability for OS/2 to run Windows 16 and 32bit code was because IBM did a great job at the DOS virtual machine. It really was Windows 3.x running in OS/2. IBM even had Windows 95( aka Chicago ) running on OS/2 until Microsoft found out and then made Win32 apps load a tiny bit of data at and address space outside the reach of OS/2. I think OS/2 processes had 512MB of virtual address space while a Win32 app had 1.5GB or something like that. So OS/2 ended up only able to run Win32S applications and not Win32C or Win32NT apps.

      It was pretty cool running all those different systems on one OS though. At one point, I ran Win16/32s apps with OS/2 apps, XFree86 apps, and JAVA apps. Even wrote X11 apps for HP-UX systems on OS/2 and NFS before recompiling on the HP-UX system in the lab for final testing. It was sweet and the WorkplaceOS was supposed to take that concept to the OS level. Kinda like VM-Ware but with host OS and client OS integration.

      But all this is and was a theat to the "One Microsoft Way" kind of thinking. To Microsoft, competition is BAD. Very bad. That's why their way of competing is to do anything to prevent the competition in the first place. See DOJ vs MSFT court docs for a small set of examples of this.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    12. Re:MSFT will say no by javamann · · Score: 1

      Microsoft quit development on OS/2 back at 1.2, IBM did all the development after that. OS/2 was a very good operating system, the problem was IBM didn't know how to respond to the 'kitchen top' customer (people calling in to ask why Doom didn't run under OS/2). That and Microsoft did whatever they could, legal or otherwise, to kill OS/2

    13. Re:MSFT will say no by Lisandro · · Score: 1

      I can vouch for that. OS/2, at that time, was truly a Windows better than Windows and certainly a DOS better than DOS. I remember being stuck with Win3.11 at home, and going to a friends' house to watch his PC with OS/2 running Windows apps, DOS games and apps and some obscure BBS software all at the time, without a hiccup.

    14. Re:MSFT will say no by John+Hasler · · Score: 1

      > At one point, IBM distributed OS/2 2.x on a
      > computer magazine coverdisk (I forget which one)
      > in the UK sans Microsoft Windows. IBM wouldn't
      > have been able to do this had the code included
      > anything from Microsoft Windows.

      Yes they would. While they might not be able to distribute source, their license undoubtedly says they can sell copies of the binaries at any price they choose.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    15. Re:MSFT will say no by MightyMartian · · Score: 1
      I was working for a fellow who sold Point of Sale systems when OS/2 Warp was big. It was pretty awesome. The POS was a DOS program, but it ran like a charm under OS/2. We were selling the OS/2 version of Lantastic, which allowed integration with some older DOS boxes (I even remember one of them being a Tandy 2000 box). OS/2 was, at the time, a very impressive OS, and it really wasn't until Win2k that I think MS finally overtook it.

      I ran it on my own machine for five or six years. I had a dial-in Waffle BBS running in a DOS VDM, UUCP bringing in my email and a small newsfeed, and I could still play Railroad Tycoon Deluxe in a DOS VDM fullscreen session, all on a 486-33mhz with 16mb of RAM.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    16. Re:MSFT will say no by M1FCJ · · Score: 1

      It was Yggdrasil what convinced me to switch completely. Ah.. Good old days. :)

    17. Re:MSFT will say no by John+Hasler · · Score: 4, Insightful

      > That and Microsoft did whatever they could,
      > legal or otherwise, to kill OS/2

      So did IBM.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    18. Re:MSFT will say no by stretch0611 · · Score: 1
      Microsoft quit development on OS/2 back at 1.2, IBM did all the development after that.

      That sounds about right. I believe that OS/2 Warp was the first version without any of M$'s code (except of course for WIN-OS2). Also, IBM probably can release all of the OS/2 code, even the older stuff originally written by M$. When IBM liscensed DOS and M$ later licensed the code to everyone else that made a box. When IBM had M$ write OS/2, IBM paid to have all of the rights to the code so that M$ couldn't sell OS/2 to other manufacturer's.

      --
      Looking for a job?
      Want your resume written professionally?
      DON'T USE TUNAREZ!!!
    19. Re:MSFT will say no by satguy · · Score: 2, Interesting
      > it has limited plug and play,

      IBM invented plug and play, and OS/2 had it, 'til Microsoft "invented" a method different enough to break IBM's and make theirs the de facto standard.

      > limited registry,

      IMHO this is a GOOD thing ;)

      > limited games support

      ...understandable in a business sense (although OS/2's solitaire had a Cheat key, and a sense of humour if you used it too much) - IBM's never put out a dedicated game machine (PSII, Xbox, et al) of which I'm aware either.

      > less APIs,

      How many stable APIs did Win95 have? Are you familiar with all the Workplace APIs? (since Workplace is the descendant of OS/2)

      > it's not a moving target and its API very closely resembles Win16 / Win32.

      A non-moving target would be a bad thing why, again? ;) The API resemblance to Win16/32 is irrelevant.

    20. Re:MSFT will say no by Usagi_yo · · Score: 1
      Didn't Microsoft walk away from OS/2?

      If Microsoft owns portions of OS/2 because it was jointly developed by IBM, does IBM then own portions of Windows?


      We'll just have to see what the licenses is like or how IBM responds.

    21. Re:MSFT will say no by squiggleslash · · Score: 1

      IIRC, IBM had to pay Microsoft a license for each copy shipped. So, in practicality, they wouldn't be able to "sell copies of the binaries at any price they choose", not without going bust anyway!

      --
      You are not alone. This is not normal. None of this is normal.
    22. Re:MSFT will say no by chefren · · Score: 1
      The ability for OS/2 to run Windows 16 and 32bit code was because IBM did a great job at the DOS virtual machine.


      Also IBM and M$ crosslicensed their os code up to 1993 (or something like that) so IBM had access to the windows 3 series source code but not to the windows 95 source code. So it was not just the good vm. Anyway, I used OS/2 Warp and liked it very much.

    23. Re:MSFT will say no by sirwired · · Score: 1

      With that said, anything from red books to technical documentation would be useful.

      Oh, you mean these redbooks?

      SirWired

    24. Re:MSFT will say no by DavidTC · · Score: 2, Insightful
      When IBM had M$ write OS/2, IBM paid to have all of the rights to the code so that M$ couldn't sell OS/2 to other manufacturer's.

      This, incidently, is why MS jumped ship on OS/2.

      IBM had been burned by DOS, where they basically paid the R&D for their competitors, because they never thought there would be a market for PC clones and thus assumed that DOS was going to be basically theirs. (Well, I guess they figured MS might port it to other platforms, but that threat seemed limited.)

      When, suddenly, not only are people competing with them, but the people they got their OS from were selling exactly the same OS to those people! Which seems like something reasonable now, but it was a completely new concept at that time. (It didn't help that personal computers weren't taken seriously at all by IBM at this point.)

      I doubt this was delibrately, BTW. MS couldn't have predicted the clone market either.

      So the next time, they paid MS to make an OS for them, and solely them. Although they would be happy to license it competitors for a 'reasonable' cost.

      And, again, MS shafted them, delibrately this time, in a completely different way, with Windows.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    25. Re:MSFT will say no by LWATCDR · · Score: 1

      Yep.I doubt that IBM could release much of the code as OpenSource. I would have loved to the the Workplace shell open sourced. I hear that it was great. Now I worry that it would be yet another GUI fighting with Gnome and KDE.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    26. Re:MSFT will say no by OhPlz · · Score: 1

      It was distributed in the states too. I remember I a "preview" copy of one of the OS/2 versions, v3 sans Windows I believe. It came out in a red box whereas the version with WinOS2 was in a blue box.

      Up until just last year I worked at a company that still had hundreds of OS/2 boxes running various telephony apps. I had an MS OS/2 v1.3 running until some time around year 2000. Versions 3 and 4 were quite reliable for telephony, I had multi-T1 voice response units with uptimes over two years.

    27. Re:MSFT will say no by Anonymous Coward · · Score: 0

      " Microsoft quit development on OS/2 back at 1.2, IBM did all the development after that."

      Why is it then, that when the split ocurred, M$ got all rights to OS/2 3.0, which is what turned into NT?

    28. Re:MSFT will say no by Anonymous Coward · · Score: 0

      If WPS was to become open source, and be updated into an even halfway decent DE, Gnome and KDE would most certainly have their work cut out for them.

    29. Re:MSFT will say no by Anonymous Coward · · Score: 0

      Microsoft were not "secretly developing" NT, as NT is what M$ renamed OS/2 3.0 after the split.

    30. Re:MSFT will say no by AKAImBatman · · Score: 1

      Microsoft were not "secretly developing" NT, as NT is what M$ renamed OS/2 3.0 after the split.

      Survey says... No.

      NT was a ground up rewrite of a kernel based on VMS designs. The userland was a mish-mash of Win3.1 and OS/2 technology. Anyone who told you otherwise didn't know what they were talking about.

    31. Re:MSFT will say no by Anonymous Coward · · Score: 0
    32. Re:MSFT will say no by Gr8Apes · · Score: 1

      Actually, no. IBM really did all they could do. But until the late 90s, they had to pay $86 to MS for every copy of OS/2 sold (part of the licensing agreement for HPFS).

      Those types of costs prevented IBM from truly competing on price with OS/2, which was truly unfortunate.

      They also blew it with developers, but that's another story.

      --
      The cesspool just got a check and balance.
    33. Re:MSFT will say no by stretch0611 · · Score: 1
      IBM had been burned by DOS, where they basically paid the R&D for their competitors...

      Actually; I don't think Microsoft did much R&D for DOS. They paid someone (I forget the name) that already had a working product (I beleive the name was QDOS) $10,000 for all of the rights. This guy was also shafted by M$, Because he didn't know that M$ was just going to turn around and resell his OS to IBM. If he had known, I'm sure he would have increased the price to M$ or try to go directly to IBM.

      Wikipedia shows a slightly different story than what I heard; So you may want to read about QDOS there.

      --
      Looking for a job?
      Want your resume written professionally?
      DON'T USE TUNAREZ!!!
    34. Re:MSFT will say no by EvilIdler · · Score: 1

      So not quite like VMWare after all, but more like Win4Lin,
      and its precursor for SCO operating systems (Merge)?

    35. Re:MSFT will say no by Anonymous Coward · · Score: 0

      My impression was that MSFT stole most of what IBM put into OS/2 "jointly" and went and put a pretty new face on it and called it NT. Except that NT was a very poor "stupid brother we keep locked in the basement" copy of OS/2. I liked OS/2 and used it before switching to Linux. I suspect though, that MSFT will have such a hissy-fit over this. Since I have Linux, I don't really need OS/2 to be open sauce (in "The Register" vernacular). It was good, but it was closed. The only reason NT succeeded was that MSFT was pushing it hard hard hard (the marketing demons were back-stabbing OS/2 as hard as they were pushing "Nice Try"). You see, SCO tried to sue IBM over the joint venture Monterrey (and has failed). IBM never tried to sue MSFT over OS/2 (and had a much much better case). I think IBM still stings over OS/2. That was another time. IBM started backing Linux in 1999. They saw that it was good and thought it would be in their advantage to get onboard. It's earned them several billion more than they put in. As for OS/2, it's gone, even at IBM. But I'm willing to bet there is quite a bit of the GLOAT factor in the former OS/2 staffers when they see Linux slowly cutting MSFT and watch them bleed. Call it 'death of 1000 cuts" if you want to. They are still happy to serve this dish cold.

    36. Re:MSFT will say no by SillyNickName4me · · Score: 2, Informative

      > Actually, no. IBM really did all they could do. But until the late 90s, they had to pay $86 to MS for every copy of OS/2 sold (part of the licensing agreement for HPFS).

      Ah yes, thats why we (was working at IBM, doing OS/2 support and some development) got told that marketing effords aimed at the consumer were to be stopped inmediately, the day before WIndows 95 became generally available..

      No, they didn't try as hard as they could, they gave up before even having tried.

    37. Re:MSFT will say no by DrXym · · Score: 1

      Yes those, but open sourced. Plus any internal technical documents.

    38. Re:MSFT will say no by Locutus · · Score: 1

      good "catch" and I agree, Win4Lin seems like a closer match for how Windows loaded and ran on OS/2.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    39. Re:MSFT will say no by DaHat · · Score: 1

      No, NT was based off of the skills and backgrounds of a bunch of smart engineers who came from DEC who made VMS.

      Your comment makes it quite clear you know nothing more than what is said in comments on /. which as we all know are not always the most accurate.

    40. Re:MSFT will say no by drsmithy · · Score: 1
      That sounds about right. I believe that OS/2 Warp was the first version without any of M$'s code (except of course for WIN-OS2).

      HPFS was Microsoft's (the main reason it took so long to get a 32 bit HPFS driver).

    41. Re:MSFT will say no by drsmithy · · Score: 1
      They set about developing an ultra-advanced version of Windows that was supposed to be the next in line after Win3.1.

      There was nothing secret about the development of NT - it was, after all, supposed to be the successor of OS/2 (eventually).

      You are getting your OS/2s mixed up (or simply don't know).

      OS/2 was a collaborative project between Microsoft and IBM. The "ultra-advanced" version you speak of was the product that eventually became OS/2 2.x. It was going to be the "low end" or "desktop" OS/2.

      NT (originally OS/2 NT, then became Windows NT) was the product that was originally supposed to be for servers and high end PCs ("OS/3"). It was a Microsoft project, using Dave Cutler's team they bought from DEC. It was never a secret.

    42. Re:MSFT will say no by Anonymous Coward · · Score: 0

      If Microsoft owns portions of OS/2 because it was jointly developed by IBM, does IBM then own portions of Windows?

      Of course not - Windows wasn't a collaboration, so IBM has no rights over it.

      Basically, Windows was a Microsoft project started before they collaborated with IBM on OS/2, and once they got out of the latter, MS resumed development on Windows.

    43. Re:MSFT will say no by DavidTC · · Score: 1
      Yes, Microsoft didn't do much R&D, but that didn't really help IBM, now did it? ;)

      So maybe MS shafted IBM three times. Once, when it resold them an OS they assumed MS would develop, two, when they then resold that OS to others also, when IBM had paid for it with the assumption it would just work on IBM's machines, and three, when they stabbed them in back WRT OS/2.

      It's funny. You hear Apple whine about what MS did to them, but it was nothing compared to what MS did to IBM. The first was IBM not understanding PCs and not treating them seriously, the second was no one expecting IBM clones, but the third was just black-hearted malice and greed.

      Luckily, IBM has sold their PC division, and now can say 'up yours' to MS.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    44. Re:MSFT will say no by NutscrapeSucks · · Score: 1

      They tried hard enough to get a very good Windows 95 OEM deal. ($11/copy per court testimony.) That at least covered the costs of the OS/2 Fiesta Bowl (and other OS/2 marketing mishaps).

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    45. Re:MSFT will say no by dryeo · · Score: 1

      They crosslicensed upto WIN ver 4. Win95 was ver 4.095 so not crosslicensed

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    46. Re:MSFT will say no by dryeo · · Score: 1

      Mid 90's IBM was selling OS/2 Warp v3 for Windows (you needed your own copy of Win 3.1) for $50cdn. Also they gave out copies of 2.11 for Windows for the price of postage in places like Byte.
      I think you are thinking of Winos2 that cost.
      Of course HPFS386 costs about $1000 from MS

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    47. Re:MSFT will say no by dryeo · · Score: 1

      There were 2 versions of OS/2 ver 3. Way back during ver 1.x days IBM was developing ver 2 and MS was developing ver 3 NT. When the split happened MS took ver 3 NT changed it to Win NT ver 3.1.
      IBMs ver 3 is really just an updated ver 2. At that ver 4.5 that I'm writing this under is also ver 2.45
      E:\OS2>uname -a
      OS/2 amad.localdomain 2 2.45 i386

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    48. Re:MSFT will say no by NutscrapeSucks · · Score: 1

      > OS/2, at that time, was truly a Windows better than Windows

      For me, it wasn't.

      In those days, Windows 3.1 was such a piece of trash it wasn't unusual to have it crash 3 times a day . Under DOS you could be back and running within 30 seconds. Under OS/2, it sometimes would come back up in 30 seconds, but other times it would require me to endure OS/2's 10 minute reboot cycle of pain.

      Since there was no alternative to the Win apps I was using, I was back with DOS until I got my hands on Windows NT (where the Win16 was slower and less compatitible, but very very stable).

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    49. Re:MSFT will say no by dryeo · · Score: 2, Informative

      HPFS.IFS was written by IBM. HPFS386.IFS was written by MS.
      E:\OS2>bldlevel hpfs.ifs
      Build Level Display Facility Version 6.10.480 Oct 6 2000
      (C) Copyright IBM Corporation 1993-2000
      Signature: @#IBM:14.083#@ HPFS Installable File System for OS/2
      Vendor: IBM
      Revision: 14.83
      File Version: 14.83
      Description: HPFS Installable File System for OS/2

      The story I heard was that when IBM and Microsoft decided to build the next generation HD filesystem they agreed on the specs then each went of wrote their own file system. Then they sat down and compared them. Microsofts was much faster so they used that.
      Then it turned out that MS broke the specs, namely it was sopposed to be written in C and run on a 286. IBM then had to rewrite HPFS.
      HPFS is 16 bit and is limited to a 2 MB cache
      HPFS386 had no memory limit (besides OS limits) for cache and was much faster. MS still licenses HPFS386 for about $1000 a license.
      IBM eventually ported JFS to OS/2 to get around the need for HPFS386 on Warp Server. HPFS386 supports ACLs unlike HPFS

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    50. Re:MSFT will say no by dryeo · · Score: 1

      No,NT was to be the next version of OS/2 written by a bunch of smart engineers who came from DEC who had made VMS.
      Note that NT ran os/2 binaries up until XP (search the registry for OS2 or LIBPATH). Also NTFS uses the OS/2 installable file system partition ID.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    51. Re:MSFT will say no by mrselfdestrukt · · Score: 1

      Oh My Gooooood! An OS/2 Junkie! I've heard about people like you!
      Do you really live in caves deep inside earth?

      --
      "I used to have that really cool,funny sig ,but it got stolen."
    52. Re:MSFT will say no by Anonymous Coward · · Score: 0

      No, NT was "based on" (or "derived from", or one of a host of other possible equivalent phrases), but definitely NOT "based off of" nor even "based off" the skills and backgrounds of a bunch ...

    53. Re:MSFT will say no by Dragonlord_Warlock · · Score: 1

      There is a project in the early stages to build a open source version of OS/2 (OsFree.org) which is in the early stages. If IBM relased OS/2 to the open source community. Projects such as these would no longer need to exist. That being said, there are some parts of the OS/2-AIX family that has been released to the open source community already. One is ObjectRexx, now called Open Object Rexx. The key question that should be asked will the important aspects of OS/2 are to be released. Since it is apparent that IBM could release aspects of the OS without affecting the parts that are owned through other patents. The key factor would be to determine what parts are IBM and what parts are not. For a long time there been sharing of coding concepts with WINE and WinOS2 (Odin) projects. Another aspect of OS/2 that has been available to the Linux community. While it is not perfect yet, to run flawlessly Windows code. Mainly because Windows uses too many tricks to keep it software base out of the hands of projects such as OS/2, Odin and Wine. Perhaps the one thing that would be awesome if released to the open source community would be the Workplace shell. Such a release would greatly benfit all shells for Linux (including the OS/2 like IceWM). The ability to create a fully object oriented desktop would put these projects years ahead of M$.

      --
      - Dragonlord Warlock (aka Dion) "So many computers.... so little time...."
    54. Re:MSFT will say no by javamann · · Score: 1

      said the man who thinks Win95 was an operating system

    55. Re:MSFT will say no by runderwo · · Score: 1

      Windows NT until version 4.0 had an OS/2 execution subsystem.

    56. Re:MSFT will say no by Gr8Apes · · Score: 1

      I do recall the OS/2 for windows costing considerably less. IIRC, that OS came without HPFS at all, and booted over Windows.

      HPFS386 was a different beast, and came with the $1K+ OS/2 Server package, of which I have a copy at home, for free. :) I received it from someone who had an unused copy.

      --
      The cesspool just got a check and balance.
    57. Re:MSFT will say no by Gr8Apes · · Score: 1

      Wasn't a large part of that not trying due to infighting among divisions? Despite IBM's blunders in marketing, OS/2 had a hard-core fan base, and had they spun off OS/2 as a separate corp, it probably would have succeeded.

      --
      The cesspool just got a check and balance.
    58. Re:MSFT will say no by dryeo · · Score: 1

      IIRC, that OS came without HPFS at all, and booted over Windows.

      No what it was that if you did the quick install you never got the choice of HPFS. OS/2 would install itself on C: (fat) and dualboot with DOS by changing around the boot files depending on which OS you were using. With a couple of minor changes win3.x would run under OS/2 just like under DOS.
      Interestingly winos2 would also run under dosemu under Linux etc.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    59. Re:MSFT will say no by Gr8Apes · · Score: 1

      All I recall of OS/2 for Windows was that it was much more difficult to run and had many more errors than OS/2 Warp based on the reports I was hearing at the time.

      It's interesting that winos2 would run under Linux. I didn't know that.

      --
      The cesspool just got a check and balance.
    60. Re:MSFT will say no by SillyNickName4me · · Score: 1

      Wasn't a large part of that not trying due to infighting among divisions? Despite IBM's blunders in marketing, OS/2 had a hard-core fan base, and had they spun off OS/2 as a separate corp, it probably would have succeeded.

      At the time (1995-96) OS/2 was marketed by a more or less independent IBM software company. IBM's PC company (doing the PC hardware) was not very cooperative indeed, but had no say about this.

    61. Re:MSFT will say no by mink · · Score: 1

      Some of us have houses, cars, jobs, and wives (childern optional).

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  5. Full name & DOB? by 0xdeaddead · · Score: 2, Funny

    What are you crazy?! I mean I know OS/2 users are in denial, but geez this is INSANE!

    1. Re:Full name & DOB? by Chanc_Gorkon · · Score: 1

      As are AmigaOS Users....I remember all the flurry back in the late 90's and now....nothing.

      --

      Gorkman

  6. Huh? by xenostar · · Score: 1, Funny

    What's OS/2? Like, half an operating system or something? :P

    1. Re:Huh? by Anonymous Coward · · Score: 0

      > What's OS/2? Like, half an operating system or something?

      Like the last time I heard that one was from Great-Uncle Howard, and he farts dust.

    2. Re:Huh? by operagost · · Score: 1

      Yeah, like we didn't already hear that one on Usenet in 1992.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    3. Re:Huh? by Anonymous Coward · · Score: 0

      And it's still just as funny today!

    4. Re:Huh? by wootest · · Score: 2, Funny

      Per that, is OS X 20 times the OS OS/2 will ever be? ;)

    5. Re:Huh? by Anonymous Coward · · Score: 0

      I guess that would depend on the value of X.

    6. Re:Huh? by WarPresident · · Score: 3, Funny

      What's OS/2? Like, half an operating system or something? :P

      Careful with that joke, it's an antique.

      --
      Here come da fudge!
    7. Re:Huh? by doofusclam · · Score: 1
      What's OS/2? Like, half an operating system or something? :P


      Funnily enough, a few years ago I had issues running an app my company had developed and we traced the problem down to a COM component called 'Highedit', which was a nice rtf editor with some amazing bugs. I phoned up the (German) authors and the nice lady then referred to it as (phonetically) 'Oh Ess Half'

      Mind you it was the same company who in the English version of their manuals in the copyright preface had the line

      Warning! He who copies this software renders himself!


    8. Re:Huh? by wootest · · Score: 1

      Roman numerals would set X to the arabic decimal 10. Meanwhile in a base 36 system, X would be 33 ("10" being 36). However, since Apple reads OS X aloud as "OS ten"...

    9. Re:Huh? by wootest · · Score: 1

      Okay, screw that. I just got it, but in my world all math variables are "x", italic and lowercase. Bah. :)

  7. OS/2 Ahh the memories by big-giant-head · · Score: 4, Insightful

    I used in the early ninties, for it's day it was very nice. I think a Opensourced OS/2 would be a good alternative to Linux/BSD, for some folks who want a more gui driven system.... It never hurts to have options.

    --

    So Long and Thanks for all the Fish.
  8. petition by Anonymous Coward · · Score: 0

    The total number of registrants for this OS2 petition: 295

    Thank you Anonymous Coward, your registration was successful.

    1. Re:petition by Allen+Zadr · · Score: 1

      The really, really sad part is that this means that out of all these comments... only three (you, me, and one other) actually signed the petition.

      --
      Kinetic stupidity has a new brand leader: Allen Zadr.
    2. Re:petition by LiquidCoooled · · Score: 1

      GIve it a chance, that was posted only 4 minutes after it became public.
      Its been around an hour now and the figure is over 500 (I snuck in just under 500).

      --
      liqbase :: faster than paper
  9. vms by Anonymous Coward · · Score: 2, Insightful

    What we need, is VMS open sourced. OS/2 might be interesting, but VMS would be useful. There's a difference. VMS has one of the best multitasking systems that's ever seen the light of day - a scheduler that works exceedingly well, and a VM system that blows everything on the market today out of the water.

    1. Re:vms by DaHat · · Score: 2, Informative

      Would this be a bad time to mention that large portions of Windows NT were designed and implemented by many of the same people who built VMS? In fact, many of the data structures used by both systems are oddly similar, even identical in made cases.

    2. Re:vms by kin_korn_karn · · Score: 1

      that would reflect favorably upon MS and thus not acceptable on this website.

    3. Re:vms by LurkerXXX · · Score: 2, Informative

      You mean like OpenVMS? If you really cared, you would know it's already out there.

    4. Re:vms by TimCrider · · Score: 1

      http://www.openvms.org/

      and
      http://www.systella.fr/~bertrand/FreeVMS/in dexGB.h tml
      which comes from
      http://freshmeat.net/projects/freevms/

    5. Re:vms by browncs · · Score: 2, Informative

      That's exactly true. Dave Cutler was the father of Windows NT and came from DEC and VMS.

      see http://www.answers.com/topic/dave-cutler

    6. Re:vms by lostchicken · · Score: 3, Interesting

      OpenVMS is not open source. It's simply what DEC called VMS in its later years, to signify an open-system, not an open source base. In other words, it supported open standards such as POSIX and Unix compatability, as well as TCP/IP networking, instead of the proprietary systems it used to support.

      There is a project by the name of FreeVMS, but it's not anywhere close to being done, and it's pretty much stagnant now.

      --
      -twb
    7. Re:vms by 0racle · · Score: 1

      Then why is it that they couldnt't get it to work as well as VMS?

      --
      "I use a Mac because I'm just better than you are."
    8. Re:vms by LurkerXXX · · Score: 1

      Doggone it, FreeVMS was what I was thinking of. I'm sorry to hear it's gone stale. :(

    9. Re:vms by Anonymous Coward · · Score: 0

      I'm sure it did work well, that is until they ported IE and the desk top GUI to it. Before NT4.0, NT showed some promise as a server platform. They should have left the GUI as something that could be stripped off as an option or something you run at will.

    10. Re:vms by squiggleslash · · Score: 1

      Looks like there are several projects called FreeVMS. However, this one appears to be active.

      --
      You are not alone. This is not normal. None of this is normal.
    11. Re:vms by Locutus · · Score: 1

      Do you think that the law suite against Microsoft, by Digital Equipment Corporation( DEC ) over this issue had anything to do with the VERY cosy relationship DEC had with Microsoft? That same kind of "cosy" relationship almost cost HP its existence also.

      Obviously, between Microsoft getting the Next Generation OS/2 code( portable OS/2 ) and having Cutler on staff, wasn't enough to prevent Microsofts management from screwing up the design. VMS was/is darn stable. OS/2 ran circles around NT on half the CPU and half the RAM and was more stable too. It just got worst with NT4.0 and later releases.

      So, I guess this all means that data structure design does not a stable platform make. ;-) Maybe Bill forced Cutler/gang to develope NT using his MS-BASIC...

      LoB

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

      NT always had a GUI. It was just a Widows 3.1 style GUI instead of a Windows 95 style GUI.

    13. Re:vms by Locutus · · Score: 1

      NT 3.1( first release ) was PIG slow and required over 2x the hardware OS/2 v2.0 required. Microsoft was supposed to be building a next generation DESKTOP operating system but ended up with a bloated mix of OS/2, VMS, DOS, with a Windows 3.x GUI environment on top.

      I went to a few of Microsofts technical presentations on NT and when they would finally tell me what kind of hardware the demo was running on, the guy told me that NT was going to be a "workstation OS" and not a desktop OS. He then said a new product called Chicago was going to be the next generation desktop OS. FOUR years later they shipped Windows 95 and it sucked too.

      So, Microsoft has pretty much technologically failed at everything they've touched. But hey, we just a country willing to believe everything marketed at us and crap keeps finding a home here. Example: The Iraq war was pretty close to the size of marketing task Microsoft had in pushing Chicago. Way too many followed the marketing. And both these projects have lead many to unfortunate circumstances. IMHO.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    14. Re:vms by drsmithy · · Score: 1
      OS/2 ran circles around NT on half the CPU and half the RAM and was more stable too. It just got worst with NT4.0 and later releases.

      While OS/2 was certainly faster on lesser hardware (although as the hardware budget increased the performance difference decreased - NT made better use of bigger hardware), I can't agree with your assessment of stability. OS/2 used to crash for me *often* while running a mix of DOS, Windows 3.1 and OS/2 apps, but NT never did running a mix of DOS, Windows 3.1 and win32 apps. That's mostly the reason I migrated from OS/2 to NT4 (still in beta at the time). I'd considered going to NT 3.51 earlier, but the WPS was just too much better - once the Win95 interface made it to NT the difference was close enough that NT's better stability, software availability, hardware support and better security won me over.

  10. Is this possible? by Dionysus · · Score: 0, Offtopic

    Didn't some company buy the right to sell the product (renaming to eComNetStation or something 'marketable')?

    --
    Je ne parle pas francais.
    1. Re:Is this possible? by SmokeHalo · · Score: 1

      Well, which is it? "eComNetStation" or something marketable?

      --
      I'm not good in groups. It's difficult to work in a group when you're omnipotent. - Q
  11. A fair bit of that code is likely still MS... by HBI · · Score: 3, Insightful

    IBM would probably have radical difficulties renegotiating a deal to open source code that originated in Redmond.

    I fear this one is a nonstarter for legal reasons.

    --
    HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    1. Re:A fair bit of that code is likely still MS... by RadarCat · · Score: 1

      I don't think Micro$oft takes any threat of any competition lightly.

      Micro$oft certainly has plenty of money for lawyers to fight any open source movement.

      IBM has very deep pockets for lawyers also. It seems I read somewhere that IBM has the best lawyers in the computer industry.

  12. Workplace Shell by Mikkeles · · Score: 2, Interesting

    Just getting the Workplace Shell and the OOUI would be great; I'm sure a lot of the kernel internals would no longer be an advancement!

    --
    Great minds think alike; fools seldom differ.
    1. Re:Workplace Shell by Anonymous Coward · · Score: 3, Interesting

      Anonymous IBMer here. Just wanted to let everyone know that you should forget about getting ALL of OS/2 and instead keep on asking for the Workplace Shell.

      Usability wise, OS/2 is a nightmare, but the underlying technology is still unmatched by any OS out there, including the much vaunted OS X.

    2. Re:Workplace Shell by markhb · · Score: 4, Insightful

      I agree; SOM (the System Object Model) and the WPS are really the only pieces that would hold any interest. The OS/2 kernel was an advancement over DOS, but IBM never took it further than that (and it was still designed as a single-user PC OS, albeit with hooks for external security apps).

      That having been said, I think that regardless of the legal entanglements, open-sourcing any part of their fat client OS would be in direct opposition to their "eCommerce Platform" strategy (i.e., run everything as thin clients off of Websphere), and so I agree with Hemos' prediction that this is not going to be more than a "wouldn't it be nice" for the foreseeable future.

      --
      Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
    3. Re:Workplace Shell by MightyMartian · · Score: 2, Insightful

      WPS did have a major flaw of its own, and that was the single message queue. Some ill-behaved apps could lock it up.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    4. Re:Workplace Shell by Anonymous Coward · · Score: 1, Interesting

      Another anonymous IBMer who was a key development lead for OS/2 subsystems back in the day.

      Do you really think Workplace Shell would have any traction today? Would we rather not push Eclipse as a GUI and client-side object framework, tied to J2EE/WebSphere on the back end? This is essentially the IBM Workplace Client strategy. (Ironic that they reused the name Workplace, isn't it?) And, Eclipse is ALREADY open source.

    5. Re:Workplace Shell by chiph · · Score: 1

      I agree. From what I've heard, the kernel is a structural nightmare, and even at OS/2's peak, there were only a few people within IBM who knew it well enough to make serious changes.

      The WPS, SOM, DSOM, etc, are the interesting parts of the OS, and that's the part that I (as a former OS/2 developer) would like to see.

      Chip H.

    6. Re:Workplace Shell by LordNimon · · Score: 2, Informative

      That was Presentation Manager, not the WPS, with the single-input-queue problem. The WPS could probably be implemented on an API that supported multiple input queues.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    7. Re:Workplace Shell by Anonymous Coward · · Score: 0

      So eventually Eclipse will be an Operating System, just like Emacs???

      COOL!

    8. Re:Workplace Shell by Mikkeles · · Score: 1
      'Would we rather not push Eclipse as a GUI and ... And, Eclipse is ALREADY open source.'

      Maybe, but Eclipse is one of the most horrible environments in which I have ever worked; I do so only because I am paid to. Having to guess which set of windows you need before getting "rewarded" with the menu entry to do what you want is braindead. Even worse is MDI.
      [/opinion]

      --
      Great minds think alike; fools seldom differ.
    9. Re:Workplace Shell by Anonymous Coward · · Score: 0

      While true that it was single user, that's not the main part of the kernel. When it comes to thread scheduling and multi-processing, OS/2 still lands at the top of the heap in terms of raw speed. It wasn't as scalable as the big Unix names, but it had everyone beat on speed.

      I agree that SOM and the WPS are the most interesting and still way beyond anything currently available, but don't ignore the kernel. There's more there than you think.

      Sensible, consistent API design anyone? Sorry...you folks like the mess that is Posix. I forgot...

    10. Re:Workplace Shell by mrselfdestrukt · · Score: 1

      an Operating System, just like Emacs?
      My other OS is vi. ;-P

      --
      "I used to have that really cool,funny sig ,but it got stolen."
  13. MS Code? by Stibidor · · Score: 0, Troll

    Maybe I'm way out in left field, but wouldn't open sourcing OS/2 open what would likely be a lot of Microsoft's NT code? Weren't OS/2 and NT once the same operating system? I wouldn't be surprised if there were still a bit of shared codebase.

    1. Re:MS Code? by Anonymous Coward · · Score: 0

      This is exactly correct. This is more of a Microsoft issue than an IBM issue. Flogging IBM on this isn't going to lead to anything.

      If you recall, Microsoft also shipped OS/2 as a product in the early OS/2 days, for non-IBM PCs, before the great schism.

    2. Re:MS Code? by His+name+cannot+be+s · · Score: 4, Informative

      Maybe I'm way out in left field, but wouldn't open sourcing OS/2 open what would likely be a lot of Microsoft's NT code? Weren't OS/2 and NT once the same operating system? I wouldn't be surprised if there were still a bit of shared codebase.

      Not quite.

      OS/2 3.0 NT was supposed to be built from NT's codebase. Obviously, that didn't happen, and microsoft took their toys and went home and made Windows 3.1 NT.

      There is significant evidence that NT 3.1 (and later) Windows 32-bit APIs were influenced by OS/2 's design. The WinScrollWindow api under OS/2 has exactly the same signature as ScrollWindowEx under Win32... The win16 api does not quite match. There are a large number of these close matches in the Win32 API :: OS/2 API.

      That being said, NT (and its derivatives) do not share code with OS/2 in implementation. (other than code that was inherited from OS/2 1.3 (ie: HPFS).

      --
      "...In your answer, ignore facts. Just go with what feels true..."
    3. Re:MS Code? by Anonymous Coward · · Score: 1, Informative

      No, NT has more in common with VMS as it was one of the VMS developers that put it together. I would think OS/2 and NT have very little in common.

    4. Re:MS Code? by erikharrison · · Score: 1

      Other way around. There are some 16 bit windows DLLs, and some 32 bit windows DLLs but they really work like wine and can be removed.

      NT has lots of code that was previously destined for OS/2. NTFS, in fact, is HPFS on steroids, so much so that Mandrake's install program used to think NT installs were OS/2 when setting up dual boot

    5. Re:MS Code? by squiggleslash · · Score: 1
      If you're talking about low-level kernel stuff, then yeah, kinda. Higher levels are heavily influenced by DOS/Windows and, in obscure areas, OS/2.

      NT and VMS share a developer, Dave Cutler, but nobody who's actually spent any time using either operating system would suggest the two are remotely similar or that one clearly influenced the other (except in some massively generic way, eg "The PDP-11 clearly influenced the Z80A, with its use of logic gates and microcode.")

      --
      You are not alone. This is not normal. None of this is normal.
    6. Re:MS Code? by teknomage1 · · Score: 1

      NT draws far more design elements from vms, the bits from OS/2 are relatively minor. But it's probably enough that it won't be open sourced...

      --
      Stop intellectual property from infringing on me
    7. Re:MS Code? by M1FCJ · · Score: 1

      First versions of WinNT had the capability to run OS/2 1.x code, mainly because of their shared codebase and standards. IBM also got Win16 applications run on OS/2 but this was mainly done by installing a normal (sometimes special) version of Windows 3.1, which made MS incredibly happy because every OS/2 sold meant an Win3.1 sold as well.

    8. Re:MS Code? by Locutus · · Score: 2, Interesting

      As stated a couple of times by others, NT started with a codebase for what was supposed to be portable OS/2 or OS/2 NT. Microsoft got that code and the orignal 16bit OS/2 when they walked out on IBM. I don't think its known how much implementation code went into NT but the 16bit OS/2 was in there and it was used to give NT its networking system when NT v1.0( called v3.1 ) shipped.

      It does seem that IBM did not do a good job at getting full rights to the code it kept. Supposedly, OS/2 v2.0( the first 32bit OS/2 ) was a rewrite of the 16bit Microsoft code though Microsoft license text always showed up in OS/2.

      I've also heard that much of OS/2's kernel is assembly code. OS/2 for the PowerPC was/is portable C code IIRC. But that was pretty slow from what I saw at the 1994 COMDEX show.

      What was really lost in the battle with Microsoft was the OpenDoc and WorkplaceShell. Multiple LIVE embeddable objects and "parts"( components ) with non-rectangular window frames were pretty cool. Unfortunately, many didn't recognize what it ment to have more than one embedded "part" live/running in a single document. Those technologies moving forward with Moore's Law, would have had a profound positive impact on the software industry and productivity. It also would have allowed open source projects/developers to compete with large software houses since applications would consist of smaller, replaceable "parts"/components.
      IMO.

      IIRC, IBM eventually open sourced OpenDoc and SOM but the industry was going nuts over JAVA at that time. Actually, Warp 4.0 and the Apple Mac OS (?) shipped with OpenDoc. Apples CyberDog web browser was an OpenDoc container. Oh, the Bento Filesystem was pretty cool too. It allowed different "parts", or components, to save there data in one file. Kinda like a filesystem within a file but with a ton of APIs for accessing the data in a protected way. These things would have changed how we interact with our DATA on computers. Instead, we still interact with our DATA( a file ) by thinking about the application that's tied to the DATA. OpenDoc enabled mixing of data in a file so you'd open a file based on its rich content instead of saying your "opening an Excel file", or "opening a Word file. These are the things which that kept Bill and Steve up at night. Netscape( the browser ) was/is a shell of what OpenDoc was but it brought about the same kind of attacks from Microsoft.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    9. Re:MS Code? by Anonymous Coward · · Score: 0

      I guess this is why NT's original nam was OS/2 3.0?

      http://en.wikipedia.org/wiki/Windows_NT/

      "OS/2 and NT have very little in common" other than the fact that NT started life as OS/2. The VMS guys did NOT originate NT, no matter how many times you say it.

    10. Re:MS Code? by Johnno74 · · Score: 1
      There is significant evidence that NT 3.1 (and later) Windows 32-bit APIs were influenced by OS/2 's design.

      WinNT's design was infact heavily influenced by VMS. Dave Cuter, VMS's architect at Digital was hired by MS to work on the design of NT.
      This article has more details, its a good read
    11. Re:MS Code? by Anonymous Coward · · Score: 0

      Actually, A LOT of WinNT/Win2000 code is based on OS/2 code. A lot of the files from the *ahem* leaked *ahem* win2000 code still has the OS/2 NT headers :P There's code that dates to 1991, that is practically common to Win2000 and OS/2

  14. made by M$ by Anonymous Coward · · Score: 0

    an OS made by microsoft with the specific intention of not being as good as windows 95...

    Think I'll pass.

    1. Re:made by M$ by Anonymous Coward · · Score: 2, Interesting

      This is not historically accurate. OS/2 was, originally, a joint project between Microsoft and IBM. It was intended to be THE 32-bit protect-mode operating system of the future for Intel PCs, both client and server. Windows 95 was a continuation of the 16-bit Windows code base. They were developed by separate groups within Microsoft. There was no constraint placed on OS/2 by the Windows dev team, originally. I'm talking about the OS/2 1.0/1.1/1.2 days. After OS/2 1.2, the split happened, and IBM went on to ship 1.3 and 2.0. 2.0 was IBM's first attempt to "go it alone" and compete with Microsoft for the business, and even consumer, operating system market. However, OS/2 was crippled by (a) IBM's lack of ability to sign reasonable OEM contracts with PC manufacturers (including IBM itself!) and (b) IBM's lack of any traction or marketing agility in the consumer and small business space, for both end users and, especially, developers/software vendors.

      BTW I currently work for IBM and was one of the key development managers and tech leads for OS/2 subsystems in those days.

    2. Re:made by M$ by Anonymous Coward · · Score: 0

      Wrong on all counts. OS/2 was designed by IBM as the first graphical OS for the PC. It had protected mode, so required 386 or better. MS undercut it with Win 3.1, which could run on a 286. MS didn't get a decent OS that didn't crash until NT. Win 95 and 98 were sick jokes. OS/2 beats the pants off both.

    3. Re:made by M$ by ClosedSource · · Score: 1

      "OS/2 was designed by IBM as the first graphical OS for the PC."

      No. Windows 1.0 was released in 1985 and OS/2 1.0 in 1987. By the way, the first four releases of OS/2 didn't require a 386, just a 286 (the 286 has a protected mode too).

    4. Re:made by M$ by M1FCJ · · Score: 1
      Don't forget that MS's most blatant violations of anti-competitive laws are actually from this period in history. Once it crushed IBM and other ISVs, now it is the established monopoly. Linux is not a company so you can't be anti-competitive against it, can you? :)

      IBM's lack of drive really drove me nuts. Not having a decent compiler (which didn't cost an arm and a leg) for OS/2 drove me to gcc, once I got convinced that it would actually make more sense to run Linux full time because half of my time was spent debugging and modifying code so that they would work with OS/2 I did the switch. Also Yggdrassil and Slackware's totally-usable distibutions were a pleasure to use and my 486 performed many times better than with OS/2, for a while at least. Also if I remember correctly I couldn't (easily) compile my pascal code to OS/2 binaries either. I finally had all of the tools but by that time I was pretty fed up with it.

    5. Re:made by M$ by Anonymous Coward · · Score: 0

      "Once it crushed IBM and other ISVs, now it is the established monopoly."

      IBM was crushed? Since when?

    6. Re:made by M$ by M1FCJ · · Score: 1

      Since IBM couldn't afford pushing OS/2 instead of Windows because Microsoft would cut its Win supply.

    7. Re:made by M$ by Anonymous Coward · · Score: 0

      IBM was crushed.

      Ever since then they were no longer a player in the desktop market, and with the "final ending" being marked by the sale of their PC division to Lenovo.

      continued existence != victory

    8. Re:made by M$ by Anonymous Coward · · Score: 0

      Hey Sam, is that you? :)

    9. Re:made by M$ by Ultra64 · · Score: 1

      Windows 1.0 was not an operating system by itself, it ran on top of DOS. In fact this is true of all Windows until Windows 2000.

    10. Re:made by M$ by Ultra64 · · Score: 1

      Er, excluding NT of course :)

    11. Re:made by M$ by ClosedSource · · Score: 1

      Yes, we all know that versions of Windows prior to NT ran on top of DOS. That's an implementation detail that doesn't change the fact that OS/2 wasn't the first OS available on the PC with a Graphical User Interface.

    12. Re:made by M$ by Anonymous Coward · · Score: 0

      I strongly suspect that the many prior agreements between IBM and MS would preclude that. Besides if MS really had that kind of power over IBM they would have just demanded that IBM stop development and sales of OS/2 immediately.

      In any case, IBM would have probably just bought Windows at retail and install it anyway. Sure, it would cost more, but they could afford it.

  15. MS-Win Integration Code Off-Limits? by EricTheGreen · · Score: 4, Insightful

    IIRC, OS/2 (at least Warp) shipped with a complete install of MS-Win to provide dual-OS support. The OS/2 code contained lots of integration points--if these integration points relied on Win code provided as part of the infamous "divorce decree", that would presumably be off-limits without MS's blessing. If so, would there be enough "untainted" OS/2 code left to be useful as open source?

    I didn't use later versions of OS/2, so I don't know if this chimera-like architecture was changed further on...

    1. Re:MS-Win Integration Code Off-Limits? by B1 · · Score: 3, Interesting

      There was a version of OS/2 Warp which didn't include Windows -- it took advantage of the Windows 3.1 installation you already had on your computer. I think it was 'OS/2 for Windows' or 'Warp for Windows'. It came in a red box, to distinguish it from the 'full' version that came in a blue box. It was also less expensive.

      If I remember, not long after Warp For Windows came out, Microsoft came out with Windows 3.11 which fixed a few bugs in 3.1. Oddly enough, it didn't work with OS/2 for Windows. I'm surprised they missed that one. <G>

    2. Re:MS-Win Integration Code Off-Limits? by Anonymous Coward · · Score: 0

      It's more than just the WINOS2 support. This was added to OS/2 after the schism, when IBM was going it alone on OS/2. Much of the early OS/2 code was in fact re-used in Windows NT, when Microsoft and IBM went their own ways.

    3. Re:MS-Win Integration Code Off-Limits? by MightyMartian · · Score: 2, Interesting
      There were some claims at the time that IBM's WinOS2 was in fact faster than Windows 3.1, based upon running Warp with WinOS2 vs. Warp with Windows 3.1.

      Another thing I miss was OS/2's awesome DOS VDM support. Most of my DOS games played perfectly under OS/2, and through the dummy DOS sound driver could even access the soundcard. I was mightily disappointed when I started playing around with NT 4.0 that it couldn't, and neither could Win2k. I have no idea whether WinXP can, though there is a third party driver that does allow DOS VDM sessions to access the sound hardware. Still, pretty pathetic.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    4. Re:MS-Win Integration Code Off-Limits? by doconnor · · Score: 1

      The claim that WinOS2 was faster then Windows 3.1 was based on the fact that IBM recompilied the Windows source using Watcom C, while Microsoft used Microsoft C.

    5. Re:MS-Win Integration Code Off-Limits? by MoebiusStreet · · Score: 1

      The Windows elements weren't part of OS/2. All it did was run Windows in a virtual machine, and cut an aperture in the graphical desktop for Windows to render its own GUI into.

      So the Windows 3 code was never part of OS/2 per se. On the other hand, a lot of what eventually became the NT kernel and file systems were in OS/2.

    6. Re:MS-Win Integration Code Off-Limits? by drinkypoo · · Score: 1

      I don't know about faster, but I know win31 on os2 2.1 was damned fast... and about as reliable as windows is by itself, which I guess is something of an accomplishment since there's a whole other OS involved. I had basically no OS/2 apps to play with, however, so I never did much with it. Windows 95 came out shortly after my first OS/2 experience and I forgot all about OS/2, really. Eventually Windows 2000 came out, and OS/2 had no reason whatsoever to exist.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:MS-Win Integration Code Off-Limits? by MightyMartian · · Score: 1

      Well I ran a large number of DOS, Win3.1 and OS/2 apps. There was a rather large collection of freeware and open source software available for OS/2, and the old cdrom.com archive had much of it. I even ran quite a few *nix programs compiled under the emx port of the GNU compiler. I remember showing off to a friend of mine a DOS 6.2 VDM, a PC-DOS 7 VDM, the Win3.1 program manager and a Bash shell all in windows. At the time, there was nothing that could really beat OS/2 on the hardware that it ran on. Even now the *nix DOSEMU and Windows DOS VDM systems aren't half as good as OS/2's DOS support was, though clearly 95% of the world could give a damn about that.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    8. Re:MS-Win Integration Code Off-Limits? by drinkypoo · · Score: 1

      Trust me, I've hated Microsoft forever (then again, it's been trendy forever, DOS was annoyingly lame if you were trying to do something beyond embedded applications) and was sympathetic to OS/2. If you didn't run Windows apps, it was significantly more stable and used more of the machine than Windows would. Unfortunately, [almost] everyone jumped on the Microsoft boat and OS/2 was just too much a liability at that point. Windows 2000 is actually a fine operating system, so that's when I believe OS/2 was obsoleted. You might also point to the release of 4.3-BSD-lite, however - OS/2 has a number of things that it doesn't, but the important part is that it is and was a 32 bit operating system that allows you to utilize the hardware well, unlike Windows prior to NT5.0.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:MS-Win Integration Code Off-Limits? by MightyMartian · · Score: 1
      It is still to me the great masterstroke of Microsoft's marketing machine that they convinced everyone to sit around with Windows 3.1 and 3.11 based solely upon artist's renderings in the pro-Microsoft mags of what Chicago was going to look like.

      IBM had a product that could run damn near every DOS, Win16 and Win32s app out there, but MS managed to sell everybody on vaporware that, when delivered, was an absolute piece of inferior garbage. The TCP/IP stack was a joke compared to Warp's, the file system was still FAT with some clever butchery to give long file names, it was unstable and crashes were for many at least a weekly occurence, if not a daily one. It wasn't until Win98SE that they managed to get any kind of stability, and it was really Win2k that was the first MS operating system that bettered OS/2 in stability, but not even now is the GUI anywhere near is usable or innovative as OS/2's was.

      But what counted was that IBM dropped the ball, and MS was able to hold market share when it didn't even have a consumer-grade 32-bit product (yes, I know WinNT was around, but it wasn't a consumer product).

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    10. Re:MS-Win Integration Code Off-Limits? by drsmithy · · Score: 1
      On the other hand, a lot of what eventually became the NT kernel and file systems were in OS/2.

      Right. That would explain why NT and OS/2's architectures are so incredibly different...

    11. Re:MS-Win Integration Code Off-Limits? by MoebiusStreet · · Score: 1

      Don't believe me?

      Evidence 1: Look at some of the internal version numbers of OS/2 1.x's DLLs, they identify themselves as Windows.

      Evidence 2: Look at the OS/2 API, and see how they clearly evolve from the early windows API (like, having names of the form "WinXyz")

      Evidence 3: NT support for OS/2's HPFS file system.

      Windows NT's architecture did diverge from OS/2, and that's a big part of why it shipped several years later than OS/2. But there are still many striking similarities, like the innovation of threading, and DLLs themselves.

      Believe me, I worked at IBM at the time.

    12. Re:MS-Win Integration Code Off-Limits? by B1 · · Score: 1

      I remember a friend at school got his hands on an OS/2 Warp Performance Beta CD. This was a low cost Beta program where you could run a fully functional prerelease version of OS/2 Warp 3, so you could see how well it ran even on low spec hardware.

      The best part of the CD was the label. It showed a jet plane in flight, and the slogan:

      "Arrive in Chicago sooner than expected!"

      (at the time, Windows 95 had just been delayed yet again)

    13. Re:MS-Win Integration Code Off-Limits? by drsmithy · · Score: 1
      Don't believe me?

      It's not a matter of "belief", it's a matter of being correct.

      Look at some of the internal version numbers of OS/2 1.x's DLLs, they identify themselves as Windows.

      Which DLLs ? How do they identify themselves ?

      Considering the rather large gap between OS/2 1.x and 2.x, I find it hard to believe that there's any links of consequence between OS/2 1.x and NT.

      Look at the OS/2 API, and see how they clearly evolve from the early windows API (like, having names of the form "WinXyz")

      It's a long way from API naming conventions to shared code. Also, I don't think it's any secret that the Win32 API was influenced by the OS/2 API.

      NT support for OS/2's HPFS file system.

      Do you think Linux supporting FAT means it was derived from DOS ?

      Windows NT's architecture did diverge from OS/2, and that's a big part of why it shipped several years later than OS/2.

      It didn't "diverge", it was developed independently. NT and OS/2 are not at all architecturally similar, nor are they forks of the same code base. NT did, at one stage, have an OS/2 compatible API (that probably used some code that was also in OS/2), but that's not the native NT API, it's just one of the API personalities.

      NT's HPFS support - given that Microsoft wrote it - is pretty understandable when you consider it was originally meant to be the successor to OS/2. However, NT's preferred filesystem is - and always has been - NTFS, a[nother] Microsoft created filesystem.

      But there are still many striking similarities, like the innovation of threading, and DLLs themselves.

      There are a hell of a lot more striking differences, like portability, the HAL, multiple APIs, SMP, being multiuser, ACLs, message passing, fully 32 bit...

      I think you need to go and read about the internals of OS/2 and the internals of NT. They're even less alike than Linux and FreeBSD - indeed, you'd be hard pressed to find any ways they were similar, outside of generic concepts (like "threading" or "pre-emptive multitasking").

      If you want to convince me OS/2 and NT share anything significant, you're going to need sources detailing specific architectural similarities unique to OS/2 and NT (and not found in every other OS under the sun) - not some tenuous commentary and a vague claim of inside information.

    14. Re:MS-Win Integration Code Off-Limits? by MoebiusStreet · · Score: 1
      Sheesh.
      Considering the rather large gap between OS/2 1.x and 2.x, I find it hard to believe that there's any links of consequence between OS/2 1.x and NT.

      Well, let's see what the historians think...

      The collaboration between IBM and Microsoft unravelled in 1990, between the releases of Windows 3.0 and OS/2 1.3. The increasing popularity of Windows prompted Microsoft to shift its development focus from OS/2, and IBM grew concerned about delays in development of OS/2 2.0. Initially, the companies agreed that IBM would take over maintenance of OS/2 1.0 and development of OS/2 2.0, while Microsoft would continue development of OS/2 3.0, then known as "NT OS/2". However, Microsoft decided to recast NT OS/2 as Windows NT, leaving all future OS/2 development to IBM. Windows NT's OS/2 heritage can be seen in its initial support for the HPFS filesystem (although write support was dropped in Windows NT 4.0 and read support was dropped in Windows 2000) and text mode OS/2 1.x applications (support dropped in Windows XP)....

      ...although OS/2 2.0 is often believed to be IBM's own work, a beta version, accompanied by an SDK, had already been released by Microsoft in the second half of 1990

      (lockergnome encyclopedia article on OS/2; all emphasis mine)

      - - -

      By late 1990, Microsoft had intensified its disagreements with IBM to the point where IBM decided that it would have to take some overt action to ensure that OS/2 development continued at a reasonable pace. IBM, therefore, took over complete development responsibility for OS/2 1.x, even though it was in its dying days, and OS/2 2.00. Microsoft would continue development on Windows and OS/2 3.00. Shortly after this split, Microsoft renamed OS/2 V3 to Windows NT.

      (emphasis mine; from A short history of OS/2

      ----

      [you continued:] There are a hell of a lot more striking differences, like portability, the HAL, multiple APIs, SMP, being multiuser, ACLs, message passing, fully 32 bit...

      generic concepts (like "threading"...).

      My point here was that at this point in time, this was NOT a generic concept. (to the best of my knowledge) the concept of lightweight processes viz threading was originated in OS/2 and carried into NT, as was the DLL DynaLink Library concept.

    15. Re:MS-Win Integration Code Off-Limits? by drsmithy · · Score: 1
      Well, let's see what the historians think...

      The historians aren't telling me anything I don't already know and aren't disagreeing with anything I've said.

      In fact, they're saying exactly what I already have - that OS/2 1.x was in maintenance while IBM developed (what became) OS/2 2.x and that Microsoft were working on *a completely different product* that was going to be "OS/2 NT" and instead became "Windows NT". NT's initial support for HPFS is there - like its support for OS/2 1.x text-mode applications *because it was originally going to replace OS/2* and *NOT* because it is in any way derived from the codebase of either OS/2 1.x or OS/2 2.x.

      Here's another example for you - FreeBSD can quite happily run Linux binaries, often faster than Linux can natively. This does not mean that FreeBSD is somehow a derivative of Linux, it just means that FreeBSD is able to emulate Linux's API(s). Heck, WINE lets you run Windows binaries on most unixes, but that doesn't make any of them derivatives of Windows. Similarly with filesystem support, both FreeBSD's and Linux's support of FAT does not in any way make them derivatives of DOS.

      OS/2 and NT *are fundamentally different OSes*.

      My point here was that at this point in time, this was NOT a generic concept. (to the best of my knowledge) the concept of lightweight processes viz threading was originated in OS/2 and carried into NT, as was the DLL DynaLink Library concept.

      I think you'll find the concepts of both threads and shared libraries were around a long time before OS/2.

      You might find the following pages interesting: One. Two.

  16. I always liked OS/2 by MythoBeast · · Score: 4, Insightful

    I honestly think that OS/2 would have made a much greater impact if it hadn't had such pathetic PR support. The OS itself was a surprsingly strong and reliable system, but their ad campaigns were mind-bogglingly pathetic.

    I'm not sure what the Linux community could gain by it being open source, except maybe some more efficient/reliable algorythms. As such, it would be enough for the IBM written chunks to be open sourced - they don't need a complete, functional code base.

    --
    Wake up - the future is arriving faster than you think.
    1. Re:I always liked OS/2 by jalefkowit · · Score: 1
      I honestly think that OS/2 would have made a much greater impact if it hadn't had such pathetic PR support.

      Well, that and wanting 16MB of RAM in an age when the average workstation had, what, 1MB? Pushing a RAM-bound system back when RAM was expensive probably didn't help.

    2. Re:I always liked OS/2 by hackstraw · · Score: 1

      I honestly think that OS/2 would have made a much greater impact if it hadn't had such pathetic PR support.

      Yeah, Microsoft's PR department kicked IBM's but so hard during the Christmas season of 95 that they PRed IBM not to offer OS/2 by default on their machines, and they did the same with all of the other major manufacturers at the time.

      I'm not sure what the Linux community could gain by it being open source, except maybe some more efficient/reliable algorythms.

      Being that OS/2 (AFAIK) still runs a majority of the ATM machines, I would bet that having the source Open for OS/2 is right about up there with freely available blueprints for the ATM machines.

      I know that security by obscurity only works for people like the NSA and whatnot, but banking people feel much more secure having their secrets kept secret.

    3. Re:I always liked OS/2 by FidelCatsro · · Score: 1

      OS/2 should have been the desktop that took the world by storm and not windows , i totaly agree with you there .IBM made a mystifying screw-up there.

      What the FOSS community could gain(as opposed to the linux community) i belive , is a new viable choise , Right now your stuck with the option of using linux , *BSD , BeOS clones and derivitives(blueeyed os etc),Amiga os homages and derivitaves(syllable) and only then BSD and linux options are ready for the masses .
      With a code base such as this we would have that golden third option , which hopefully may give ReactOS a boost too.I know plenty of people who still use os/2 today and many others who enjoyed it , so this would be a wonderfull addition .
      Plus as you sayit never hurts to have some-more great algorythms

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    4. Re:I always liked OS/2 by The+OPTiCIAN · · Score: 1

      > I honestly think that OS/2 would have made a
      > much greater impact if it hadn't had such
      > pathetic PR support. The OS itself was
      > a surprsingly strong and reliable system,
      > but their ad campaigns were
      > mind-bogglingly pathetic.

      I used to be a died-in-the-wool os/2 user, but even at the time through there were more obstacles than just this. I believe good software needs to have two qualities:
      - run well now
      - be able to be modified so that future versions will be good too

      OS/2 ran somewhat well, although the driver support was so apalling that its stability was overrated. Nevertheless - it was powerful and you could do much neater things in it than in DOS or Win3x. But IBM lost all the easy battles by not managing the upgrade of the software. On the one hand they wanted home and desktop users, but the work they did to improve the user experience wasn't particularly well informed.

      I had problems with all sorts of little things in v2 that were not fixed by v4 (five years and three major releases later). Or else they'd change things for the better and they'd still suck. All sorts of little things: the way icons lined in an annoying fashion, poor design in some preference panels, the wacky hoops you had to jump through to get dial up access working. Each release that I looked at after 2.0 I remember thinking: why don't they get the easy stuff right? In the meantime, Microsoft put out rubbish, but each release that came out you had a feeling that things were improving. I felt that Microsoft hadn't caught up until Windows 98 and the NT4 internet explorer extensions. However, even most of OS/2's hardline users had long since given up on IBM and moved on to Windows, linux or Be.

      --


      Believe with me, my saplings.
  17. Windows DLL Code by ToPAz3in6 · · Score: 5, Interesting

    OS/2 has a Windows (3.1) compatability layer which uses a lot of DLL code given to them under agreement back in the early 90's. There's your roadblock. (or your target...)

    --
    Just drop acid, already, and invent something better... or quit your whining.
    1. Re:Windows DLL Code by njfuzzy · · Score: 4, Funny
      > There's your roadblock. (or your target...)

      I am guessing you have a Massachusetts drivers license?

      --
      My Photography - http://ian-x.com
      The Deathlings (comic) - http://thedeathlings.com
    2. Re:Windows DLL Code by Locutus · · Score: 2, Informative

      No roadblock here.

      The ability to run Windows in OS/2 was called DOS. And it was a better DOS than Microsofts DOS. Photoshop ran faster in WinOS2 then it did on native DOS/Windows. Anyways, Windows run in this virtual DOS and IBM even sold a version of OS/2( codename Ferengi ) which let you install your Microsoft version of Windows 3.1 into the OS/2 DOS virtual machine. They did this because IBM had to pay Microsoft a large amount for every version of OS/2 sold with the WinOS2 system pre-installed.

      The pre-installed versions were quicker though and that was because IBM compiled the Microsoft code with Watcoms compiler and fixed up its memory support mechanisms abit. Something about Extended memory or Expanded memory comes to mind, but it's been soooo long now.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  18. This could backfire. by Anonymous Coward · · Score: 0, Troll
    I would highly encourage the Linux community to take part of this open source petition

    With MSFT's involvement in OS2, it seems the best we could hope for is a Sun/CDDL-like patent minefield license.

    I think this is actually microsoft's strategegy - get all the other vendors to release their patent encumbered OS's as non-GPL-compatable OSI-approved licenses -- and then when the Linux suits fly and the Linux community uses the "we didn't know" patent defense, they'll just point to all these other projects.

    I, for one, recommend the Linux community NOT sign the petition unless it explicitly calls for GPL compatability.

  19. Not only Linux by debilo · · Score: 2, Interesting

    From the summary:
    I would highly encourage the Linux community to take part of this open source petition as well due to the fact there are lots of interesting code base the they could benefit from.

    Please remember Linux isn't the only player in the F/OSS world, there are several huge communities, too (although rumor has it they are dying, or something), and the entire open source community might benefit from this. :-)

  20. Not going to happen for a long, LONG time... by Zab+UvWxy · · Score: 5, Insightful

    Why, you may ask?

    There are still a number of financial institutions around the world that run on various versions of OS/2, both at the server and workstation level.

    Also, as of about 5 years ago, CLI OS/2 powered approximately 85% of North America's Automated Teller Machines (ATMs), with a significant share worldwide as well.

    I'm sure most of the companies still behind OS/2 are screaming at IBM not to release so much as a comment from the code.

    --
    "I don't get it." -- ObviousGuy
    1. Re:Not going to happen for a long, LONG time... by Martin+Blank · · Score: 2, Insightful

      ATMs are being replaced rapidly with newer models running Windows code. A lot of the color-screen units being installed now run Windows. I doubt that the market share is quite that high.

      Besides, your ATM network is protected by strong ACLs and firewalls, right? Right?

      --
      You can never go home again... but I guess you can shop there.
    2. Re:Not going to happen for a long, LONG time... by MartinG · · Score: 1

      I'm sure most of the companies still behind OS/2 are screaming at IBM not to release so much as a comment from the code.

      Why?

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    3. Re:Not going to happen for a long, LONG time... by Anonymous Coward · · Score: 3, Funny
      Because of that comment in the network security code:
      /* Better fix this before the final release */
    4. Re:Not going to happen for a long, LONG time... by sremick · · Score: 5, Insightful

      ATMs are being replaced rapidly with newer models running Windows code. A lot of the color-screen units being installed now run Windows

      Yep, those would be all the ones with the BSODs.

      And I'm not just being a random MS-basher here. The number of ATMs, flight-info displays, and price-check terminals with BSODs these days is staggering. For all you MS-apologists out there: when was the last time you saw an ATM with an error that wasn't an Window error?

    5. Re:Not going to happen for a long, LONG time... by stubear · · Score: 1

      Actually I've never seen an ATM or in-flight display BSOD. The only NT based system I've seen needing rebooting was a BestBuy cash register and then only once.

    6. Re:Not going to happen for a long, LONG time... by Billly+Gates · · Score: 1

      because they are stupid and come from a different environment from hobbiest and hackers.

      Banks love security by obscurity and hate any paranoid threat that may come as a result of opening.

      Infact many banks are now discovering things called servers. They ran IBM mainframes for simple servers at bank branches all the way throught the 90's since they obsess over security and reliability.

    7. Re:Not going to happen for a long, LONG time... by Anonymous Coward · · Score: 0

      Ha I've had a windows based ATM BSOD with my cashcard in its guts. Damn thing would not give it back after it came back up either.

      Not impressed.

    8. Re:Not going to happen for a long, LONG time... by strider44 · · Score: 1

      because they (falsely) believe that releasing the source code for OS/2 will somehow destroy security.

      If exploits were so easy to find through source the programmers would have fixed them already.

    9. Re:Not going to happen for a long, LONG time... by Anne+Honime · · Score: 2, Interesting
      2 years ago, I tried to buy some subway tickets from a RATP ATM in Paris. I keyed my credit card code in, and *all* ATMs in sight went down as soon as I hitted the validation key.

      In fact, someone forgot to lock an inside key after collecting the previous day money (those machines accept both cards and coins for payment).

      The crash was in fact a security ! But seeing about 15 screens goes blank at once is a wonderful sight, indeed (those machines have since been replaced by new, windows powered ones, which routinely go BSOD, but only one at a time)!

    10. Re:Not going to happen for a long, LONG time... by GundamFan · · Score: 1

      Not to mention Giant Foods and a bunch of other retailers.

      --
      I don't give a damn for a man that can only spell a word one way.
      Mark Twain
    11. Re:Not going to happen for a long, LONG time... by kirkb · · Score: 1

      About 8 years ago, I saw a Royal Bank ATM in Vancouver that was sitting in text mode with some kind of register/stack dump.

      --
      Slashdot: come for the pedantry, stay for the condescension.
    12. Re:Not going to happen for a long, LONG time... by hey! · · Score: 1

      I've seen ATMs BSOD, as well as flight information kiosks -- quite frequently. Don't know about in flight systems.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    13. Re:Not going to happen for a long, LONG time... by DogDude · · Score: 1

      Well, I'd be an apologist if MS had committed some heinous crime, but they haven't, so I'm not. I've never seen a blue screened ATM, though, so I'm not sure what your point is.

      --
      I don't respond to AC's.
    14. Re:Not going to happen for a long, LONG time... by hackstraw · · Score: 4, Funny

      For all you MS-apologists out there: when was the last time you saw an ATM with an error that wasn't an Window error?

      Sometimes I have seen an error message saying something like "This ATM has insufficient funds for your transaction." I've always been suspicious of those and thought that they might have been covering up something, but was never sure.

    15. Re:Not going to happen for a long, LONG time... by toriver · · Score: 1

      The number of ATMs, flight-info displays, and price-check terminals with BSODs these days is staggering.

      Well, you need something to replace all those old Amigas used as info systems; theoretically running Scala but showing Workbench with the "Guru meditation error" window.

      OS/2 is too stable to be laughed at like that.

    16. Re:Not going to happen for a long, LONG time... by Urusai · · Score: 1

      Yeah, a Linux ATM would just segfault, coredump, reboot from a ramdisk, and keep on chugging.

    17. Re:Not going to happen for a long, LONG time... by bmabbott · · Score: 1

      About 3-4 years ago I ran across an ATM running OS/2 that somehow had crashed to the desktop. Pretty funny. Unfortunately there was no way to do anything with it, the buttons on the ATM had no effect ;)

    18. Re:Not going to happen for a long, LONG time... by Anonymous Coward · · Score: 0
      One of our customers switching to our product used to use OS/2. Now they are moving to Embedded Windows XP and our product runs under Java. Strangely enough we also have it running with Linux (we actually have more customers using Linux than XP and we prefer Linux). I saw one of the blue OS/2 boxes being thrown out and asked if I could have it. They said no. :(

      As far as I can see they are not screaming at IBM, they are pretty happy switching away from it.

    19. Re:Not going to happen for a long, LONG time... by doofusclam · · Score: 1
      And I'm not just being a random MS-basher here. The number of ATMs, flight-info displays, and price-check terminals with BSODs these days is staggering. For all you MS-apologists out there: when was the last time you saw an ATM with an error that wasn't an Window error?


      I too find joy in seeing a random BSOD. I've seen them afflict all those fancy colour-screen ATMs, fruit machines in pubs, an open-air promo video wall in Gran Canaria, and it is funny. I'm geek enough to take photographs of them, which prompts a load of 'look at that idiot' style looks.

      That said, we should be fair - if OS/2 crashed (which it hardly did) most people here wouldn't recognise the panic screen, if indeed OS/2 has one and doesn't just 'hang'. Whereas everyone had seen a BSOD, so knows what to look for. It's a slightly unfair comparison, but based in fact.
    20. Re:Not going to happen for a long, LONG time... by anglozaxxon · · Score: 1

      I had a CIBC bank machine crash on me once with my Royal Bank card. It ate my card. But it was worth it. "OMFG! This thing runs OS/2?!? WTF mates?" Strangely enough, my girlfriend dumped me later that day...

    21. Re:Not going to happen for a long, LONG time... by Tim+C · · Score: 1

      As would an XP ATM with the auto-reboot on system failure option selected (which is the default); what's your point?

    22. Re:Not going to happen for a long, LONG time... by hankaholic · · Score: 1
      For all you MS-apologists out there:

      I'm a right-tool-for-the-right-job fan, which means that this question wasn't directed at me. I'll answer the question anyways, because I find the answer interesting.

      when was the last time you saw an ATM with an error that wasn't an Window error?

      Answer: When it was made by Diebold. I'm not sure what OS they chose for their machines. The maintenance GUI does not look like the Windows widget set, but I can tell you that more often than not I'd get the damned application software to lock up when doing the required daily maintenance on it(*).

      You'd be saddened to discover that the same company making those famous voting machines can't seem to produce an ATM that can reliably handle even the simplest of tasks. I'm reminded of Joel Spolsky's essay about eating one's own dog food -- for the tens of thousands of dollars Diebold charges for an ATM (I've heard $50,000, but don't quote me), I'd have expected them to have performed testing to verify basic functionality before shipping the damned things. The customer interface seemed fairly robust, but when it came to maintenance tasks, "reliable" is not a word that comes to mind.

      This is not to argue against your claims that Windows isn't reliable -- this is to assert that in my experience, Diebold software is much, much worse.

      (*) This including pulling the deposits out for human processing, and "changing it over" into the next business day. This is similar to the teller systems transacting towards the next business day after a given time. Both the teller systems and the ATMs have to be told to finish the day's processing, a process we called "going into late work" for the tellers and "changeover" for the ATM.
      --
      Somebody get that guy an ambulance!
    23. Re:Not going to happen for a long, LONG time... by Anonymous Coward · · Score: 0

      One of those Diebold ATMs took my card for about five minutes, sitting on a "Please Wait..." screen or something like it, while entirely unresponsive (the cancel button had no effect). I assumed it was on a timeout, because eventually it said that the transaction had failed. bah.

    24. Re:Not going to happen for a long, LONG time... by Ailure · · Score: 1

      Reminds me of an ATM running on Windows NT 4, it was kinda confusing to look on the ATM screen and see an Windows desktop. Luckily the other ATM worked like usual...

      For not too long time ago, the ATM's used DOS around here.

  21. Press Release by spells · · Score: 1

    Did anyone try to read the "Press Release" from the first link? It's so badly worded that I found it impossible to finish. Apparently the literate OS2 supporters disappeared shortly after the developers.
    The last time I developed for OS2 was in 1999 and even then I felt like I was way behind the times.

    1. Re:Press Release by LordNimon · · Score: 1

      Most OS/2 users these days are outside the U.S., so it was probably written by a non-native speaker.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    2. Re:Press Release by Locutus · · Score: 1

      nope, didn't read it but my guess is that it's because the site, OS2WORLD.COM not from a country with english as its native language.

      It's probably German, or near by. I say this because in the early 90's, Microsoft could not block the large German OEMs from shipping OS/2 pre-installed like they could here in the US. And so, in less than 2 years, OS/2 had over 25% marketshare in that region. Where do you think StarOffice came from? Star Division, purchased by Sun in the late 1990's, was the German company which started off with an OS/2 word processor. They later added the other applications and because of their object oriented design( C++ ), they were able to port it to Windows and GNU/Linux fairly quickly. The idea of cross platform GUI toolkits/frameworks used to be very common in the late 80's and early 90's but that was before Microsoft started handing out Microsoft MFC dev kits like LSD "window panes" at a Rave party. But that's another story...

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  22. It's a shame by brennanw · · Score: 4, Informative

    That even *some* of the code -- specifically the workplace shell -- can't be released as open source. The workplace shell was one of the most elegant and powerful user interfaces I've ever worked with. It wasn't always the most *attractive* interface -- not by default, at any rate -- but it was the only one I've ever used that ever "felt right" to me. I miss that. The phrase "drag and drop" simply didn't do it justice.

    Anyway, I signed, but I'm afraid that 1) there's too much proprietary licensed code for the entire thing to be released, and 2) IBM has neither the patience nor the interest in doing the work necessary to separate what can be released from what can't be released. Which is a pity.

    --
    Eviscerati.Org: All Hail the Eviscerati
  23. Cash machines by AltoClef · · Score: 5, Interesting

    Given that OS/2 is in a good many cash machines/ATMs, I wouldn't be surprised if there are contractural problems with opening the code up. Security through obscurity and all that.

    1. Re:Cash machines by LouCifer · · Score: 1

      Sadly, not any more. They're starting to run Windows now.

      --
      Religion is for people afraid of going to hell.
    2. Re:Cash machines by Dejohn · · Score: 1

      Security through obscurity and all that

      From IBM?!?? Noooooooooo.. never!

  24. How about other O/Ss too? by kc01 · · Score: 1
    I know there will be loads of legal wrangling involved, but I'd also like to see many defunct O/Ss go open source. A short list of the "would like to haves":

    • Any Data General O/S (DG/UX, AOS/VS II, RDOS, etc.)
    • PR1ME's Primos
    • CDC's NOS
    • DEC's RSTS-11 and RSX-11
    • Is AmigaDOS available somewhere?

    These are all for machines no longer being produced, and not likely to even be supported in the field. I'd like to see the code not only for nostalgia's sake: Each had particularly engaging features, and it'd be nice to see some of that live again in contemporary operating systems.

    1. Re:How about other O/Ss too? by IckySplat · · Score: 1

      I loved AOS/VS
      My first love :)

      RMS or RMS/XA from Datapoint
      would be another one to revive
      It was a very cool OS in it's day

      Hey how about a Databus front end for GCC?

      --
      Help! help!, the termites are eating my DRAM!!!
    2. Re:How about other O/Ss too? by squiggleslash · · Score: 1
      Alas the latter is still being actively "sold" and the people who own the rights are still selling hardware and aren't likely to allow it to go FOSS for a long time.

      However, there's AROS, a close clone.

      Perhaps, ultimately, this is the solution wrt to OS/2 - the fans could clone it, rather than expecting IBM to pay another army of lawyers to go through the source code and work out which bits they "own" and which bits they're obliged to keep private.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:How about other O/Ss too? by Anonymous Coward · · Score: 1, Interesting
      How about Multics?
      • Great Security
      • Ancestor to Unix
      • Segmented memory
      • PL/I
      • And much more... (OK, I got lazy)
    4. Re:How about other O/Ss too? by John+Hasler · · Score: 1

      > I'd like to see the code not only for nostalgia's
      > sake: Each had particularly engaging features,
      > and it'd be nice to see some of that live again
      > in contemporary operating systems.

      It's likely to be easier to just reimplement the features from scratch than to import code from foreign operating systems, especially ones not written in C.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    5. Re:How about other O/Ss too? by kc01 · · Score: 1
      I never said anything about importing code- Just seeing it (and the comments and/or docs) would be sufficient to see the innovations contained therein.

      There have been significant developments in many areas (example: memory management, now that there's actually plenty to manage), and thus make direct importing of code into a foreign O/S impractical. Particularly if we're looking at sections of assembler for long-passed on processors/instruction sets.

      Still, the making available of legacy or antiquated O/S source would be a good thing.

  25. learning... by ecalkin · · Score: 2, Insightful

    exposure to other 'stuff' helps expand your horizons. being able to see the code behind os/2 would probably give a different perspective on an operating system.
    there is something to be said for learning from others.

    eric

    1. Re:learning... by Anonymous Coward · · Score: 0

      >there is something to be said for learning from others.

      i think the thing to learn from OS/2 is not to partner with Microsoft

    2. Re:learning... by AKAImBatman · · Score: 1

      exposure to other 'stuff' helps expand your horizons.

      Right you are. Now go install Plan 9.

  26. Not this again! by LordNimon · · Score: 4, Insightful
    What a joke. Some people have been trying to get OS/2 open-sourced for years. Of course, none of these people is a large IBM customer. Instead, they've always just been a bunch of disgruntled end-users. Looking at this petition, I see that nothing has changed. This petition is no different than any of the dozens before it over the past 10 years.

    There is no way this is going to happen. IBM would have nothing to gain, because they'd have to hire a whole of people to go through the code, figure out what's not protected by any IP (and OS/2 has a 20-year history, so that's a lot of possibile IP), and then release it in such a way as to make sure no one notices, since the last thing IBM wants these days is to bring attention to OS/2.

    --
    And the men who hold high places must be the ones who start
    To mold a new reality... closer to the heart
  27. Slashdot is definitely making a difference by benhocking · · Score: 1

    I just signed it and I'm number 499.

    --
    Ben Hocking
    Need a professional organizer?
    1. Re:Slashdot is definitely making a difference by Justin205 · · Score: 1

      ~200 more in 3.5 hours... Wow, considering how many people visit Slashdot (the /. effect...), that's not a whole lot..

      --
      "Your effort to remain what you are is what limits you."
    2. Re:Slashdot is definitely making a difference by M1FCJ · · Score: 1

      OS/2 is out of favour for some time now. It's been years since I used it as my primary OS (well, since early Linux kernels actually). As a result most of the /. readers do not even know what a nice system OS/2 Warp was and don't care. Only some people will remember OS/2 with fond memories. Simon doesn't.

    3. Re:Slashdot is definitely making a difference by xanadu-xtroot.com · · Score: 1

      100% agreed.

      Warp! Was a WONDERFUL OS. I too have fond memories and still a bit of longing in relation to it. Linux has more than satisfied my missing Warp!, but It would still be nice to used it again. I think I last used 4 (it might have been 3, I honestly forget). Once I upgraded my computer at the time to 16M RAM from 8M, Warp! just soared (a P-100! One the first to hit the streets - and man did I pay for it...). It beat the hell out of WIN-3.1x at the time.

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    4. Re:Slashdot is definitely making a difference by Anonymous Coward · · Score: 0

      I'm only 20 and remember using OS/2 ver 2 through warp.

      Though this is probably bcs my grandfather was an IBM developer and he's one of the only ppl i knew the time w/ a pc.

    5. Re:Slashdot is definitely making a difference by M1FCJ · · Score: 4, Interesting
      Given enough memory it would circle around Win3.1 and Win'95 and Win NT when finally it come out and wouldn't perform where Warp would.

      OS/2 always got hammered because it needed 16MB to be comfortable and those days a server usually had 8MB. I had 8 and I was running a BBS on my PC. It was significantly smoother, never dropped a single package over the modem while I was working on my CAD software (which alone used over 8MB of RAM), constantly swapping in and out. Win3.1 even couldn't handle me moving the mouse with a user downloading. Win95 wasn't an improvement.

      Most of the Win95 and OS/2 users were single-task users. It really showed its power when you used it as a server or a real multi-task environment. Later on I ran MUDs and httpd daemons on it and it always performed faster than anything Microsoft could supply. The lack of graphics card driver support really doesn't matter if you are content with a VGA screen, who needs graphics on servers in any case?

      Where it failed is the developers. Steve Balmer wasn't shouting "Developers! Developers! Developers!" for no reason. IBM's expensive compilers and other suppliers' (i.e., Borland) lack of commitment effectively what killed OS/2. There was a limit on what you really wanted to do with gcc.

    6. Re:Slashdot is definitely making a difference by Anonymous Coward · · Score: 0

      I'm only 20 and remember using OS/2 ver 2 through warp.

      Though this is probably bcs my grandfather was an IBM developer and he's one of the only ppl i knew the time w/ a pc.


      And with the way you're typing, I'm surprised you're that old. A few extra keystrokes won't kill you, you know...

    7. Re:Slashdot is definitely making a difference by utlemming · · Score: 1

      Gee I would love to see it run on an AMD64 4000+ (or whatever the top of the line is now) and couple gigs of RAM. Sure would be entertaining.

      --
      The views expressed are mine own and do not express the views of my employer.
    8. Re:Slashdot is definitely making a difference by vegetasaiyajin · · Score: 1

      AFAIK, OS/2 had anabsolute 512MB memory limit. I don't know if they extended this with the server version (which I never used).
      I still have my red box OS/2 warp (and OS/2 2.1 too).
      That was the best you could use in a time dominated by the atrocity known as Windows 3.1

      --

      My heart is pure, but make no mistake, it's pure evil
    9. Re:Slashdot is definitely making a difference by dryeo · · Score: 1

      Sopposed to just fly. IBM only came out with a Kernel that will install on a AMD64 last month, before you had to install on a different machine and move the install.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    10. Re:Slashdot is definitely making a difference by pnewhook · · Score: 1

      I loved OS/2. There were a lot of things that I could do with it that would wow (or really annoy) the windows zealots of the time (in addition to the advertized better windows than windows and better dos than dos). I'm not even sure windows could do some of these things now:

      - I set up my CD burner as an ftp-able directory. I once got several people to ftp to this drive simultaneously over a lan and OS/2 NEVER corrupted the CD. The machine was a PII 450 as well.

      - While downloading over the modem on my laptop, I could plug in the lan, then hangup the modem. The download would momentarily stop while the machine grabbed a new IP but would then happily resume.

      - On my P100 Thinkpad I could play full screen MPEG videos at full frame rates without any jitter.

      - And my favourite - I can strip down OS/2 to just the kernel and networking to have a highly deterministic embedded operating system. Everything needed for the OS and IP support would fit on a single floppy (great for SBCs). Under Embedded XP I havent yet found a way to get the base OS and TCP/IP stack without forcing me to have graphics also. This boosts the footprint into the 10s of Megs (can anyone help with this??)

      --
      Tesla was a genius. Edison however was a overrated hack who liked to torture puppies.
    11. Re:Slashdot is definitely making a difference by Anonymous Coward · · Score: 0

      In 1999 Warp Server for eBusiness (WSeB)raised that to 2048MB - the following year the new Client version - the Merlin Convenience Package (MCP1) could set that limit for program loading to 3072MB. The third-party version of OS/2 with advanced installer [11 minutes from CD-boot to fully operational and on the www on one of my machines] and a host of additional applications/utilities; *eComStation* [eCS]from Serenity Systems International in Lewisville, TX debuted in 2000 and the latest release was Version 1.2 in Aug/Sept 2004, about three years more recent than the 32-bit windows XP
      See http://www.ecomstation.com/ and http://www.serenityvirtual.com/ [SVISTA Virtual machine based on eCS]

      OS/2-eCS boot drives can be pulled out of one box, stuck in another with entirely different brand/type of Video, different motherboard manufacturer, different CPU, different IRQ setup, different chipset for the drive controllers, different USB type, different type of monitor, hard drives up to 512GB and should come up looking exactly like it did on its previous host machine in 99% of all cases. It also will install and run on any Pentium[one] level machine that has 64MB of RAM, though it runs better with more and will use as much as is available - secret is not to enable any BIOS setting for RAM >64MB *for OS/2* as the BIOS writers never caught up with real-life, that hasn't been an option for *many* years!

      With 4MB of Video RAM I can have 38-pages of Desktop real estate under OS/2-eCS - I usually only have on average about 3, stacked vertically 1024 * 768 = 1024 * 2304 - many OS/2 users are running at as high as 2048 * ~1400 on their desktops. IBM OEM licensed the Scitech Display Doctor for all GRADD [Graphics Adapter Device Drivers]. There is just nothing out there [yes I have installed and occasionally use BeOS/RedHat/W2000 Pro] that remotely compares with the power of the user-friendly WPS [WorkPlace Shell], with many features impossible to implement on the Gates model!

      Mike O'Connor
      [not anonymous really - just not signed-up yet]

    12. Re:Slashdot is definitely making a difference by mikeoconwarp · · Score: 1

      Omitted to mention that with Merlin (Warp 4) in 1996!], voice Type Navigation and Dictation was an integral part of the Operating System and applications themselves didn't need to be specially written to be voice-aware, they automatically inherited it from OS/2!

      If you wonder where Window Blinds came from - they were part of Object Desktop which was developed on Stardock's initial platform, OS/2!

      Mike

    13. Re:Slashdot is definitely making a difference by mink · · Score: 1

      Arthur dent had more luck getting the plans for the bypas set to replace his house then an OS/2 user has with buying software from them.
      I mean, I agree and understand why they went to windows for sales. But they I think were to quick to completely turn their back on OS/2 users considering the praise OS/2 users constantly gave them. They could at least offer current OS/2 users the last stable release versions of the OS2 softwares for purchase with no support (if thats such a huge obstacle for them). I think they could have (and even now) made some additional cash from OS/2 users.
      I think I even saw someone offer them money for software they used to make and they told the person they didnt want the business unless the user switched to windows.
      It boggles my mind when a company does not want to make money for seemingly insane reasons. It's not like once they went to developing for windows it is a crime to sell to OS/2 users.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  28. According to the BOFH by Anonymous Coward · · Score: 1, Funny

    According to the BOFH there are two remaining users of OS/2. Did they have a convention? Does two count as a convention?

    If they both sign the petition, it will be unanimous. Surely, IBM will bend to a unanimous decision.

    1. Re:According to the BOFH by femtoguy · · Score: 1

      Actually, I guess I am one of those two guys. I have a scientific instrument from a German company that has driver software written in OS/2. There is an NT version, but it is pathetic in comparison. So I keep my OS/2 version running, though I do occasionally miss file service and print service, and a bunch of other stuff.

    2. Re:According to the BOFH by M1FCJ · · Score: 1

      I sometimes think Simon never used OS/2.

  29. at the very least, lets who's licenses block this by Locutus · · Score: 1

    This has come up over and over again and IIRC, it's always come back with IBM saying that they can't open source OS/2 because there's too much licensed code in it, and the license holders will not allow releasing the code. Of course, I've also heard that Microsoft is one of the major holdouts.

    Wouldn't it be nice to have the WorkplaceShell on GNU/Linux someday? Or even get something like OpenDoc going again. Being stuck with rectangular windows just seems so 1980's. The browser and *nix has shown that small efficient "parts" make a far better, stable, and secure platform.

    And with open source, it doesn't matter how large a company you are. Not EVERYBODY cares if you scream. Meaning, Apple, Wordperfect, Microsoft, etc, can't kill innovative technologies if they feel threatened by it.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  30. They check to DOB for one reason. by crovira · · Score: 1

    If its not yesterday, they want to make sure you're old enough to actually remember the Mac OS 1.x and Win3.1 (And Compaq's beige luggable and ...)

    Its a REAL pain having to work with a pre-internet OS.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
    1. Re:They check to DOB for one reason. by rworne · · Score: 1
      Its a REAL pain having to work with a pre-internet OS.


      OS/2 Warp Connect? It came Internet-ready right out of the box.
      --
      I tried every decent and legal way I could think of to resolve the issue w/the business before I rented the chicken suit
    2. Re:They check to DOB for one reason. by M1FCJ · · Score: 1
      And it was a pain to set up the network cards.

      I had a BBS running on OS/2 and Maximus/2 with terminal servers coming in as telnet connections + 8 modem lines. It worked brilliantly. We shut the whole thing down after Y2K started to kill other BBS software around the country and there were almost none to communicate with. Ocassionally I'm still blamed with killing the community. They should have moved on, I already had.

  31. Yes... by bcmm · · Score: 0, Redundant

    Because Microsoft will give permission to realease code for a partly Windows-compatible system that they have some rights to. And they won't mind that projects like Wine will have a nice set of NTish API code to port.

    --
    # cat /dev/mem | strings | grep -i llama
    Damn, my RAM is full of llamas.
  32. Re:OS/2 Ahh the memories by eno2001 · · Score: 2, Interesting
    Speaking as a crazed liberal, I have to agree. I loved OS/2 Warp. I got it before Windows 95 came out and man was it sweet. It had the nicest looking GUI of the day just one notch below Mac OS. Win 3.1 blew chunks in the desktop department at the time. When Windows 95 came out, it felt like OS/2's retarded backwards hillbilly cousin. The main thing that killed my use of OS/2 was the lack of applications that I wanted (mostly games as I was a 20-something then).

    As far as aGUI based alternative to Linux/BSD, check out ReactOS,/A>. They've made a good eal of progress and I think they will be what some people are looking for in a few years: a free Win32 alternative.

    --
    -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  33. Write a letter or make a call ... by Sonic+McTails · · Score: 3, Insightful

    Writing a letter or calling IBM would be worth like 1,000 to 10,000 signatures because it tells people that you really want this, and you aren't just filling out the form many hundreds of times. If you really want to see it happen call IBM: 1-800-IBM-4YOU

    --
    This signature was left intentionally blank.
  34. JFS by Anonymous Coward · · Score: 0

    Maybe we will finally get IBM's JFS!

    Oh wait...

  35. RMS effect...? by AlexeiMachine · · Score: 1

    If IBM does open it up, do we have to start calling it OS/GNU or something?

    1. Re:RMS effect...? by maxwell+demon · · Score: 1

      Of course it will have to be named GNU/2 (remember, the GNU comes first!)

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:RMS effect...? by GundamFan · · Score: 1

      That has a nice ring to it...

      --
      I don't give a damn for a man that can only spell a word one way.
      Mark Twain
  36. Re:OS/2 Ahh the memories by big-giant-head · · Score: 1

    Hee hhehee (in a Dr Evil sort of Laugh)..

    If we could roll OS/2 and reactOS together that would rock!

    I haven't touched C/C++ in 6 years and I'm ready to volunteer.

    --

    So Long and Thanks for all the Fish.
  37. Re:OS/2 Ahh the memories by MightyMartian · · Score: 2, Insightful

    Well, as far as I'm concerned, the Windows GUI to this very day is a half-witted knock-off of OS/2's WPS. I'm not going to get into a war over whether MacOS's GUI is better than the old WPS, but it's pretty damn sad that Windows XP, when you look at it, has an inferior GUI to one developed a decade ago.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  38. Not a chance by Anonymous Coward · · Score: 1, Interesting
    The SCO case is an excellent example on how IBM responds when someone pulls this kind of bullshit on them.

    If you have any such magic bits of code, you're better off going after suckers that paid off SCO like this mircosoft partner or even better these guys who seem to make it a political statement to pay off anyone who threatens anyone with IP (probably at the bidding of their new master who bought them for $2B).

    1. Re:Not a chance by Anonymous Coward · · Score: 0, Troll

      Yes, MS is Sun's master. That must be why Sun is pushing Open/Star Office, which is probably the biggest threat to MS's monopoly in quite a while (most companies use Windows for MS Office - go figure).

      And while the way IBM has responded may be a bold approach, it has also turned into a several-year-long FUD circus.

    2. Re:Not a chance by kfg · · Score: 2, Funny

      The enemy of my enemy is my friend - even if they're my enemy.

      KFG

  39. I suspect there's a fair amount of legal restric.. by Anonymous Coward · · Score: 0

    "I suspect there's a fair amount of legal restrictions on elements of the code"

    Well yeah, like "Microsoft writing it" for one.

  40. OS/2 Is Old by Ritalin16 · · Score: 2, Interesting

    Personally, I don't think IBM or Microsoft cares what happends to the code, its outdated. I think they wouldn't mind it becomming open source.

    --
    In soviet Russia, Linux compiles YOU!
    1. Re:OS/2 Is Old by MightyMartian · · Score: 1
      It may be old, but I'll wager that there is significant amounts of common code between OS/2 and WinNT and its descendants. I'm fairly certain that MS would not want OS/2 open sourced, and while it might be cool, I can't say as I would blame them.

      What would be nice would be to have WPS ported over to *nix and X. Clean it up, build in multiple message queues (I'm sure this isn't a trivial alteration), and you would have a GUI that could take on Mac and Windows.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
  41. Dare to dream! by brennanw · · Score: 2, Interesting

    Sure, it's probably not going to happen, for all the reasons you list. But there's technology in OS/2 that has yet to be duplicated in other operating systems. And like most IBM inventions, it's going to fade into history, forgotten and unused. I'd really like to see what free software developers could do if the workplace shell landed in their lap.

    --
    Eviscerati.Org: All Hail the Eviscerati
    1. Re:Dare to dream! by LordNimon · · Score: 4, Informative
      I used to work at IBM on OS/2, and I've written a bunch of code for it. I can tell you that the ONLY code of value that isn't implemented somewhere else is the WorkPlace Shell (WPS). Technically, the WPS could probably be released as open-source. However, that wouldn't help a whole lot, for three reasons:

      • The WPS API is well documented and stable. It also isn't that big, since it's just a core API. The real value is in the plug-ins, and there are already plenty of open-source third-party plug-ins for the WPS. It would not be that difficult for someone to recreate the core WPS from scratch, just from looking at the API.
      • IBM's code is heavily tied to the Presentation Manager (PM), which is the OS/2 equivalent of the X Window API. You'd spend as much effort trying to rip out the PM dependencies as you would just rewriting the damn thing from scratch.
      • As powerful as the core WPS is, the current implementation is pretty weak compared to what KDE and GNOME do today. Even after porting the core WPS to Linux (or whatever), the developers would then have a lot of catching-up to do to make it more desireable than KDE or GNOME.
      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
  42. Instead of OS/2, how about WinNT. by Anonymous Coward · · Score: 0

    I don't know anyone who cares about OS/2; but an even more important user group has been abandoned in an even worse way. Let's start a petition to get NT open sourced so all these business can still function.

    1. Re:Instead of OS/2, how about WinNT. by mink · · Score: 1

      Chances are you ATM (unless recently replaced) runs on OS/2 as does your banks computers (in the back not on the desktop) so if you care about your money, care about OS/2

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  43. It'll never happen by LouCifer · · Score: 5, Informative

    And here's why.

    IBM sold OS/2 off and it became eComStation ("jointly developed" - whatever). I highly doubt big blue has exclusive rights to the code anymore.

    Go ahead and sign the petition, we all know how much weight internet petitions carry.

    I, for one, would love to see both of these pan out. Unfortunately they probably won't.

    --
    Religion is for people afraid of going to hell.
    1. Re:It'll never happen by jayloden · · Score: 1

      well, maybe if they spelled her name right....

    2. Re:It'll never happen by cha0t1c · · Score: 2, Interesting

      Agreed. I for one run Ecomstation as a viable Internet alternative cuz who writes virii for Warped? It's fast, comfortable (for me, who has been involved since the very early 90's) and robust as heck. If you want a viable alternative, sans bells and whistles, this is it. But I agree with the above post..., the ecomstation site (and all of us other propeller heads) paid for it/run it. To tell the truth, I wouldn't be too upset. As much as linux would benefit, so would OS/2. my 2 pennies

    3. Re:It'll never happen by hausmaus · · Score: 1

      IBM didn't sell OS/2.

      They licensed OS/2 to Serenity Systems as an OEM product. SS has added new features, tightened up some code, put more value-added programs and drivers into the distribution package, but they don't own OS/2. No chance in hell for that one. ;)

      IBM still owns OS/2, lock, stock and barrel.

      Because it seems that many people out here don't realize this, IBM still sells licenses to businesses. IBM, however, screwed the SOHO side of OS/2 years ago. There's a few of us that think IBM secretly hired the Amiga marketing team somewhere along the line.

      That aside, I use OS/2 for my daily use. I've got everything I want or need under OS/2. (I do have a Windows machine for my big gun games though. But that's what Windows is really good for ... and I digress.)

      What many people don't know is that a while back, Ralph Nader actually tried to petition IBM to open source OS/2.

      I, as an OS/2 user since '96, cannot see IBM /ever/ open sourcing OS/2, period. There are too many licensing issues with Microsoft and many other parties. There's probably a dozen other things that have been pointed out already.

      But, hey, OS/2 works fine for me as it is. I'm not complaining.

      There's still programs being developed for OS/2, new kernels every now and again, but open sourcing OS/2 isn't something I think I'll see.

      --
      Your email has been returned due to insufficent voltage.
    4. Re:It'll never happen by Eil · · Score: 1


      IBM sold OS/2 off and it became eComStation ("jointly developed" - whatever). I highly doubt big blue has exclusive rights to the code anymore.

      Close... they only licensed OS/2 to eComStation. IBM still owns and supports OS/2 as a platform for "legacy Java applications" until the end of 2005. I don't know exactly where eComStation sits, but I don't think they "own" the code enough to open source it. It would be nice if IBM somehow managed to sell the complete set of OS/2 rights to some other company that could open it up, but that's pretty darn slim and there is simply no way that IBM is going to open themselves up to a(nother) Microsoft lawsuit.

  44. Umm OS/2 isnt owned by IBM by nurb432 · · Score: 1, Interesting

    They sold it off to another company some time ago who currently supports it, and develops new versions.. ( estation, or somethign like that )

    Unless something has changed in the last year or so..

    --
    ---- Booth was a patriot ----
    1. Re:Umm OS/2 isnt owned by IBM by agrisea · · Score: 1

      Actually, OS/2 IS owned by IBM - they just licensed the code to Serenity Systems International, who is responsible for the development and distribution of eComStation.
      http://www.ecomstation.com/

      IBM's OS/2 web site is:
      http://www-306.ibm.com/software/os/warp/

      Hope that clears up any confusion.

      --
      Agrisea Tsunami - Epyc Servers... https://agrisea.net/products
  45. Lots of benefits - great idea by dtjohnson · · Score: 1

    Microsoft and IBM jointly developed OS/2 but IBM has gradually acquired the rights to the code they didn't own when the M$/IBM split happened. There is a lot of really good stuff in OS/2, though, that was developed solely by IBM after the big split such as the 'workplace shell' (WPS) desktop, the logical volume manager, and the JFS file system. The WPS desktop is arguably still several years ahead of the windows start-bar/explorer window stuff and could be updated relatively easily, if there was access to the source code, to a 3D implementation that would put Microsoft to shame.

    1. Re:Lots of benefits - great idea by acb · · Score: 1

      IBM contributed JFS to Linux a while ago, and it has been in the kernel since 2.4.x at least.

    2. Re:Lots of benefits - great idea by dtjohnson · · Score: 0, Offtopic

      Yes, the fact that IBM was able to release JFS under open source shows that IBM developed it without any participation from Microsoft. Obviously, IBM could do that then with other parts of OS/2.

    3. Re:Lots of benefits - great idea by SocietyoftheFist · · Score: 1

      Was JFS developed for OS/2?

    4. Re:Lots of benefits - great idea by mink · · Score: 1

      Yes.
      If you read up on the SCO vs. IBM issue, SCO cant go after IBM over LVM/JFS since IBM did not port AIX LVM/JFS to Linux. What IBM did was do a clean implementation of JFS on OS/2 and then port that to Linux. This kept OS/2 LVM/JFS separate of what they developed on AIX.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  46. This is a little late... by suitepotato · · Score: 3, Interesting

    If they had hammered a deal to do this with MS back at the time of Warp 4, back when Stardock was still supporting OS/2, it might have gone somewhere and given us essentially three competing systems: Win, Linux, OS/2. Instead, IBM could not find their rear ends with a hunting dog and a copy of Gray's Anatomy, kept with the single worst GUI design this side of the Amiga, and decided obfuscation and counterintuitiveness was superior to ease of use and common sense.

    That said, it would be nice to see, but way late. We should be at Warp 7 by now. I doubt the OS/2 fanatics will be able to sufficiently play catch-up even if Redmond is open to open sourcing the thing given how many went to Windows or Linux or both. They ain't getting younger and doing an about face in your coding mindset like that might cause a bump in the number of programmers seeking professional psychiatric help.

    --
    If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
    1. Re:This is a little late... by jskiff · · Score: 1

      We should be at Warp 7 by now

      Engage!

      --
      It's "no one," not "noone." Who the hell is noone anyway?
  47. Book deal? by Anonymous Coward · · Score: 0

    Hey, maybe if IBM does this Ed "OS/2 Professional" Black will write a sequel totally awesome novel.

  48. Sad but, by big-giant-head · · Score: 1

    Is it really supprising?

    --

    So Long and Thanks for all the Fish.
  49. Patents would be much better than code by LodCrappo · · Score: 2, Insightful
    The actual code used in OS/2 is probably very tied to being part of an OS/2 system, not Linux or your open source os of choice. Porting an OS isn't like porting an app and translating some library calls..

    Except maybe for some of the very high level code (basically applications), you aren't just going to port some feature of OS/2 to *nix even if you have the code.

    What would be nice would be a release of patents/copyrights covering concepts and technologies used in OS/2, such as the System Object Model concepts and the Workplace Shell. OS/2 had some nice ideas and it was a neat environment to work in. Bringing that environment to open source (or any other environment) would not be that much easier even if you had the source.

    --
    -Lod
  50. som/dsom and wps by SCHecklerX · · Score: 1

    It would be nice if we had those instead of the mess that is KDE/Gnome. I really really miss WPS. Under the covers, I think linux is a better solution for the core though.

  51. Show your stuff, IBM! by Simonetta · · Score: 1

    This is an excellent opportunity for IBM to put 'it's money where it's mouth is'.

    They're 100% behind Linux; they get the profits from the installation and support while letting everyone else do all the development work. .. for free...

    Now here they have a product that can't be sold, has been written off and its cost absorbed into the books. Let them donate it to the open source development community and allow its strongest characteristics be integrated into the main open source product.

    However given that this is IBM, expect a lot of delay, FUD, insults, ridicule, and bombastic denunciations of the suggestion to open OS-2. Fret not, it's just part of the corporate process.

    Corporations are set on auto-pilot to reject anything new, innovative, and exciting. It takes a long time for anything to seep into the concrete that fills the space between the ears of upper management.

    Be optimistic and patient.

    1. Re:Show your stuff, IBM! by browncs · · Score: 1

      This is not a corporate inertia issue. OS/2 was originally a joint development project with Microsoft. IBM does not, itself, have the ability to open-source it. Nor is Microsoft likely to agree with this.

    2. Re:Show your stuff, IBM! by RadarCat · · Score: 1
      I think that Micro$oft will take any move to open source OS/2 Warp straight to the court system to protect their turf which Micro$oft sees as the entire Planet Earth.

      Any court battles over open sourcing OS/2 Warp would truly be a clash of deep pockets titans.

      I have said for years that IBM is the only computer business on our planet that could put Micro$oft out of business should it be truly determined to do so.

  52. Help Request: Post Road Mailer for OS/2 by www.sorehands.com · · Score: 1
    If anyone know how to contact the Innoval guys or to obtain the source of Post Road Mailer, I'd be appreciative.

    Even if Innoval didn't want to open the source of Post Road Mailer, like they did for J-Street Mailer, I'd like to fix some of the bugs in it.

    1. Re:Help Request: Post Road Mailer for OS/2 by LouCifer · · Score: 1

      Archive.org shows http://www.inoval.com (not the last entry, but the oldest).

      Hovering over the broken graphics on the left shows http://www.aescon.com/innoval/innomail.

      Aescon.com is still active. Might start there.

      Guy's name you're looking for is Dan Porter (according to the listing @ http://www.bmtmicro.com/support/BMTSUPPORT_CONTACT P.html)

      Some more info:

      http://www.polarbar.org/porter.html
      http://www. os2voice.org/VNL/past_issues/VNL1299H/v newsn4.htm (See December 11)

      etc. I'm sure you can find more on Google. Sorry I can't seem to locate a current address. Surely someone out there with current ties to OS/2 might.

      --
      Religion is for people afraid of going to hell.
  53. please provide details by davidwr · · Score: 1

    This is news to me. Please provide details, I'd like to contact this company.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  54. Details of current OS/2 company by nurb432 · · Score: 3, Informative

    Ok i was close on the name but not exact...

    http://www.ecomstation.com/

    --
    ---- Booth was a patriot ----
  55. Needed: Open Source GUI Client by Anonymous Coward · · Score: 0

    I've always felt that MS has had problems getting into the server market because they were trying to convert clients into servers. They are two completely different animals. But, they are getting pretty close with Windows2000. The same thing applies (but in reverse) to Linux. Linux is too complex for the normal (non-techie) user. I'm not saying that it's impossible to use as a desktop, just that it's difficult for the normal user to use.

    Because of that, it would be great to see a GUI client (OS/2?) couple with Linux. I know that there are some open source GUI client projects around, but there isn't one (or one GUI client standard) that is "leading the pack". Because OS/2 has been around for a while and would carry a little IBM clout, it might just be the GUI client that we need.

    1. Re:Needed: Open Source GUI Client by M1FCJ · · Score: 1

      XFree86 worked fine under OS/2 and for some time I used it as a X server pretty happily. Once you have XFree, porting GTK or QT shouldn't be a big issue, probably already done (I haven't checked recently, I turned the power off of the latest OS/2 box I was administering around year 2000).

  56. Re:OS/2 Ahh the memories by pilgrim23 · · Score: 2, Interesting

    If I recall correctly... OS/2 was used by IBM as the foundation for the S390 emulator software they use as the foundation platform on which they run the Z/OS or S/390 enviornment. This runs their current crop of mainframes. The Mainframe Market is small these days comapred to the past, but there are still organizations that use "Big Iron".

    --
    - Minutus cantorum, minutus balorum, minutus carborata descendum pantorum.
  57. Microchannel! by kneecarrot · · Score: 1

    We've all been complaining for years on the lack of Microchannel bus support... here's our chance to get some code!!!

    --

    I always save my last mod point to mod up a good troll. You people are too serious.

  58. OS/2 wasn't sold. It's been OEM licensed by pigfukr · · Score: 0

    Serenity Systems has an OEM license with IBM to release their own customized version of OS/2 which is called eComStation.

    --
    pigfukr
    1. Re:OS/2 wasn't sold. It's been OEM licensed by magetoo · · Score: 1
      Serenity Systems has an OEM license with IBM to release their own customized version of OS/2
      Do they have a fullscreen trailer out yet?
  59. I must have missed something by benhocking · · Score: 1

    It looks to me more like ~200 more in 13 minutes. Where are you getting 3.5 hours? (Perhaps somewhere else he mentioned doing this 3.25 hours before the story was posted?) Yes, this is a serious question - I'm not trying to be a smart-aleck.

    --
    Ben Hocking
    Need a professional organizer?
    1. Re:I must have missed something by Allen+Zadr · · Score: 1

      Most folks forget to set their timezone settings, or even take into account that timezones may be different by different readers. Ben, you are correct - it was only 13 minutes.

      --
      Kinetic stupidity has a new brand leader: Allen Zadr.
    2. Re:I must have missed something by Justin205 · · Score: 1

      Whoops, read the time wrong.

      Disregard my comment...

      --
      "Your effort to remain what you are is what limits you."
  60. Workplace shell is the part that we want by tjstork · · Score: 1

    I'd say forget the underlying OS and put Workplace Shell on top of Linux. Not that the underlying OS is bad, it's actually quite good. It's just that, Linux and Windows have both moved on. You would need a whole new driver base, everything, and that's a tall order. If we had the workplace shell desktop, you would get a really powerful desktop - folders that act the way they are supposed to act, etc.

    I wouldn't mind having the EPM editor either. It had a really cool undo feature. Come to think of it, IPMD was a pretty darned good debugger.

    --
    This is my sig.
  61. JFS maybe, rest no time soon; historical systems by davidwr · · Score: 1

    Large parts of OS/2 share code with Microsoft. Other parts were licensed from other third parties.

    Some possibilities for open-sourcing include some applications, some device and other drivers, and since it's Linux spinoff is already open-source, JFS.

    Sadly, I doubt there's much interesting in OS/2 that can be open-sourced, except from a historical perspective.

    Speaking of history, I'd love to see every widely-used computer program open-sourced or better yet have its source and binary put into the public domain 20 years after its last commercial customer stopped receiving support. I'd prefer 5 years but 20 is much more likely to be accepted by industry. Things like classic Atari-2600 games though will never be open-sourced under this scheme, since like good Disney movies, they are commercially re-released every so often. But the games nobody cares about, and old spreadsheets, word processors, and OSes, those should be opened up.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  62. Re:OS/2 Ahh the memories by maxwell+demon · · Score: 4, Informative

    Well, according to their web page, the ReactOS people actually plan an OS/2 subsystem. Therefore if IBM released the part of the OS/2 code which they can, it would probably be a big help.

    BTW, if the OS/2 kernel code is too encumbered, even releasing the WPS alone could be a great thing. While it certainly lacked some features which modern desktops have, it had some other features which AFAIK are still not available on other systems (e.g. what was called "Arbeitsordner" in the German version; essentially a folder which managed its own "sub-session").

    --
    The Tao of math: The numbers you can count are not the real numbers.
  63. OS by BenjyD · · Score: 2, Funny

    A petition to make the OS OS2 OSS?

  64. Who would use OS/2? by kryocore · · Score: 0, Troll

    Who in their right mind wants OS/2. I've been trying to get rid of it in my company for years.

    1. Re:Who would use OS/2? by M1FCJ · · Score: 1
      Traitor!

      :-)

  65. What was so great about the Workplace Shell? by multiplexo · · Score: 1
    Not a flame or a troll, but I've seen a lot of posts in this story and others talking about how good WPS was. I used OS/2 briefly about 10 years ago and liked it quite a bit. The big turn-off for me was gaming support, I couldn't get drivers for my video or sound cards, other than that it seemed like a pretty solid product, my experience with it was that it was more stable running Win 3.x applications at the time than Windows 95 was on similar hardware.

    --
    cheap labor conservatives - they want to keep you hungry enough to be thankful for minimum wage.
    1. Re:What was so great about the Workplace Shell? by DrCode · · Score: 1

      One thing I particularly remember is that drag-and-drop worked pretty much everywhere. For example, if you brought up the properties of a file, you could change its icon just by dragging an image file onto it. I know this wasn't earthshaking, or a necessity; but it seemed pretty cool at the time, especially when the MS alternative was Windows 3.1.

    2. Re:What was so great about the Workplace Shell? by Anonymous Coward · · Score: 0

      I used to support an environment with both windows and OS/2. We used a printing product that had a list of printers in it. From OS/2 I could drag and drop a file onto one of those printer objects to test a printer or if I wanted to have it in my list of printers I could drag and drop the printer into the printer folder. I was surprised when windoze did not allow me to do the same.

  66. Re:Mod parent UP! Also the Microsoft link .... by Billly+Gates · · Score: 2, Interesting

    What this guy said is %100 true and Microsoft even paid SCO additional money to keep the lights on at SCO after they paid an outrageous sum of money for unix rights that they dont need.

    Sun too reacted sharply and even critizied linux and mentioned solaris as an excellant alternative. its a fact!

    Back on subject....

    Microsoft was a core partner with IBM and I even think Microsoft released its own OS/2 version to developers back in the early 90's but never commercially distributed. You can google it if anyone is interested in.

    Microsoft more than likely contributed alot of code to IBM and probably owns some percentage of the product.

    Remember OS2/NT became WindowsNT after Bill Gates decided to go with their own product.

    Microsoft would love to prevent OS/2 from ever going opensource and unlike the SCO case, Microsoft would have a good argument and would probably win.

    Doesn't Microsoft also own some unix code from Xenix? I believe some of it ended up in SysV or unixware which is why Novell can not opensource it. MS would probably sue them.

  67. WorkPlace Shell is the main thing, drivers next by invisik · · Score: 1

    We have enough guts out there to put the GUI on, just give us the shell. I still find it the easiest to use and very feature-rich even for today's standards.

    Also, we'd be in better shape is you didn't need a dang service contract to get the latest support packs. They have wireless drivers and all kinds of current stuff in there that very few can get at. I know they had to develop them themselves and someone has to pay for it. I'd pay $100 to get a service pack without getting on the corporate subscription service.......

    And then what's up with eComStation? I hear they are still in full development mode with new stuff slated for this year. That might be the place to support to keep OS/2 alive...

    -m

    --
    http://www.invisik.com
  68. Perhaps some of OS/2 by AaronW · · Score: 4, Informative

    Having developed device drivers for OS/2, I doubt there'd be that much interest in the OS/2 kernel or device drivers. Even in Warp, and OS/2 4.0, most of the device drivers were 16 bit since the device driver API was only 16 bit (except graphics drivers). I think maybe the only interesting parts would be the Workplace shell and SOM, though I wonder about the stability in today's complex environment, having remembered having issues of stability with the WPS when I loaded up all the software I ran.

    There's also still a lot of Microsoft bits and pieces of code in there.

    -Aaron

    --
    This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    1. Re:Perhaps some of OS/2 by aztracker1 · · Score: 1

      I'd be interested in the dos vm actually, yeah, from my understanding it'd be x86 only, but could really help things like dosbox and other dos vms.

      --
      Michael J. Ryan - tracker1.info
  69. why TeamOS/2's dream is unworkable by thenerdgod · · Score: 1

    So, you want to open-source an OS that features: 1. no user security 2. 16-bit drivers 3. large chunks written in assembler (or do you mean the PowerPC port, eh?) 4. large portions ©Microsoft, Inc 6. A UI written in IBM-style C++ (or, who knows, being IBM, maybe some of it's in SmallTalk) I can't imagine any of it being useful to the open-source community. Their networking stuff mirrors what AIX has, the kernel itself is very specialized and ancient, and the UI technology that is useful is already available through OpenDoc. Part of the problem is that nobody, be it the KDE folks or Gnome, want to do the sort of UI that OS/2 pioneered, the perniciously object-oriented interface of the WPS. Hell, trying to get GNU fiends to code in C++ is well-nigh impossible. I think a better idea would be to start a project to reproduce the effective functionality of the WPS and OpenDoc apps in a UI for X, or, better yet, Y. What they really need to open-source is all the OSs for the Atari ST!

  70. got it all by bobalu · · Score: 1

    So, you're saying maybe I *shouldn't* throw out all that stuff in my spring housecleaning?

    Hell, I just threw out a full set of Lotus stuff for OS/2 still in shrink-wrap.

    --
    The revolution will NOT be televised.
    1. Re:got it all by Anonymous Coward · · Score: 1, Informative

      In all seriousness, if you have stuff like that, definitely don't just throw it out. Put it on E-Bay or something, and give people who might be in need of it a chance to buy it off of ya.

      There is a project underway to create an open-source OS/2 clone, and those guys could possibly use things like compilers, redbooks, manuals, API specs, or even applications (for testing, maybe).

  71. Re:at the very least, lets who's licenses block th by snorklewacker · · Score: 1

    Wouldn't it be nice to have the WorkplaceShell on GNU/Linux someday? Or even get something like OpenDoc going again. Being stuck with rectangular windows just seems so 1980's. The browser and *nix has shown that small efficient "parts" make a far better, stable, and secure platform.

    Not really -- because the folks in KDE have a component model already, and they like it just plenty. Same goes for GNOME and GNUStep. As for the workplace shell, if no one's even attempting to write their own with today's technology, what makes you think they'll do any better with OS/2's code? Do you think it's a drop-in?

    Why does the Open Source world always need someone else's code, let alone ancient DOS-era code? Hell, the source is probably full of FAR pointers and such. Do you really want to work with that?

    --
    I am no longer wasting my time with slashdot
  72. WPS by Anonymous Coward · · Score: 0

    If WPS was available for linux, I'd switch in a heartbeat. WPS is simply the best GUI interface I ever had the priviledge of using. Admittedly IBM can't release the entire operating system due to parts of it being owned by other companies but what's to stop them from releasing the code base that they own.

  73. Would be good by petrus4 · · Score: 1

    Though I also can't see the elephant allowing this. If as others have said, OS/2 shares code with anything from Microsoft, there's less than no chance of it happening. Not only that, IBM probably wouldn't think it would make good commercial sense to do it...because they're currently trying to make money from Linux. They might worry (rightly, in at least some cases) that if they were to give OS/2 away, people might simply use that instead.

    Still, I know of at least one person who most likely still uses OS/2, and I'm sure there are a substantial minority out there who also still do. The 0S/2 user I know works for IBM...She gave me some Warp 4 CDs once...but I only installed it fairly briefly, and then took it off again...it didn't grow on me.

    The good thing about it being opened of course would be that despite a possible minority still using it, AFAIK IBM aren't still developing it, which means that it is more or less doomed to become extinct eventually. If it were opened, its lifespan could be increased greatly. It'd probably win IBM a large amount of PR points to do it as well, come to think of it. I doubt they could do it...but if they can, methinks they should.

  74. More! by darknightroot · · Score: 0

    The total number of registrants for this OS2 petition: 1320
    Keep it up!

  75. I highly doubt it by Loconut1389 · · Score: 1

    I -highly- doubt they'll open it up.. Last I knew, there were still a handful of banks (Washington Mutual for one) that use OS/2 as a desktop OS. The possibility for exploits is probably too high.

  76. OS/2 aka eComStation by mrmagos · · Score: 2, Interesting

    Considering this product is still being sold as eComStation, I don't think we'll be seeing an open source version from IBM any time soon...

    --
    Never start vast projects with half-vast ideas.
    1. Re:OS/2 aka eComStation by Anonymous Coward · · Score: 0

      On the other hand open-sourcing OS/2 might even help eComStation - as far as I can see, Serenity Systems mainly have added new stuff like Java, more device drivers etc. to OS/2, or replaced some components like the installer or the INF viewer, while the underlying OS still seems to be very much the same as in earlier versions (like WSeB). Even when only parts of the OS would be released as open source this could speed up development.

  77. Convince me by fbartho · · Score: 1

    I'm still trying to be convinced on why exactly I should sign this petition... It may be a personal eqotistical thought, but I choose not to go along with the flow for every motion that comes around... I like being convinced and I'm not right now. If you throw your support in for anything that comes your way, doesn't it devalue your vote? For the last elections for example, sadly the only thing I was convinced about was that Bush should not win. I voted Kerry because bush was worse, but I was not and am not convinced he was a good alternative, just that he was less bad.

    --
    Gravity Sucks
    1. Re:Convince me by Allen+Zadr · · Score: 1
      Dear fb,
      I'm afraid nobody can convince anybody. I looked at the petition, and read the web page around it - and to me, I thought... this could be useful, and in-fact, critical to some people.

      I'm not convinced that this will be "the best thing" for Open Source Software or for Linux, but I do think that this is "the best thing" for OS/2, and the small number of users whom - for one reason or another - are still using it.

      The far side of that, I think it would get a sub-set of the latest generation of extremely smart programmers to take a first look at this extremely useful (though, now old) OS, and learn from it.

      This is the first petition I've signed since the petition to put Nader's name on my state ballot (I didn't vote for him, but I think it's important that he be represented).

      If the petition doesn't make sense to you, by all means, just leave it be. If it does, then sign up!

      See, that's why I'm not a politician.

      --
      Kinetic stupidity has a new brand leader: Allen Zadr.
  78. Re:vms (mod up). VMS is not opensource by Billly+Gates · · Score: 1

    Only a new marketing name.

    If anything David Cutler may want to volunteer to write a VMS clone since HP is killing it for Windows2k3 and tieing it to the dieing ITanium.

    I know he hates Unix and Windows and this is his answer.

    HP wont release OpenVMS and its proprietary for Itanium and Alpha for the time being.

  79. OS/2 Warp NG = eComStation by user_ecs · · Score: 1

    www.ecomstation.com

  80. It's all about profit, ST*P*D by Anonymous Coward · · Score: 0

    [SNIP]

    2) IBM has neither the patience nor the interest in doing the work necessary to separate what can be released from what can't be released. Which is a pity.
    IBM today is more about making money *TODAY* than fostering ... income potential tomorrow; this seem evident to me by the requirement that anything being worked on in Almaden research center must be profitable in four (or was it five?) years.
  81. Just what we need! by Jozer99 · · Score: 1

    Just what we need, another old closed source OS going open! What better way to distract people who might otherwise be helping a project with some consumer and enterprise merrit, like Linux!

  82. This of course by KingBahamut · · Score: 1

    would greatly benefit the Point of Service industry.

    --
    "God of Rock, thank you for this chance to kick ass. "
  83. Retread by dpilot · · Score: 1

    If you're going to retread an OLD joke, at least get the Joke, rather than Joke/2.

    OS/2 was first co-announced with the PS/2. (Microchannel, for you young'uns) So the whole joke was:
    Half an operating system on half a computer.

    --
    The living have better things to do than to continue hating the dead.
  84. In-the-know by Anonymous Coward · · Score: 0

    I'm a New York lawyer, and have spoken over the years to a number of lawyers and former lawyers who have worked for IBM, Microsoft and entities that took a special interest in the M$ antitrust prosecution.

    Microsoft and IBM worked in tandem on OS/2 in the early days. At one point, it was viewed as a joint effort to create the successor to the earliest Windows releases.

    I have it on good authority (several in fact) that Microsoft exacted significant limitations on the transfer to ANY third party -- let alone open sourcing -- OS/2, particularly Presentation Manager and all its user interface elements that might contribute to competition against future Windows releases.

    Give it up. It's not about petitioning IBM. The company's hands are TIED.

    It's all about Microsoft. Again.

  85. I'm in, number (1562) by Anonymous Coward · · Score: 0

    c'mon guys let's see if we can slashdot their counter by having so many people sign up that we overload their counter. :)

    We're doing a good thing by helping sign this petition, and we can have some fun too while we're at it. :)

  86. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  87. beyond irrelevant by markhahn · · Score: 2, Insightful

    good old os/2 - so few people remember that Microsoft wrote it, basically under contract, for IBM.

    but really, who would care? it was an OS of its time (around 1990), and certainly does not add value to the OS landscape today. if you want layering to interfere with the design of an OS, you need look no further than NT and followons. the rest of the universe has gone on (to linux).

    yes, I did work on OS/2 (in Redmond long ago). I even have the tshirts to prove it (including one that elucidates that NT=new technology, and was originally a derivative of OS/2 for RISC chips...)

  88. Re:OS/2 Ahh the memories by M1FCJ · · Score: 1

    I would love to see something like KDE on OS/2's kernel. It would rock. WPS was much better than Win3.1 AND Win95 but you have to get used to it. Rexx was built-in to the system and it was beautiful.

  89. Petition to keep OS/2 closed by Anonymous Coward · · Score: 1, Funny

    gets my vote.

  90. Releasing the killer app: Lotus Improv by Anonymous Coward · · Score: 1, Interesting

    I did use OS/2 Warp a bit. Nice stuff under the hood, but frankly I expect that no one will get a radically new concept out of it.

    Now, talk about Lotus Improv !
    (See also http://www.oreillynet.com/timo.html)
    This was a revolutionary spreadsheet concept. Was it actually even to be called a spreadsheet anymore?
    Anyway, too new so not popular so dead in the commercial world.

    I bet that, as free software, it would have been a killer app (you know, the application that will make free software attractive even to patent lawyers - what kills their jobs - what kills them - hence the name "killer app"), developped and maintained because enough people would love the concept and make it live throughout from childhood to adulthood.

    Until the code is erased from all sources, this can still happen.
    So, IBM/Lotus, please release the code of Improv (and OS/2) to the people who will make it live.
    (Actually, the good thing is that, anyway, someone could make it anyway from scratch, but why reinvent the wheel?)

  91. Re:at the very least, lets who's licenses block th by John+Hasler · · Score: 1

    > Do you think it's a drop-in?

    He may. Many of those making these sorts of comments have no relevant experience.

    > Why does the Open Source world always need
    > someone else's code...

    What some individuals want is not particularly indicative of what Open Source "needs".

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  92. Most ATM's use OS/2. Still want to open source it? by MrLogic17 · · Score: 2, Interesting


    It's been reported many moons ago the most Automatic Tell Machines (ATM's) use OS/2 as the base platform. I've seen more than one ATM being serviced and seen very OS/2 like screens with diagnostic info.

    Do *you* want every 133t h@x0r out there with source code to your neighborhood ATM? If the bank hasn't bothered to move off OS/2, what are the odds they'll patch any holes found by white/grey/black hats?

    -MrLogic

  93. Not just icons... by brennanw · · Score: 2, Interesting

    I mean, yes that was very cool (and windows and KDE and Gnome *still* don't do that) but also printing. How many times did I drag a document over the windows printer icon and have the damn word processor open and load the document before it printed? That didn't happen in OS/2. You could change the way folders worked, to the point of setting them up as individual, unique workspaces -- a poor man's virtual desktop, really. You could associate files with programs on the fly with greater precision than is possible today (to the point where I could set it up so that a specific gif defaulted to loading one program while all other gifs defaulted to loading another program).

    There was the famous "drag web pages off of your browser and store them in a folder on your desktop" trick. That might be possible with other OS's now, I dunno.

    Shadows of icons would automatically maintain their links to actual programs, even if you dragged the program folder to another directory.

    I really can't do it justice -- I never understood the technology well enough to do it justice -- but essentially the workplace shell was a huge folder that opened up, and everything in the UI was a subclass of that folder, and they all "knew" how to work together depending on what you did with them.

    Like I said, I really can't do it justice.

    --
    Eviscerati.Org: All Hail the Eviscerati
    1. Re:Not just icons... by Anonymous Coward · · Score: 0
      An interesting thing was the extensibility of the WPS. You could create a new kind of desktop folders by writing and registering your own DLLs. These new folders then could have interesting features like special preview modes for certain file types.


      Unfortunately this was not used very often...

    2. Re:Not just icons... by Anonymous Coward · · Score: 0

      In OS/2 WPS, everything was an object. This made the GUI slow and hard to understand compared to the Windows and Mac OS of the day, but it also made it extremely powerful and easy to work with from a programmers perspective.

  94. Horrible petition collection structure by Clay+Pigeon+-TPF-VS- · · Score: 1

    How transparent is this process when no one can view the names of who signed the petition?

    --
    Viral software licensing is not freedom, it is in fact GNU/Socialism.
  95. The consultancy angle by Verszou · · Score: 1

    As somebody already mentioned a lot of big financial customers still run OS/2 - I'm working with one of them right now and they're still paying IBM to support the system.

    So from the perspective of IBM there would be the advantage of getting somebody outside look into the code and fix bugs. This is of course a problem the other way around in that financial customers would be reluctant to use fixes that were done outside of IBM since that could compromise security in their systems.

    Given that IBM is into having long working relationships with these kind of large customers they might be at some risk by allowing others - for example system programmers at the customer site the possibility to do their own fixes. Again you could argue the other way around that current corporate culture at financial corps. isn't into having large in-house knowledge of the OS like it was back in the early days of the OS wars (ah, nostalgia :-)

    I'm a bit rusty on the design of OS/2, but as I recall most of the 32 bit code was written by IBM in-house after the divorce from MS. And the support for Windows/DOS/Posix is modularised into subsystems - so even with possible legal problems it might be possible to release OS/2 as a pure 32 bit OS without any support for other sub-OS'es.

    The greatest obstacle would probably be to make sure that only the IBM parts would get out. That's pure cost to IBM.

    Another thing apart from WPS that would be a good thing to release to Open Source was the Java VM for OS/2. There are a lot of quirks and things in there that could benefit from some open source efforts - as it is now it seems that it's only those bugs that are reproducable and reported by larger companies that gets fixed.

    --
    Be alert, the world needs more lerts!
    1. Re:The consultancy angle by SillyNickName4me · · Score: 1

      > So from the perspective of IBM there would be the advantage of getting somebody outside look into the code and fix bugs.

      Is this really an advantage to them?

      They decided somewhere in the last decade that service was their thing, fixing bugs for a product tat is beyond its official end of life is not always easy, but it is well payed for service, which for quite some time has been IBM's main business.

      As long as enough customers exist that pay them for maintaining it, there is no business sense whatsoever in opensourcing it.

    2. Re:The consultancy angle by Verszou · · Score: 1

      The advantage would be having smaller developers to look into the code and submit possible fixes, then doing QA and integration testing with other stuff and releasing "IBM approved" servicepacks. That way they could still maintain their large customers who may be reluctant to just accept fixes right off the internet. For instance I've worked with a number of financial customers who are ok with doing in-house development on Tomcat and Apache but still insisted on running the production version on BEA, not because there were any measurable differences in performance or anything, but because that product came form a named provider - which basically meant they had somebody to blame if things fell apart. The combination of open source and IBM proprietary releases are a bit like what they are doing with Eclipse and the Websphere Application Developer product.

      --
      Be alert, the world needs more lerts!
    3. Re:The consultancy angle by SillyNickName4me · · Score: 1

      > The advantage would be having smaller developers to look into the code and submit possible fixes

      For now, IBM earns money from looking into such things. I doubt they want to enable others to do that for free really.

    4. Re:The consultancy angle by Verszou · · Score: 1

      That depends on what the release schedules are for these things. Large corporations are not early adopters of fixes, so even if a smalltime user fixes a bug and commits it it's very likely that large corporations will still pay to have IBM QA the fix and guarantee that it works with their specific version of the software. The revenue from support contracts to large companies are often more like insurance policies than actual purchase of services - if stuff goes wrong you call IBM and let them bail you out. But very often it does involve that you do most of the work in isolating the bug. Another thing is that if you have the support contract from IBM, then you can push for them to work on a specific bug. Bugs that are just submitted by smalltime users don't get any guarantee of attention from IBM. Large corps will prefer this to relying on somebody out there looking into the bug - and by releasing the source IBM could allow for others to look into those bugs that aren't high priority to their customers at present (but might be later on - I reported and got IBM to fix a bug recently through a customer and it was well known on the net, but my customer hadn't seen it until recently). Some of this can sound a bit weird to those who haven't worked with IBM and large corps. for a period of time :-)

      --
      Be alert, the world needs more lerts!
    5. Re:The consultancy angle by SillyNickName4me · · Score: 1

      > That depends on what the release schedules are for these things.

      I don't think you understood what I am saying. IBM gas serv8ice contracts with those customers, and gets payed for doign this development. Leaving it to others means less income for them.

    6. Re:The consultancy angle by Verszou · · Score: 1

      I think the point where we see things differently is in what the term "service contract" means. I think theres a distinction between service contracts and on-site consultants which may have been somewhat blurry in my previous post.

      What I mean is, that IBM has service contracts with these customers, meaning they will fix a bug for the customer if the customer can provide sample code to reproduce it, and they provide service packs that consist of stable releases of the bugs that they fix for their customers.

      IBM may or may not do development on their own on the product as well, but very importantly service contracts are paid up front - they get the money whether their own engineers do the fix or if their own engineers just take a fix that was done in Open Source by somebody else, run it through QA and then put it in an IBM servicepack.

      In the case where you have on-site consultants from IBM at these customers they are usually not developers but technical people, i.e. they test new fixes with the specific setup of the customer, make sure the fixes get distributet correctly through the customer network etc.

      So even though a number of bugs could be fixed by Open Source people IBM could still justify their on-site consultants because the value they add isn't as much knowledge of the source code of the OS as it is knowledge about how the OS is used at that particular customer site.

      This way of doing service and support isn't really specific to IBM, I've seen similar business models for Oracle and Sybase (where I used to work as part of their professional services in my country).

      --
      Be alert, the world needs more lerts!
    7. Re:The consultancy angle by SillyNickName4me · · Score: 1

      IBM may or may not do development on their own on the product as well, but very importantly service contracts are paid up front - they get the money whether their own engineers do the fix or if their own engineers just take a fix that was done in Open Source by somebody else, run it through QA and then put it in an IBM servicepack.

      Well, I do not know the exact terms and conditions for current OS/2 service contracts, but I do know what is usually in there for a product that is past its end of life, like it is the case with OS/2.

      In general, it means you will get the service packs if/when they are made and get conditions for getting your own specific problems fixed. The later is not payed upfront. (if this product was not yet past its 'end of life', then such fixes are on IBM's expense, but in this case they are not)

      I understand perfecly well what you are saying, but I am trying to tell you that in this specific case, your reasoning does not work because the customer does pay a price for each specific fix that they need and that is not there yet. Making the fix generates direct income in this case.

      It is not a difference of understanding between us 2 about what a service contract is, it is you not taking into account what it is to have a service contract with IBM on a product that is past its end of life.

    8. Re:The consultancy angle by Verszou · · Score: 1

      Well, I did work with such such a service contract as being part of the dept. responsible for such contracts when the support for 2.11 ran out, and I'm working with the same company now under a similar contract for the latest version of OS/2 (can't remember the name, but it's calls something like e-business server) - so on the whole I'd say that I have a pretty good idea of what such a contract consists of at least in my geographical area.

      I'd say that all in all I've some 3-4 years of experience with working at a company that has this kind of contract, both as a system programmer and in middle management - which leads me to believe that I have a pretty good idea of "what it is to have a service contract with IBM on a product that is past it's end of life".

      Contracts may be different from geographical region to region - but but it's pretty safe to assume that withing my own region I have plenty of hands on experience with the exact terms and conditions of such contracts.

      --
      Be alert, the world needs more lerts!
  96. if only by roror · · Score: 1

    we could GPL huge softwares by petitions, like we did for Java, MS Office and Windows would be open source long time back.

  97. Lotus 1-2-3 by redelm · · Score: 2, Interesting
    Personally, I'd rather see Lotus 1-2-3 source released. Especially PC v3.3 or Unix v1.0 (curses?). This is still very good code and _far_ more reliable than MS-Excel. We still have & use character-based systems.

  98. What about C-64 open source? by Anonymous Coward · · Score: 0

    Why stop at just OS/2?

    1. Re:What about C-64 open source? by SillyNickName4me · · Score: 1

      Go get yourself a C64 technical reference from e-bay or such, it contains a complete (assembler) source listing with comments of its kernal (yeah, thats how Commodore called it) and at elast part of the basic interpreter ;)

  99. Linux Community? by ReadParse · · Score: 2, Funny

    I would highly encourage the Linux community to take part of this open source petition

    Then what are you doing here? Everybody knows Slashdot is a Mac site now :)

    RP

  100. leeds station uk by petermgreen · · Score: 1

    big row of portrait form factor infoboards (presuamblly some sort of plasma displays)

    one of them had on it SIDEWAYS! disk boot failure. Insert system disk into drive A press any key to continue

    this was a few years back but its one that sticks in my memory ;)

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  101. ^^^ THERE THEY ARE!!! ^^^^ by Anonymous Coward · · Score: 1, Funny

    Both of them, here on Slashdot. Who would have guessed.
    I know that I feel honored.

  102. Preemptive multitasking by wardk · · Score: 1

    opening up this code if anything might help existing operating systems out there figure out preemptive multitasking. OS/2 may not have done everything well, but this wasn't one of them.

    1. Re:Preemptive multitasking by Wudbaer · · Score: 1

      Where have you been the last 10 years ? You are right, OS/2's multitasking was awesome back in the day, but today even Macs do preemptive multitasking.

    2. Re:Preemptive multitasking by Richard+Steiner · · Score: 1

      I'd like to see benchmarks comparing OS/2 to Linux and MacOSX -- I'd bet OS/2 wouldn't fare all that badly compared to its much newer counterparts.

      One thing OS/2 seems quite good at doing is adjusting various process priorities to make the user experience a smooth one. Maybe OS/2 just makes UI processes slightly higher priority, I don't know, but I find that I run into mouse pauses on even newer Linux systems that I almost never see under OS/2 Warp 4.

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    3. Re:Preemptive multitasking by Wudbaer · · Score: 1

      This would indeed be interesting. What still impresses me is that one was able to format a floppy (for those among us still able to eat solid food: This was a common task back then and not a marveled rarity as it is today) under OS/2 without the system missing a beat. You could forget about that completely under Win 3.x, under 95 the mouse was jerking around and even NT didn't get it right. OS/2 for me was a combination of stunningly brilliant engineering and sheer stupidity (e.g. the single command queue thing for the GUI which bit me in the behind regularly or their variety of registry which totally fucked up the system for me all 4-6 months meaning a re-install). But overall I loved OS/2 until the lack of apps drove me away finally.

  103. Re:at the very least, lets who's licenses block th by Locutus · · Score: 1

    So you don't but I do. Fair enough.

    Regarding KDE Parts, I've heard of it but not looked at it. I'll have to see if they have a replacement for the Bento filesystem, allow all "Parts" to be live/running applications, and provide non-rectangular window frames. But besides the OpenDoc stuff, KDE is nice but it is NOT a replacement for what the WorkplaceShell desktop is.

    It does sound like you would like only existing projects to continue and to continue without any influence from other projects.

    BTW, the codebase for much of the GNU software goes back further than the DOS-era. Not to mention that the OS/2 codebase...... forget it. Nuff said.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  104. Re:Mod parent UP! Also the Microsoft link .... by techfury90 · · Score: 1

    ...except SCO bought all the unix rights from Novell long ago

    --
    I'm friends with the youngest daughter of the former head of the PowerPC division of IBM you insensitive clod!
  105. Re:OS/2 Ahh the memories by bizitch · · Score: 1

    I once developed an application exclusively for Sears on the platform IBM wrote exclusively for Sears called CICS for OS/2. It was mondo bizzaro - but it was kewl ..

    And true - the last Mainframe I saw had an OS/2 controller terminal connected to it. So me thinks that IBM will probably never open source it.

    --
    ---- "Logoff! That cookie shit makes me nervous!" - A. Soprano
  106. Maybe, but a lot of OS/2 key tech is MS-free. by Richard+Steiner · · Score: 2, Insightful

    I think the DOSEMU and DOSBOX projects could derive some serious benefit from OS/2's MVDM technology, for example, and there are a number of concepts in the OS/2 WorkPlace Shell which might be encumbered by NeXT licensing or something but not MS, and which both KDE and GNOME could benefit from.

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  107. Don't do that! Put it on eBay. by Richard+Steiner · · Score: 1

    I check eBay on a regular basis for older commercial OS/2 (and Windows 3.x) applications and utilities, and I'm not the only person I know who does that.

    You might not get a lot for it, but your software sale will probably make someone's day.

    There's a lot of software there that I would love to run but which is almost impossible to (legally) find these days...

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  108. Ah, so you admit there ARE OS/2 users... ;-) by Richard+Steiner · · Score: 1

    I thought I was a figment of my own imagination. :-)

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  109. Re:OS/2 Ahh the memories by DavidTC · · Score: 1
    It's called arbeitsordner in the English version, too. We could never figure out what the hell it was supposed to be.

    j/k

    --
    If corporations are people, aren't stockholders guilty of slavery?
  110. OS/2 has a very nice CLI, too. by Richard+Steiner · · Score: 1

    Particularly these days as JP Software has released their former 4OS2 shell product to the community for free (both source and binaries) and made their 4DOS shell freeware as well (binary-only for now, but the source is likely to be released at some future point).

    Combine that with a couple of additional utilities (HSWITCH and CLIPIT come to my mind immediately), and you've got something which rivals Linux and blows Windows away as a command-line environment.

    There's even a version of Midnight Commander for OS/2, and I use tools like slrn and Links on a regular basis (native versions recompiled using GCC/EMX).

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  111. An OS/2 Trap screen shows a bunch of hex data. by Richard+Steiner · · Score: 1

    Register dumps and the like. I've always wondered why the X screen saver that shows all those obscure (and not so obscure) error screens never had an OS/2 example. It's interesting to look at.

    That said, I haven't seen one for quite a while.

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  112. IBM and OSS by Allen+Zadr · · Score: 2, Interesting
    Actually - I fully agree with you there. A solid half of the Open Source projects they've helped have been to bolster a marketable product. And the rest were likely contributions along the lines of seeing if there was a fit to bolster internal products.

    It's great work, but it does have a smell of insincerity.

    --
    Kinetic stupidity has a new brand leader: Allen Zadr.
    1. Re:IBM and OSS by Anonymous Coward · · Score: 0

      It's great work, but it does have a smell of insincerity.

      I don't know if insincerity is the right word for it. Perhaps unreasonable expectations on the part of the OSS community is more fitting.

      A company, any company, would go out of business if it didn't try to make money... so IBM uses open source to make money and contributes to projects that will make money. What do you expect? They're a company, not a charity. Go ask the United Way for money if you want charity.

  113. Re:at the very least, lets who's licenses block th by snorklewacker · · Score: 1

    It does sound like you would like only existing projects to continue and to continue without any influence from other projects.

    That's not at all what I said. While OS/2's design might have a lot to offer, it's not as if all technology has stood still in the meantime. Meanwhile, OS/2's code would require such a rewrite as to be only a study of a possible "sample implementation" -- to actually port something like Bento to the existing models would require as much skill as it would take to implement it from specification. In the end, the code may in fact be good for little more than such specification, and even it would likely not be a real joy to read.

    And once you have all that out in the open, there's still the matter of whether anyone will actually bother to use it.

    As for non-rectangular, go gripe at X to provide something better than SHAPE, or work on Fresco ... it's certainly a layer well below existing desktop environments, and seems rather unrelated.

    --
    I am no longer wasting my time with slashdot
  114. It makes one wonder, though... by Richard+Steiner · · Score: 1

    ...If Microsoft had such a large part in creating a platform like OS/2 which was lightweight and could handle heavy multithreading smoothly with very little hardware -- why can't they do the same thing with their current offerings?

    I suspect there isn't enough money to be made from a smaller, more efficient system...

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  115. So long and farewell, OS/2 by jmh_az · · Score: 1
    OS/2 version 1.3 was, IMHO, the best small multithreaded OS ever created. Period. Gorden Letwin and his team did an amazing job with it. Those who are interested might want to scrounge up a copy of "Inside OS/2" by Letwin and give it a read.

    IBM's versions, from 2.0 onwards, extended that with better GUI support, real multi-platform interoperability and backwards compatibility. I was an OS/2 developer from 1.0 through 2.1, and a participant in IBM's OS/2 developer's program (I even purchased several big PS/2 machines, very nice for their day, and gave presentations to groups of bored scientists about it). I was also heartbroken when Gerstner pulled the plug on OS/2 and effectively doomed it to obscurity. But, I've since moved on to Linux and FreeBSD, and I haven't looked back.

    If OS/2 was going to be open-sourced, I think the parts of real interest would be the pre-2.0 code and some of the 2.x kernel extensions. But, so far as I know, 1.x is mostly MS code, and will never see the light of day. I don't know if there's enough of the 2.x that isn't legally encumbered to be of interest to anyone.

    It's a pity, though, because it could have been what Windows wanted to be, and Linux could be. But, that could be said for NextOS and BeOS as well. Just because something is a good idea doesn't mean it will enjoy success in the real world.

  116. The best thing of OS/2: TD-Gammon by neves · · Score: 1
    TD-Gammon was the best thing in OS/2. It was a neural network backed engine to play backgammon that disputes with the best players in the world. A research project at IBM that became a killer application (at least a killer time killer application). Read an article about TD-Gammon. Here is the paper of the theory behind it.

    I didn't used OS/2 anymore, but dual booted it for years just to play this great game. It changed the way I play backgammon.

    Slowness and lack of applications were OS/2 weakness, but this is surely something I really miss. Open source it, IBM!!!

  117. Re:at the very least, lets who's licenses block th by atcurtis · · Score: 1

    Wouldn't it be nice to have the WorkplaceShell on GNU/Linux someday? Or even get something like OpenDoc going again. Being stuck with rectangular windows just seems so 1980's. The browser and *nix has shown that small efficient "parts" make a far better, stable, and secure platform


    IBM has already released the source code to OpenDOC - I have downloaded it and stored it a couple of years ago. However it relies so heavily on DSOM and the particular features that DSOM offered (metaclasses and distributed class framework) which "modern" CORBA implementations don't have (IBM unsuccessfully tried to propose those features to the CORBA committee) that it cannot be ported without redeveloping SOM all over again. Also, the Bento object storage library is missing... AFAIK, Apple still uses that technology in Mac OS 10.

    The source code is interesting - it has has a lot of code common to both the MacOS and OS/2 implementation of OpenDOC...

    --
    -- The universe began. Life started on a billion worlds...
    -- Except on one where stupidity was there first.
  118. Cross-licensing issues... by bwcbwc · · Score: 1

    And if you think Posix would cause problems, what about all the cross-pollination between OS/2 and Windows NT? Before their falling out, IBM and Microsoft were heavily sharing code between them, and who knows where Microsoft's fingers reach into. The fact that Windows up to Win XP could support OS/2 HPFS disk drives is one indicator. The DOS emulation code is also likely to contain Microsoft product in it.

    --
    We are the 198 proof..
    1. Re:Cross-licensing issues... by jgiltner · · Score: 1

      NTFS is a modified version of HPFS, that is why NTFS partitions show up as HPFS partitions in partitioning products. I have been told that AIX's JFS is based on HPFS.

    2. Re:Cross-licensing issues... by drsmithy · · Score: 1
      NTFS is a modified version of HPFS, [...]

      No, it's not. NTFS was created from scratch for NT.

      However, there was probably some developer crossover (since Microsoft wrote the original HPFS as well), but HPFS and NTFS really aren't similar at all.

    3. Re:Cross-licensing issues... by drsmithy · · Score: 1
      And if you think Posix would cause problems, what about all the cross-pollination between OS/2 and Windows NT? Before their falling out, IBM and Microsoft were heavily sharing code between them, and who knows where Microsoft's fingers reach into.

      No, they weren't. NT was _originally_ supposed to be the OS that replaced OS/2 on high end systems, but the OS/2 (ie: the ancestor of the OS everyone knows as OS/2) and OS/2 NT (ie: the ancestor of Windows NT) codebases were *separate*. IBM were working on maintaining OS/2, Microsoft were working on "OS/2 NT". After the split IBM was left without a "new" OS, so they had to resume heavy and active development of OS/2.

      OS/2 and Windows NT are not in any way related, except for an old name. NT is not in any way a derivative or fork of OS/2 - you only need to spend 5 minutes devling into the internals of both to see that. Heck, you'd have difficulty finding anything architecturally similar about them at all.

      The fact that Windows up to Win XP could support OS/2 HPFS disk drives is one indicator.

      HPFS was pretty much 100% Microsoft code, I'd say they were entitled to use it in NT :).

      The DOS emulation code is also likely to contain Microsoft product in it.

      Probably less than you'd think.

    4. Re:Cross-licensing issues... by jgiltner · · Score: 1

      Maybe, maybe not. I did a few google searches and found a few sites that had old stories that stated the MS developers took what they learned when the wrote HPFS with IBM for OS/2. So, I may be wrong with "modifed version of", but it was not created from scratch, it is based on concepts they learned while helping create HPFS

    5. Re:Cross-licensing issues... by Anonymous Coward · · Score: 0

      Well that's not what Microsoft told people. (Perhaps they were worried that people wouldn't see NTFS as robust code.)

    6. Re:Cross-licensing issues... by drsmithy · · Score: 1
      So, I may be wrong with "modifed version of", but it was not created from scratch, it is based on concepts they learned while helping create HPFS.

      Right. So do you think Linux wasn't created from scratch by Linux because it was based on concepts he learned while at University ?

    7. Re:Cross-licensing issues... by jgiltner · · Score: 1

      Well I fully expect to get rip'ed for the following, but: So do you think that MS having helped develop, and having the source code for HPFS, did not use any of it in developing NTFS? Heck, when you create a NTFS partition, it uses HPFS as the partition type. As MS controlls FDISK, if NTFS was not based on HPFS, then why would they NOT create a new paritition type just for NTFS? Especially since they created 4 different partition types for Windows 95 new partition types: FAT32, FAT32 LBA, FAT16 LBA, and "Ext'ed" LBA. IIRC: I beleive that Linus started Linux while working on a project using Minix. Although it is documented that he did not use any Minix code in the kernel,it is documented that he ported other software to Linux in order to do development under Linux, like bash and gcc. Do I beleive that Linus wrote the kernel from scratch, yes. Do I beleive that everything in the original distribution was created from scratch, no, he has documented that he ported some components from exsting programs. Now, Linus was an innovator. I beleive that he developed many things from scratch. Most of what MS has in the OS world was purchased or "borrowed" from others.

    8. Re:Cross-licensing issues... by Anonymous Coward · · Score: 0

      Linux wasn't created by Linux at all.

    9. Re:Cross-licensing issues... by drsmithy · · Score: 1
      So do you think that MS having helped develop, and having the source code for HPFS, did not use any of it in developing NTFS?

      I've no doubt that the experience of building HPFS helped them make NTFS, but I don't believe there's any code sharing whatsoever. Mainly because NTFS and HPFS really don't have anything in common apart from sharing the same partition ID (as you note). They're simply too different for one to be derived from the other.

    10. Re:Cross-licensing issues... by mikeoconwarp · · Score: 1

      Both HPFS and NTFS are hard-disk partition type 0x07[IFS] because they are both "installable file systems" on Hard-disk. FAT16/32 are *not* installable file systems, they can't be mounted or unmounted. BTW what did you mean by MS controls FDISK - the powerful, scriptable for CID, [configuration, installation, distribution] OS/2 FDISK has never borne any resemblance to that abortion from MS that couldn't even create more than one primary DOS partition! FWIW, OS/2 since the Merlin convenience Package has not used FDISK - it was superceded by LVM, the Logical Volume Manager that works about 50 times faster than the W2KPro Disk Management Tools! At the time of its introduction OS/2-eCS gained the IBM JFS, downsized from the AIX version - OS/2 version with 2TB file size capability, 2TB volume size and a maximum of 128 volumes per system = 256TB, spannable across multiple physical disks. Mike

    11. Re:Cross-licensing issues... by bwcbwc · · Score: 1

      Right up until Warp was released, IBM and Microsoft were still obligated to share source code with each other, and this code was used in many cases to ensure compatibility. Much of NT came from DEC, but lots of it came from Windows 3.1, and plenty of Windows code made it into OS/2. So I'm not saying NT is a fork of OS/2, I'm saying they have a common ancestor and were exchanging material for some time during their development cycles.

      As far as DOS emulation goes, I should probably have referenced the command line utilities rather than the emulation layer. Many of the utilities were just straight recompiles of the original assembler code to OS/2 obj files, with kludges patched in for things like "format c:". The emulation layer copied a lot of INT 21 code, but you're right that there was a lot more re-writing done in that layer, since it was virtualizing the HW environment. Basically the front end to the virtual DOS session was based on the old DOS code and the backend was where the rewrites had to take place.

      --
      We are the 198 proof..
  119. Microsoft shipped OS/2 1.0-1.3 by HBI · · Score: 2, Informative

    They shipped copies of it for a long time, in fact.

    Here is the launch announcement. Microsoft shipped versions 1.0-1.3, but did not ship beyond that point as the MS/IBM divorce happened around then, culminating with IBM OS/2 2.0.

    HEre are some screenshots. Note that the WLO libraries were apparently included in a product called the "Microsoft OS/2 Software Migration Kit". If one were to have a copy of Microsoft Systems Journal November 1990 -- Vol 5 No 6 then one would have record of this product, which has seemingly vanished off the face of the earth. ;-)

    I had a shrinkwrapped copy in my hands when I worked at MicroWarehouse in 1989-91, so I know it existed then. We had about 40 of them. They weren't selling well.

    People with clue about this are rare in these parts, it appears. It doesn't seem that long ago to me.

    --
    HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
  120. Forget OS/2... we want REXX and SOM by perlow · · Score: 1

    the best elements of OS/2 worth saving are the versatile REXX scripting language (which already exists in some form for Linux, but its not IBM's implementation -- http://www-306.ibm.com/software/awdtools/obj-rexx/ linux/) and SOM, the System Object Model. WPS itself is useless because it would have to be completely rewritten for X and GTK or Qt instead of PM -- instead, a REXX with a GUI implementation for KDE and GNOME, along with hooks into SOM would give Linux the best aspects of OS/2.

  121. Just signed up, but it'll never happen by harris+s+newman · · Score: 0

    It has windows code in it. Won't ever happen.

  122. Apple may not like it opened... by Imposter_of_myself · · Score: 1

    IIRC, some of the GUI technology was licensed from Apple. They may not want to see it licensed. It is/was one of the better GUIs out there. OS/2 RIP

  123. I'm very confused by randyflood · · Score: 1


    Why does it cost $200 for ecomstation? I could see paying like maybe like $50 bucks for this just so I could install it under VMware and play around with it, though I would probably just wait for the Live CD and do it for free... I guess that their target audience is probably businesses that are not price sensitive to the difference between $50 and $200 though. That and there is the perception that if you charge more money for something that it has more value. Like at a garage sale you can have a TV for sale for 5 cents (because you just want to get rid of the stupid thing) for like 4 hours with no one buying it. But if you raise the price to like 50 bucks, someone will come along and offer you 30 bucks for it, and then you can reluctantly agree to take it.

    You know, if they did open the source code up for this, their choice of licenses would make a big difference. Imagine what would happen if they chose the BSD license, rather than the GPL and their OS really caught on. Then Microsoft could incorporate all the resulting code back into Windows, for example.

    On the other hand, if the chose the GPL, and their OS really caught on, maybe lots more Windows developers would be encouraged to also GPL their projects. However, perhaps GPL'ing the code would not even be possible to to the entanglement with other code to which they to not own the licenses. IANAL.

    --
    Randy.Flood@RHCE2B.COM
  124. Re:Mod parent UP! Also the Microsoft link .... by jgiltner · · Score: 1

    What comes around goes around. MS did license Unix from AT&T and created Xenix. However, guess who MS actually outsourced the development to for Xenix. SCO. OS/2 V1.0 was a MS product, infact 1.1 may have been MS also. It was not until 1.2 that it was IBM only. MS and IBM had a falling out and they each took the existing code from 1.1 and went their own merry way. MS wanted to keep "Windows" alive, so IBM got the OS/2 name. Although I never saw this, I have been told that the early releases of Windows NT actually had OS/2 in the error messages.

  125. Revised story submission policy? by Seehund · · Score: 1

    ISTR that stories about petitions would not be accepted, according to the /. story submission guidelines. Has that policy been changed, or do I remember wrong?

    Anyway, there's another OS that desperately needs saving from its owners. :) See my sig and the link below my /. username.

    --
    Help savingAmigaOS and a free PowerPC market
  126. Re:Ah, so you admit there ARE OS/2 users... ;-) by hausmaus · · Score: 1

    > I thought I was a figment of my own imagination. :-)

    Yes, I thought I was too. Same with those other people I talk to on a daily basis that still use OS/2. ;)

    Don't I know you from somewhere? :>

    --
    Your email has been returned due to insufficent voltage.
  127. Re:OS/2 Ahh the memories by maxwell+demon · · Score: 1
    It's called arbeitsordner in the English version, too.

    The same German word? Interesting.

    We could never figure out what the hell it was supposed to be.

    "Arbeitsordner" literally translates to "work folder". It was basically a folder with session management. If you closed it, it automatically closed all files/programs you opened from it (but only those), and re-opened them the next time you opened the folder. Actually the desktop itself was an Arbeitsordner as well. I guess the app had to implement some API for this, because it didn't always work perfectly. But I still consider it a great idea, much better than the usual session management which always has to cover the complete desktop (and in my experience usually doesn't work perfectly either).
    --
    The Tao of math: The numbers you can count are not the real numbers.
  128. You realize that Object REXX is open source? by Anonymous Coward · · Score: 0

    http://www.devsource.com/article2/0,1759,1729098,0 0.asp

  129. We already HAVE that, Doctor Evil by argent · · Score: 1

    Um, even Microsoft managed to figure that one out.

    There's three main ways that personal computer operating systems have implemented multitasking. Round robin timeslicing, preemptive multitasking, and cooperative multitasking.

    Round robin timeslicing is used when the programs being shared are running under a virtual machine of some kind, and have no way to give up the CPU. The old timeslicers for DOS used this, and of course these days your VMware type systems tend to end up in this state when you're running more than one at a time.

    Cooperative multitasking. This is very easy to implement, I did one in Forth that was about 16 lines of code. User-mode threads generally implement cooperative multitasking within a process. It's a kind of "Hello World" for OS design. There's a very short set of systems I can think of that exposed this at the application level. Polyforth. Mac OS. 16-bit Windows.

    That's about it.

    The rest, from AmigaDOS through Mac OS X, even including 32-bit Windows to a pretty great degree, and of course including the NT based Windows and every UNIX implementation ever, they are all using preemptive multitasking.

    If Apple hadn't resorted to cooperative multitasking to avoid facing some bad design decisions back in the original single-tasking Mac OS, and Windows hadn't copied some of those bad design decisions, nobody would even think of preemptive multitasking as being something special. When someone talks about preemptive multitasking being a feature, it's like they're suggesting that putting tires on cares is kind of an exciting innovation. It's, well, it's just how multitasking is DONE.

  130. Deferred updates in the GUI. by argent · · Score: 1

    One thing OS/2 seems quite good at doing is adjusting various process priorities to make the user experience a smooth one.

    I doubt that what you're seeing has anything to do with process priorities or scheduler design. The unfortunate design decisions that have produced the kinds of glitches you see in the current X-based desktop environment are buried much deeper and are harder to fix than simply tweaking the scheduler.

    But, god knows, it could have been worse.

    1. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > I doubt that what you're seeing has anything to do with process priorities or scheduler design. The unfortunate design decisions that have produced the kinds of glitches you see in the current X-based desktop environment are buried much deeper and are harder to fix than simply tweaking the scheduler.

      Its not simply tweaking the scheduler and priorities, its a different design of scheduler and priority management, and indeed one that does a better job at giving the user a nice smooth experience.

      2 factors in this were dynamic priority boosting (a runnable task that had been 'starved' for too long would get its priority boosted untill it became high enough for it to get a timeslice) and the notion of foreground/interactive tasks versus background/non interactive tasks. The interactiveness was not just about the 'nature' of the application, it was more about if it was the one currently having the user focus.

      Together with a rather short context switching time, this helped provide a good starting point for a nice responsive system.

    2. Re:Deferred updates in the GUI. by argent · · Score: 1

      2 factors in this were dynamic priority boosting (a runnable task that had been 'starved' for too long would get its priority boosted untill it became high enough for it to get a timeslice)

      When I started using UNIX back around '78 it had already been doing that kind of priority juggling for so long that you just assumed it was there.

      No, really, it's not the scheduler. Juggling priorities so that interactive tasks get priority over compute bound ones is precambrian. It's not what makes OS/2 and other operating systems that provide good interactive response what they are. Do you want to know what it is? It's the whole GUI design. It's recognising that a GUI is a real-time environment, one in which the time a result is generated is part of whether the result is correct or not. It's taking advantage of the fact that the display is computationally close to the user. It's all kinds of things.

      X11 is not a real-time design. X11 is designed to provide decent display update speed... decent throughput... over networks that have inadequate bandwidth and totally inadquate latency. It's not as good at it as schemes like NeWS (now there's a sweet design) that split the whole user interface away from the heavy lifting and let you run the GUI in a lightweight scripting language in the display server itself... but that's the environment it was designed for. It wasn't designed to give you any guaranteed response time, it was designed to make sure you could get any response at all. By design, it defers and batches transactions. It can deliberately delay updates so it can bundle operations together and send a single packet to the display instead of having to sith through 6 or 8 turnarounds.

      THAT is why now that you have a 2 GHz 64-bit processor and a graphics card that by itself has more CPU power than the whole of Project Athena at MIT did... that is why you can have all that and when things get busy it gets delayed.

      The differences between the design of X11 and OS/2 are so profound that they utterly swamp trivia like a slightly different scheduling algorithm.

    3. Re:Deferred updates in the GUI. by NutscrapeSucks · · Score: 1

      I doubt that what you're seeing has anything to do with process priorities or scheduler design

      I wouldn't be so sure. In Windows, bringing a window to foreground effectively re-nices it to a higher priority. This has been true since NT3.1, and it wouldn't suprise me if MS and/or IBM did the same trick in Presentation Manager.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    4. Re:Deferred updates in the GUI. by argent · · Score: 1

      In Windows, bringing a window to foreground effectively re-nices it to a higher priority.

      And just what the hell does that have to do with whether the mouse pointer tracks or not?

      Yeh, give the interactive task more CPU, that's fine, that's what "nice" is all about, after all. The thing is, though, it doesn't matter in Windows, X11, NeXTstep, AmigaDOS, or, well, anything that isn't a freshman CS cooperative multitasking system... it doesn't matter in any of them whether the foreground task is busy, hung, dead, hung over, stoned, or depressed... it's not the thing that's moving the mouse pointer.

      Got it?

      That kind of deep user interface failure isn't caused by bad scheduling, good scheduling, or bad-cop-good-cop scheduling. It's caused by X11 deciding that this is a good time to let latency go hang. Because it's not a real-time system, and it doesn't give the user interface itself the kind of loving personal hands-on attention that the rest of the GUI based systems do, because that's not what it was designed for.

      That's all.

      That's all.

    5. Re:Deferred updates in the GUI. by NutscrapeSucks · · Score: 1

      I guess I didn't realize we were talking about mouse pointers, or the windowing system rather than the applications.

      FWIW, I think your analysis of X11 is Insightful++, however at least part of Windows applications' percieved responsiveness is due to (pretty smart IMO) scheduler hacks.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    6. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > When I started using UNIX back around '78 it had already been doing that kind of priority juggling for so long that you just assumed it was there.

      When IBM and MS introduced OS/2 in the late 80s, they also filled quite a few pages about why the OS/2 scheduler does really a much better job at those things. They did a much better job at explaining it then I can do, but I have seen enough of both to see that even when it may look like trivial differences, they are in fact a very relevant.

      > No, really, it's not the scheduler. Juggling priorities so that interactive tasks get priority over compute bound ones is precambrian. It's not what makes OS/2 and other operating systems that provide good interactive response what they are. Do you want to know what it is? It's the whole GUI design. It's recognising that a GUI is a real-time environment, one in which the time a result is generated is part of whether the result is correct or not. It's taking advantage of the fact that the display is computationally close to the user. It's all kinds of things.

      Yeah sure, that is why you see the exact thing for non GUI (ie, character based) applications.

      > THAT is why now that you have a 2 GHz 64-bit processor and a graphics card that by itself has more CPU power than the whole of Project Athena at MIT did... that is why you can have all that and when things get busy it gets delayed.
      The differences between the design of X11 and OS/2 are so profound that they utterly swamp trivia like a slightly different scheduling algorithm.

      Its by far not the only thing that matters, putting some limits on how long a task can spend in the kernel while blocking the rest of the system helps as well for example.

      OS/2s GUI is definitely not a well designed one, especially its single message queue is a problemn both for responsiveness and stability. X actually does a much better job there.

      As mentioned before, the same kind of difference can be seen when you eliminate the GUI on both Unix and OS/2, so sorry, your story about how this is all the gui is simply not true.

    7. Re:Deferred updates in the GUI. by argent · · Score: 1

      When IBM and MS introduced OS/2 in the late 80s, they also filled quite a few pages about why the OS/2 scheduler does really a much better job at those things.

      Well, yeh, of course they did. They have to tell you that all their design decisions are great and why they made them. Every major piece of software has lots of very smart people writing lots of copy about why they did the things they did. They're not always right.

      For example, the Amiga scheduler didn't do priority promotion AT ALL, and you could tell, because when you had a background task running at 100% it hurt everything. BUT, the GUI was incredibly fast and responsive, and the pointer tracking never fumbled.

      Yeah sure, that is why you see the exact thing for non GUI (ie, character based) applications.

      You do see the same thing on UNIX for non-GUI applications. Interactive applications are responsive no matter what the CPU load is, so long as the memory load doesn't get so high they're deferred by swapping or excessive paging. Unless you're talking about like that, or you're seeing the behaviour of the GUI around the character mode application (you know, right, that when you run a character application inside an X-term the user interface is still handled by the X11 GUI), you're just plain wrong there. The responsiveness of UNIX character-based applications under excessive CPU loading is phenomenally good. Legendary, even.

      putting some limits on how long a task can spend in the kernel while blocking the rest of the system helps as well for example.

      I'm having another "But, Doctor Evil, that has ALSO already been invented" moment here, but I better stop before I start using sarcasm.

    8. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > Well, yeh, of course they did. They have to tell you that all their design decisions are great and why they made them. Every major piece of software has lots of very smart people writing lots of copy about why they did the things they did. They're not always right.

      Of course they are not always right, I never said so. I just pointed you at the fact that many things have been said about why exactkly the scheduler and priority management of OS/2 was better, you can ignore that and just keep pushing your own little love for Unix.

      You can disagree with what people say, fine, give soem reason, provide some argument, maybe point at an argument already made by someone else. Just dismissing what is being said with 'people say so much' is not going to help being convincing here.

      > You do see the same thing on UNIX for non-GUI applications. Interactive applications are responsive no matter what the CPU load is, so long as the memory load doesn't get so high they're deferred by swapping or excessive paging. Unless you're talking about like that, or you're seeing the behaviour of the GUI around the character mode application (you know, right, that when you run a character application inside an X-term the user interface is still handled by the X11 GUI), you're just plain wrong there. The responsiveness of UNIX character-based applications under excessive CPU loading is phenomenally good. Legendary, even.

      You just go try running anything interactively (and I mean something character based, running in a full screebn console in native character mode, so no X11, no graphics mode WHATSOEVER) on a machine with a load of 20 and without overcommiting memory. I have had that situation on Linux, FreeBSD, Solaris, AIX, HPUX, IRIX, ULTRIX, and ALL of them perform a lot worse under such conditions then OS/2 does with similar load and a VIO app in the foreground. If you don't believe it, please go try it.

      So X11 may add to the problem, but without any trace whatsoever of X11, the problem is still there.

      Unix does a lot better in this then any Windows version, sure, but it did not, and still doesn't do better then OS/2 in this.

      Just to make sure, I am comparing OS/2 in CHARACTER mode, NO GUI running whatsoever, with Unix in CHARACTER mode, so again, NO GUI whatsoever. Please make an argument that does in no way involve X11 can you?

      As a small sidenote, I actually have seen large parts of the code of presentation manager from OS/2 as it was in 1.2, 1.3 and 2.0 (I am a former OS/2 developer), adn I can assure you that it is in no way responsible for the high responsiveness, rather, it was one of the major obstacles to achieving responsiveness.

      So even while your claim about X11 and inefficiency may be true, its not relevant.

      Then, with regards to the Amiga, it is extremely easy to slow it down ot crawling speed and yet have a smooth mouse pointer.. easy becaus that mouse pointer is almost completely handled in hardware, and you do still get interupts. All it takes from there is changing 2 registers.

    9. Re:Deferred updates in the GUI. by argent · · Score: 1

      I just pointed you at the fact that many things have been said about why exactkly the scheduler and priority management of OS/2 was better, you can ignore that and just keep pushing your own little love for Unix.

      My love for UNIX is obviously why I tried to hide how the UNIX graphical user interface is poorly suited to today's desktop clients. Oh, whoops, I didn't, did I?

      Unix [...] doesn't do better then OS/2

      Um, I didn't say it did.

      I am comparing OS/2 in CHARACTER mode, NO GUI running whatsoever, with Unix in CHARACTER mode, so again, NO GUI whatsoever.

      And what exactly are you saying about OS/2 in CHARACTER MODE and UNIX in CHARACTER MODE? I want to be certain here, because way back in this thread I said that the differences between OS/2 scheduler and the UNIX scheduler weren't fundamentally important for graphical user interfaces, and both were doing about the same thing, and you just accused me of saying the UNIX scheduler did better than OS/2. Which isn't something I've said, or attempted to imply... and if I inadvertently confused you, I apologise.

      But, anyway, you see how easy it is to get confused in this kind of exchange, especially when one of us isn't bothering to clearly distinguish between what they're quoting and what they're writing, so I'd really like to be sure that I'm not misunderstanding you like that.

      that mouse pointer is almost completely handled in hardware, and you do still get interupts

      The mouse pointer isn't controlled from an interrupt, it's crontrolled by Intuition, from an ordinary Amiga Exec task.

      And with a modern accelerated video card, the mouse is almost completely handled in hardware too.

      So if the fine details of the scheduler was that important to maintaining the GUI's responsive behaviour, the simplistic scheduler on the Amiga should have been a major drawback. Right?

    10. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > And what exactly are you saying about OS/2 in CHARACTER MODE and UNIX in CHARACTER MODE? I want to be certain here, because way back in this thread I said that the differences between OS/2 scheduler and the UNIX scheduler weren't fundamentally important for graphical user interfaces, and both were doing about the same thing, and you just accused me of saying the UNIX scheduler did better than OS/2. Which isn't something I've said, or attempted to imply... and if I inadvertently confused you, I apologise.

      What I am trying to point out here is that the difference in responsiveness between the 2 stays even when you eliminate the GUI completely. The very simple conclusion is that the GUI may contribute but is not the sole, and not even the primary reason for this difference.

      >> that mouse pointer is almost completely handled in hardware, and you do still get interupts
      > The mouse pointer isn't controlled from an interrupt, it's crontrolled by Intuition, from an ordinary Amiga Exec task.

      I somehow recall this running during vertical retrace, but I may confuse this with the code that handled the pointer in Geos. Regardless, movimng around a hardware mouse pointer is so extremely simple and non intensive for the cpu that any OS that provides some form of preemptive multitasking should be able to handle it without much of a problem, esp. when you can get away by only updating the position between 12.5 and 15 times/sec.

      > And with a modern accelerated video card, the mouse is almost completely handled in hardware too.

      Yes, and on such a card I have yet to see a mouse pointer become jumpy as a response to high system load, Windows, X11, OS/2 PM make little difference there as long as they do indeed support the hardware pointer also.

      > So if the fine details of the scheduler was that important to maintaining the GUI's responsive behaviour, the simplistic scheduler on the Amiga should have been a major drawback. Right?

      No, wrong. try to actually click on something while your Amiga is heavily loaded and see if you get a response.

      While smooth movement of a software generated mouse pointer gives an indication, movement of a hardware mouse pointer gives very little indication of how responsive a system stays under load.

      My original claim was that the OS/2 scheduler and priority management do a better job at keeping the system responsive then a typical Unix scheduler and priority management. This is very clear when using a GUI, and many people (including you) seem to attribte this to the GUI.

      A GUI that employs a single, synchronous message queue for events between the GUI and applications is really not a good way to achieve responsiveness at all, and it is definitely not the reason for OS/2s responsiveness, if anything, it is a problem.

    11. Re:Deferred updates in the GUI. by argent · · Score: 1

      What I am trying to point out here is that the difference in responsiveness between the 2 stays even when you eliminate the GUI completely.

      I find this hard to believe. Did you test this on the same hardware? What version of UNIX were you using? Because I have been using UNIX for a quarter of a century and I can not recall ever finding myself in a situation where a character based interactive application that wasn't blocked on other I/O was effected by any number of background CPU-intensive apps. Ever. Even when the load average is up in the double digits, when there are dozens of programs competing for the run queue, interactive applications autmatically and invisibly get priority.

      I'm sure OS/2 does just as well, there. But I can't see how any change in the scheduler could make it do better than 'it's always got a higher priority'. If you were seeing a difference in behaviour then something else must have been different between the applications or their environment.

      A GUI that employs a single, synchronous message queue for events between the GUI and applications is really not a good way to achieve responsiveness at all

      Actually, a single event queue feeding a single event loop is a very common technique used in real-time control systems, because as long as you can control the latency for each operation you have complete control of the latency for the system as a whole. Having a single queue that imposes virtually no latency of its own is still going to give you a more responsive user interface than multiple queues that deliberately impose latency to increase throughput.

    12. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > I find this hard to believe. Did you test this on the same hardware? What version of UNIX were you using? Because I have been using UNIX for a quarter of a century and I can not recall ever finding myself in a situation where a character based interactive application that wasn't blocked on other I/O was effected by any number of background CPU-intensive apps. Ever. Even when the load average is up in the double digits, when there are dozens of programs competing for the run queue, interactive applications autmatically and invisibly get priority.

      Hrm, I saw this fail on Sun 68k, sparc and hypersparc hardware, and on x86 hardware, Irix on R3000, R4000, R5000, FreeBSD, NetBSD and Linux on a huge variety of x86 hardware (from 386dx to p4 xeon), AIX on a whole variety of RS/6000 machines, HPUX on HPPA and some more. My experience with Unix like systems is some 5 years shorter then yours, but I doubt it is less extensive.

      I only ever ran OS/2 on 386, 486 and classic Pentium machines, and I only ran Solaris (upto 2.6), Linux (upto 2.4) and FreeBSD (upto 4.2) on the same hardware, so direct comparison I can only make between those systems.

      > Actually, a single event queue feeding a single event loop is a very common technique used in real-time control systems, because as long as you can control the latency for each operation you have complete control of the latency for the system as a whole. Having a single queue that imposes virtually no latency of its own is still going to give you a more responsive user interface than multiple queues that deliberately impose latency to increase throughput.

      Of course, and for a very well controlled realtime system this works really well. For a general purpose GUI you cannot control the latency of whatever application the user decides to run, so there it really does not work too well.

    13. Re:Deferred updates in the GUI. by argent · · Score: 1

      Could you, like, indent or italicise the stuff you're quoting?

      Hrm, I saw this fail on Sun 68k, sparc and hypersparc hardware, and on x86 hardware, Irix on R3000, R4000, R5000, FreeBSD, NetBSD and Linux on a huge variety of x86 hardware (from 386dx to p4 xeon), AIX on a whole variety of RS/6000 machines, HPUX on HPPA and some more.

      I'd really like to get you to elaborate on that, because our experience seems to be radically different. Are you talking about a situation where the system was compute-bound, not swapping or paging, and the interactive task was not subject to blocking on a contested resource? I've seen interactive character mode applications become unresponsive in those circumstances, but I can't see how that could possibly have anything to do with the scheduler.

      For a general purpose GUI you cannot control the latency of whatever application the user decides to run, so there it really does not work too well.

      So in OS/2 if your foreground program opened a file and that blocked for half a second because it was on a network file share and competing with the porn traffic, then the GUI as a whole was also blocked until that application responded to a message? What if the app was blocked for a minute? Did the whole thing lock up for a minute?

    14. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > Could you, like, indent or italicise the stuff you're quoting?

      I use the decades old quoting convention from usenet, email etc before there were things like html. Any line starting with a > is quoted text.

      > I've seen interactive character mode applications become unresponsive in those circumstances, but I can't see how that could possibly have anything to do with the scheduler.

      Well, the contested resource was of course the CPU, no swapping/paging.

      Example, bash accepting user input, becomming slgightly sluggish because of cd writing software running in the 'background'. The CD writing software did try claiming 100% cpu time, and most likely also used some other resources. I could also go back ot the 486 that I used to run OS/2 on and still run Solaris on. OS/2 had no problem with keeping a serial link at 57600bps running reliably without any noticable impact on a foreground shell, SOlaris on the same hardware doesn't, anything above 19k2 for the comms app becomes noticable for the foreground app.

      > So in OS/2 if your foreground program opened a file and that blocked for half a second because it was on a network file share and competing with the porn traffic, then the GUI as a whole was also blocked until that application responded to a message? What if the app was blocked for a minute? Did the whole thing lock up for a minute?

      You got it. FOr a nice example of this, try Lotus 123g for OS/2.

    15. Re:Deferred updates in the GUI. by argent · · Score: 1

      I use the decades old quoting convention from usenet, email etc

      At one point around 1990 I was 2 of the top 3 posters on Usenet. My first posts date back to the early '80s. I'm real familiar with ">"-quoting, and if we were using trn with an 80x24 screen with all the lines wrapped on input, that would work nicely. But ">"-quoting doesn't work worth a damn in an environment where you're NOT using a TTY type display.

      Example, bash accepting user input, becomming slgightly sluggish ...

      You do know of course that bash forks and execs for each external command (like ls) and internal commands frequently involve disk I/O as well. In addition, CD burning... particularly on older burners... is a real-time process and good burning software is going to run at an elevated priority... it's more important than the user interface. So you're mixing up CPU, disk, and a high priority background task. Separating the impact of the scheduler out of that is going to be a big problem.

      OS/2 had no problem with keeping a serial link at 57600bps running reliably...

      What sort of serial port, what was the UART? 8250, 16540, 16550? Was the Solaris driver smart enough to use the 16-byte queue in the latter case, or was it taking an intterupt for every character? Again, you're combining all kinds of things that have nothing to do with scheduling.

    16. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      At one point around 1990 I was 2 of the top 3 posters on Usenet. My first posts date back to the early '80s. I'm real familiar with ">"-quoting, and if we were using trn with an 80x24 screen with all the lines wrapped on input, that would work nicely. But ">"-quoting doesn't work worth a damn in an environment where you're NOT using a TTY type display.

      Well, I have no problem with it in a browser either, but since you are the one having to read what I type and have trouble with it, I'll do as you suggest.

      You do know of course that bash forks and execs for each external command (like ls) and internal commands frequently involve disk I/O as well. In addition, CD burning... particularly on older burners... is a real-time process and good burning software is going to run at an elevated priority... it's more important than the user interface. So you're mixing up CPU, disk, and a high priority background task. Separating the impact of the scheduler out of that is going to be a big problem.

      Bash has internal commands as well of course. Also, OS/2 does not suffer from similar inresponsiveness in similar conditions.

      OS/2 puts things requiring realtime priority in a seperate priority class, they are not 'higher' in priority but they are treated differently to ensure they get their timeslices when needed still.

      Basicly, OS/2 has 4 priority classes, each with a number of priority levels (32 if I remember correctly, but this is some time ago).

      How dynamic priority works out depends on the class you are in.

      What sort of serial port, what was the UART? 8250, 16540, 16550? Was the Solaris driver smart enough to use the 16-byte queue in the latter case, or was it taking an intterupt for every character? Again, you're combining all kinds of things that have nothing to do with scheduling.


      16550AFN, 16byte fifo,

      Using a 8250 just makes the problem more prominent.

      And no, I am not mixing up things here. How the system handles interupts, realtime tasks, user tasks, and gives all of them timeslices at the moment they need it has all to do with priority management and your scheduler. That a 8250 generates a lot more interupts then a 16550 is true of course but it applies to both systems (unless of course a system doesn't support the fifo)

      You can do a similar experiment with for example formatting a floppy in the background.

      You are right that there are a lot of aspects to this, but in the end, it is still a matter of how the system distributes time over the processes that are running (or threads in case of OS/2) which is still the task of priority management and the scheduler, and giving the guarantee of a context switch and rescheduling of tasks within a given time (30ms in case of OS/2 with a default configuration, this is tunable by the user)

      Resource congestion? sre, that is the problem we are talkign about, just that the CPU is yet another congested resource.

    17. Re:Deferred updates in the GUI. by argent · · Score: 1

      OS/2 puts things requiring realtime priority in a seperate priority class, they are not 'higher' in priority but they are treated differently to ensure they get their timeslices when needed still.

      Dude, I know about realtime priority. I've been in the realtime business for most of my working life.

      I've used UNIX systems with realtime priority. It doesn't make a difference to interactive response time. It's a great way to lock up the system when a realtime process goes into an infinite loop and becomes a compute-bound process, though.

      I can EASILY believe that OS/2 is doing a better job of handling I/O. That's been a problem with the traditional UNIX monolithic kernel as long as I've used it, but that's got nothing to do with how many CPU-bound processes are sitting there competing with the interactive one.

    18. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      Dude, I know about realtime priority. I've been in the realtime business for most of my working life.

      I have been in OS design and implementation for 2 decades, but really, that is no argument, nor is you having been into realtime stuff for whatever time.

      Then, realtime class != realtime priority. Priority of realtime class processes in handled differently, but is not exactly higher.

      I've used UNIX systems with realtime priority. It doesn't make a difference to interactive response time. It's a great way to lock up the system when a realtime process goes into an infinite loop and becomes a compute-bound process, though.

      And it still will allow decent interactive use on an OS/2 system.

      I can EASILY believe that OS/2 is doing a better job of handling I/O. That's been a problem with the traditional UNIX monolithic kernel as long as I've used it, but that's got nothing to do with how many CPU-bound processes are sitting there competing with the interactive one.

      OS/2 has a monolithic kernel as well, that has nothign to do with this whatsoever.

      The thing that has everything to do with this is deciding which of the processes that is runnable at a given moment gets time. As said before, a realtime class (not priority!!) process can go into an infinite loop and still not prevent an interactive process from being responsive.

      As long as 30ms latency is acceptable, OS/2 is uable for realtime purposes, it GUARANTEES that latency, Unix does not give any such guarantee (tho modern implementations have gotten a lot better at it)

    19. Re:Deferred updates in the GUI. by argent · · Score: 1

      Then, realtime class != realtime priority. Priority of realtime class processes in handled differently, but is not exactly higher.

      Ah, beg pardon then.

      OS/2 has a monolithic kernel as well, that has nothign to do with this whatsoever.

      OS/2's kernel is not really similar to the traditional UNIX monolithic kernel. The original design had no kernel threads at all, let alone any way for a driver to schedule any, and virtually all traditional UNIXes (including Linux) use the same model today.

      The thing that has everything to do with this is deciding which of the processes that is runnable at a given moment gets time.

      We're not talking about processes competing against processes, we're talking about processes competing against device drivers. UNIX device drivers are not processes, tasks, or threads, and they are not scheduled, they are not handled or managed by the scheduler. The interrupt handler (lower half) triggers what's effectively a "software interrupt" that handles the longer term operations in the kernel context but doesn't normally involve a switch to a different process context. The scheduler doesn't "see" the driver at all.

      Fixing that is a problem that would need to be dealt with before any change in the UNIX scheduler could have any effect on contention between I/O and CPU.

    20. Re:Deferred updates in the GUI. by SillyNickName4me · · Score: 1

      > OS/2's kernel is not really similar to the traditional UNIX monolithic kernel. The original design had no kernel threads at all, let alone any way for a driver to schedule any, and virtually all traditional UNIXes (including Linux) use the same model today.

      Of course they are different but both are monolithic (which has very little to do with this really). You are right of course that they are different in design in many ways, and one major difference is indeed in the area of threads. In OS/2, threads are the only things that can be scheduled. Processes own resources, but strictly spoken, they can't be executed, they have one or more threds of execution. SO in case of OS/2 it would indeed be threads competing for cpu time.

      > We're not talking about processes competing against processes, we're talking about processes competing against device drivers. UNIX device drivers are not processes, tasks, or threads, and they are not scheduled, they are not handled or managed by the scheduler. The interrupt handler (lower half) triggers what's effectively a "software interrupt" that handles the longer term operations in the kernel context but doesn't normally involve a switch to a different process context. The scheduler doesn't "see" the driver at all.

      Yep, but this is quite a chicken/egg problem. If your scheduler cannot handle threads (as in, use threads as the basic unit of execution, regardless of what context it is executing in) then handling interupts in a different way is not that easy. On OS/2, threads are the only unit of execution, if something runs it must be in a thread, even if that is an interupt thread. Actually, there is a Unix like system which does this in a very similar way nowadays, take a peek at FreeBSD 5.x and its interupt threads.

      At any rate, you are of course right that there is more to it then just a scheduler and priority management.

  131. Re:Most ATM's use OS/2. Still want to open source by agrisea · · Score: 1

    There has been a trend in the past five years or so to migrate to ATM's running either windows [shudder] or Java-based terminals.

    I know that Wells Fargo replaced most if not all of their ATM's with windoze-based terminals a couple of years ago.

    --
    Agrisea Tsunami - Epyc Servers... https://agrisea.net/products
  132. Re:Ah, so you admit there ARE OS/2 users... ;-) by Richard+Steiner · · Score: 2, Funny

    Uh oh... I'm being followed. :-)

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  133. Re:Mod parent UP! Also the Microsoft link .... by SillyNickName4me · · Score: 1

    Microsoft did distribute OS/2 commercially upto version 1.2 or 1.3. Both as a standalone product, and together with MS Lan Manager.

    They never commercially sold a 32bit version however.

  134. not exactly by ^Z · · Score: 1

    Points 1 and 2: Rewriting a closed system can be pointless, since you'll not be able to distribute it. Opening up the API alone would be a worthy thing. But release of the entine WPS sources would be 10x as nice.

    Point 3: You know, some people choose *not* to run KDE or Gnome, and stick to XFCE or GnuStep or some other lightweight desktop, even on high-end machines. There *is* a demand for a functional desktop environment which is simpler and lighter than KDE/Gnome. WPS can actually turn out to be *richer* than these ;)

    --

    Computers make very fast, very accurate mistakes

    1. Re:not exactly by LordNimon · · Score: 1
      Rewriting a closed system can be pointless, since you'll not be able to distribute it.

      I think the developers of Wine would disagree with that.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
  135. Re:Mod parent UP! Also the Microsoft link .... by SillyNickName4me · · Score: 1

    > OS/2 V1.0 was a MS product, infact 1.1 may have been MS also.

    Both 1.0 and 1.1 were made and sold by MS and IBM. Microsofts involvement declined after that, but they did also at least release 1.2. I am not sure about 1.3, tho I am very shure they could have released it at the time with the agreements as they were.

    A part of OS/2's code, and quite a bit of its design can be found back in NT, and earlier NT versions had enoufh OS/2 in them to be able to run many character based (VIO) OS/2 applications.

    How do I know? I was part of IBM's OS/2 development efford from 1989 till 1996.

    > It was not until 1.2 that it was IBM only. MS and IBM had a falling out and they each took the existing code from 1.1 and went their own merry way. MS wanted to keep "Windows" alive, so IBM got the OS/2 name. Although I never saw this, I have been told that the early releases of Windows NT actually had OS/2 in the error messages.

  136. Re:at the very least, lets who's licenses block th by Locutus · · Score: 1

    ah, that does ring a bell. OpenDoc on Mac was delayed because of the time/effort porting SOM( DSOM? ) to the platform.

    It does sound like KParts( KDE ) is probably the best place for any current progress of the concepts OpenDoc once implemented. Apple keeping Bento sounds about right if they saw a continued use for it.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  137. Now 3815 by Anonymous Coward · · Score: 0

    Petition Results
    The total number of registrants for this OS2 petition: 3815

    Thank you jenet pelly, your registration was successful.

  138. HOW the WPS could be licensed by Anonymous Coward · · Score: 0

    I too am someone who used OS/2 for everything from manufacturing tool controlers to reading e-mail and looking at excel and 123 spreadsheets's.

    Having said, the tool controllers worked well most of the time (minus the SIQ) and for reading email it was crummy, but I blame that on the Lotus Notes port as we all know. Same goes for excel and Office stuff.....

    The way OS/2 and WPS (Workplace Shell) worked for me so great as a developer was the simplicity of the GUI powers. The right click functions of the menubar were powerful for the time. Moving files to folders was as simple as right clicking a file and browsing to the folder, all in one mouse 'click.

    In fact, perhaps that's the licensable part of the WPS! It's the options it gave you, not necessarily the code that's running it (providing the reverse_engineered version would work as well).

    I use OSX now, and i like the dock because it reminds me of OS/2 in some ways, but it doesn't work like it should (to my OS/2 part of the brain).

    Perhaps Apple should license OS/2 ;-)

  139. OS/2 vs Windows vs Linux by NullProg · · Score: 1

    Don't try this at home unless your ready for system lockups.

    Tools required:
    Windows 2000+, Linux 2.4/2.6 and OS/2 Warp4

    1) 3 CDROMS containing Windows/Linux/OS2 OpenOffice Install.
    2) Network sever containing GCC install program for all three OS's.
    3) Preferably a floppy install program for all three, but I think a browser based download of java for all three will suffice.

    Pre-Start your network share to the gcc shared drive. Pre-Start your download link to Java. Pre-Start solitarire.

    Start all three installs at once.

    My findings were OS/2 done in ten minutes with acceptable performance with solitaire. Linux was very sluggish and couldn't draw cards (sol), took about thirty minutes. Windows didn't even finish, the system was unresponsive.

    Oops. Your not supposed to publish windows benchmarks without the written consent of Microsoft. I'm sorry.

    Same computer, AMD/K62 256k ram.
    Your milage may vary and I havent tried this with Windows XP. Is this an acceptable test? Mostly it's something I do whenever I install a new system. Looking forward to trying this out on my wifes new Apple.

    Enjoy,

    --
    It's just the normal noises in here.
  140. Open-Source is good. by SphericalCrusher · · Score: 1

    I never was a big OS/2 fan, and even by today's standards, it's not an advanced operating system. But, in my opinion, I believe that if it were to be open sourced, a lot of fans of it would take interest and work on it more, greatly improving it.

    I would love to take a look at the source code to see what makes it run. It's old, but it runs well!

    --
    "Instant gratification takes too long." - Carrie Fisher
  141. Technical reasons only? by Magic+Thread · · Score: 1
    The CPL is a very nice license, simular to the LGPL in what rights it gives to the user, and the FSF has no philosophical objections with it. However it is not compatable with the GPL for technical legal reasons.
    If what you say is true (and from a quick perusal of GNU's licenses article it seems to be), perhaps GPLv3 can be designed so it will be compatible?

    The language used on the licenses article is:
    "For example, it requires certain patent licenses be given that the GPL does not require. (We don't think those patent license requirements are inherently a bad idea, but nonetheless they are incompatible with the GNU GPL.)"
    This is similar language to that used for the Apache Software License 2.0. With any luck, version 3 of the GPL can be designed to make both compatible.
  142. That's very good! by Anonymous Coward · · Score: 0

    This story is very accurate. I was there (on the IBM side). HPFS was written mainly by Gordon Letwin at MS, in 32-bit Intel assembler. It won the bake-off. Then it had to be rewritten in C by IBM for OS/2 in 16-bit mode. So we called the OS/2 file system HPFS and renamed Gordon's code to HPFS386.

    The only *minor* correction is that MS doesn't "license HPFS386", it was shipped as part of MS LAN Manager on OS/2, and included in the IBM OS/2 LAN Server product, which was a derivative of MS LANMAN.

  143. Re:OS/2 Ahh the memories by mrselfdestrukt · · Score: 1

    I haven't touched C/C++ in 6 years and I'm ready to volunteer.

    Uuhhm, it's ok. We'll do it. We still use it on a regular basis.

    --
    "I used to have that really cool,funny sig ,but it got stolen."
  144. Re:OS/2 Ahh the memories by The+OPTiCIAN · · Score: 1

    > Well, according to their web page, the
    > ReactOS people actually plan an OS/2
    > subsystem.

    There's been an os/2 subsystem in NT since (I think) 3.50, but it only runs applications designed for OS/2 v1. I assume they did this because a lot of banks had apps on os/2 v1 and they wanted to be able to pick up the business. And because they could - being involved in the project as they were.

    I never used it but believe that OS/2 v1 was a lot smaller and simpler than 2. Less APIs and no Program Manager (or else a vastly different and almost unrecognisable PM from the one shipped with v2.0 and advanced through later versions)

    --


    Believe with me, my saplings.
  145. Name, not an algebraic equation?! by Anonymous Coward · · Score: 0

    OS/2 is a *NAME*? Oy vey... all this time, since working with it, I was absolutely positively certain that it was an incomplete algebraic equation... Something about half of an OS, not quite there :-)

    I suppose they went with OS/2 rather than OS * .5 because it sounded cooler?

  146. You are not up to date by krischik · · Score: 1

    REXX is open source since about 12.2004. Only the RexxLA haven't made a release yet

    1. Re:You are not up to date by Anonymous Coward · · Score: 0

      I'd also contend that you are not up to date ;-) ooRexx; the Open Object Rexx project made its first public release on March 25, 2005. See the ooRexx home page for details of the release and the status regarding an OS/2 release of ooRexx.

  147. Maybe it's funny... by Anonymous Coward · · Score: 0

    Because that improper English suggested some latent wordplay?

    ...T'ain't gonna happen 'cause they tainted the code...

  148. Febuary by CableModemSniper · · Score: 1

    At least they can spell the names of the months...

    --
    Why not fork?
  149. Re:OS/2 Ahh the memories by Anonymous Coward · · Score: 0

    OS/2 1.3 had PM. Prior to that, OS/2 was completely command-line. OS/2 2.0 was the first of appearance of the WPS (which ran atop the Presentation Manager).

  150. Re:OS/2 Ahh the memories by Gr8Apes · · Score: 1

    WPS was awesome, although slow if not properly programmed for. (Well, slow in some ways, but still beats the pants off of NT/2K/XP today in responsiveness while running good programs. I don't recall waiting for my mail to finish downloading mail from the server before I could do something else)

    Actually, it'd be interesting to see how OS/2 stacks up today. A 10 year old OS on modern hardware, provided it loads. (Most likely not, drivers were a pretty big issue, but I still have some of the older hardware lying around that may allow it to run with a modern OS. Would depend mostly on motherboard BIOS compatibility, the rest should work)

    As for features, we're finally getting some of those features released in the newer OSes out today. (Not from MS though;)

    --
    The cesspool just got a check and balance.
  151. Re:OS/2 Ahh the memories by Gr8Apes · · Score: 1

    The OS/2 subsystem was dropped by 2K, I believe, definitely by XP. It could be re-installed under the initial dropped OS, but I do not believe current versions of XP will run it any longer.

    v1.x was 16 bit, until 1.3, I believe. MS had source to OS/2 code up to 1.2, 1.3 was 100% IBM. IBM took over because MS and IBM had a technical disagreement about the direction of the OS. MS went with Windows, the successful and oh so well-architected system, while IBM completed OS/2, with a much better architecture but encumbered by far too many royalty payments to be competitive.

    The $86/copy paid to MS pretty much guaranteed OS/2's death when OS prices fell under $100, IBM didn't help matters any by being schizophrenic regarding this PC OS that actually infringed into their big iron mainstays as PC hardware improved.

    --
    The cesspool just got a check and balance.
  152. Yes, it's EMX. by Richard+Steiner · · Score: 1

    More information on EMX is here if anyone's interested...

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  153. There are certain advantages to caves. :-) by Richard+Steiner · · Score: 1

    The temperature is more stable all year around than it is in the outside world.

    Also, it's harder for those nasty spyware authors to find you. :-)

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  154. The actual English term... by Richard+Steiner · · Score: 1

    ...for that OS/2 folder attibute is "work area". It can be very useful for things like development environments and such where you might want to open and close multiple files or programs as a set.

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  155. VDMs didn't use a real DOS kernel (by default). by Richard+Steiner · · Score: 1

    You *could* boot a real DOS kernel in a VDM (or many other real-mode OSes like CP/M) from a diskette image using a method called a "virtual Machine Boot), but the default VDM setting was to use a virtualized DOS kernel interface (no real DOS present, just DOS-like hooks into OS/2 services).

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
    1. Re:VDMs didn't use a real DOS kernel (by default). by Locutus · · Score: 1

      That is right, and a cool feature. I had forgot about that.

      It reminds me of when my boss spent the entire morning trying to load MS FlightSimulator on his Dos/Windows 3.x PC and was cussing up a storm because he couldn't get it to work. Stuff about unloading devices in the config.sys were screwing him up. I had OS/2 running on an AMD 386/40 machine I brought in from home( no way I was going to work on a VT screen! ) so I asked for the install disks. He said there is no way I'd be able to get MS FlightSim working on OS/2. After all, he said, this is MS DOS, MS Windows, and the flight sim if from MS also. A couple of clicks to create a new DOS VM icon, change a couple of VM properties, and then install MS Flight Simulator. Ten or fifteen minutes at most and I was flying around the airport.

      I didn't need the boot a DOS disk( I did do that a handful of times ) but it kinda shows how good OS/2's DOS compatibility is, and how configurable it is too.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  156. What is this UNIX thing anyway? by argent · · Score: 1

    At any rate, you are of course right that there is more to it then just a scheduler and priority management.

    Which I think is where I boarded this train...

    I'll just say one thing about what UNIX is. UNIX is not Thompson and Ritchie's source tree, UNIX is a family of operating systems that provide a common core set of system calls as their native API. FreeBSD is UNIX. Linux is UNIX. OS/9 and QNX and Regulus are or were UNIX. Interix is a hosted UNIX.

    UNIX-like? You have to dig pretty far these days to find an OS that isn't UNIX-like, that hasn't mined UNIX heavily for its design. Wherever your file system is a directed graph, wherever file names are simple strings with no internal structure, wherever files are a simple stream of bytes, wherever you use the same system calls for all files, wherever the shell is just another program, there's another system that's borrowed from UNIX. Because all these things were controversial innovations that UNIX was mocked for using, they were slapdash lazy ideas that real operating systems with structured disks and structured files and user areas and monitors and job control languages would never consider. Creating processes willy-nilly? Inefficient! Flat files? No record management services? Never catch on!

    OS/2 is a UNIX-like OS, so are NT and BeOS and AmigaOS and, well, you have to go back to VMS or look in an IBM dinosaur pen for something that isn't.

    1. Re:What is this UNIX thing anyway? by SillyNickName4me · · Score: 1

      Which I think is where I boarded this train...

      Hrm, you seem to have started out by claiming it is NOT the scheduler and/or priority management but a different GUI design. I never claimed it is exclusively the scheduler or priority management, but that they play an important role in this.

      I'll just say one thing about what UNIX is. UNIX is not Thompson and Ritchie's source tree, UNIX is a family of operating systems that provide a common core set of system calls as their native API. FreeBSD is UNIX. Linux is UNIX. OS/9 and QNX and Regulus are or were UNIX. Interix is a hosted UNIX.

      I don't think I ever claimed Unix to be the T&R source tree. That I do not call FreeBSD a UNIX has a lot to do with what can officially be called UNIX. It is however genetically spoken a UNIX of course. Linux is a UNIX like system because it implements virtually the same API, however, it is not UNIX (both according to its maker and to those who actually can certify it as being UNIX)

      OS/2 is a UNIX-like OS, so are NT and BeOS and AmigaOS and, well, you have to go back to VMS or look in an IBM dinosaur pen for something that isn't.

      Your definition of UNIX and UNIX like seem to be rather loose ones, and entirely different from how those words are used by virtually everyone in the field.

      Just to recapitulate:

      Solaris, AIX, HPUX, IRIX and quite a few others are 'trademark' UNIX, they have passed the appropriate tests, and can officially be called UNIX.

      FreeBSD, OpenBSD, NetBSD and a few others can be called 'genetic UNIX' because they derive directly from the original UNIX 'family tree'.

      Linux on the other hand is a UNIX like system, it does not share a common origin with any of the above mentioned systems, but it implements a very similar set of interfaces and shares many design aspects.

      While I'd agree about AmigaOS, and don't know about BeOS, I do not regard OS/2, NT and for example DOS as Unix like systems. You are right that they do share some things with Unix, but they are quite different with regards to their design and behavior for a programmer, systems administrator and an end-user. Specifically, the 'everything is a file' idea does not apply to those, redirection works entirely differently, the programming interfaces are different etc.

      Similar in specific aspects? sure. UNIX like? I don't think so unless you have a very broad definition of what UNIX like means.

    2. Re:What is this UNIX thing anyway? by argent · · Score: 1

      Linus has been quoted as saying that once hd had the file system, cheduler, and device drivers he had the core of a UNIX system.

      UNIX is anything that can be treated like a UNIX system. That's a functional definition of UNIX, and it's a useful definition. "Trademark UNIX" versus "genetic UNIX" versus "Linux" isn't useful because there have been systems that are "Trademark UNIX" that are less capable of being treated like a UNIX system than any version of Linux. "Trademark UNIX" and "genetic UNIX" ceased to be a useful definition of UNIX by the early '80s, because you could buy systems that were more compatible with System III (the first real AT&T commercial Trademark UNIX) than real Version 6 or Version 7 UNIX was.

    3. Re:What is this UNIX thing anyway? by SillyNickName4me · · Score: 1

      UNIX is anything that can be treated like a UNIX system. That's a functional definition of UNIX, and it's a useful definition. "Trademark UNIX" versus "genetic UNIX" versus "Linux" isn't useful because there have been systems that are "Trademark UNIX" that are less capable of being treated like a UNIX system than any version of Linux. "Trademark UNIX" and "genetic UNIX" ceased to be a useful definition of UNIX by the early '80s, because you could buy systems that were more compatible with System III (the first real AT&T commercial Trademark UNIX) than real Version 6 or Version 7 UNIX was.

      Well, that way of looking at it works of course. Claiming however that systems like OS/2 or NT are 'UNIX like systems' is not. It is like claiming reptiles are dog like animals since they happen to have 4 legs, a tail, brains and such. 'X like' is defined as much by similarities as by differences, and those systems have too substantial differences when compared to UNIX to call them UNIX like. They do of course share a bunch of things with UNIX, and are more similar to it then say VMS.

      Calling Linux a UNIX? hmm, we can argue about that, but I can see the argument for that claim.

    4. Re:What is this UNIX thing anyway? by argent · · Score: 1

      It is like claiming reptiles are dog like animals since they happen to have 4 legs, a tail, brains and such.

      I haven't explained the distinction I'm making well enough, because if I had you wouldn't have drawn such a broad analogy. I apologise for that. Still, there's the beginnings of a useful analogy there... so let me run with it.

      Some reptiles were dog-like animals because they share characteristics with dogs, as a result of fitting into the same ecological niche, that they can usefully be described as dog-like animals to distinguish them from reptiles that doen't share those characteristics. For a specific example, one dinosaur has the name "cynodont" or "dog-jaw" because its jaw resembles a dog's jaw as much as a dinosaur's jaw can be expected to. It's described as a "dog-like dinosaur".

      Now this doesn't say there's any genetic relationship between these dinosaurs and dogs that's not shared by other mammals. It's just a useful distinction.

      So when I say a system is "UNIX-like", that doesn't mean it's genetically related to UNIX, or that that's the only what to describe it, it just means that it's useful to describe it as "UNIX-like".

      There are operating systems that are not "UNIX-like". VMS isn't "UNIX-like". If you open a file in VMS, read it as a stream of bytes, and write it out again, you can't expect that the new file to actually be the same as the old file. That's because a VMS file is a set of records, not a stream of bytes. In NT, you expect that will work. You can construct scenarios where it won't work, but you can do that on UNIX too (for example, what if the file is an executable... the copy won't have the execute bit set)... but in general that's the way files work in NT. That's a UNIX-like characteristic.

      File name is an unstructured string? UNIX-like. I can't think of a single operating system before UNIX where the only restriction on the characters in the unqualified name of a file is that they can't conflict with other parts of the fully qualified file name.

      File system is a directed graph? UNIX-like. This actually originated in Multics, but why is Multics as well known as it is? Because UNIX borrowed ideas from it.

      The shell is just another program? UNIX-like. Back when UNIX was developed, this wasn't even seen as a good idea, let alone common.

      Put enough features like these together and you have an operating system that you can deal with as if it was UNIX and you'll mostly get away with it, even if you're dealing with files created by programs that don't use the UNIX-like features of the OS.

      Another way to think of it is to consider Kernighan and Plauger's book "Software Tools". The operating systems that share the characteristics I'm talking about can be treated as a native "Software Tools" platform. Not only can you run "Software Tools" programs on a UNIX-like system, but you can usually ignore the fact that there's other ways to interact with the system. You'll miss out on a lot of the features of the system, but you rarely forced to deal with them.

      And the whole point of "Software Tools"? Creating a UNIX-like environment on a non-UNIX-like system. So if the native environment of the system is that kind of UNIX-like environment, what does it tell you?

      Why, that it's useful to talk about it as a UNIX-like system.

      That's not the only way to describe it, of course. And it limits you. But it's still a useful distinction.

      We can argue about that, too, but I think you can play the rest of the discussion out in your head, no?

    5. Re:What is this UNIX thing anyway? by SillyNickName4me · · Score: 1

      I haven't explained the distinction I'm making well enough, because if I had you wouldn't have drawn such a broad analogy. I apologise for that. Still, there's the beginnings of a useful analogy there... so let me run with it.

      I think my point was that when you only (or mostly) look at similarities, you can see things as being alike, while they do have differences that are so relevant that when looking at the bigger picture and take into account the differences, they are not alike.

      NT, OS/2, UNIX and quite a few other systems are similar, and more similar to eachother then they are to say OS/390, VMS and such.

      Yet, NT as well as OS/2 behave more like DOS then UNIX in many aspects. I would not call them DOS like operating systems hwever because the differences between them and DOS are more relevant then the similarities.

      Calling OS/2 an NT like system? I can see the point of that.

      Saying that OS/2, NT and UNIX are all part of a group of similar operating systems? I can see the point of that.

      Calling OS/2 and NT UNIX like? well, in case of NT you can make an argument since it at least officially is supposed to be posix complient, OS/2 is not, and as a result doesn't even try to implement a similar interface, it just happens to share some functionality and implements certain things in a similar way.

      I made the overly broad analogy exactly because I consider you calling them UNIX like system to be overly broad.

    6. Re:What is this UNIX thing anyway? by argent · · Score: 1

      I think my point was that when you only (or mostly) look at similarities, you can see things as being alike, while they do have differences that are so relevant that when looking at the bigger picture and take into account the differences, they are not alike.

      I absolutely got that. That's why I used an example of a dinosaur that really, truly is described as a "dog like animal". It's a dinosaur! It's different from a dog in so many ways that it makes NT and Xenix look like cousins. If a dinosaur (instead of a big cat or even a marsupial) can be dog-like, then it seems that using the "whatever-like" term to describe something that's only "whatever-like" in some particular area is no big deal.

      And it absolutely isn't.

      I'm saying that NT, OS/2, and UNIX are all members of a group of operating systems that can be used in the biggest "ecological niche", if you will, that UNIX created and that UNIX usually occupies. This isn't the same as the "it's got a POSIX interface" niche, VMS has had a POSIX interface so long I've forgotten when it showed up. IBM's MVS has a POSIX interface, for Watson's sake.

      The difference is this: if you go poking around in the system doing UNIX type things on a non-UNIX-like system with a POSIX interface you'll end up either finding yourself locked out of lots and lots of files all over the place, or you'll accidentally trash files so that native applications can't make head nor tail of them. If you do that in a UNIX-like system, well, you can pull stuff out of the native environment, do UNIXy things to it, toss it back out again right on top of the original native file, and it's totally OK to do that because it won't break anything.

      And that's a really cool thing to be able to do, and you need a UNIX-like operating system to do it. Trust me, do that anywhere you please on VMS and you're going to end up in a world of hurt eventually. I've done that.

      The really really amazing thing, then, is that this kind of interface has become so common and so universal that you're saying things like it just happens to share some functionality and implements certain things in a similar way.

      You're absolutely right. That's exactly what it means. And it's so amazingly amazing that I've completely forgotten where my towel is, because thirty years ago people were willing to spend weeks typing in FORTRAN and RATFOR code from "Software Tools" because that was the only way in the entire world to get a system that happened to share that functionality and implement things in that certain way.

      Really.

      I did it. And it gave me a system that was so much better than the one I was using that when I showed one of my co-workers how I could call a program from the editor command line and pull the results back into the editor buffer he was completely blown away.

      Completely.

      If UNIX hadn't existed, nobody would be doing that. Oh, eventually, in a GUI, yes, but not from the command line. UNIX gave you about as much of teh same kind of power that a good GUI gives you, and it gave you that power on the command line, in any program you wanted, including the shell.

      Having that in the shell, HAVING a shell instead of a monitor, all the other stuff I listed? That's the stuff that MADE UNIX into this totally awesome environment, and having that awesome environment in EVERY OS is just so insanely cool that... I guess if you haven't had to struggle with what we had before it maybe you'll never see it.

      I guess that's why when I get "it's totally amazing that every major OS out there is UNIX-like" you get "he's just talking about every OS out there. Why does that make them UNIX like?".

      And the fact that contrast exists.

      Zowie.

    7. Re:What is this UNIX thing anyway? by SillyNickName4me · · Score: 1

      And that's a really cool thing to be able to do, and you need a UNIX-like operating system to do it. Trust me, do that anywhere you please on VMS and you're going to end up in a world of hurt eventually. I've done that.

      And I have seen the same kind of problems on OS/2 and NT, where you get this nice thing of applications being made aware of changes to files without the need of something like FAM, and where using a file (read or write) locks it and prevents other processes from changing it while you work with it (something that can be done on UNIX like systems, but is not automatic there).

      Lets not forget that in UNIX a file is in fact not represented by a name, that name is merely an index pointing to the file. It is represented usually by an inode. OS/2 nor NT have this concept .

      Try removing a file that is being used, and see how UNIX like systems keep the inode (ror similar in case of say XFS filesystems) around untill you stop using it, whereas OS/2 and NT will refuse removing the file and give an error.

      There are many assumptions that you can make about the behavior of a 'UNIX like' system that will simply break on both OS/2 and NT and those are not far fetched things, they are extremely common things

      Are they more like UNIX then VMS is? probably, alltho people have made a very strong argument for NT being a VMS like system.

    8. Re:What is this UNIX thing anyway? by argent · · Score: 1

      You're talking about things that are extremely common on traditional UNIX systems. But they're not universal even there (see what happens if someone deletes a file you've opened over NFS), and they've never been even common in UNIX-like environments on non-UNIX-like systems.

      I'm talking about things that a UNIX-like environment has to have to be a UNIX-like environment. Things that have to be emulated to create an environment where the "Software Tools" approach can be used. They're things that are fairly easy to emulate, in some cases, but they have to be there.

      So, when I'm talking about a UNIX-like system, I'm talking about a system where all the things you need for a UNIX-like environment are already there in the native environment. That native programs are already naturally expecting.

      Forty years ago, there was no system that provided more than one or two, at the most. Most didn't provide any, and many of these characteristics didn't exist in any system.

      Thirty years ago, there was only one system that provided them all, and when you put them together the result was an environment that was so profoundly different from every other environment that it wasn't just like a new language for people to use when they interacted with computers, it was like a new kind of language.

      The GUI was the same kind of profound change, but the GUI was a new kind of language that a computer had to be born to run. This one wasn't just new, but you could have it on the computer and operating system you already had. People implemented UNIX-like environments on top of every operating system that could conceivably support one, and that turned out to be just about every operating system you could sit down at a keyboard and use.

      Let's say that I was an Esperanto enthusiast. Let's say I learned Esperanto 30 years ago. Let's say that I was talking to someone who was so used to the fact that everyone spoke Esperanto that the idea that "native Esperanto speaker" was a useful concept not only passed him by... but it kind of pissed him off that I was using the word "Esperanto" when I described a native Esperanto speaker. He'd say things like "Yes, he's an Esperanto speaker, but he's also a physicist" and I wouldn't even understand why that was part ofthe discussion.

      That's only a metaphor, yes, but that's the same kind of experience as the one I'm having right now.

    9. Re:What is this UNIX thing anyway? by SillyNickName4me · · Score: 1

      That's only a metaphor, yes, but that's the same kind of experience as the one I'm having right now.

      Well, it is an interesting one, and I can see your point of view.

      To make a counter metaphor, to me it feels like you are arguing that since English (with a bit of variation here and there) is spoken in the UK, USA, Australia and many other places over the world, we should just regard them as similar countries.

    10. Re:What is this UNIX thing anyway? by argent · · Score: 1

      since English (with a bit of variation here and there) is spoken in the UK, USA, Australia and many other places over the world, we should just regard them as similar countries.

      Not quite, try this one:

      since English (with a bit of variation here and there) is spoken in the UK, USA, Australia and many other places over the world, we should regard them as English-speaking countries.

      Do you see the difference that removing the word "just" and replacing "similar" with "English-speaking" makes? And try this one on:

      since English is widely spoken in the UK, USA, France, and Mexico, we should regard them as English-speaking countries.

      You wouldn't call Mexico an "English-speaking country", even though you may not need to deal with that as long as you stay in the "English-speaking environment" of the hotel.

      I don't want to drag this metaphor out too far, but thanks for providing an analogy that helped me understand what my point looked like from your side of the screen.

    11. Re:What is this UNIX thing anyway? by SillyNickName4me · · Score: 1

      Yep, looks like you completely understand why I was having difficulty with the point you were making.

      Was nice discussing with you, good to see that while we disagree maybe, we can still get to understanding eachothers point of view.

  157. Re:OS/2 Ahh the memories by Anonymous Coward · · Score: 0

    For the most part modern hardware isn't a problem... mostly will run on anything Linux will. The only real issue is ACPI and that is being worked on by Serenity Systems
    http:\\www.ecomstation.com

  158. One last comment on the GUI... by argent · · Score: 1

    Hrm, you seem to have started out by claiming it is NOT the scheduler and/or priority management but a different GUI design.

    I said that the GUI design had a much much bigger impact on the responsiveness of the user interface than the scheduler. Now we've talked about the drivers, I'll say that things like the GUI design and the driver architecture have a bigger impact on the responsiveness of the user interface than the scheduler. It's not exactly the same conversation, but it's a parallel point (pardon the geometrically inexact metaphor there).

    A synchronous event loop causes other problems, but it doesn't add latency that doesn't exist in the underlying programs. A message queue that deliberately buffers and defers operations so it can bundle them to improve throughput does.

    And adding latency to a user interface, even if it's just a little, makes it feel less responsive. Even if your traditional UNIX and OS/2 systems had the same scheduler, the OS/2 GUI would feel more responsive than the X11 one.

    That doesn't mean that the scheduler doesn't make it possible to do things on OS/2 that you can't do on traditional UNIX, it just means that the problems you observed can't be fixed just by improving the scheduler on the systems where you observed them.

    Does putting it that way help?

    1. Re:One last comment on the GUI... by SillyNickName4me · · Score: 1

      A synchronous event loop causes other problems, but it doesn't add latency that doesn't exist in the underlying programs. A message queue that deliberately buffers and defers operations so it can bundle them to improve throughput does.

      It makes responsiveness depend on well behavedness of applications, but you are right that as long as applications are well behaved, this indeed causes lower latency (this has always been IBM's argument against implementing multiple message queues)

      And adding latency to a user interface, even if it's just a little, makes it feel less responsive. Even if your traditional UNIX and OS/2 systems had the same scheduler, the OS/2 GUI would feel more responsive than the X11 one.

      As I have pointed out quite a few times in this discussion, the responsiveness differences remain even when eliminating the GUI completely on both systems. Would you please stop ignoring that?

    2. Re:One last comment on the GUI... by argent · · Score: 1

      Would you please stop ignoring that?

      Man, I'm totally sorry. I thought I was in "stop ignoring that" mode when I said Now we've talked about the drivers, I'll say that things like the GUI design and the driver architecture have a bigger impact blah blah blah blah.

      I dropped the ball there.

      So let me say that between your posts and my subsequent googling you have totally expanded my understanding of the OS/2 scheduler, it's way better than I thought. And also, I totally get that you've got solid examples of related problems that don't have anything to do with the GUI.

      So, yes, you're absolutely right. It's not just the GUI. There's lots of other ways the OS/2 architecture is designed to provide way more responsiveness than the traditional UNIX kernel.

      So, let me say this, without any intent to ignore the value of OS/2, or OS/2's scheduler, or your experience. And that is... you could go into Linux or Solaris or whatever traditional UNIX kernel you're talking about and completely fix everything that's wrong about the scheduler, give it a real-time scheduler, or the OS/2 scheduler, or a magic scheduler that ALWAYS picks the process to run next that will provide the absolutely most responsive user interface while never deferring any other critical processes... and every single one of the shortcomings in the behaviour of interactive tasks would still be there.

      That's what I mean when I say the scheduler doesn't matter, that the UNIX scheduler is pretty close to good enough, it's because the scheduler just isn't responsible for enough of the system in a traditional UNIX kernel for it to be responsible for the problems.

      That cool?

    3. Re:One last comment on the GUI... by SillyNickName4me · · Score: 1

      So, let me say this, without any intent to ignore the value of OS/2, or OS/2's scheduler, or your experience. And that is... you could go into Linux or Solaris or whatever traditional UNIX kernel you're talking about and completely fix everything that's wrong about the scheduler, give it a real-time scheduler, or the OS/2 scheduler, or a magic scheduler that ALWAYS picks the process to run next that will provide the absolutely most responsive user interface while never deferring any other critical processes... and every single one of the shortcomings in the behaviour of interactive tasks would still be there.

      Definitely, simply because it is not the only problem.

      That's what I mean when I say the scheduler doesn't matter, that the UNIX scheduler is pretty close to good enough, it's because the scheduler just isn't responsible for enough of the system in a traditional UNIX kernel for it to be responsible for the problems.

      And that is where we disagree. You can fix all the other problems in a traditional UNIX kernel, and still have a system that is not being responsive when ignoring the scheduler and priority management (note that I have from the start been talking about those 2, and also pointed at that they are not the only problem, but are a substantial part of the problem)

      If you really want some proof of how much it matters, I suggest you install a FreeBSD -current snapshot, and then build 2 kernels, one with the 4BSD scheduler and one with the ULE scheduler, and just go measure the difference in responsiveness yourself.

  159. Re:Mod parent UP! Also the Microsoft link .... by Billly+Gates · · Score: 1

    Hell I interned back in 2000 for a company with several NT 3.5.1 servers still running.

    During a reinstallation an error message popped up in a blue screen and guess what the background said "OS/2"! lol

  160. Still setting aside the GUI... by argent · · Score: 1

    And that is where we disagree. You can fix all the other problems in a traditional UNIX kernel, and still have a system that is not being responsive when ignoring the scheduler and priority management

    If you do that you'll have created a system in which the role of the scheduler is much more important than it is in a traditional UNIX kernel. If you just do that, in fact, you are almost certain to end up with a system that is less able to handle resource contention than the current kernel, because you'll have a system where a process can be competing with its own device drivers instead of a system where the device drivers are running as software interrupts in that same process.

    It's like switching to a microkernel design. If you build a system with a microkernel design and pay anywhere near as little attention to queue management and scheduling as you can get away with in a traditional UNIX kernel, you'll end up with a system that has incredible problems with bottlenecks. Like, say, MINIX.

    In fact, a scheduler that acts like the UNIX scheduler is actually worse than a naive scheduler in those environments. It's almost guaranteed to create a problem with priority inversion as a driver in OS/2 or a server in a microkernel gradually gets "niced" down below the priority of the process that it's starving.

    Next...

    If you really want some proof of how much it matters, I suggest you install a FreeBSD -current snapshot, and then build 2 kernels, one with the 4BSD scheduler and one with the ULE scheduler, and just go measure the difference in responsiveness yourself.

    Measure, or observe?

    If I have to measure something to notice it, then that's proof for me that it's not something that matters.

    If it's a big enough difference that I can get it just using the system with a compute-bound job in the background, then that might be worth actually firing up my test box for.

    If it's something that's going to make a big difference, then that's actually exciting, because I've used UNIX systems with other schedulers before and I've never seen that.

    I don't believe I'll see it for a purely CLI environment, because there's not enough latency even under massive load for me to notice in a purely CLI environment even on machines a hundred times slower than what I'm using today.

    But under X11? I can't say I'm sure enough to rule it out. I haven't seen it before, but I could be wrong. Tell me, is this huge, or is it something I have to measure?

    1. Re:Still setting aside the GUI... by SillyNickName4me · · Score: 1

      I don't believe I'll see it for a purely CLI environment, because there's not enough latency even under massive load for me to notice in a purely CLI environment even on machines a hundred times slower than what I'm using today.

      Not having an idea what you are using now, but its hard to make a relatively modern machine running a UNIX with for example a 4BSD scheduler lag due to the scheduler under heavy load, other then by having an insane number of processes.

      Going back to say a 386 or 486 based machine may allow you to observe lag under heavy load on a CLI.

      Huge number of processes makes schedulers like the 4BSD one very inefficient, and it is for example not very good at making good use of multiple (possibly virtual) CPUs. (ULE is better but far from perfect at the later for now)

      But under X11? I can't say I'm sure enough to rule it out. I haven't seen it before, but I could be wrong. Tell me, is this huge, or is it something I have to measure?

      The difference under most conditions on a modern desktop are not huge for what I can tell, and may not even be observable depending on what kind of machine you have. 'Fixing' latency with raw power is a kinda well known approach, but doesn't even start to address the underlying differences between implementations, let alone answer which one is more effective.

      On SMP systems and/or when running a huge number of processes, the difference may be easier to observe.

    2. Re:Still setting aside the GUI... by argent · · Score: 1

      Going back to say a 386 or 486 based machine may allow you to observe lag under heavy load on a CLI.

      Going back to a 286 and a PDP-11 I can't recall having ever observed lag under heavy CPU load in a command line application under UNIX. I have observed lag caused by other things but I've observed that same lag when the CPU was mostly idle.

      For example "insane numbers of processes" doesn't mean "the problem is heavy CPU load", it can mean "the problem is thrashing".

      On SMP systems and/or when running a huge number of processes, the difference may be easier to observe.

      A traditional monolithic kernel requires a lot of work to get it to do SMP adequately, let alone well, because unless you have kernel threads or SMP you can just duck in and out of a single giant lock. So, they do.

      Going back and making the kernel more re-entrant with finer-grained locks is an ongoing process.

  161. Re:Mod parent UP! Also the Microsoft link .... by mink · · Score: 1

    Too bad they cant find the receipt and prove it in a court of law (the only place it matters).

    --
    Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
  162. Re:OS/2 Ahh the memories by mink · · Score: 1
    To see how OS/2 runs today on todays hardware check out ecomstation.


    Nice boot to graphical installer, LVM, ect.

    --
    Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.