Slashdot Mirror
Windows XP EULA Discrepancies
Greg Edmiston writes "I came across some interesting ambiguities upon reviewing the Windows XP EULA which turn common scenarios into potential EULA violations. Among the potential violations include VNC, dual-processor workstations with graphics cards, and running Gnutella. Just some food for thought."
But, seriously, who gives a shit what's in any MS EULA? We all know there's going to be bullshit in any MS EULA, just as we all knew they were going to try and patent their .NET stuff, just as we all knew they'd worm their way out of real antitrust punishments. I hate to sound pessimistic here, but c'mon, does the real world ever show up around here? Ignore EULAs (MS or not) and get on with your day.
Yes, this'll hurt my karma, but I've got plenty to spare and this is actually therapeutic.
And the circumstances the author has in mind that is a breach of the license:
There is no issue here. The license refers to *incoming* connections from other devices to the workstation running XP Pro, not *outgoing* connections to other devices from the workstation, as the author describes.
Microsoft obviously want to discourage people from running servers from the XP Pro operating system (which is designed for workstation use) to encourage the purchase of more costlier Windows Server and Advanced Server operating systems.
It's good to know that Microsoft can hold AOL hostage any time they like:
Remember: umount it before you fsck it.
OK, some of this is FUD, but there are real restrictions going on here.
...available to you *from MS* through the use of the Product.
Blkdeath>They don't want you to set up a dozen dumb terminals and use them to run a Windows XP desktop
The language also seems to remove the possibility of running a single instance XP over VNC from Linux. Of course they let you use Linux in this way from their own framework, but *they control* how you do it.
MS>Internet-based services provided to you or made available to you through the use of the Product."
Blkdeath>..don't want to be tied to a web service
Then MS could make everything perfectly clear with an extra clause, e.g.
When you are in a court of law, judges and juries notice such details.
EULAs usually are not worth the paper their printed on. Just BUY the software and the EULA does not apply. If you go to Microsoft and LICENSE software it will apply. Check it out here
"You may permit a maximum of ten (10) computers or other electronic devices (each a "Device") to connect to the Workstation Computer to utilize the services of the Product solely for File and Print services, Internet Information Services, and remote access
This just slays me. For the last two years I am just dumb-struck by how much MS is pushing us back in time, not forward. For all their PR and hype about how wonderful things are, it is all just BS lately. Only 10? Hmmm - I seem to recall Windows for Workgroups 3.11 being able to handle at least 50 -- more actually, depending on what you were doing. We had printers and file locations shared off Win3.11 computers all over the place. I remember, one room full of dumb terminals, with just a floppy boot disk, a shaved down copy of WordPerfect 5.1, and a few NET USE commands that allowed a whole department of secretaries access to file storage and printing. I cannot fathom with all of the technological leaps and bounds that have occurred in the last decade why they are doing this, other than greed. Maybe it's "If they exceed 10, then they have to buy more OS licenses, or better yet a server" WTF????
At a time when more and more families have multiple computers in the house, the older ones being passed down to the kids, why on earth would they pull this now? I have 7 computers at home, my entire house is networked, even the garage. What about smart refigerators, tvs and such, that allow you to print whatever out? I'll tell you what MS, I'll allow as many computer connections to my shared printer as I please, and if your OS locks me out after 10, then I will think it truely a piece of trash. And the home version -- utterly useless -- another grab at getting more $$ out of innocent families and consumers who don't know any better, to force them to go back and pay $100 more for the Pro version. Nice work MS.
While I'm on my rant, let me throw in a little 2K bashing. Don't get me wrong, I think some of the functionality built in to AD is pretty sweet, if you wanted to use it. But MS has decided it is the ONLY way to get things done. In the past, there were many ways to approach a task, and as a consultant you got to pick which method of computing/access/production worked best. But those options are gone now. Like printing. It's cool that you can manage printers and assign them to people, if that's what you wanted to do. But tell my again, why, why, why, in this day and age, I am writing VB scripts just to get a network printer out???? I handle enough user accounts, I really don't want to manage computer accounts now too. That should be my choice. And now of course, the home user is faced with the lovely task of managing user accounts. Really a bad move MS.
Does anyone remember back when, if you wanted to get a printer to work you had to go to the back of the book and get the printer codes? Or modems, you needed the AT command to access one. Those days are long gone, and I don't miss them. But here I am, using little VB scripts that seem vaugly familiar to the old batch files of days gone by. And what is that stupid ConPrt utility again?? Why on earth do I have to leave the OS, go to a resource kit, just to be able to allow users (who don't have access to the printer folder) to print? Come on MS - this is not rocket science. We have been setting up printers for so many years now. It's real simple, when a printer is installed, you ask: Is this printer just for you, or for everyone who sits here? Third party vendors have been doing it for years. I have a team of 5, and not one of them understands VB scripting, but they were great little ghosters, knew how to put printers on and move the computers out. Now they can't make a move unless I get everything ready for them. Utterly useless, unless of course, I send them out for training and pay big buck for some MS classes - or maybe this is part of the big picture too?
For all of it's advanced possibilities, I often feel like I am back in mainframe land. And why do I think that this home/pro thing is not working? Because of 'word on the street'. I have long lost count over the number of home users I know who tell me they can't stand XP, have spent hours upon hours on the phone with tech support, just to get something as simple a shared printer connected, which they had working fine until they tried to bring XP into the mix. And then they spend even more $$ to bring it in to a shop, to have the drive reformatted so they can put Win98 back on!
That actually felt good -- thank you.