Slashdot Mirror

An anonymous reader writes, "PC manufacturer Acer is complaining that Microsoft has jacked up the price of Vista, and that the basic versions are so basic no one will ship them. Since the collapse of the Microsoft anti-trust case under the Bush administration in 2001, manufacturers have no choice but to accede, adding hundreds of dollars to the cost of each PC. With Gates now proclaiming victory over European regulators, Microsoft once again seems unstoppable. But Microsoft had drawn itself close to the Republican Party. With the Republicans now evicted from the House and Senate, is it time to look at the Microsoft anti-trust suit? Could Microsoft be compelled to lower its inflating Vista prices, or to open their tech or even supply funding to Linux-flavored Windows such as Wine? What do Slashdot readers think about the likelihood of another go at breaking up the Windows monopoly?"

Roblimo writes "For years there's been fear that the Wine Project would get sued by Microsoft at some point, and this fear has kept IBM and other major free software-using companies from participating openly in it. Now the Software Freedom Law Center, headed by Columbia University law professor Eben Moglen, is offering free legal services to Wine (and other FOSS projects) to allay corporate fears and head off potential lawsuits."

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."

jvm writes "Attempting to raise the level of the discussion, Dan 'theoddone33' Olson has put together a list of ten critical observations that every potential Linux gamer should consider before buying Transgaming's WINE-based product Cedega (formerly WineX). Dan invites credible rebuttals to the points he's raised. The debate over the value of Cedega/WINE as a solution for the nascent Linux gaming community continues..."

Kelly McNeill writes "osViews/osOpinion received the following letter from SpecOpS Labs. This letter is in response to the WINE HQ Weekly Newsletter, Issue 222 dated May 14, 2004, entitled "PROJECT DAVID USES CODEWEAVERS CROSSOVER OFFICE". Their objective in writing this letter is to clear up some of the issues raised on the statements contained in the aforementioned Newsletter, which they believe might misrepresent their efforts to expand the availability of Windows applications on Linux."

Alex_Ionescu writes "WineHQ brings us the scoop on the latest developments in ReactOS, as well as on Steven Edward's excellent job on porting Wine to MingGW and linking the two platforms together. This is an interesting insight into the WINE and ReactOS project, and a must-read for anyone interested into the future of Windows-replacement projects like these."

Alex_Ionescu writes "WineHQ brings us the scoop on the latest developments in ReactOS, as well as on Steven Edward's excellent job on porting Wine to MingGW and linking the two platforms together. This is an interesting insight into the WINE and ReactOS project, and a must-read for anyone interested into the future of Windows-replacement projects like these."

SilentBob4 writes "Today, a review of CrossOver Office 3 (written by Preston St. Pierre) as well as an interview with the founder of CodeWeavers Inc., Jeremy White (written by Adam Doxtater) have been published for mass consumption. It looks like CrossOver Office/Wine has come a long way since the dark ages of Linux science. Congratulations to the developers on both teams on a job well done. The interview with Jeremy is better than any I have seen recently."

This almost turned into a "State of the Wine Project" discussion, but that's where your highest-moderated questions led, and Jeremy responded with his usual wit, wisdom, and candor. 1) Moving Target - by andrew_j_w

Do you ever get disheartened when Microsoft announces a new API, as that means you've suddenly got a whole load of new code to replicate? DirectX would seem to be a prime example of this. How do you see .Net/Mono in relation to Wine? Do you think they will ever become the prime method of running Windows applications under *nix?

Jeremy:

We really don't care what APIs Microsoft publishes - the only thing that matters to us is what APIs are used by the applications we want to support. In fact, Wine only implements about half of the Windows APIs. Now some (like my wife) might argue that's because we're just lazy, but the truth is that over half of the Windows APIs have never been used!

So we certainly do have a moving target, but it's a target that moves at a relatively slow pace. We'll begin to feel some serious pain when applications are released as 'Longhorn only', particularly if those applications are dependent on some form of DRM or on some technology that is locked up by patents.

But luckily for us ISVs move much more slowly than Microsoft, so we should have plenty of time to keep up.

In fact, we get more pain from Linux distributions, who work at break neck speed to break Wine.

2) Educational Software - by north.coaster

It seems like most of the effort so far has been to get office productivity software (ie. Microsoft Office) to work on Linux. However, there is a market for low cost home computers that Linix could help to fill if the educational software that kids use (such as the Reader Rabbit series) could run on Linux. Why is this potential market being ignored?

