February 2005 - Wine-Devel - list.winehq.org

Re: [OLE #62] Rework the RPC dispatch layer

by Alexandre Julliard

Mike Hearn <mh(a)codeweavers.com> writes: > ChangeLog: > - Rework RPC dispatch layer to be simpler and not get confused by > server/client duality > - Make threads shut down at the right time and not access freed > memory after apartment destruction > - Rename stub_dispatch_thread to client_dispatch_thread > - Add some more tracing This badly breaks the regression tests, apparently triggering a bug in the named pipe handling on the server side. I'm afraid I can't apply the patch until this is fixed. -- Alexandre Julliard julliard(a)winehq.org

Feb. 2, 2005

Re: RESEND: Enable GCOV Code Coverage

by Alexandre Julliard

Mike Hearn <mh(a)codeweavers.com> writes: > Also the patch looks small, it's mostly documentation, and minimally > invasive. I see no reason to reject it, hopefully Alexandre has just been > bogged down with the WM rewrite and the huge volume of patches going in > lately. The changes may be small but they are ugly IMO. I don't think we need a configure option for that, it should be possible to simply do a 'make CFLAGS=xxx' with the appropriate options. -- Alexandre Julliard julliard(a)winehq.org

Feb. 2, 2005

Re: advapi32:registry.c tests failing

by Steven Edwards

Hi, --- Aaron Arvey <aarvey(a)cs.hmc.edu> wrote: > I wanted to know if there was something I'm misunderstanding or missing. > If not I'm going to change the registry.c tests to work on Windows XP and > thus fail on Wine. I am seeing this under Windows XP as well. Thanks Steven __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com

Feb. 2, 2005

More nagging

by Jeremy White

We have 34 folks signed up for Wineconf now. I note that only 9 of the 15 folks from CodeWeavers are signed up...so I have some internal nagging to do. If cost is an issue, note that we have a (very) limited pool of funds available to sponsor travel; just note that in your rsvp (or email me privately). The web page again is here: http://www.winehq.org/site/wineconf Please rsvp! I think this will be my last nag message before we start assuming we've got everyone and start planning accordingly. Cheers, Jeremy

Feb. 2, 2005

Re: Regressions in window focus behavior

by James Hawkins

On Wed, 2 Feb 2005 10:12:59 -0500, Paul Rupe <prupe(a)myrealbox.com> wrote: > The move of update region handling to wineserver > (http://www.winehq.org/hypermail/wine-cvs/2004/12/0100.html) back in > December caused a regression in Hamster 2.0.0.1. After this patch, Hamster > steals focus constantly. When I switch virtual desktops in KDE, it > immediately switches back and reactivates the Hamster window. This is even > with KDE's "Prevent focus stealing" set to Extreme. Hamster can be > downloaded from <http://www.tglsoft.de/misc/hamster_en.htm>. > > Another patch from Jan 31 > (http://www.winehq.org/hypermail/wine-cvs/2005/01/0724.html) provokes the > same behavior in Remedy. Switching to another desktop or minimizing > the window yanks me back to it immediately. > > Both apps seem to be resisting the hide message from the window manager, but > I don't understand the interaction of these patches well enough. > > -- > Paul Rupe <prupe(a)myrealbox.com> "She smiled, in the end." > > This pattern is also observed with Ares Lite. Trying to minimize the application causes it to pop right back up. -- James Hawkins

Feb. 2, 2005

Regressions in window focus behavior

by Paul Rupe

The move of update region handling to wineserver (http://www.winehq.org/hypermail/wine-cvs/2004/12/0100.html) back in December caused a regression in Hamster 2.0.0.1. After this patch, Hamster steals focus constantly. When I switch virtual desktops in KDE, it immediately switches back and reactivates the Hamster window. This is even with KDE's "Prevent focus stealing" set to Extreme. Hamster can be downloaded from <http://www.tglsoft.de/misc/hamster_en.htm>. Another patch from Jan 31 (http://www.winehq.org/hypermail/wine-cvs/2005/01/0724.html) provokes the same behavior in Remedy. Switching to another desktop or minimizing the window yanks me back to it immediately. Both apps seem to be resisting the hide message from the window manager, but I don't understand the interaction of these patches well enough. -- Paul Rupe <prupe(a)myrealbox.com> "She smiled, in the end."

Feb. 2, 2005

Re: DLL Load Question: Please Help!

by Mike Hearn

On Tue, 01 Feb 2005 22:53:39 +0300, Sergey Efimoff wrote: > Unfortunately, I cannot use Wine as a main process (did you mean the > stuff which is now made by preloader?). My project is a complex > multi-threaded application, and the DLL mentioned above is to be only the small part of it. Why does that matter? The main reason people want to avoid their app depending on Wine is for dependency reasons, but even that is solvable. What making a Winelib app means is basically CC=winegcc CXX=wineg++ ./configure OK, so it's a bit more work than that, but really it's not a huge deal. At the end you get a shell script instead of a binary and when run your app will start up and act just like a normal UNIX app, except that you can now call Win32 APIs like LoadLibrary. The main problem is that now your program requires Wine to be present in order to start. So it's not optional. If you don't like that, just put your program code into a library, libfoobar-app then have two little stub programs that load it: one that doesn't use Wine and one that does. Then the user can pick the right one for their situation. thanks -mike

Feb. 2, 2005

Re: RESEND: Enable GCOV Code Coverage

by Mike Hearn

On Tue, 01 Feb 2005 10:39:00 -0600, Robert Shearman wrote: > I think the issue with this patch is that it isn't it doesn't appear to > be useful for a significant number of people and could be maintained as > an external patch by the people who do think it's useful. Maybe you > could try to persuade us as to why everyone should be using gcov? I'd really like to see this one go in: I think it would not be hard to set up automated dumps of the gcov output and convert them to something nice and easy to read. For people who want to volunteer but aren't sure where to start, or who aren't quite ready to dive into app compat work extending the test suite is a great thing to do. In particular it'll let us easily identify things like error codes that may be incorrect (ie, were guessed). Given the number of times we've been nailed by people guessing error codes for obscure situations and not marking them as guesses, any tool that can show what we're not testing gets a +1 in my book. Also the patch looks small, it's mostly documentation, and minimally invasive. I see no reason to reject it, hopefully Alexandre has just been bogged down with the WM rewrite and the huge volume of patches going in lately. thanks -mike

Feb. 2, 2005

Re: Wine legalities

by Ira Krakow

Another thought. Microsoft maintains a publicly available Website for the MSDN, at: http://msdn.microsoft.com It has code, knowledge base, API docs -- a large part of the MSDN subscription CDs. It could be argued that by doing this, Microsoft has released their copyright to the public domain. At the least, they have expanded the right of fair use, I think (I'm not a lawyer). Food for more legal thought. Ira

Feb. 2, 2005

Re: [Wine]How can I run an already installed Flash MX 2004 (on an /NTFS partition)?

by Scott Ritchie

Ok I finished the winetools package when I should have been sleeping, so you're gonna need to be my usability guinea pig. Install the winetools package from the same place the wine packages are (winehq), then use it to setup wine for you and install dcom. Thanks, Scott Ritchie On Wed, 2005-02-02 at 10:34 +0200, Emre Sevinç wrote: > > Scott Ritchie wrote: > > I'm almost done with the winetools package which should make installing > > DCOM98 an easy one-click affair for you. I'll update you in a day or > > two if I finish. > > Well, is there no way to use the Flash.exe which is installed on my MS > Windows 2000 partiton? > > Do I have to install Flash MX 2004 into a fake windows dir. created by > WINE? > > I still don't have any configuration file, will I need such a file (in > both cases?) The reason > why I don't have one is described below, in my previous mail. > > I hope you can help. This is the first time I installed and tried to > use WINE and it > is really important for me. > > Thanks in advance, > Emre Sevinc > Istanbul Bilgi University > http://www.bilgi.edu.tr > > > > > Thanks, > > Scott Ritchie > > > > On Tue, 2005-02-01 at 19:35 +0200, Emre Sevinc wrote: > > > > > First I tried wine from the Debian unstable repository. It didn't work > > > for installing Flash MX 2004. > > > > > > Then I was given advice and I tried the latest version so grabbed > > > and installed the .deb package from the winehq repository (Wine > > > 20050111) > > > > > > Yes, I also tried to install DCOM98.EXE by following the > > > instructions from http://navi.cx/svn/misc/trunk/winekb/NativeDCOM.xml > > > but it also had some problems (please refer to > > > http://www.winehq.org/hypermail/wine-users/2005/02/0000.html ) > > > > > > Now, ok, I give up installing FLASH MX 2004 on a fake windows > > > drive but I just want to learn: > > > > > > I already have an MS Windows 2000 partition (NTFS) on the same > > > hard disk and I was able to install Flash MX 2004 when I booted > > > windows. Can I use this Flash MX 2004 which is > > > already-installed-on-windows-system with WINE? > > > > > > If the answer is yes then I'll say: How? > > > > > > Current situation: > > > > > > $ wine /NTFS/Program\ Files/Macromedia/Flash\ MX\ 2004/Flash.exe > > > err:module:import_dll Library MSVCIRT.dll (which is needed by L"Z:\ > > > \NTFS\\Program Files\\Macromedia\\Flash MX 2004\\xerces-c_2_1_0.dll") > > > not found > > > err:module:import_dll Library xerces-c_2_1_0.dll (which is needed by > > > L"Z:\\NTFS\\Program Files\\Macromedia\\Flash MX 2004\\Flash.exe") not > > > found > > > err:module:LdrInitializeThunk Main exe initialization for L"Z:\\NTFS > > > \\Program Files\\Macromedia\\Flash MX 2004\\Flash.exe" failed, status > > > c0000135 > > > > > > > > > Now you may wonder about my wine configuration and ask what my > > > ~/.wine/config > > > is and I must say that, well, I've run the latest WINE it created some > > > directories > > > under ~/.wine (it was a fresh start, I had already deleted the > > > ~/.wine directory > > > from the previous Debian installation) but THERE IS NO config (or > > > similar) file. > > > > > > So, can somebody be kind enough to show me config file or tell me what > > > kind > > > of file I must create in order to simply run the Flash MX 2004 which > > > is > > > already-installed-and-working-on-windows-system? > > > > > > winesetup? No, please! :) Now that I added the winehq repository to my > > > /etc/sources.list when I try to apt-get winesetup it says that it is > > > going to remove wine. So I prefer to copy the config file (the RIGHT > > > one) > > > from somewhere or create it by using the information that some WINE > > > user > > > or hacker will provide. > > > > > > > > > > > > > > > > > > > > >

Feb. 2, 2005