Windows XP EULA Compared to GPL 428
cranos writes "The Sydney Morning Herald is running an article comparing the XP EULA to the GPL. Basically it's just reinforcing what we already knew but it could be a nice little piece to show your PHB next time."
It would be nice if they would simplify them (Score:3, Funny)
GPL: "Do what you want with it, but give credit where credit is due"
MS: "You have no rights. All your base belong to us."
Re:It would be nice if they would simplify them (Score:5, Informative)
You're confusing GPL for the BSD license. The GPL is "1) Do what you want with it, 2) as long as derivative works are GPL as well (see 1)".
Re:It would be nice if they would simplify them (Score:4, Informative)
If you keep the derivative work in house, you don't have to GPL it.
Re:It would be nice if they would simplify them (Score:3, Insightful)
Re:It would be nice if they would simplify them (Score:2, Insightful)
>credit where credit is due"
It's not GPL, but good old (not current) BSD license.
Re:It would be nice if they would simplify them (Score:3, Insightful)
GPL "Make sure that others can do what you have been able to do."
MS "Make sure that others can't do what you haven't been able to do"
Re:It would be nice if they would simplify them (Score:3, Interesting)
The GPL is really summarized as:
Meanwhile, the MS EULA is pretty much just
Both licenses pretty much say:
News for nerds? (Score:5, Funny)
Re:News for nerds? (Score:3, Insightful)
Goblin
Re:News for nerds? (Score:4, Insightful)
Voila! Apples are different from Oranges" said American Agricultural Research magazine today
What i really want to know is whether old 'apples' are still good. To be more specific, it would be nice for them to compare Win2k's Eula (with service packs), to that of XP. The only reason right now that i don't go with XP is that i can't change my hardware willy-nilly like i do quite often. I have legal copies of everything (campus-wide license), so i really don't like the fact that they can tell me what i can/cannot do with products, my hardware, which they have nothing to do with.
Re:More like... (Score:4, Funny)
But turds are the industry standard. Besides, a billion flies can't be wrong...
mirror (Score:5, Informative)
Ugh, forget this idiot. (Score:5, Informative)
Just do a little searching on Sam Varghese and see what an idiot this supposed journalist is. His articles are little more than the whining of an ill-informed, angst-ridden gadget-geek.
His "article" on Mono, for instance. [smh.com.au]
Get a name, and get real (Score:2, Interesting)
If you've got a beef with the journalist, so be it. The research, however, confirms to me, the impressions I've felt for a while. The MS EULA should really be called MSCYA ( or maybe MSCBA ).
Mono SUCKS! (Score:5, Funny)
His "article" on Mono, for instance. [smh.com.au]
Man, mono sucks, I dunno what your problem is. First time I tried it, I got it from my girlfriend, and I couldn't even get out of bed for a week. Damned doctor had to run all kinds of tests on me. I tell ya, I don't ever want to try using mono again.
If this guy says .NET is worse than mono, that's pretty bad. I don't know what this .NET thing is, but it sounds like plague or polio or something.
Forbidden Uses (Score:5, Interesting)
But why would a EULA make a user agree to not use a particular product as a webserver or fileserver?? Before I turned to Linux, I had an old computer running Windows 98 acting as a fileserver. If I wanted to do that with XP Pro I'd be in violation of the EULA?
Technicaly, that means that anyone who enables file and printer sharing is violating the EULA! If MS is so against it, why do they build it into their products?!
-Shadow
Re: (Score:2)
Re:Forbidden Uses (Score:3, Interesting)
XP home edition cannot be used as a webserver or fileserver.
You can use XP Pro for your webserving/file serving needs.
Home edition doesn't have IIS built into it. Only XP Pro does.
The comparison was between the XP home edition EULA and GPL.
Re:Forbidden Uses (Score:2)
Re:Forbidden Uses (Score:5, Insightful)
Mod Parent Up! (Score:4, Interesting)
To be able to do so, we'd have had to upgrade to a server version of the product. We'd have had to upgrade around 600 PCs across the US, not to mention the licensing costs.
Don't know how it all hashed out in the end, although we decided at the time to dump the functionality rather than hand over our wallets.
Re:Forbidden Uses (Score:3, Interesting)
I'm not sure if the same is true for XP, but in 2000 Pro the IIS didn't allow to create virtual hosts either. Only one site and that's it.
Of course, with a 10 connection limit, there's not much point in having virtual webs, except for testing purposes, maybe.
Re:Apache on Windows (Score:5, Insightful)
Netscape used to do quite nice business by pointing out that their webserver could run very happily on NT Workstation (indeed, in their opinion, better than others on Server) and that the combination of the NTWS and their license was still cheaper than NT Server.
At which point MS change the license and prohibit using NTWS as a server. If you want that, buy NT Server - which is way more expensive and, look, happens to come with a 'free' web server...
If I choose to dig my garden with a teaspoon, that is my right. If I choose to run a removal firm out of a Mini, that is just as much my right. Why, therefore, should it be legal for a software company to prohibit me using something for a purpose they did not intend and do not believe it suitable for? If I'm happy with it, I should be able to.
Re:Forbidden Uses (Score:3, Informative)
Well, there is a huge difference in a fileserver and MS file sharing. I do believe that they mean a dedicated file server, dedicated to serving files over a network, whereas normal file sharing for home users would just include the odd file transported over the network, while the main use of the computer is home/office use. Thus cramming a load of 200gB HDs in a case, installing WinXP on it and chucking it in a corner to chew away on serving files indefinitely would be illegal, while using windows file shar
You're not thinking like an MS business person: (Score:5, Insightful)
Don't Think So (Score:4, Interesting)
I installed XP pro. By default, it enables print sharing and creates admin file shares for hard drives. I think the EULA in this case is to prevent a customer from bugging MS with their printer not doing network stuff properly.
No one ever reads these licenses. If they are read, they are usually misunderstood or ignored. A lot of what is in them is just so MS can say "well, we told you not to do that" if someone calls the support line with a problem.
Some of the terms are crazy. If you don't like them, just ignore them or use another product.
The EULA is virtually unenforcable in any event. If you disagree with a EULA, the EULA says to return it to the place of purchace. If the place of purchace refuses to accept a return, the EULA has been voided. In that case, the product reverts to standard copyright law.
There are a thousand ways lawyers could turn it. None of them would end up in the small guys favor.
Re:Don't Think So (Score:5, Insightful)
1) Ms puts things in their EULA so that they won't have to provide support.
2) No one ever reads EULA.
3) People misunderstant the EULA
4) MS will never enfor the EULA.
5) You can ignore the parts the of EULA you don't like.
6) The EULA is unenforcable.
and finally.
7) Use another product.
Hey! Number 7 is what this topic was all about in the first place.
Re:Don't Think So (Score:4, Interesting)
MS spreads the same FUD. It's simply trying to counterattack when you are under attack. What should the people do? just bend over and take it when MS launches an attack on you?
Re:Don't Think So (Score:3, Insightful)
I really don't think this is true. I don't think everybody is as greedy and evil as the MS execs are. You seem to think that there are no ethical business people in the world but I don't agree with you.
The vast majority of business owners would not resort to illegal tactics to improve or sustain their market share. Sure Enron, MS, Worldcom and a handful of businesses are perpetrating fraud and crimes but it's not f
Of course it makes sense for MS (Score:3, Interesting)
Various points to consider: (Score:4, Insightful)
And since MS reserves the right to alter the EULA at their discretion, the one you have during evaluation and the one that they give you when you buy (or even after you buy) can be very different things.
2) People's requirements change.
3) What sort of moron buys MS at all?
You forgot the part about considering: (Score:3, Informative)
2) The GPL issue you raise is misleading. We were talking about the license for usage, not for distribution. The GPL is not concerned with how you run the programs under it on your computer. MS can (and has) altered EULAs about usage.
3) If you've paid for MS products with your own m
Re:Forbidden Uses (Score:5, Insightful)
An EULA is entirely redundent here. Since it would simply duplicate copyright law. You might just as well sticker every physical object you own with "you may not take this without permission"....
Re:Forbidden Uses (Score:2)
Please explain how building web services and file sharing services into an OS "out-of-the-box" is protecting them from some crazy "pirating" violation. I'm really interested in your logic behind this as it makes zero sense to me.
"comparing"?!?! (Score:5, Informative)
How about Max OSX vs. a bicycle?
Or perhaps a puppy vs. lear jet?
The GPL is not an EULA - it's a distribution license. Maybe if the MS EULA dictated terms under which you can distribute WinXP, then you might be able to compare them.
I just have to ask - what's the point?
Re:"comparing"?!?! (Score:3, Informative)
It does:
One transfer of ownership allowed, no copying.
Next question?
Re:"comparing"?!?! (Score:3, Insightful)
One transfer of ownership allowed, no copying.
Next question?
Do you know the difference between distributing (making copies of) and transfering ownership (moving around one copy)?
The MS EULA does not dictate distribution terms (actually, it does -- it says you can't distribute.
Re:"comparing" (for a good reason) (Score:5, Insightful)
I see your point, they are different. But there are ties. You need to know what you are getting into when you install software.
The GPL says "do what you want - BUT if you decide to distribute it, you must follow these rules...."
The MS EULA says "by installing this software, you agree to the following terms....".
Yes, they are different, but MS has been FUDding the heck out of the GPL. So someone compared it to their EULA. (not very well, mind you, but whatever)
You are right, they are different things. But people need to understand that they are different things, and WHY they are different. I think they should have a nutshell comparison of the two:
GPL: "You own this software, do what you want with it. If you redistribute it in any way, follow the courteous rules defined in the license agreement."
MSEULA: "We own your ass, and can change the terms of owning your ass whenever we want. We reserve the right to own your ass in the future."
Re:"comparing" (for a good reason) (Score:3, Informative)
More accuratly copyright law says "you cannot distribute a copyright work without permission from the copyright holder". The GPL says "you have permission to distribute this copyrighted work subject to the following conditions".
Re:"comparing"?!?! (Score:3, Insightful)
The GPL is not an EULA
I've used many pieces of software which wouldn't allow me to use them without clicking "I Agree" to the GPL. How is that not an EULA?
Re:"comparing"?!?! (Score:4, Insightful)
Because you're not violating anything if you get around having to click on that? Treating the GPL like an EULA doesn't make it an EULA.
BTW, what apps were these?
Re:"comparing"?!?! (Score:4, Informative)
Many GPL-covered applications packaged for Mac OS X put a copy of the GPL in the "license" slot in the standard OS X installer package. This causes it to be displayed in the same way that an EULA would be on a proprietary package. I imagine this is the same on Windows GPLed programs that use the standard installer.
It doesn't really matter. As has been pointed out several times now, the GPL isn't an end-user license at all, and it isn't an agreement either. It's an assignment of permission to copy and make derivative works from a piece of copyrighted software -- a license, not a "license agreement".
The GPL isn't even a contract (certainly not a "contract of adhesion" like MS EULAs), and it it expressly disclaims covering the act of running the covered program [slashdot.org]. It presumes that if you came by your copy of the program legally (as by buying it or being given it) you already have the right to run it on your property -- the only things you need permission from the author to do are those things normally restricted by copyright law.
Re:"comparing"?!?! (Score:3, Informative)
Isn't this a violation of the GPL? I thought the GPL only allows you to redistribute the software if you place no restrictions on it's use.
Section 6 of the GPL (emphasis mine):
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms an
Conflates GPL and LGPL (Score:5, Insightful)
Vaccine not virus- stop the FUD madness (Score:5, Insightful)
The GPL has vaccine-like properties. Virii have the connotation of being malicious. The GPL ensures that software, once freed, stays free. And like a vaccine, you can't get it accidentally- you have to deliberately ingest it (i.e., link it into your own code). A virus is something you might get whether you like it or not.
Try linking to some Microsoft code and then check the licensing health of your application. What's that you say? You have to convince Microsoft to allow you this privelege, just like you would have to obtain permission from the author(s) of GPL'd software to make nonfree extensions?
The vaccine metaphor is more apt- the GPL allows healthy usage of code and prevents non-free cancers, parasites and virii from growing on otherwise free (healthy) software projects. Proprietary licenses can be viewed as more of a tourniquet, cutting off all unapproved growths, for better or for worse.
Wake up (Score:4, Insightful)
Re:Wake up (Score:5, Insightful)
A vaccine also spreads throughout your system, should you choose to take it. The key difference is that a virus will attempt to spread of its own accord but a vaccine requires the conscious effort of the user to spread. You can't "accidentally" include GPLed code in your programs, nor will GPLed programs intentionally write GPLed code into your programs.
Re:Wake up (Score:3, Insightful)
Or even into your data. Some proprietary applications claim to apply an EULA to the data you use them with.
Re:Vaccine not virus- stop the FUD madness (Score:3, Informative)
As I understand it, if you're not REDISTRIBUTING your software, you don't have to release any source code. So you could grab Apache (is that GPL? assuming it is), use all of it for your OWN INTERNAL Web Server, but adding some proprietary customizations for your web store, and not release your final source.
Now, if you tried to sell that new webserver software to other web stores, THEN you'd have to release your code, and then yes, IMH
Newsflash! (Score:2, Funny)
In other news today an Australian newspaper compared huge man-eating white sharks with soft, nice furry koalas.
The short version: Koalas are nicer (despite their sharp little teeths).
Sorry... Could not resist... =)
Re:Newsflash! (Score:2)
That's what everyone thinks until they encounter a drop bear [geocities.com]
MS trying to make us violate their EULA? (Score:5, Interesting)
Yet network and internet filesharing is still built into Windows XP...
Re:MS trying to make us violate their EULA? (Score:5, Informative)
They are comparing the XP Home edition EULA.
The professional version which you are using doesn't have that clause.
Re:MS trying to make us violate their EULA? (Score:2)
Re:MS trying to make us violate their EULA? (Score:4, Informative)
I am going to assume based on the phrase "utilize the services of the Product" that the clause refers to network connections rather than the physical attachment of other devices to your computer. So, file-sharing and print-sharing and connection-sharing are okay, but only to ten other computers. It would be fairly easy to violate this term. Suppose you hold a LAN party and 14 of your friends come over. There's a recent patch for one of the games you plan to play, and you use a FileZilla FTP server [sourceforge.net] to share it across the LAN so everybody can get it without mucking about with Network Neighborhood. Boom, you've violated the license.
One of the other posters has suggested that the restriction only applies to the number of computers accessing yours at any given time -- so you could give access to thousands of different computers, so long as there were never more than ten connected at one moment. I don't have XP, so I couldn't say -- does Network Neighborhood have a built-in connection limit in WinXP? Anyway, that would only apply to Network Neighborhood. Using Apache or any of a whole slew of other server-type programs could invalidate your license pretty quick.
Btw, I lifted that bit of license clause from the original report, not the summary that Slashdot has linked to. Another poster supplied a mirror of the PDF file. [slashdot.org] It's lengthy, but worth reading.
Re:Someone set you up the bomb (Score:4, Funny)
All depends on what you need... (Score:4, Interesting)
Re:All depends on what you need... (Score:2)
GPL'd software is much better than leasing. It's more like someone has an endless supply of self-replicating cars and is giving them away to anyone who will agree not to lock theirs up in a garage, and let anyone who asks get a copy of their car. Hmm, this illustrates the problems with equating software with material objects!
[This post somewhat inspired by Neal Stephenson's "In the Beginning was the Command Line" [spack.org]...but his analogy is much better
In summary... (Score:4, Insightful)
XP EULA protects rights of developers at expense of users.
Re:In summary... (Score:2)
Re:In summary... (Score:5, Insightful)
GPL protects the rights of users,
grants external developers extra rights,
copyright holder retains rights
EULA restricts users rights,
restricts external developers,
grants extra rights to the copyright
holder from the external users.
*BSD* protects the rights of users,
grants external developers even more
extra rights than GPL
copyright holder retains original rights
"puts paid to the myth"?... WTF? (Score:2)
Anybody know exactly what the expression "puts paid to" means?
Am I close in interpreting this as "discredits"?
It's an Australian thang, isn't it?
Re:"puts paid to the myth"?... WTF? (Score:2)
There is an error in the article! (Score:5, Informative)
"cannot be used as a webserver or fileserver"
but
"shouldn't be ever used as a webserver or fileserver"
Re:There is an error in the article! (Score:2)
Re:There is an error in the article! (Score:3, Insightful)
I will leave the idea of MS software being "fit" for any purpose to the MS bashers. But it appears more like a way to say nothing while implying much, to keep people from doing what they have the legal right to do, and MS can't stop them from doing.
Re:There is an error in the article! (Score:2)
Will this change anything? (Score:2, Interesting)
Do I really think that this will cause MicroSoft to release some of thier tools un
percent of license dealing with user's rights (Score:3, Interesting)
Why not just report what the licenses actually say; what is one supposed to glean from how many words they use
saying it?
(*: Note, fellow slashdotters; this is the one and only way to spell the word 'ridiculous'. Thank you. Don't even get me started on 'loose'/'lose'...
Re:percent of license dealing with user's rights (Score:2)
puts paid? (Score:3, Funny)
Re:puts paid? (Score:5, Informative)
No warrantee (Score:2)
What's going on?
Re:No warrantee (Score:2)
One thing was forgotten.. (Score:3, Funny)
How does it compare to other OS? (Score:3, Interesting)
Anybody like to cite interesting portions of the EULA of those systems?
Different 'End Users' For Each License (Score:3, Interesting)
I think there is a flaw here. The MS XP EULA's 'end user' is refering to a person who simply uses the product, there is no option to be a 'developer user' here.
The GPL 'end user' is including the EULA 'end user' and a 'developer user' into the same pot. I'm sure the EULA would look much different if MS intended people to actually modify the source code.
So afai can see you have two different groups here. If linux actually ever becomes rampant on the desk top I don't think the "Over half (51 percent) of the GPL focused on extending users' rights" is going to really matter to the majority of the actual users. This 51% seems to only apply to 'developer users' not your plain old Joe Six-Pack user, and believe me there will be much more Joe Six-Packs than developers on a widley used OS. So now half the GPL is meaningless to most of the users?
Here's your freedom, oh I'm sorry you can't actually use it?
Re:Different 'End Users' For Each License (Score:5, Insightful)
Follow up (Score:3, Insightful)
I was just pointing out that the differences in end users throws off the articles statistics.
The study found that while 45 percent of the EULA was concerned with limiting users' rights, only 27 percent of the GPL concentrated on this aspect.....And while 40 percent of the EULA limited remedies, the corresponding figure for the GPL was 22 percent.
If you take away the 51% of the GPL that has little mirror i
Re:Follow up (Score:3, Insightful)
Another error in the article (Score:2)
The study pointed out that if a developer wanted to create free or open source software which he or she wanted to use in proprietary software without that proprietary software itself coming under the GPL, they could use the Library GPL, which was specifically designed for this purpose.
The developer, as the copyright holder, is free to release their code under whatever restrictive licences they like, even if it was previously released under GPL.
Agencies/Companies requiring EULA type licenses. (Score:3, Interesting)
In a phone conversation with an IT worker-bee at a State Government agency I was informed that we could not use certain software due to fact that it is freeware. The word freeware, not Open-Source was used. In my amazement I was blurted out that it was one of the "dumbest things I ever heard" and was told that the State IT governing board wanted a license just in case they needed to sue somebody. This begs the questions:
1. Doesn't the EULA, as mentioned in the story exclude most remedies, including litigation?
2. Do you really think you can win such a case?
3. If you do win (and pig's fly), will that change the software, or will you get some monetary settlement? Meaning your stuff is still broken.
This comparison is something I will definitely keep close for my next conversation involving proprietary vs OS licenses. BTW the software in question was Tomcat.
PHB? (Score:2)
OK--I have a little Karma to burn, so I'll ask the question.
What's a PHB?
The only thing I could come up with was "Player's Handbook", but I know that can't be right. It sounds like some corporate term, but it's not one I'm familar with.
Re:PHB? (Score:5, Funny)
>Hang your head in shame!! You call yourself a geek??
Someone who knows the AD&D reference but misses the business reference? I'd let him keep the geek status....
how a monopoly values it's users (Score:5, Interesting)
Some features about software covered by the EULA:
Really Apples vs Oranges? (Score:4, Interesting)
Most of the comments suggest the GPL is developer-oriented whereas the EULA is user-oriented.
What is the EULA for Free SOftware then? Unlimited use, unlimited copying, no requirements or obligations to provide second or third-parties?
Someone needs to write the definitive GEULA. (or should that be GNEULA?)
Re:Really Apples vs Oranges? (Score:4, Funny)
Though it would be essentially redundant, I guess our GNEULA could look like this:
#1 - Please read up on Copyright law to learn what you are able to do with this software. This is basically your distribution/fair-use rights. We could have written the law text here, but since the gov't has done it already we figure we'll save our breath.
#2 - Read our included LICENSE.GPL, LICENSE.BSD, or other file to learn about the additional freedoms you have.
#3 - Instead of Yes/No, there is only an 'OK' button. This is because you have to accept Copyright law (it is not a question), and we don't care if you accept #2 or not (if you don't want your extra freedoms, no harm to us).
Microsoft's EULA's shouldn't be enforceable (Score:3, Interesting)
After getting all the paperwork done, getting the loan from the bank, and even having the realtor say "It's all yours," I went to move in. Surprisingly, I discovered a note on the front door of my new house.
It read "Although you have purchased the physical property and the materials used in building this house, the architectural designs are still copyrighted by us. Because of this, we reserve the right to tell you how you may use it. By opening this door and entering the house, you agree to abide by the terms of this agreement."
It went on for five pages, but some of the points in there were the following:
-You may not use your front porch to say anything negative about the realtor.
-You must call us up to get permission if you wish to modify the house in any way (e.g. install new cabinets, doorknobs, shower heads, light bulbs)
-We may place hidden video cameras in the house to collect information about how it's being used.
-You may sell the house to another buyer only once.
and of course my personal favorite:
-We may change the terms of this agreement at any time by posting them on our website.
Okay, obviously I'm lying here. None of this really happened. But my point is that the agreement on the front door would have been legally unenforceable. It was not presented at the time of the purchase, it was never signed by me, and if they tried to sue me for breaking the agreement, they would be laughed out of court.
And yet, every one of these points have had similar clauses in Microsoft software licenses. Furthermore, the EULA is not signed at the time of purchase. I never even see it until I install the software. What's the difference between the EULA and this hypothetical note on the door? In my opinion, neither of them should be legal.
So if the EULA can change at any time... (Score:3, Interesting)
The second would be that I am bound to whatever the EULA is at the time I am found to not be in compliance with it. Again that doesn't seem to be legaly binding either, as I agree to what the EULA at the time I agree, not at the time it is used against me.
I definetly not, nor was I ever, a student of law, any lawer types out there can tell me how I can bound to a contract that can change at any time?
Re:So if the EULA can change at any time... (Score:3, Informative)
Of course you only agree to th3 EULA that is current when you argee to it.
However it say that any UPDATES (read service packs) May come with an updated EULA, and that IF you install them you have to argree to the new EULA which could say anything about anything (even if the service pack does not update it)
Basically, if you want to keep current they hold you by the balls.
Difference is more notable to a community (Score:3, Insightful)
Most people aren't programmers. Most programmers don't have time to fix every bug or add every feature they want.
That the GNU GPL gives *you* these freedoms isn't the important part, it's that it gives *everyone* these freedoms.
MS EULA treats people as lone individuals and prohibits sharing/helping. The GPL expects this and flourishes when sharing and helping occur.
Ciaran O'Riordan
What the world really needs... (Score:3, Insightful)
are more laywers pretending to be IT people.
From the article:
Okay, so what we have here is an analysis of "legal documents" by a group of people who are not lawyers. Hmmm, that somehow knocks the whole analysis idea. This is more like having a mechanic perform an autopsy and write a coroner's report.
The real difference (Score:3, Funny)
GPL: My program is finished! You can take my baby and do whatever you want with it!
MS EULA: You use our program and your first born baby belongs to us.
Re:wait... (Score:3, Insightful)
Re:Eh? (Score:2)
The whole article is 30 pages long. The section you quoted is just a reference to one aspect of the GPL.
Re:For the Click Lazy (Score:3, Informative)
The study itself [cyber.com.au] seems to be unaccessable, but you can find a html version [google.com] in Google's [google.com] cache.
Re:What counts as a derivative work? (Score:2)
Jeroen
Re:What counts as a derivative work? (Score:3, Funny)
and if you ever use a GPL software, YOU are GPL'ed as well!!
DO NOT USE GPL SOFTWARE, IT IS EVIL!!
-- this information ad was brought to you by Microsoft PR Department --
Re:LGPL (Score:3, Informative)
As I understand the LGPL, there are two situations:
Re:cannot be used as a webserver (Score:3, Informative)
That's OK. I dont expect Windows XP to be a webserver. Just install Apache and use Apache as a webserver.
There's a license limit of how many connections you can have at any given time. This license limit is part of XP for any app. I extremely doubt any non-MS software checks whether or not their on XP Home or XP Pro and throttles the connections, but its there in the license. If Slashdotters can complain about people violating the GPL then what will