Jeremy:

Yes! I would dearly love to support schools and the use of Linux. Especially when you consider LTSP, Linux is just such a great fit for the educational environment.

Unfortunately, the reality of Wine and economics makes this hard. See, we do our best when we can focus in on a small number of applications (e.g. Microsoft Office) for which a lot of people are willing and able to pay money. Schools, unfortunately, have the reverse situation - they need support for tons and tons of applications, and they have no money .

Now the very first thing I'm going to do when I win the lottery is go buy a stack of kids games and pay some Wine hackers to get them to work (seriously; you can ask my co workers, they're sick of me talking about this pet project). Unfortunately, the last lottery ticket I bought was a bust.

But I am really encouraged in a variety of ways. First, we always hope that our paying customers will help us to do enough 'collateral damage' that more than just the applications we focus on will work; that seems to be really happening now. Second, there is a real growth in the games/DirectX support in the Wine project. There is a great group of games hackers on the Wine project - volunteers all - and their work is really helping Wine to run a lot of games (the fact that Half-Life now works in CrossOver has somehow made the proportion of QA time to development time go up around here *grin*).

Finally, we are starting to get some support for educational software; we have a very meaningful pledge for Acclerated Reader on our compatibility center (http://c4.codeweavers.com). We hope to get to that soon, and we're told that will help unblock a lot of educational organizations.

3) Isn't this effort endangered by software patents? - by rben

If the EU really does pass the software patent law under consideration and the U.S. adopts that treaty that Bush is pushing, won't MS just be able to sue any compatibility products out of business?

Jeremy:

Yes, I think that all xGPL software is seriously threatened by patents.

Wine, I think, is safer than a project like Mono, in large part because Microsoft has only really started an aggressive patent process recently. I am not aware of any patent that the Wine project infringes upon, and no such infringement has been brought to our attention in the 10 years of the projects history.

That doesn't mean that the patent laws cannot be used as a club against Free Software projects, particulary when you realize that volunteer projects and smaller companies like CodeWeavers generally cannot afford to even fight for a dismissal of a ridiculous claim.

With that said, I think that there is a large number of very determined people in our community, myself included, that will fight strenously to see that any such abuse of the patent system will be challenged.

Further, Microsoft making the choice to use patents as an offensive weapon will be a clear sign that they are becoming desperate. It is fairly rare for a large company to use patents offensively against a smaller entity; it is generally frowned upon by the courts, and would also play very poorly in PR circles.

So, yes, it's a worry, but there will be reasons to rejoice should Microsoft try to wield that hammer.

4) LGPL Licensing - by Stealth Dave

How has the switch to LGPL affected contributions to the project, both positively and negatively? When the switch happened, there was a lot of noise from groups like Transgaming who needed to license proprietary technology from third parties, and the formation of the ReWind project. Has there been a noticable effect on contributions to WINE from outside groups as result of the licensing change?

Jeremy:

Okay, I'm biased on this one. I am a strong advocate of the LGPL.

However, I think the effect has been extremely positive. For example, here is the historic count of lines of code added to Wine each year:

2003: +247,471
2002: +159,393
2001: +104,641
2000: +119,796
1999: +164,910
1998: +132,235
1997: +48,566
1996: +56,748
1995: +19,345
1994: +42,746
1993: +36,487

1998/1999 was when Corel's involvement in Wine was at its highest (and Wine owes Corel a debt of gratitude; they were great to Wine).

2003 was the first full year of the LGPL. You do the math.

Further, prior to the LGPL split, game development in the public Wine tree was pretty well dead. Everyone was waiting for Transgaming to return their changes, and nothing was happening.

After the split, it became clear that those changes weren't coming back to the public tree. This led to a number of volunteers taking up the challenge and improving Wine's DirectX and other game support. This has led to a resurgance in Wine's activity on games. Historically, Wine has always been focused on games, so I am personally gratified to see it return to those roots, since it's not an effort we've been able to help on much (because folks don't buy large corporate support contracts for games :-/).

Additionally, a number of people seem to prefer the LGPL; we seemed to get an influx of new blood to the project as a result of the change. Further, our cooperation with other xGPL projects like ReactOS improved, and so we got some further energy from there as well.

5) MS Security Updates Apply? - by PSaltyDS

I can see that security holes that come from Windows OS code shouldn't effect the CrossOver Office Win98-like implementation of the APIs. Security holes that come from the MS application's code may or may not be present in that environment, but how do I know? What types of MS security updates apply to my CrossOver environment, and which don't? Are any of the security houses (like e-Eye) testing for vulnerabilities in the Linux/CrossOver (or Linux/WINE) space?

