Slashdot Mirror
Microsoft Admits Targeting Wine Users
Buddha Joe wrote in to mention that the lack of Windows updates for Wine users is the result of a Microsoft's active targeting of Wine users. ZDNet has the story. From the article: "As the most popular third-party translation technology in use, Wine was the first emulator to be specifically tested for via WGA"
Do you admit to targeting wine users?
Reply:
In all fairness, most alcoholics are Microsoft's customers. We need them.
The Linux/Unix market has already cornered the stoner folks. Just look at the latest release of Solaris.
Oh... That Wine...And you mean 'targeting' much differently. Are we on the air????
It could be worse, it could be Monday.
Microsoft is still not under ANY obligation to update YOUR emulator.
...for the separation of Microsoft's Operating Systems business from the Application business, this would be it.
It's too bad this didn't happen a while back during the trial years.
From the article: "The spokesperson said users who are not running Windows XP or Windows 2000 natively can still download updates for Microsoft Office from the Office Update Web site."
To those who were saying "what about me? I'm only using Office under WINE," you can still get updates.
Bill Clinton: Pimp we can believe in. - The Shirt!!!
And I'm thrilled to have Microsoft say that Wine is the "the most popular third-party translation technology in use".
The one thing I felt she didn't emphasize enough though was that this is not a problem for Wine - we shouldn't (and mostly don't) need any OS component downloads from Microsoft. In fact, we're just finishing up work to make any need for DCOM or MSI or any other 'common downloads' from Microsoft unnecessary.
It's always nice when the other guy blinks :-).
First of all, wine is not an emulator as noted on their web page. And of course MS isn't under obligation to update the emulator, only their software. IE- WINDOWS. Their targeting of Wine and other API translators (like Wine) is nothing more than a stunt to anger the users of Windows within a Linux operating system.
If you're going to post rants, make them obvious so we can mod them down. This is nothing more than the obvious BS it is.
This is a true businessman at work. While everyone else is crying foul, this man is rallying around this news. Anyways, most of the updates coming out of MS might mess up a working Wine installation.
The issue is not Microsoft updating WINE. It's Microsoft refusing to update copies of their own software because they are running under WINE rather than their own OS. Remember, these could be legitimately purchased copies of MS applications that MS refuses to update.
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
The article on ZDNet is REALLY short and there's no excuse for anyone not reading it.
As it's already mentioned you don't have the right to use Windows Updater if you don't own Windows. It's just like you can't use Redhat Network unless you own Redhat. Only Redhat is even more restrictive with their update services than Windows Update, granted their services are more comprehensive.
Some interesting tidbits from the article...
White, CEO at CodeWeavers (acompany that utilizes Wine), said 'he was excited rather than worried to hear that the WGA validation tool was blocking Wine. "The reason we love this is because this shows that Microsoft is aware of Wine at very high levels," said White. "For us it's exciting -- it is an acknowledgement of us as a threat."
Also, the spokesperson for windows 'said users who are not running Windows XP or Windows 2000 natively can still download updates for Microsoft Office from the Office Update Web site.'
So you can still get the updates manually, which is something anyone running Wine over linux probably has the expertise to do.
The only reason we have Windows machines where I work is because of Microsoft Office file compatibility. Wine and consequently Codeweaver's CrossOver Office is a HUGE threat to Windows OS, and it's a good sign that Microsoft is forced to recognize this.
--David
Trying to run windows crap in OS2 is one of things that killed it. IBM spent so much time trying to run windows inside OS2, they completely missed supplying good OS2 native apps.
Wine is good for running old windows apps that you have ( I still Office 7 !!!???? and open office of course), but if anyone spends too much time trying to emulate windows (ala os2) then MS will simply screw you over. As soon as one thing works, they will break it.
If you are using a current MS app either 1) run windows 2) find/create a linux based alternative.
People will scream that yadddadda M$ app is just what they need. Trying to build a 'better windows than windows' is a game no one can win (not even IBM).
So Long and Thanks for all the Fish.
So, they check for a registry key to see whether or not it is on WINE. Do virii/worms/other malicious intruders now have an easier way to prevent software updates in a slightly secretive manner? Can't they just make the same key on a valid copy of Windows?
This check creates a possibile vulnerability for future trojans/viruses to exploit - they could just place this Wine key into the Windows registry, and thus block Windows updates for the user.
and cannot cancel rights granted by the Fair Use doctrine.
Right. And Gnu's Not Unix. Except, it is UNIX in everything but the official license.
So I take that to mean that Wine is not an emulator of Windows. It's Windows, from someone other than Microsoft.
In the computer world, most uses of the word 'emulation' are referring to making a piece of software work like and replace a piece of hardware. VMWare works like and replaces an X86 box. A microprocessor emulator works just like a physical chip. Mame simulates a piece of hardware that is found in game systems.
When we write pieces of software that work just like some other piece of software, we consider that to be an alternative implementation, not an emulation. Linux is not an emulation of UNIX, it's an alternate implementation. Wine is not an emulator of Windows, it's an alternative implementation.
Emulation isn't about just the implementation, it's about the LEVEL of implementation. Emulation is about making a useful device in software that behaves just like a device in the physical hardware world.
OK, this is the cue for anyone else to jump in with some counterexamples to prove me wrong...
Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!