Slashdot Mirror


Microsoft Agrees to License Windows Source Code

msbmsb writes "Stepping away from previous tradition, "Microsoft Corp. said Wednesday it will license its Windows source code to comply with a European Union antitrust ruling." But in an effort to stop the cloning of the OS, developers will still have to pay an unspecified amount for the code. This is an addition to the "12,000 pages of technical documents and 500 hours of free technical support" to those who purchase a license."

66 of 423 comments (clear)

  1. 12000 Pages? by unheard02 · · Score: 5, Funny

    Man, and all we get is clippy to help us out.

    --
    "If you have legs and are flammable, you are never blocking a fire exit." -- Mitch Hedberg
    1. Re:12000 Pages? by GoodOmens · · Score: 2, Funny

      Bets on when it will be leaked?

  2. How much? by Average_Joe_Sixpack · · Score: 4, Funny

    But in an effort to stop the cloning of the OS, developers will still have to pay an unspecified amount for the code.

    One Cajillion Dollars

    1. Re:How much? by Spy+der+Mann · · Score: 2, Informative

      The question is, who would try to clone such an impossible to understand and bad developed SO [sic]???

      These guys would.

    2. Re:How much? by Orion+Blastar · · Score: 3, Funny

      You forgot, Steve Ballmer dressed up as Dr. Evil, putting his pinky to his lips:

      "We shall license the Windows source code, for, ....... One Cajillion Dollars! Muahahaahahahahahahahahaah!"

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
  3. Ok.... by Tragek · · Score: 4, Interesting

    I'll admit it, I'm shocked. However, I have to ask the question? What is this going to change?

  4. Is this the beginning or end of windows? by Anonymous Coward · · Score: 3, Interesting

    Once this hits pirate land, are we in for more trouble than good?

  5. Should help Security by WebHostingGuy · · Score: 2, Interesting

    With the actual source and another pair of eyes looking at it, there should be more security fixes and hopefully a more secure OS.

    --
    Quality Hosting e3 Servers
    1. Re:Should help Security by dotgain · · Score: 4, Funny

      Yeah, I can see it now. People flocking en masse to fix the holes, and pay for the privilege!

    2. Re:Should help Security by hackstraw · · Score: 2, Interesting

      With the actual source and another pair of eyes looking at it, there should be more security fixes and hopefully a more secure OS.

      Iff they accept patches. I don't know if their build and release system can handle such a thing right now, this is entirely a different model for them if they adopt it.

      Why is it that about 80% of the Microsoft headlines are basically a recital of the Henry Spencer quote -- "Those who don't understand UNIX are doomed to reinvent it, poorly."

      If MS is to license their source (but not freely of course) and if they were to take patches back from the community, then they are back to Aug 25th, 1991 20:57:08 GMT when Linus sent out the first mail to usenet announcing Linux.

      Hopefully, someone will benefit from this change. We Linux weenies have for years. I'm still upset about the only Linux kernel freeze that I got in 1997. However, Donald Becker fixed the bug he introduced in the 3com 509 driver, and all has been good since then.

      Hmm....

      Brainstorm. How about people sending the patches under an incompatible license to MS. What would they do then?

  6. Will it compile? by ptaff · · Score: 4, Interesting

    The question is will it be complete and compile? Don't they have to hide parts of Windows that are licensed from other companies?

    Windows will still be distributed as binaries, having this source code does not give any guarantee about what's really running on your system.

  7. Comment removed by account_deleted · · Score: 2, Insightful

    Comment removed based on user account deletion

  8. Unspecified amount? by jpsowin · · Score: 4, Funny

    developers will still have to pay an unspecified amount for the code

    That means it's either free, or will cost trillions of dollars. I vote for the latter.

    DEVELOPER: I'd like to purchase your code, please.
    MS: Sure, no problem! Sign here.
    DEV: Wait, how much is this again?
    MS: It's an unspecified amount.
    DEV: Oh, okay, that's right. Here is my signature. My company will foot the bill.
    MS: We will send the bill soon--it will take a few weeks to finish printing. Very good doing business with you, sir. You are an intelligent man. We are a small company.

  9. Not sure of that... by meringuoid · · Score: 4, Interesting
    If they publish XP but not Vista the usefulness will be limited.

    Ever been annoyed at having to keep a FAT32 neutral-zone on your dual boot system because nobody's yet worked out how to write to NTFS without wrecking everything?

    That's the kind of thing this will hopefully lead to. It's all about interoperability. Unfortunately, knowing MS, the terms and conditions will be fricking deadly, and no open-source coder will so much as look at MS code for fear of contaminating themselves legally, so we shouldn't get too optimistic...

    --
    Real Daleks don't climb stairs - they level the building.
    1. Re:Not sure of that... by MMC+Monster · · Score: 2, Informative

      http://www.fs-driver.org/

      Or maybe this one. It's the one I use. Works great in XP with SP2 and all other patches applied. The only thing is, if you want to resize the ext2/3 partition (using partition magic) you have to use the applet in the control panel to unmount it first.

      --
      Help! I'm a slashdot refugee.
  10. Nothing new by truthsearch · · Score: 5, Informative

    In the US Microsoft already offers their code to governments, schools, and some limited corporations. All sign NDAs of course. The only news is that it's now happening in Europe. So don't be all surprised people outside MS are seeing the code. This isn't anything new.

  11. Re:What a bunch of crap... by NeedleSurfer · · Score: 3, Insightful

    Because they are abusing a monoppoly, even simpler because they have a monopoly. Because this monopoly is gained and maintained trough the code they created, don't abuse of your monopoly and drastic measures won't have to be taken.

  12. The code's already out by truthsearch · · Score: 2, Insightful

    The code is already "out there" in the US government, some schools, and some corporations. And it hasn't hit the streets yet. I imagine few are afraid of the NDA. But they all probably fear that MS put something special in each copy of the code in order to track down the source of any leaks.

    1. Re:The code's already out by bogado · · Score: 5, Funny
      MS put something special in each copy of the code


      And you know what that is? Love... MS takes cares that each copy of the windows code has that special touch that makes the code seem likes it got freshly out of your mom's computer.

      Windows, now with something special(TM).
      Available to you for only an unspecified amount of money.
      --
      []'s Victor Bogado da Silva Lins

      ^[:wq

  13. Re:What a bunch of crap... by MarkByers · · Score: 5, Insightful

    They aren't forced to do anything. If they don't like the laws in Europe, they are free to trade elsewhere.

    More likely though, they will lobby to change the laws because they don't want to lose one of their biggest markets.

    --
    I'll probably be modded down for this...
  14. Already been done (sort of) by stikves · · Score: 4, Interesting

    Actually, Microsoft is already licensing the Windows source code. However the significance of the new event is, they will not be choosing the licensor (at least not as much as before).

    For a list of microsoft shared source licencing programs look at http://www.microsoft.com/resources/sharedsource/Li censing/default.mspx. You'll see that the top item mentions "access to Microsoft Windows® source code for internal development and support purpose". And as far as I know there are already many utility producers (Symantec, WinInternals, etc) that can access NTFS source codes.

    Anyways do not keep your hopes too high. As you can see there are many shared source licenses (some are even like BSD), however Windows is not becoming "Open Source" soon.

    1. Re:Already been done (sort of) by BigDuke6_swe · · Score: 2, Informative
      Taking part in a shared source program with Microsoft has been criticized before by the open source community for being a great risk to the developer that looks at the MS code.
      Isn't there the same problem with this new initiative?

      http://www.ossl.nl/opensource.org/advocacy/shared_ source.php

      Shared source licenses include a requirement that the licensor agree to treat Microsoft's code as confidential proprietary data. It follows that any developer, once he has seen shared source code, can be enjoined under trade-secrecy law from any activity that Microsoft considers to be competitive with its code.

      Shared source, therefore, behaves like a virus that infects developers' brains. Once you let it into your organization, you must keep careful track of which developers have been contaminated, avoid deploying them to any projects which might compete with a Microsoft product, and even erect "Chinese walls" between projects so that no knowledge from shared source can leak into projects with competitive implications. Failing to implement any of those precautions could result in your organization's being sued for ruinous compensatory damages by Microsoft's armies of lawyers.
      --
      Zere vere zwei peanuts valking down der Straße, and von vas assaulted...peanut
  15. Another great move by Microsoft by Anonymous Coward · · Score: 5, Insightful

    Nicely played by Microsoft.

    As usual - they're not giving what anyone asks for (afaik - noone actually wants to have to look at the internals of windows), they just want to get the documentation on the protocols used so that they can intercommunicate.

    By offering to license Windows, Micrsofts "crown jewels", MS has done two nice things (for them).
    1) They appear to be bending over backwards to meeting the EUs demands; and
    2) They will manage to set any number of unreasonable licensing terms (both monetary and otherwise), to turn this into yet another profit center (and ensure that open-source can't use any of it...)

    Imo, the EU should tell them that this is *not* what was asked for, and while it's nice and whatever, please just provide what you were asked for.
    Otherwise please pass go, please pay $2million dollars.

  16. Consequences by doublegauss · · Score: 3, Insightful
    This will have no consequences whatsoever on piracy. Those people don't give a toss about source code, all they need is to copy the executables.


    This will have consequences on projects like Wine, Samba or ReactOS because some legal mechanism will be in force so that you can't look at the Windows source and rewrite it, let alone cut-n-paste it. What those guys need to do is ensuring any development is clean-room. What I see as conceivable is that someone (the FSF for instance) pays for one licence and the devotes some effort into releasing documents which describe accurately the internals in plain language. Obviously, the people who do this job must not contribute any code to any project.

    1. Re:Consequences by js3 · · Score: 4, Insightful

      yea but once you have access to the source, they can come after you for copying their implementation. As a developer I find this push to release the windows source sort of strange. We need proper documentation not source code, if something is broken we can point to the manual and have it corrected, instead of following the broken implementation in the source only to find it "fixed" in another version of the os and breaking compatibility.

      --
      did you forget to take your meds?
    2. Re:Consequences by JabrTheHut · · Score: 2, Interesting
      yea but once you have access to the source, they can come after you for copying their implementation.

      They would have to prove you copied it. If you were stupid enough to cut and paste their block of code into yours, you will get done. If not, say you already had some code written and just needed to know a few things, you could tweak your code according to what actually happens in the protocol, rather than what microsoft has documented incorrectly. There is a catch, which I will get to below.

      We need proper documentation not source code, if something is broken we can point to the manual and have it corrected

      Why would microsoft ever do such a thing? Why would MS ever release real documentation?

      instead of following the broken implementation in the source only to find it "fixed" in another version of the os and breaking compatibility

      Compatibility is a two-edged sword. If they break compatibility, it hurts their users too. Some of them might care, and some of them might be big enough to demand a fix. If Microsoft have to release their updatd source code then that's a win for everyone except microsoft.

      Where this might fall down is if MS cheat, and instead of releasing current code release something a few years old and broken, something I believe has already happened once...

      Anyway, on to the catch, this from the samba developer's page:
      Important: In order to avoid any potential licensing issues we require that anyone who has signed the Microsoft CIFS Royalty Free Agreement not submit patches to Samba, nor base patches on the referenced specification. We require, too, that patches submitted to Samba not infringe on any known patents. Finally, as with all GPL work, the submitter should ensure that submitted patches do not conflict with any third-party copyright.
      --
      Work like no one is watching. Dance like you've never been hurt. Make love like you don't need the money.
  17. Re:What a bunch of crap... by Pope · · Score: 2, Insightful

    When one of those game developers is a 95% monopoly on home and office computers and their software comes pre-installed on all hardware with cost-prohibitive terms to the hardware manufacturers against installing a competitor's game software, then we'll have a look at the merits of a case against that game developer.

    --
    It doesn't mean much now, it's built for the future.
  18. Re:What a bunch of crap... by Guppy06 · · Score: 5, Insightful

    "Why should any company be forced to reveal their trade secrets?"

    Why should any murderer be forced to spend time in prison?

    Answer: because they were convicted in a court of law (or, in Microsoft's case, courts) of comitting a crime and are now being punished.

    "Is Blizzard going to be forced to reveal their source code so that we can write a better version of Gear?"

    Hold off your whining until Blizzard is prosecuted for abusing monopoly powers.

  19. Wahoo! by Billly+Gates · · Score: 4, Funny

    Now I can learn how to create secure bugfree code from the masters.

  20. Uh... right... so where's that documentation? by Lifewish · · Score: 2, Interesting

    So MS get ordered to hand over documentation for their protocols. They do so. It's crap and they're ordered to go back and do it properly.

    So they respond with "figure it out yourself. After paying us some cash obviously."

    Does anyone actually think this is an acceptable response?

    --
    For the love of God, please learn to spell "ridiculous"!!!
  21. Re:Wait... That seems... SLANTED??? by oneiros27 · · Score: 5, Funny

    You act like it's something new ... just watch any infomercial, or commercial for exercise/kitchen gadgets at 2am:

    Have you ever wished you could figure out how to make your application work with Microsoft Windows?

    Now you can!

    How much would something like this be worth?

    We don't know, either ... just send us a blank check, and ask for rush delivery!

    Act now, and we'll throw in 12,000 pages of documentation*.

    But wait, there's more ... we'll also throw in 500 hours** of FREE tech support!***

    --
    * some pages intentionally left blank
    ** no refund for time spent on hold
    *** free tech support may incur phone charges on your part.
    Offer not valid in countries we're not getting sued for unlawful business practices

    --
    Build it, and they will come^Hplain.
  22. Re:Europe by pubjames · · Score: 2, Funny

    Spoken like a true Brit. Those Europeans aren't like us Brits, we're fricking great at everything.

    Can someone mod me as "insightful" as well please?

  23. Re:How will a price render cloning impossible? by RingDev · · Score: 2, Insightful

    If you charge $2.5 million for the code license you can greatly reduce the number of buyers. With some deep buried taging you could even identify which buyer's code was leaked, and then sue them in to oblivion.

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
  24. sweet by Tachikoma · · Score: 3, Funny

    i hope it gets leaked on the web.
    that way i can cut-and-paste it into a Obfuscated code contest!

    --
    i don't care
  25. O_o by SaidinUnleashed · · Score: 2, Funny

    Did I just see a pig fly by overhead?

    --
    Shiny. Let's be bad guys.
  26. Re:I can speak to this by hunterx11 · · Score: 2, Funny

    I can assure you that the Man Moth is no myth--he is very much a reality.

    --
    English is easier said than done.
  27. MS has already licensed the code to universities by I'm+Don+Giovanni · · Score: 2, Informative

    This isn't a big deal.
    Microsoft has already licensed Windows source code to over 100 universities, listed here:
    http://research.microsoft.com/collaboration/univer sity/ntsrclicensees.aspx

    More details:
    http://research.microsoft.com/collaboration/univer sity/NTSrcLicInfo.aspx

    --
    -- "I never gave these stories much credence." - HAL 9000
  28. Indeed! What a bunch of crap... by Saeed+al-Sahaf · · Score: 2, Insightful

    Though Microsoft was defined as a monopoly in court, and it is certainly politic to tow that line here in Free Beer Land, clear vision reveals that people do have choice, there is still Apple, various Linux, and an assortment of BSDs. Irrational hyperbole can't change the facts. Question: If, as you say, Microsoft is a monopoly, are you than admitting that Linux and BSD are not viable operating systems? Of course that can't be true can it? We know in fact that Linux and BSD are viable operating systems.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Indeed! What a bunch of crap... by Zathrus · · Score: 2, Insightful

      Question: If, as you say, Microsoft is a monopoly, are you than admitting that Linux and BSD are not viable operating systems? Of course that can't be true can it? We know in fact that Linux and BSD are viable operating systems.

      Thanks for the sarcasm! Now go read up on the legal definition of monopoly. Pay particular attention to the concept of "de facto monopoly". In order to be a monopoly you do not need to be the only provider of a service -- merely an overwhelming majority. The other key part is that you must attain that status not through level competition, but by doing illegal things to your competitors (sabotaging products, not properly sharing information even handedly, giving preferential treatment to resellers based on whether or not they sell a competitor's product, etc).

      And yes, MS was found guilty of being a de facto monopoly. That has no bearing on whether or not Linux, BSD, and Apple are "viable operating systems" or not.

      If you're going to start talking about the facts, then it's useful to actually know them first.

    2. Re:Indeed! What a bunch of crap... by Zathrus · · Score: 2, Informative

      You are not forced to use their products due to that lack of any others because of the actions of Microsoft

      Yeah, and back in the early 1900s you didn't have to buy Standard Oil either. Sure, the only non-Standard Oil store was 50 miles away, but you had that choice!

      The history of Windows (and MS products on it) is remarkably similar. Sure, you can use DR DOS. Oops, for some reason Windows 3.11 won't work with it! We're sure it's their problem though. Use MS-DOS instead. And you can use something other than Excel or Word too... except that those applications don't have the undocumented-yet-supported APIs that let Word/Excel run faster and more stable. Oh, and by the way -- Dell, Gateway? You can sell any operating systems you want. But you'll pay for Windows no matter what. Oh, sure, you don't have to do that -- but then we'll just charge you twice as much per license. That's fair, right?

      Methinks you have a short memory for the "actions of Microsoft".

    3. Re:Indeed! What a bunch of crap... by Zathrus · · Score: 2, Informative

      Ah yes, the secret undocumented Microsoft super-API

      It's not undocumented. There were several books (not by MS of course) that documented the undocumented API calls in Windows 3.0, 3.1, Windows95, and Windows98. The better of them even listed what advantages they had over the documentd calls and which Microsoft programs used them. If something like Word or Excel used them then you could damn well count on them being available in later versions as well, even though they were not officially supported.

      Were they super? Generally no... but they did have advantages in ease of use (mostly) or speed (less often). There were a few cases where a single API call replaced a hundred lines or more of convoluted logic to acheive the same thing.

      Note that I don't have an issue with undocumented APIs -- they're common in software. And there are reasons you don't expose them, particularly if the API in question is actually a clever hack that may break later on because it takes advantage of unexpected behavior, or a "feature" that you should really get rid of at some point. The issue is that Microsoft's own application division appears to have had access to these calls (and their documentation) when nobody else did. At that point in time Microsoft had a de facto monopoly on the OS (which, realistically, was done in a fair marketplace), but not on application software (they were, at best, in distant second). By leveraging the OS monopoly they were able to create an application software monopoly -- and that's illegal.

      Go ahead. Google for "Undocumented Windows API". There's plenty of hard evidence for this "meme".

  29. this shouldn't actually work by mAIsE · · Score: 2, Insightful

    They have been asked to document their protocols such that their competitors (mostly open source) can compete. Licensing their server software is much like asking a politician one question and them answering the question they wanted you to ask. Of course the open source vendors can not sign the NDAs this will require. and Microsoft can't seem to get their shit together to document their protocols, probably their biggest problem behind the scenes.

    I will be personally surprised if this is accepted or even an appropriate response to the council.

  30. So, anybody read the article? Raise your hands now by anzev · · Score: 3, Insightful

    Well, the artcile cleary states:

    Microsoft is to open up the source code behind its server communication protocols, in an attempt to get the European Commission off its back.
    I'm pretty sure this isn't Windows... actually, being a developer myself I KNOW this is not the Windows source code. It's just source code to the protocols. It's a great step forward no less, but anyway.

    There will be no additional charge for access to the code.

    Er... and the article summary states that developers will have to pay an unspecified amount of money... Ok...

    RTFA! That's all I have to say. It's a really short article you know.

  31. Re:Europe by stunt_penguin · · Score: 2, Funny

    And also why the Irish economy is kicking the British economy's ass. Britain is in decline, while Ireland and much of europe is in the ascendency.

    --
    When the posters fear their moderators, there is tyranny; when the moderators fears the posters, there is liberty.
  32. Re:Europe by lisaparratt · · Score: 2, Funny

    Like any self respecting Brit would use the term "fricking"!

  33. What's needed is protocol specifications, not code by Big+Jojo · · Score: 2, Insightful

    This is an end-run around the requirement to provide complete and accurate protocol documentation, for the purposes of third party inter-operation.

    Notice how any third party that uses that code in lieu of the protocol documentation is now unable to inter-operate without forking money over to Microsoft ... sleazy.

    Of course, many of us have long suspected that Microsoft really doesn't understand software engineering disciplines well enough to make their products adhere to such specifications. They may think "here's the code" is the best they can do without actually revising their development practices. Well, tough noogies, this is just the price for their previous abusive practices.

  34. Troll, but I'll bite by rewt66 · · Score: 3, Insightful

    Ever hear of a "free" market? Does that concept ring a bell?

    The problem with a monopoly is that there is no free market any more. The monopoly exerts too much control. So to get a normal, free market to function again, you have to control the monopoly.

    Digression: Though corporations are legal persons, they aren't real persons. Therefore I don't give a rip about freedom for corporations. I care about freedom for real people - for human beings. If restoring human freedom requires restricting corporations, I'm for it. (And it's looking more and more like this is the case, and not just with monopolies like Microsoft.)

  35. Stop cloning or emulation? by beforewisdom · · Score: 2, Insightful

    I think the implicitly stiff fee is to slow down OSS developers from discovering the undocumented hooks in windows so they can make better windwos emulations.

  36. Really? by OwlWhacker · · Score: 2, Insightful

    No one is forced to use Microsoft software. They offer a product, and if people don't like it, they don't have to use it.

    But most of the time nobody can use any alternatives because Microsoft uses proprietary file formats, protocols and APIS. Microsoft locks people into Windows via these proprietary methods, the competition cannot freely integrate with many Microsoft solutions.

    That's why the E.U. wants Microsoft to provide data on its protocols: so that other companies can get their products to work with Microsoft's.

    The question is, why wouldn't Microsoft use open protocols in the first place?

    HTTP, POP3, SMTP and FTP are all non-proprietary protocols that Microsoft uses, and that other companies also use. The only reason Microsoft has its own closed protocols is to get them used by the majority of computer users, via its monopoly, thereby unnecessarily locking out or making life extremely difficult for the competition (e.g. Samba).

  37. Re:And it will LEAK 24 hours later! by Aranel+Alasse · · Score: 5, Insightful

    Shouldn't we hope that it doesn't leak? I don't really know much about it, but I'd imagine that Microsoft has patents and such all over their stuff. If it gets out, and similar looking code appears elsewhere (i.e. in open source code projects), couldn't there be lawsuits and accusations flying everywhere?

  38. Doesn't mean anything by argent · · Score: 2, Insightful

    EXISTING customers who are ALREADY paying for documentation on the Windows server networking protocols will now be allowed to see the source code to the protocols for no additional charge.

    They won't be able to modify, extend, or redistribute the code, even in closed applications.

    This is only by the most liberal interpretation "opening" the code, and it's really not licensing the code except as reference material.

  39. Re:Nothing new here by killmenow · · Score: 2, Informative
    Your understanding does not jive with my memory. This entry in Wikipedia sums up more accurately how I remember it (I was working as a consultant doing Citrix installations and such at the time):
    Microsoft licensed the source code to NT to Citrix, and in 1995 Citrix began to sell WinFrame, a stand-alone system based on Windows NT 3.51 (MultiWin). Development of WinFrame 2.0 was derailed in early 1997 when Microsoft withdrew the license to NT 4.0 from Citrix, although later negotiations led to Microsoft agreeing to license Citrix technology for Windows NT Server 4.0, resulting in Windows Terminal Server Edition. Citrix agreed not to ship a competing product, but retained a set of "enterprise-level functionality" which it could sell as an extension to Microsoft's products. This toolkit was initially sold under the name 'Metaframe.' This complementary relationship continued into the Windows 2000 and XP eras, with Citrix offering Metaframe XP and Presentation Server. [emphasis mine]
    As I recall it, Microsoft basically incorporated Citrix technology into NT4 for TSE and was going to just shove Citrix in front of the bus, so to speak. Many in the press at the time were calling it a death knell for Citrix even. Citrix managed to negotiate with Microsoft, agreeing to stop selling WinFrame, a fully competitive product, and focus only on MetaFrame, their add-on product. Citrix has managed to survive and flourish; but, make no mistakes, it's not because Microsoft didn't try to cut and run.
  40. Continued Support Opportunity by SteveX · · Score: 2, Insightful

    This creates a huge opportunity for companies to take over supporting legacy operating systems.

    License the Windows XP code today, wait a few years for Microsoft to stop supporting it, and then sell support contracts to companies that have chosen not to upgrade and still need security patches and bug fixes.

  41. Re:And it will LEAK 24 hours later! by GoodOmens · · Score: 2, Interesting

    Yes but being illegal if its leaked doesn't stop you from downloading Microsoft Office or Windows off your favorite P2P network / torrent site / usenet ....

    However this does bring up a more legite question: "Will Apple have to do the same?" or since darwin is already open source does it matter?

  42. The original EU decision from march 2004 by fritsd · · Score: 5, Informative
    I'm sorry, but I see a lot of nonsense in this discussion thread :-) as if nobody remembers what this is all about, so here it is: Here is the summary of the EC's punishments/remedies decision, from march *2004*: http://europa.eu.int/rapid/pressReleasesAction.do? reference=IP/04/382&format=HTML&aged=0&language=EN &guiLanguage=en (note where it says Microsoft should comply within 120 days) and this is a quote about whether source code should be disclosed:
    "
    * As regards interoperability, Microsoft is required, within 120 days, to disclose complete and accurate interface documentation which would allow non-Microsoft work group servers to achieve full interoperability with Windows PCs and servers. This will enable rival vendors to develop products that can compete on a level playing field in the work group server operating system market. The disclosed information will have to be updated each time Microsoft brings to the market new versions of its relevant products.
    To the extent that any of this interface information might be protected by intellectual property in the European Economic Area(6), Microsoft would be entitled to reasonable remuneration. The disclosure order concerns the interface documentation only, and not the Windows source code, as this is not necessary to achieve the development of interoperable products.
    "
    So, this is not about Microsoft's precious source code or trade secrets *AT ALL*. It is all about interface documentation to ensure interoperability in a heterogeneous computer network (i.e. so that a computer not running Microsoft software can still communicate with the computers that do, e.g. using Samba).
    It may be the case that Microsoft's statement from today seems to imply that they are doing something relevant, but it is *NOT* a reply to the original *DEMAND*, which was "just tell us how computers can communicate with computers running MS-Windows".
    Source code is not the same as documentation! A meaningful reply to the demand would be a document with the full interface protocol, that's all... no source code necessary.
    --
    To be, or not to be: isn't that quite logical, Slashdot Beta?
  43. Re:What a bunch of crap... by nm42 · · Score: 2, Informative
    if they don't, then the CEO can go to jail

    Nice try, but officers of a company are protected by something called the Business Judgement Rule. If an officer decides some action (not trading in EU) is warranted (releasing source code might, in his eyes, jeapordize their product), they cannot be punished just because the shareholders disagree with that action. As long as they acted in Good Faith, they are protected - even if the choice was wrong.

    They could be ousted by the shareholds and replaced, but they would not be criminally liable.

  44. Re:What a bunch of crap... by Overly+Critical+Guy · · Score: 2, Informative

    No one is forced to use Microsoft software.

    Wrong, Microsoft strong-armed OEMs into bundling only Windows throughout the 90s, levying special little fines if they dared offer competing products. So technically superior alternatives like OS/2 and BeOS weren't given a fair chance, and consumers never got to try them out.

    --
    "Sufferin' succotash."
  45. Re:Europe by Cal+Paterson · · Score: 2, Interesting
    "can you trust the UK unemployment numbers???"

    If thats a question, you obviously have no idea exactly just how crooked these figures are. We do all kinds of idiotic things to get the results that get the baby-kissers re-elected:
    • Only people actively looking for jobs are on the register (people who don't apply at the job centre who aren't caught on the census are excluded).
    • You must claim benefits (and you can't claim benefits if you fit into a number of pigeon holes - house in too high a class, you know what I mean)
    • If you partner works, you don't qualify for the list.
    • If you're not unemployed long enough, you don't qualify (it takes a certain ammount of time to get on the list)
    • Conversely, if you are unemployed long enough, you're taken off the list, as you can no longer claim benfits.
    • There is often a long lag time before anyone realises you should be on the list.
    • A lot of the time, if you've just left school and can't get a job, someone will classify you as being in further education or training.
    • There are a METRIC FUCKLOAD of other exceptions which you probably fall into.

    And all these measures generally remove quite alot of people who are generally included in the fiigures quoted for other countries. Also, if references another countries figures in relation to ours, they will normally pick the worst figures they can find. Generally, they can normally get away with picking figures that are up to 5 years old (the obviously pick the highest) and the ones that include all kinds of weird crap (ie, if there are a set of figures that will factor in an estimate for people that have probably been missed, they will use those).
    UK unemployment figures are wildly inaccurate, and i don't think other countries fudge the figures to the extent we do.
  46. Codeweavers/Cedega/WINE by fufinache · · Score: 5, Insightful

    If I had the money and the knowledge to set up one of those internet money pools, I would try to pool together some money so that Codeweavers, or maybe even Cedega can get a copy of the code. I'm sure a this could go a long way to help linux acceptance.

  47. Are you sure? by bmajik · · Score: 2, Interesting

    My understanding is that previous disclosures of Windows Source typically had "no develop" and "no commercial spinoff" clauses. I.e. you couldn't necessarily use the Windows source to try and make your pay-ware version of $whatever work better.

    I think this changes that. Now software companies working on plugsin/whatever for windows will be able to continue working on those things, even after looking at the windows code.

    That is a pretty significant change, I think. Previous source offerings were primarily for academic institutions, govt code/assurance audits.

    I suppose there have been a few previous Windows source licenses that allowed for product development. Sysinternals, Mainwin, and OpenNT come to mind.. but perhaps these were all US based entities?

    Note - i have no specific knowledge of these issues, i am just stating my impression.

    --
    My opinions are my own, and do not necessarily represent those of my employer.
  48. Interoperability shouldn't need the source code by Rob+Y. · · Score: 5, Insightful

    The whole point of the EU's interoperability requirement was so that people could build compatible systems. Nobody want's to clone Windows (or at least that isn't an EU requirement). And just because somebody wants to be able to serve files to Windows desktops doesn't mean that they want to steal Microsoft's intellectual property. They just want to be able to support 90+ % of the systems out there. And maybe if MS hadn't broken the law, they wouldn't be forced to allow that. But they did.

    Offering the source code with draconian licensing terms doesn't do it. They just need to release detailed specs for the bits of Windows that are required to interoperate with the system. That means the filesystem layout, networking protocols, and I'd argue, codecs that are 'built in' to windows enough that website dev's use them as 'always available' facilities.

    And the specs should be made available for free. No restrictions on use. That's the whole point. If MS has the ability through its monopoly position to set de-facto standards, they should not be able to use those standards to further entrench their monopoly. A requirement to publish the specs would remove that incentive.

    This offering is a big old red herring, and the EU should reject it.

    --
    Posted from my Android phone. Oh, I can change this? There, that's better...
  49. Re:What a[n actual] bunch of crap... by Overly+Critical+Guy · · Score: 2, Interesting

    You can do that now because of the anti-trust trial, but it doesn't matter because 10 years ago, Microsoft made sure you couldn't do that. This created a monopoly, and all the applications became dependent on the Windows platform, which made the monopoly huge, and competing offerings irrelevant. In other words, you can do that now because competitors are so irrelevant in the face of the monopoly, which was made so huge by preventing those competitors from competing in the first place.

    --
    "Sufferin' succotash."
  50. MS-fixer by NaeRey · · Score: 2, Insightful

    If they will truly open theri ssource code on the streets, we might soon see some 'WindowFixer' websites, sellin windows security patches. That's not the worst of ideas. Actually would somewhat help us, and more people would not-stop using windows, or probably many would use the 'FixedWindows' version... or something.

  51. What if someone uses it to make a better Windows? by Orion+Blastar · · Score: 2, Interesting

    What if the Windows clone has fewer bugs, fewer security flaws, runs faster, and is a better quality than Microsoft Windows and sells for a lower price? Can they sell it outside of Europe then?

    --
    Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
  52. Are windows becoming a commodity? by thanasakis · · Score: 2, Interesting

    I have the feeling that this product is more and more moving away from the realm of products and into the realm of neccesities. Sooner or later people will want to create products that have the same API as windows (essentialy windows clones). So far they ae not able because M$ is potentialy able to stop them, but when we are talking about an OS that has >90% share, will they be able to keep it up? AT&T had monopoly and lost it also.

  53. DEC did the same thing with VMS by maynard · · Score: 3, Interesting

    Long ago Digital used to provide the source for VMS on Microfiche so that they could comply with government and business security requirements without really giving up control over their OS crown jewels. Looks like this is a similar move by MS. It's similar to a the legal strategy of information overload - dumping tens of thousands of irrelevant documents into the hands of the opposition to force them to waste time and resources looking for that needle hidden in the proverbial haystack.