Jeremy:

Actually, much to our great surprise, the Windows Update service runs fully and completely in CrossOver. Further, we go to great pains to make sure that Office service packs apply cleanly (and we mostly succeed :-/).

We also go to all kinds of interesting lengths to avoid problems with viruses and worms. For example, we have a hack in our flavor of Wine*, in the CreateProcess call (the code to start an executable) that basically checks to see if the parent process is outlook.exe, and if it is, we crash and burn, preventing many of the worms and such from running. We also have customers that have set up chroot environments, and since Wine runs in user space, that is a theoretically perfectly secure environment.

Finally, one advantage of Wine/CrossOver, is that any infection is cleaned quite quickly with rm -rf ~/.cxoffice (and easy backup/restore methods exist).

But, for all of that, I don't want to dismiss this issue. I think anyone using Outlook (anywhere, not just CrossOver) should use a strong server side scanning product. Further, I think that the use of IE in Wine should be constrained to only those cases where it absolutely has to be used. The real truth is that when you're running Linux, you're inevitably going to be less paranoid about updating and securing any Windows environment, and that sort of neglect can lead to trouble.

* Changes such as this hack to Wine are internally referred to as 'Proprietary advantages'. We are seeking patents on such methods of gaining a market advantage (grin).

6) Viral Licensing Question - by KlomDark

Aren't you worried that you'll corrupt Linux with the viral Windows licensing scheme?

Jeremy:

Now you've learned my dirty secret, and I'll have to kill you all. I've actually been hired by Microsoft to poison this little communist enclave you have going here. You'll note that since our introduction of CrossOver Office, OpenOffice has withered and died on the vine, clear proof that we do great harm to open source projects. The dissolution of Mozilla into Firefox was a clear gesture of despair on their part over our support for IE.

Further, our use of 'proprietary advantages' to create lock in has clearly emboldened companies such as Novell to preserve and extend their proprietary lock ins on products such as the Ximian Connector...

Bwahahahaha. You're all doomed!

[grin]

7) Source-level Compatibility? - by cgreuter

I hear a lot of talk about binary compatibility with Windows, but not so much about source-code-level compatibility. What sort of efforts, if any, are being made toward letting people trivially recompile existing Windows programs to run natively under Linux/X? Have any commercial software vendors considered taking this approach?

Jeremy:

My original passion for Wine had nothing to do with running existing code. I've always loved the source porting angle much better than binary compatibility (hence my ill fated affair with TWIN aka Twine).

The good news, is that after seeing the error of my ways, we put a lot of energy into making source compatibility work extremely well. Francois did a lot of work on this, and Dimi and a few others have picked it up and really made this process sing.

I understand that the Windows build of Abiword now compiles and runs cleanly in Wine. I know that simple applications, like all of the Petzold examples, build and run in Winelib.

What's interesting (to me, anyways, the rest of you can yawn and skip to the next question) is that I've come to realize that source compatibility really isn't that important. The difference to the end user between a gcc compiled Winelib app and a Visual C++ build Windows app running with Wine is...nothing, except maybe the Visi C compiler builds slightly better, faster code.

Corel realized this; they spent an enormous amount of energy working towards a source port, and eventually just shipped a binary solution. It wasn't popular, but it was wise, imho.

However, what Winelib does allow, that *is* wicked cool, is that you can port a Windows app to a non x86 platform quite easily. I don't really know of anyone that really values this (i.e. is willing to pay big bucks for it), but it's cool, nonetheless.

8) Microsoft Source? - by NinjaPablo

If Microsoft were to release more source code (legally, not the leaked source from a while back), or if Microsoft approached the Wine team and offered access to portions of the Windows source code, would you accept it? What if it involved an NDA or adding non-GPL portions to Wine?

Jeremy:

Well, I would refuse any kind of legal agreement that would jeapordize the ability of Wine to move forward openly and free of any MS license entanglements.

But that doesn't mean we couldn't use further help; there are certainly large areas of the Windows API that we struggle to understand, and we could certainly use some help. I, for one, would like to have seen the consent decree put in place an oversight board; while Microsoft has opened their documentation considerably since that decree, we have no one to turn to to ask for further clarifications and further information.

9) Tax Software? - by mengel

