Microsoft Blocking Wine Users From Downloads Site
IamTheRealMike writes "In January, Microsoft announced a new anti-piracy initiative called
Genuine Advantage. From this summer onwards all users of Microsoft Downloads will be required to validate using either an ActiveX control or a standalone tool. Yesterday Ivan Leo Puoti, a Wine developer, discovered that the validation tool checks directly for Wine and bails out with a generic error when found. This is significant as it's not only the first time Microsoft has actively discriminated against users running their programs via Wine, but it's also the first time they've broken radio silence on the project."
Didn't they do something like this with the Trillian protocol on MSN Messenger? They hate third parties.
There are 2 types of people in the world, those who find that stupid binary joke funny, and those who don't.
Windows 3.1 deliberately refused to run under DR-DOS, the competitor to MS-DOS at the time. The deliberately vague error was caused by a block of obfuscated code--google for DR-DOS AARD.
One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
"At Microsoft, security is our number one priority. You should turn off ActiveX controls and click 'no' to any dialog boxes. Service Pack 2 adds protection against these ActiveX controls, and with Windows Server 2003 ActiveX controls and other harmful content are blocked by default. This is for your own safety."
"Ignore all that, turn ActiveX on again, else you won't be able to download from us!"
What the hell?
Guy asked me for a quarter for a cup of coffee. So I bit him.
What if you have a valid purchased Office running on Wine and want to get updates for it?
I can understand Microsoft not supporting Windows downloads for Wine, but they should support Office downloads for Office, regardless of how it is run.
Sadly, the only people that are gaining anything, even when MS loses anti-trust cases, are the lawyers. I don't see this one getting that far, though.
I'm guessing that the only real downloads a Wine user would be making are updates for Office, correct? I'm drawing a blank on what else it could be. I haven't had the time to read my MS office EULA yet, but I'm guessing it doesn't specifically call out that it has to be run on Windows. That doesn't mean that MS has to provide you support if you're not. This is an automated incarnation of what has happened for years:
me> I need support
support> You're computer case isn't blue, is it?
me> yes, it is, thanks for asking
support> We don't support our software on computers with blue cases. Thanks for calling.
me> argh!
I think we've all been in that boat at one point or another.
Jerry
http://www.syslog.org/
It's just the same idea of 'compatibility' for Microsoft - changes are intended to break competitor's products.
The license for any non-OS product from Microsoft says nothing about having to run it on Windows. They assume you will, but WINE breaks that assumption. They are just pissed off about it... they may actually get themselves in trouble by not allowing people who paid for their products to update them. Just because somebody can run microsoft office on Linux doesn't mean it was pirated.
Reminds me of this...
How MS played the incompatibility card against DR-DOS
I've got to say that they DON'T have a right. I was a victim of their DR-DOS isn't compatible trick. I was forced to go buy Dos 6.0 and then it ATE MY DATA! I became rather negative towards this convicted monopolist when I found out they had done that on purpose!
Oh - did you notice that last sentence - CONVICTED MONOPOLIST. They have to play by a different set of rules.
If they are selling a package - say "Office" and someone wants to run that on another platform, then MS doesn't really have the right to restrict where it runs. They may imply they do through EULA's, etc. but this would like be easily proved as monopolist behavior - and oh yeah - they've been convicted of that already!
This behavior fits that model EXACTLY!
Have you compiled your kernel today??
I run Microsoft Office under CodeWeavers' Crossover Office, both of which are licensed (read: I paid for it), so yes, I find the news disturbing.
It also appears to be a very shortsighted move on their part while under a worldwide antitrust microscope.
one better than mcleodeight
Realistically, Microsoft isn't going to put themselves out of business, with this stupid trick or any other. They'll be around, and be a damn big company, for a veeery long time.
What I do hope and halfway expect will happen is that they'll find themselves "in trouble" by Wall Street standards -- steadily declining profits turning into steady losses, with a corresponding implosion in stock proce -- and that this will force them to become a good company making a good product at a good price in order to gain their customers' trust and support. It's happened before; if someone had told me 20 years, hell, 10 years, ago that IBM in the 21st c. would be considered one of the good guys, I'd have laughed my ass off.
The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
A lot of people are saying MS has the right to restrict downloads to people who own their software. I agree that they are liable to their customers, but some of their customers run wine.
I have a legal copy of Windows which is currently unused. I don't like dual booting. I don't like running under an x86 emulator. I like using Wine (or commercial variants of it) if I absolutely need to run win32 software. At the very least, my license to Windows should entitle me to downloads from MS--not whether or not I am using Windows to download them. They should at least give you the opportunity to enter in your product key. I'd still feel like this was obnoxious & be pissed at them, but at least people in a similar situation would be able to download programs from them.
I think what many object to is that they're being vague, at best, about what is the source of the "problem". If a message came up saying something like "Windows emulators are not supported for this operation", then there would be little room to complain. However, this is not the case, and many, myself included, suspect that MS is deliberately being vague about it, rather than having the courage (and smarts) to just be upfront about it.
Ben Hocking
Need a professional organizer?
Microsoft may have the right to refuse Windows upgrade downloads, but why do they refuse downloads of "productivity" apps like MS Office suite? As long as the software application is duly licensed, what right does Microsoft have to force the user to run it under "Genuine Windows" only?
... `till WINE won't run.
Good old Microsoft.
Same as it ever was.
If you can hack around this, more power to you, but MS is under no legal or ethical obligation to support your efforts.
Of course, there's a difference between not supporting your efforts, "accidentally" breaking your efforts, and actively trying to stop your efforts from working. This appears to be a pretty clear case of the third item in that list.
Daniel
Hurry up and jump on the individualist bandwagon!
It's not like their restricting you from running Windows on a competing platform.
What does this have to do with anything, and who said this is what was happening?
I read the article, and unless I missed something, this is NOT the complaint.
I don't use WINE to run Windows(c) OS, I run it to run some (work required) Office apps and some games.
The Office apps were purchased and presumably have rights to be updated the same as any other user of Office apps. Same with the games.
But Microsoft is saying that, because I am using a valid purchased version of their software on an OS other than Windows (by using WINE) they will not allow updates from their servers.
This is the mirror image of their antitrust loss - they were accused of using their market possition (monopoly) in the OS to maintain and grow their market position in other markets, while here they are using their market possition in the other areas to maintain their possition in the OS market.
You say you were a victim of the DR-DOS 'trick', where a competiting product was specifically checked for and then bogus 'error' messages were given, or the applications just didn't work as expected - not because of a problem with DR-DOS, but because the app was PROGRAMMED to work differently when used with DR-DOS. Like is happening here?
You say you worked at WordPerfect. Isn't that the company that worked with Microsoft to be compatable and competitive, then Microsoft changed the APIs and didn't publish them to competitors of their Office (specifically Word(c)) and royally screwed WordPerfect over?
Novell - didn't I hear their networking applications were deliberately 'broken' by Microsoft so that Microsofts' market share of networking would not be threatened? Like here?
They're just saying "don't expect to be able to use our bandwidth and download from us without being a customer first".
No, they are just saying "don't expect to be able to use our bandwidth and download from us without being a Microsoft Windows OS customer first (even if you are a valid Microsoft Office customer)." Very different than what you posted.
Acts of massive stupidity are almost never covered by warranty. --me.
No, they don't. As a CONVICTED MONOPOLIST they are explicitly prohibited from forcing owners of one of their products (such as Office) to use another of their products (specifically Windows).
Microsoft has every right to block someone from updating Office when it's being run from a Non-Microsoft Operating System...
8 ba0-3d24-4f00-aab1-dd9ff4aacfc9/en_client_eula.pdf
No, they don't. Read the EULA and it says NOTHING of the kind.
I quote from the MS Word 2003 EULA found at http://download.microsoft.com/download/1/2/5/1253
"Installation and use. You may:
(a) install and use a copy of the Software on one personal computer or other device; and
(b) install an additional copy of the Software on a second, portable device for the exclusive use of the primary
user of the first copy of the Software."
If you can point out in the EULA where I missed it and there is a statement saying I have to run this software under MS Windows, I'd appreciate it.
Until such time, I have the right to run the software under any OS I want.
-Charles
Learning HOW to think is more important than learning WHAT to think.
Sean.OutaHere()
"Unsupported configuration" merely means "I'm not going out of my way to make it work for this configuration. If it happens to work, it works, if it happens to fail, it fails. Too bad. I'm not going out of my way to do anything about it." But what Microsoft actually does when they misuse the word "unsupported" is to deliberately cripple the configuration, adding EXTRA code to look for that configuration and deliberately fail on it. (As they did in this case) They go out of their way to ensure it fails.
That means "unsupported" is not telling the whole story. It's deliberate deception.
Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.
Brilliant move, Microsoft. Now some dweeb living in his mom's basement will write an ActiveX virus that creates the Wine key in the registry, then exits.
The next time you go to Windows Update, whether you run Wine or not...