World Wine News

Hi folks,
Google announced the 2008 programme today and I wanted to use the opportunity to talk about the next steps we should take to get ready.

I will start a separate thread to start collecting project ideas, presenting the ones mentioned on the wiki page [1]. New project ideas are very much welcome. If any of you feels like mentoring one of the projects, please mention that. If you're a student with your own project idea, please mention that as well.

We will then have to discuss if we believe the projects are doable in a Summer of Code timeframe. When we talked about last year's projects on WineConf, it was the common opinion that we didn't do a very good job on that for 2007. I don't have a surefire solution for this, we should try being a bit more conservative though.

I will add some more documentation to the SoC wiki page, does anybody have a good idea what we could call the post-mortem analysis? I know this is a correct technical term, but in my opinion it sounds a bit negative. Lacking a better alternative, I'd call it review. Can the native speakers come up with something else?

Maarten, you wrote a wiki page about your 2007 experience. Could you add it to the "Helpful Links" section?

[1] https://wiki.winehq.org/SummerOfCode

Cheers,
Kai

Hi all,

I'm planning on being administrator for wine project with the summer of code 2008.

I'm looking for mentor volunteers. If you don't know what that is read take some time to read through http://code.google.com/soc/2008/faqs.html If anyone is interested, please contact me privately.

I'm also looking for project ideas, if anyone has an idea for a project for the summer of code, please update https://wiki.winehq.org/SummerOfCode . I would prefer projects that can be done by small changes at a time, like implementing changes to get an application to work, instead of something dractic like a dib engine. It should preferably be doable in 2 to 3 months by someone who doesn't have a lot of wine experience yet.

I'm also looking for people who want to help out in other ways, like updating the wiki page and creating some additional information that would be useful to students.

Cheers,
Maarten.

* Implementing a WinePluginApi so other programs can use Windows DLLs inside of Linux apps

* Improving our HTML/Win32 Help viewers.

* Implementing the ASIO audio infrastructure for Cubase

* Implement the MS Wsock dll (dlls/mswsock), an enhanced winsocket implementation

* Valgrind and Wine integration (see: Wine_and_Valgrind)

* Complete the Wine Web browser (aka. Internet Explorer) ie. frame controls, toolbar, status bar

* Full URLMoniker implementation. (IE working with builtin urlmon.dll)

* Implement transacted mode for OLE32 Storage (STGM_TRANSACTED)

* Improve cmd.exe compatibility

* Get Mozilla compiling as a Winelib application (http://www.winehq.org/winelib#mozilla)

* Run the Mauve Java test suite against Sun's Windows JRE, and file bugs / write test cases in C / fix anything it finds

* Run the MDAC conformance test suite against Microsoft's MDAC, and file bugs / write test cases in C / fix anything it finds

* pick some real-world app or game that doesn't work well, and improve Wine so it installs and runs the app better. (Some good examples might be Photoshop, Visual Basic, a game etc)

* pick a Windows feature that is incomplete in Wine, and improve the feature and its conformance tests. (Some good examples might be riched20, DirectPlay, etc)

Hey, the Valgrind developers finally merged the Wine support patches! I just built Valgrind from svn as described here: http://valgrind.org/downloads/repository.html and on a fresh install of Gutsy, it just worked, no patches.

To run Valgrind's tests under Wine, I configure valgrind with --prefix=/usr/local/valgrind-svn, then do something like

cd wine-git/tools wget http://kegel.com/wine/valgrind/runtests.patch wget http://kegel.com/wine/valgrind/valgrind-daily.sh wget http://kegel.com/wine/valgrind/valgrind-suppressions wgethttp://kegel.com/wine/valgrind/valgrind-split-pl.txt -O valgrind-split.pl patch -p2 < runtests.patch Then to run all the tests, I do

cd ~/wine-git sh tools/valgrind-daily.sh

or to run just one test, I do export RUNTEST_USE_VALGRIND=1 cd ~/wine-git/dlls/riched20/tests make test I've only verified that this works well on one machine so far, but I have high hopes. Anyone else feel like giving it a whirl? -Dan

Soldat on Wine:
The default configuration does not work, but unlike in Vista, when Soldat crashes, it doesn't bring the entire operating system down with it - the process just terminates. To get it to work, I have to turn all the settings way down, but it works... slowly.

Darwinia on Wine:
Again, its shocking to see better application compatibility on Wine than in an actual version of Windows. Although Darwinia fails to run in Vista unpatched, it runs fine under Wine (even at a tolerable speed)

Conclusion:
This post is clearly a bit biased. What shocked me though was how easy it was to find games that didn't run under Vista but did in Linux by using Wine or DOSBox. I'm not a huge gamer, so I don't have a huge collection of games to try out, but even still with just a few hours of frustrating work, I have been able to show that not only is Linux a reasonable alternative to Vista for gaming (XP is still king though), but also that Linux handles application failures more gracefully than Vista. Every game but Blackthorne crashed my Vista box, this didn't happen a single time under Linux.

It looks like they added hooks to the linux kernel to accept windows nt syscalls. Maybe they even allow using the system's normal shared library loader instead of Wine's special one. This is something I've often wanted to do, but it was way lower priority than getting wine working. I haven't looked at their project at all, no idea if it was done well.

We would, I think, like to move wineserver into the kernel sometime. It's been discussed before. Linus is not opposed to having native support for win32 system calls. A fellow at Redhat wrote a kernel module for wine a number of years ago, but it just wasn't time yet.

For a related BSD thingy, see http://www.kernel-traffic.org/wine/wn20010313_87.html#1 That project was still going as of 2006, I think, but didn't get terribly far.

- Dan

Hey, http://bugs.winehq.org/show_bug.cgi?id=11678 is fixed, and VCToolkitSetup.exe now installs for me!

Still more to do before .net 1.1 apps run, see http://bugs.winehq.org/show_bug.cgi?id=11742

And there are a few ugly looking nonfatal problems running the .net 1.1 installer, but they can wait.

Hi,

I just want to mention that I've managed to install Visual Studio 2005 completely with WINE.

1) installed "vcrun6" (with winetricks)
2) applied 1 patch fromhttp://bugs.winehq.org/show_bug.cgi?id=8439#c3
(Required for overall installation)
3) applied patched fromhttp://appdb.winehq.org/appview.php?iVersionId=3754
(Required for .NET 2.0 installation)
4) applied "msi: ACTION_RegisterProduct store all InstallProperties"
patch from wine-patches I've sent recently (Without this patch Visual Studio 2005 will think that MS XML 6.0 and some others is still uninstalled!)

Installation goes without problem, however running "devenv.exe" causes several problems with .NET 2.0 packages and crashes a lot :( too bad. Most crashes and errors are because of few missing WINE API functions, and incomplete .NET 2.0 support. Still I think WINE's close to run Visual Studio! which will be great news for multi-platform developers.

See attached screenshots from my MacBook Pro running OSX 10.5.2 at: http://bugs.winehq.org/show_bug.cgi?id=8439