Every year I end up having to boot MSWindows in order to run Tax software. It's pretty much the only time I boot MSWindows anymore, and I end up doing a lot of work to keep that environment around and running just for that one, annual, task. And it's not just me, we have had several [slashdot.org] articles [slashdot.org] here at Slashdot discussing this topic at great length.

Are you guys working on a deal with any of the tax software publishers to ensure their software runs under Wine each year?

If not, would you consider it?

Jeremy:

Well, we're working very hard to encourage ISVs of all kinds to work with us to bring their products to the Linux market.

And we've had some very positive responses, but I can't really tell you much more than that just yet. However, I will tell you that we are not working with any of the Tax software providers.

Candidly, that's a pretty tricky one. Because each version of Tax Software is so ephmeral, and because we get such a short time window to test and work on it, they're really hard to nail. Further, it's not clear to me that we'd really make enough money to begin to cover the costs involved. If we could, I'd do it in a heartbeat.

Feel free to assemble a possee of interested folks at http://c4.codeweavers.com; we will absolutely listen to customer demand.

10) Project David - by mfh

We've heard that Project David could be a CrossOver Office rip-off. To what extent is David a fraud and what are your options to combat those who would misrepresent themselves using your products for VC or even illegal/infringing sales revenue?

Jeremy:

Well, I don't know anything more about Project David than anyone else who reads Slashdot, but imitation is the sincerest form of flattery, I always say. It's clear from Mike McCormack's research that it uses a version of Wine that we've released. Note that that's not necessarily fraud or a rip off of any kind - our Wine is LGPL, and it allows for just that sort of thing.

My opinion is much like others on Slashdot - they're clearly in the early stages, and don't really have a particularly impressive set of web pages. Further, they haven't really described their technology in any meaningful way.

However, this is one of the great things about the LGPL. It allows for us to have competitors spring up and try to build on our work. This is - heaven forbid - good for customers. We have to work harder and better to make sure that we continue to give our customers what they crave.

The only thing that bothers me when folks like the Project David guys come along is when they don't honor the work of those that have gone before.

I am only here today because I am able to use the hard work of many, many people who have generously given their work to us all to use. I think Alexandre has successfully eradicated the last line of my code in Wine (and he stubbornly rejects my patches, too), so nothing is Wine is anything I have built. And yet my entire livelihood and that of my family is built on Wine.

I am deeply grateful to the people that let me sell their work - even though I have paid them nothing - and the least I can do is respect and acknowledge their work.

So it bugs me when people like Project David (and others like it) come along touting their wonderful Windows compatibility without giving any props to the people that have worked so hard on Wine.

Ain't illegal, ain't fraud, but it just isn't cool in my book.

[/soapbox]

At any rate, I think that's it. Thanks for asking!

Cheers,

Jeremy

There have been recent reports about programs from Israel, Canada, and The Philippines that let you run Windows software in Linux. Are they really new? Can they succeed? Is this whole effort worth the time and trouble going into it? CodeWeavers CEO and Wine maven Jeremy White ought to know, since he's been working to bring Windows software to Linux users for many years -- with quite a bit of success. We'll forward 10 - 12 of the highest moderated questions posted here to Jeremy, and run his answers as soon as we get them back.

IamTheRealMike writes "Well, the attendants are back home and the writeups have been written - WineConf 2004 is over, and Brian Vincent of Wine Weekly News fame has written a comprehensive account of the conference. Wine hackers the world over congregated in snow-covered Minneapolis to talk shop and try and locate the magic bullet to make Wine better, faster. Cheers!"

IamTheRealMike writes "Well, the attendants are back home and the writeups have been written - WineConf 2004 is over, and Brian Vincent of Wine Weekly News fame has written a comprehensive account of the conference. Wine hackers the world over congregated in snow-covered Minneapolis to talk shop and try and locate the magic bullet to make Wine better, faster. Cheers!"

jvm writes "If you're a gamer with a pulse, you've probably heard about the impending release of Valve's Half-Life 2. As a gamer and a Linux user, I always get a little stirred up about the whole Half-Life situation, where we have a dedicated server but no client. So here's my reflection on the sad situation, past and present. How will the rest of the Linux gaming community react to the release of Half-Life 2? Boot into Windows? Wait for WINE or WineX support? Get the Xbox version? With so many Half-Life servers running on Linux, will the same be true for Half-Life 2?"

Shisha writes "Linux Planet is running a story about a new Wine offspring. Basically the Canadian company Transgaming decided, that their version of Wine, WineX, is good not only for running games, but for other Windows programs too. So why not try to sell it? For marketing reasons they're selling it to corporations under the AclereX name. Their website has a datasheet with more details about what they are actually offering. Unlike CodeWeavers, they don't seem to be targeting individuals at all, they'd rather sell to corporations. So no downloads available, sorry. Still it could speed up Wine developement, which is always good. Wine Weekly News discusses some of the reactions of the original Wine authors."

orv writes "When Andreas Mohr found that his new wireless networking card wasn't supported under Linux rather than returning the card and getting himself a supported one, he decided to set up a project to write his own drivers instead - http://acx100.sourceforge.net. Companies such as D-Link had initially promised to release linux drivers for these cards but later backed down from that promise and announced that Linux would not be supported and that customers should not hold on to the cards in the hope of getting them working, as shown on their current FAQ. Texas Instruments, the makers of the chipsets upon which these 802.11b+ cards are based refused to release code or specifications for the cards, no doubt for similar reasons that were recently discussed here. The fact that the current alpha release is certainly as good, and in some areas better, than the binary drivers that escaped from one of the card manufactureres speaks volumes for the quality and determination of the team to create their own drivers."

bltfast32 writes "I don't know how many people have been following this, but this is definitely worth keeping an eye on. Whil Hentzen, prominent FoxPro and Linux advocate, has received some heat lately for publishing a HOWTO in the March 2003 FoxTalk issue for running Visual FoxPro 8.0 on Linux with WINE. Of course, the aforementioned heat, is coming from Redmond. Here is a link to a nice summary of the interactions by Whil." That summary mentions the Register article online here. bltfast32 also points to another article which requires registration.

An anonymous reader writes "Brian Vincent of Wine Weekly News fame has started a new series of interviews with the Wine developers, over at the newly redesigned WineHQ site. The first interview features Über-hacker Ove Kåven, while the second one (hot off the press) features long-time Wine hacker Dimitrie O. Paun. Cheese anyone?"

An anonymous reader writes "Brian Vincent of Wine Weekly News fame has started a new series of interviews with the Wine developers, over at the newly redesigned WineHQ site. The first interview features Über-hacker Ove Kåven, while the second one (hot off the press) features long-time Wine hacker Dimitrie O. Paun. Cheese anyone?"

An anonymous reader writes "Brian Vincent of Wine Weekly News fame has started a new series of interviews with the Wine developers, over at the newly redesigned WineHQ site. The first interview features Über-hacker Ove Kåven, while the second one (hot off the press) features long-time Wine hacker Dimitrie O. Paun. Cheese anyone?"

An anonymous reader writes "Brian Vincent of Wine Weekly News fame has started a new series of interviews with the Wine developers, over at the newly redesigned WineHQ site. The first interview features Über-hacker Ove Kåven, while the second one (hot off the press) features long-time Wine hacker Dimitrie O. Paun. Cheese anyone?"

e8johan asks: "I have been thinking about trying to sell a Linux based thin client solution to different markets, like schools. One of the big problems with migrating to Linux is the loss of old applications such as Microsoft Office. Has anyone tried to combine Wine and the LTSP? Does it work? If so, it would enable me (and anyone else) to sell services based on a free (as in libre and beer) server running both open office and their proprietary equivalents in a Windows-like environment, thus reducing the migration costs and making the offer more attractive." While this would be an interesting to tackle, would the licensing terms on some proprietary packages complicate such a system?

S asks: "In my opinion, one of X11's most underrated features is the ability to export the display of an [X] application to an X-Server that can be physically separated from the application's host (use a remote display). I have used this countless times to dramatically increase my ability to 'get stuff done' from a distance. Recently I discovered Cygwin's ability to run XFree86 in rootless mode (startx -- -rootless) where there is no main X root window, and imported displays get their own 'native-looking' window on the Microsoft Windows platform. This also has saved me much headache when working from a Windows machine to do Linux-type things. My question is: Is there some way to export the display of Microsoft Windows windows to a remote X-Server? I'm not talking VNC/RFB here, and terminal services (via rdesktop) ALMOST fits the bill, but I don't want a root window. I want to simply export the display of (say... photoshop) to my X workstation. Googling is not an easy task; 'windows' is too much of a generic term to get usable results. What I have found, however, suggests Wine as a buffer between native Windows GUI calls and the X protocol, but offers no actual solution. Does anyone know of software that allows allows Windows to export the display of its windows to an X server (ie, an X-Client wrapper for Windows)?"

taviso writes "Ever wondered what would happen if you could compile and run cygwin under wine ? What about compiling wine under cygwin ? well these guys have, and are planning to nest the two environments as many times as possible to see if wine can take the strain, and not without good reason: 'Having such virtualization environments run within each other is an important milestone in the lives of these projects, it is a remarkable technical feat that requires a great deal of maturity'. "

willo asks: "I recently built an on board computer for my Grand Cherokee. The initial uses for it include music, gps navigation, on board diagnostics and a baby cam so I can see how my kid is in that rear facing seat. After lots of research and testing, I'm really disappointed with the mapping software out there for Linux. Gpsdrive provides the basic functionality I need, but the street names are built into the image and are difficult to read at a glance while driving. Not to mention that it has to download the maps it needs ahead of time. Xastir can handle almost any map out there, but it reads through every map for each redraw! It also seems to lack the ability to zoom intelligently based on location. Note that it's not really designed to be a navigation aid, but rather a ham radio APRS tool. (I am a ham). Delorme Street Atlas USA does what I really want, but it's been a pain to make run properly under wine. Is anyone else out there working on a decent navigation application?"

"To be really usable navigation software should do the following:

• handle maps efficiently and draw them quickly
• have intelligently organized map sets for countries/states. (You can't download a friggin map in the middle of Montana!)
• include serial gps/gpsd support. (just about everyone has this)

I've found a few references to mapping projects that seem to just be vaporware.

Map Sources do exist for this! Bruce Perens made TIGER/line data availible. NAVTECH is the map source for pretty much all the vehicle navigation systems out there, and high resolution maps are availible from the Geographical Information Survey."

FeeDBaCK writes: "As many of you may not know, Wine is currently being ported to Mingw for the ReactOS project. An update to the status of some of the Wine native Dlls under Windows was posted to the wine-devel mailing list. What this means is that there are now some Wine Dlls, which contain no Microsoft code, that appear to be interchangeable with the official Microsoft Dlls with no apparent loss in functionality. These Dlls include imagehlp.dll and riched32.dll. This comes as a great win for Wine, and brings them one step closer to bringing Windows applications to Linux." There's still a list of not-yet-functioning ones, but this is nice news.

Mister Snee writes: "As of the latest WINE release, the developer who's been working on the ActiveMovie and DirectShow code for the last nine months suddenly pulled it all from the source tree, citing fears of trouble under the DMCA." And an anonymous reader submits: "TransGaming Tecnologies is offering much of its own proprietary code up for exchange if Codeweavers are willing to relicense some of their code under the less restrictive (more free) X11 licence (eg contributing it to the X11 fork of wine, Rewind). Details can be found at this post by CEO Gavriel State. This all came from the Codeweavers-dominated recent licence change (to the LGPL) which was done in an attempt to steal TransGaming's Direct3D code and force them to open up all their work (thus have no means to make money)." Your attitude toward these license machinations may vary; Codeweavers seems unlikely to oppose people making money from WINE development.

Mister Snee writes: "As of the latest WINE release, the developer who's been working on the ActiveMovie and DirectShow code for the last nine months suddenly pulled it all from the source tree, citing fears of trouble under the DMCA." And an anonymous reader submits: "TransGaming Tecnologies is offering much of its own proprietary code up for exchange if Codeweavers are willing to relicense some of their code under the less restrictive (more free) X11 licence (eg contributing it to the X11 fork of wine, Rewind). Details can be found at this post by CEO Gavriel State. This all came from the Codeweavers-dominated recent licence change (to the LGPL) which was done in an attempt to steal TransGaming's Direct3D code and force them to open up all their work (thus have no means to make money)." Your attitude toward these license machinations may vary; Codeweavers seems unlikely to oppose people making money from WINE development.

Mister Snee writes: "As of the latest WINE release, the developer who's been working on the ActiveMovie and DirectShow code for the last nine months suddenly pulled it all from the source tree, citing fears of trouble under the DMCA." And an anonymous reader submits: "TransGaming Tecnologies is offering much of its own proprietary code up for exchange if Codeweavers are willing to relicense some of their code under the less restrictive (more free) X11 licence (eg contributing it to the X11 fork of wine, Rewind). Details can be found at this post by CEO Gavriel State. This all came from the Codeweavers-dominated recent licence change (to the LGPL) which was done in an attempt to steal TransGaming's Direct3D code and force them to open up all their work (thus have no means to make money)." Your attitude toward these license machinations may vary; Codeweavers seems unlikely to oppose people making money from WINE development.

Moridineas writes: "Since the wine project decided to change from an X11 style license to an LGPL license, a BSD fork has emerged, called Rewind (for 'Re-engineering Windows,' or something like 'Rewind to the old Windows days' in the words of Ove Kaaven) and currently hosted at http://rewind.sourceforge.net (but looking for a new home). The announcement of the fork and some additional information was posted to the wine-license mailing list [winehq.com]. At least one company [transgaming.com] has already stated that they will not be able to work with the LPGL wine (citing among other things, possible DMCA violations) and will be actively helping Rewind (with cash and code it seems)."

uhmmmm writes "The Wine developer's votes are in. Wine will change license, as was suggested would happen, but it's not yet decided to what exactly. Alexandre notes 'We now have to decide the implementation details, like the exact license used, whether to require copyright assignments, etc.'"

isolation wrote to us about the proposal to change the Wine license to LGPL. Jeremey's got his ideas and reasons in the e-mail there, and it makes sense - Jeremy's a smart guy. There's a call for opinions on this as well, so read through it, and offer commentary.

matroid writes "Wired reports that the upcoming WINE version 1.0 may be just what Linux needs to get users to migrate from Windows to Linux."

Dr. Spork writes "If you want to read a discussion about OSS licenses that is not a flame war, check out this week's Wine Weekly News. Among the highlights are Gavriel State's arguments for keeping WINE on a BSD-style license. His company has been criticized for not releasing some very cool D3D code. He claims one reason is because 'there are companies out there who will benefit significantly from commercial use of this code, and who can afford to sponsor a portion of the development cost. Until such a sponsorship happens, we cannot apply the WineHQ license to that code.' GNU purists might think it's in bad taste to use the code as a hostage, but in a world where many rich companies rely on OSS, perhaps this signals the emergence of a new business model. You might call it 'code brokering,' and interestingly, you can't do it with the GPL."

ghost_crab asks: "After finally getting the guts to fdisk all my M$ problems away, I find myself happier and less stressed. Now all I want for Christmas is a good, solid Flash editor, a la Macromedia's Flash, or even Adobe's Live Motion, neither of which run well with WINE. I have queried both companies for projected *nix releases, and both have instead emphatically supported the EvilEmpire. A search with Google and of SourceForge gives one little hope. Is anyone working on Flash for Linux? Open Source or Not - I would be thrilled to pay for a good Flash Editor. Is there hope for those of us who claim to be graphic designers yet cannot stomach Windows for even one more day?" Is there anyone out there working on replacements for the plugins that are only available for Windows?

Flash support on Linux has always been questionable for me. I can get it to work in Netscape Communicator. Mozilla doesn't seem to want to recognize the plugin and Konqueror? Well, Konqueror just locks up hard when it encounters Flash content...either that or it throws up lots of windows when it tries to go to Macromedia's site, which bothers me to no end. Unless other OSes gain access to richer-than-HTML-content, their users will slowly find themselves left behind in a web that's becoming more and more centered on Win32-only content, which would not be a good thing.

Eugenia writes "OSNews talks with Alexandre Julliard, the WINE project leader and also CodeWeaver's coder, regarding the future of WINE, the obstacles of the development, the WINE commercialization and lots more. An interesting read overall."

dcd asks: "It is interesting from time to time to look at what others are searching for using Google Zeitgeist The number 2 gaining request was for Moorhuhn3, which seems to be a freeware game that is popular in Germany. Searching for 'moorhuhn linux' brings up this page which when translated on google are directions and links to play it on Linux using WINE. Now two questions come to mind: Has anyone found a 'real-time' method to find out what is actively being searched for on google (I think alta-vista used to do this); Has anyone tried this freeware game, and was it interesting? For the curious, here's another web page describing this game and Linux." Back in a time before Google, I used Metacrawler for searches and that had Metaspy which I think is a good example of what the submittor is describing. I haven't tried this Moorhuhn Chicken game, but after visiting the sites, I must say it looks intriguing.

LiquidPC writes "ONLamp.com has a detailed new article on setting up and using Windows Applications in WINE, one of the many FreeBSD ports you could have alot of fun with. It also suggests going to WineHQ to find out which programs will work in wine, and which ones will not, so you dont have to waste all your time testing."

kossico asks: "For any Mac users that have needed to run Windows(tm) applications, Virtual PC has probably helped them a lot. Does anyone know of any free/opensource projects that attempt this on Mac a la Wine? If not, who wants to start one?"

Vesuri writes "TransGaming Technologies has released a patch for Wine which makes it possible to run Direct3D applications under Wine. I ran 3DMark2000 and I was impressed - it really DOES work like they promised. It's not perfect but it's a really good start!"

chromatic writes: "Looks like a company called TransGaming Technologies has been improving DirectX support in Wine. They plan to use a modified Street Performer Protocol to make money, and will eventually relicense their patches under the Wine license. Maybe I'll finally be able to run Thief!" And maybe one day Xbill will run on Windows.

Thanks to Jeremy White of Codeweavers for sending over some of the previews of Wine 1.0. I had a chance to see this during ALS, and was very impressed by what they are doing. 1.0 has Gnome/KDE integration, as well as new (better) config program, and some new launcher features. As well as doing this, they've also WineHQ, for all the Wine news that you can drink.

LLurex writes: "There's a short comment and screenshot on Ian Schmidt's Wine Page about everyone's favourite Windoze Emulator finally running Excel2000 and Word2000 (imho the only really good applications Microsoft ever published)! No more lame excuses, time to switch OS ..." The screenshot of Excel looks pretty much, well, like a screenshot of Excel. With this, two of the most persistent reasons not to run Linux appear to be fading; of course, what's to stop Microsoft from releasing versions that won't work under Wine, ever? That could be a good reason to stick with GNUmeric and pico.

identity0 asks: "I was looking at old Slashdot stories, and there seems to be a few stories about various console emulators being sued for copyright and/or patent infringement. Now I have a question: is there a legal difference between "hardware emulators" like the console emulators, and "software emulators" like WINE? And what are the legalities of both kinds of emulators? The WINE FAQ says it's not an emulator because 'Wine provides low-level binary compatibility, but currently only for OSes running on Intel-compatible chips.' - but since Windows also only runs on Intel boxes, I think I can call it an emulator."

zigzag noted a nice article Summarizing the Wine Architecture. It has some interesting technical stuff, as well as poll results asking what Wine's priorities should be (running Office came first, followed by games. I vote games, but I'm sick of having to run Diablo2 on my crappy old laptop w/o 3D Acceleration since it's my only windows box). Anyway, not a lot there, but this is a seriously important project so take a gander.

aliya writes: "Microsoft has announced Office and IE5.5 for Mac OS X in mid-2001. Given that OS X is based on BSD, what are the ramifications for those trying to get these apps on unix? Seems like a generic OS X-to-unix API translation would be a lot easier than Win32 API-to-unix. Not that I'm a big fan of the MS Office monopoly or the broken IE5 implementations, but it seems like this is going to have major ramifications for any application ported to Mac OS X." Of course, Microsoft promised products before which have mysteriously failed to appear, but still...interesting.

Sukru Tikves writes "Today on Wine Weekly News' future issue I read from that ' The Wine team is preparing to begin on the road towards the long-awaited Wine 1.0 release, but there's still some way to go, and many usability issues to clean up before even a public beta release is possible. While the wizards churn out the machine-readable source code, the Wine Weekly News plan to help by providing human-readable language mere users can read. ' "

Egonis Similaris writes " WINE 991031 (Hallowine) has been released." My main personal WINE wish is to use it to run Quickbooks. Has anyone else gotten QB to work reliably under WINE?

Douglas Ridgway writes "Alexandre Julliard, leader of the Wine project, will be moving to Silicon Valley to work full-time on Wine. See the press release for details. "

mecca writes "CodeWeavers has announced they are in the process of merging the Willows TWIN code and Wine code in order to help port Windows software." Interestingly this project is being spear-headed by Rob Farnum, the key architect of Twin. The resulting code will be under the LGPL (Twin is LGPL'd, Wine is BSD'd. So the LGPL wins).It would appear that the Wine guys are cool with this. Some Twine code is available now, and more should come soon. Codeweavers is offering employment including to people who don't want to move to cold Minnesota.

mecca writes "CodeWeavers has announced they are in the process of merging the Willows TWIN code and Wine code in order to help port Windows software." Interestingly this project is being spear-headed by Rob Farnum, the key architect of Twin. The resulting code will be under the LGPL (Twin is LGPL'd, Wine is BSD'd. So the LGPL wins).It would appear that the Wine guys are cool with this. Some Twine code is available now, and more should come soon. Codeweavers is offering employment including to people who don't want to move to cold Minnesota.