July 2002 - Wine-Devel - list.winehq.org

Re: warcraft 3

by Jesse Allen

Matthieu Foillard wrote: >>> Using wine using opengl (compiled from cvs), start using wine path/War3.exe -- -opengl : fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403aad78,00010023,2):stub fixme:win32:CreateIoCompletionPort (ffffffff, 0000, 00000000, 00000000): stub. then it seems to start fullscreen but does not display anything, so that i must kill it. any ideas ? <<< Okay, have you checked other opengl games under wine? You could run a trace on opengl and see if it's actively running wglSwapLayerBuffers, or other things as well (Create/Destroy context). Did you use the no-cd patch? If nothing comes up with the opengl trace, then you might not be getting past the CD check. Does it minimize the game? This might be interesting if its the case. Please look here where I explain a problem about this: http://www.winehq.com/hypermail/wine-bugs/2002/06/0422.html Basically I said, sometimes opengl apps minimizes when other windows (like a messagebox) become active, and after restoring the opengl window, it produces no output. Here is another interesting note: some people have the same trouble with the movies on real windows like we do on wine. I suggested to rename the movies folder to them, and guess what it worked! But what happens after they do this? the game minimizes, so it's possible this is happening. Here are some references to the problem: http://www.battle.net/forums2/opensupport/posts/ia/27048.shtml http://www.battle.net/forums2/opensupport/posts/fa/27045.shtml Other than that I don't know. I sent Andreas Mohr a more detailed howto, but I pretty much covered everything already. Jesse

July 11, 2002

Re: RFC: Re: [ros-kernel] Shell32 and dplax

by Tony Lambregts

Steven Edwards wrote: >--- Eric Pouech <eric.pouech(a)wanadoo.fr> wrote: > > >>Steven Edwards a écrit : >> >> >>>>in short, moving to NT architecture is the way >>>> >>>> >>to >> >> >>>>go, but >>>>it'll need some time >>>>may be we could also create a metabug on >>>> >>>> >>bugzilla >> >> >>>>for this >>>>and link all known issues to this meta-bug. >>>> >>>> >>>I will start a meta bug for this and being to >>> >>> >>track >> >> >>>these issues as I find them. With any luck we will >>> >>> >>be >> >> >>>able to help with these issues in the next few >>> >>> >>months. >>ok >>btw, is this intentional ? (you didn't cc >>wine-devel) >> >> > >no it wasnt. but yes I will start a meta-bug for these >issues and wait on input from the bugzilla guys as to >if they want to group the issues in another way. > >Steven > >__________________________________________________ >Do You Yahoo!? >Sign up for SBC Yahoo! Dial - First Month Free >http://sbc.yahoo.com > > > > I would suggest using a keyword insted of a metabug. Perhaps ROS or ReactOS, It would be much cleaner. You can even have more than one keyword if you think it is appropriate. ie 9xism. Tony Lambregts

July 11, 2002

RE: Any advice on how to debug this?

by Medland, Bill

> -----Original Message----- > From: Andreas Mohr [mailto:andi(a)rhlx01.fht-esslingen.de] > Sent: Wednesday, July 10, 2002 2:03 PM > To: Medland, Bill > Cc: Wine devel (E-mail) > Subject: Re: Any advice on how to debug this? > > > On Wed, Jul 10, 2002 at 01:11:59PM -0700, Medland, Bill wrote: > > > -----Original Message----- > > > From: Alexandre Julliard [mailto:julliard(a)winehq.com] > > > > > > That's a common problem with Win9x dlls. It cannot be > completely fixed > > > because we don't control the layout of our address space; > there are > > > some hacks that could be done in the loader to make it > less likely to > > > happen, but I'm not convinced it is worth the trouble. Our efforts > > > would probably be better spent making sure the builtin > versions of the > > > offending dlls work properly. > > > > > > -- > > > Alexandre Julliard > > > julliard(a)winehq.com > > > > > Thanks Alexandre. I guess the lesson is to use NT dlls > wherever possible. > No way. Wine still has lots of problems with NT DLLs, since > they are... > NT DLLs ;) > Wine's support for NT API is too damn incomplete, so you'll > have more luck > with Win9x DLLs in most cases. > Or just choose to not use *any* Windows DLLs. Might help. But that means I would have to fix yet more of the bugs in comctl32.dll.so ;-( Actually what I was doing was trying to run the native comctl32 to see if it corrected the visual bugs so that I would know that it was within that dll. I'll see what I can do about fixing them in a bit. Bill

July 10, 2002

Re: Any advice on how to debug this?

by Andreas Mohr

On Wed, Jul 10, 2002 at 01:11:59PM -0700, Medland, Bill wrote: > > -----Original Message----- > > From: Alexandre Julliard [mailto:julliard(a)winehq.com] > > > > That's a common problem with Win9x dlls. It cannot be completely fixed > > because we don't control the layout of our address space; there are > > some hacks that could be done in the loader to make it less likely to > > happen, but I'm not convinced it is worth the trouble. Our efforts > > would probably be better spent making sure the builtin versions of the > > offending dlls work properly. > > > > -- > > Alexandre Julliard > > julliard(a)winehq.com > > > Thanks Alexandre. I guess the lesson is to use NT dlls wherever possible. No way. Wine still has lots of problems with NT DLLs, since they are... NT DLLs ;) Wine's support for NT API is too damn incomplete, so you'll have more luck with Win9x DLLs in most cases. Or just choose to not use *any* Windows DLLs. Might help. -- "My attitude is, everybody should try competing with Microsoft once in their life. Once." - Marc Andreessen, former Netscape lead employee, in a "browser wars" interview

July 10, 2002

Re: winedbg font selection?

by Carl Sopchak

On Wednesday, July 10, 2002 03:52 pm, Andreas Mohr wrote: > On Wed, Jul 10, 2002 at 03:45:27PM -0400, Michael Cardenas wrote: > > Andreas Mohr wrote: > > >Of course you're aware of the fact that wineconsole has a context menu, > > >right ? Had no clue... > > > > > >;-)) > > > > > >Andreas "Why does nobody ever realize simple things" Mohr They're simple if you know them! > > > > Well, that's the problem with context menus, by definition, they're > > hidden. Although, since xterm has one, I guess I should've figured that > > one out too. What's "xterm"?? (Actually, I know what it is, but I never use it. How should I know how it works??) > > Hmm, I could be mistaken, but AFAIK wineconsole is supposed to keep its > settings. > Seems like that is broken, though, of course. It not only doesn't save the setting between runs, it's not saved between popping it up in the same run! In fact, changing the setting DOES NOT change the font! (At least on my system: current cvs, red hat 7.3) > It's on my ToDo list, but feel free to fix it. > > > and I've read the debugger documentation on winehq, and I don't recall > > that menu being mentioned. > > Err, well, it's not a winedbg thing. It's a *wineconsole* thing. > But it's probably not even documented for wineconsole... > Feel free to fix that ! :) I'm trying to fix other things, right now. Maybe when I'm done with that... So, can I get the font to something else (thru the registery, .Xdefaults, anything), or do I have to live with it?? (Guess it wasn't all that simple, after all...) Carl

July 10, 2002

Re: DOSEMU team

by Shachar Shemesh

WOW, if wine is advanced enough to catch and spread outlook bugs, we must be really moving along. Seriously, though. If anyone here knows "friest", and corresponded with him on the subject of "DOSEMU team", and is using Windows, please check your system. You are infected with a variant of the "klez" virus. Shachar

July 10, 2002

Re: RFC: Re: [ros-kernel] Shell32 and dplax

by Jason Filby

Small steps are best - they usually lead to things getting done in the end. A more NT-architecture-friendly WINE would really help us guys working on ReactOS! - Jason --- Eric Pouech <eric.pouech(a)wanadoo.fr> wrote: > > IMHO the way WINE handles certain things is really > > fubar. > basically, since Wine evolves like Windows did (16 bit => > win32 � la Win9x => NT infra), wine suffers from the same > defaults :-( > > however, I agree with you that spreading wineserver calls > all over the DLLs is a bad idea > IMO, the ultimate design would be to only have wineserver > calls in NTDLL, but that's a long way to go... > it would permit nice things as: > - portability on windows for testing the various DLLs > - (should be good for ReactOS) > - would allow to resign drop in replacement for NTDLL, like > moving (part of) wineserver inside the Linux kernel > - ... > > to start with, I think keeping the wineserver calls only > in the holy three DLLs should be an acceptable short term > target > > BTW, I did extend a bit the PSAPI implementation (for some > missing API) and was also upset by the calls to toolhelp > for that > > in short, moving to NT architecture is the way to go, but > it'll need some time > may be we could also create a metabug on bugzilla for this > and link all known issues to this meta-bug. > > A+ > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Two, two, TWO treats in one. > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > reactos-kernel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/reactos-kernel __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com

July 10, 2002

RE: Any advice on how to debug this?

by Medland, Bill

Thanks Eric > -----Original Message----- > From: Eric Pouech [mailto:eric.pouech(a)wanadoo.fr] > Sent: Wednesday, July 10, 2002 12:50 PM > To: Medland, Bill > Subject: Re: Any advice on how to debug this? > > > "Medland, Bill" a écrit : > > > > > -----Original Message----- > > So now what do we do. > > > > Having messed about, got a repeatable case and generally > bashed my head > > around I have got to the following unfortunate situation. > > > > It looks to me like: > > > > comctl32.dll includes a shared data segment. > > One of the entries in that segment, presumably during the > DllEntry, is > > populated with the address of GetSystemMetrics > > > > A second copy of comctl32 then tries to use that address to call > > GetSystemMetrics > > > > Unfortunately the second process has user32 mapped > somewhere else and so the > > call goes somewhere weird and things fall over. > > > > Any ideas as to what we can do about it? > hmm bad news... > > did you try to run your app with a NT version (instead of a > Win9x), that > could help (maybe) No, but I have now. (and ignored all the complaints about mixed versions). It works!! I think that this will be the way to go; see Alexandre's reply. > another thought, when your processes disapear under the > debugger, is the > wineserver still up and running (if it crashes, it may explain the > vanishing processes) Yes it was > another solution would be to disable the support for the shared data > segment... but in your case, it could fix this issue but open another > one TOO TRUE!! The app is very dependent upon shared data segments. > > btw, are you sure user32.dll is mapped at another address in > the second > process Yes > another fix would be to force some DLLs to be loaded at fixed > addresses > (user32 could be one of them)... > another question, are you sure the two processes load the > same user32 ? Yes > (could it be that two wine versions coexist and that a > different one is > loaded in each process) ? > > A+ > Thanks for all the help Bill

July 10, 2002

RE: Any advice on how to debug this?

by Medland, Bill

> -----Original Message----- > From: Alexandre Julliard [mailto:julliard(a)winehq.com] > Sent: Wednesday, July 10, 2002 12:51 PM > To: Medland, Bill > Cc: Wine devel (E-mail) > Subject: Re: Any advice on how to debug this? > > > "Medland, Bill" <Bill.Medland(a)accpac.com> writes: > > > It looks to me like: > > > > comctl32.dll includes a shared data segment. > > One of the entries in that segment, presumably during the > DllEntry, is > > populated with the address of GetSystemMetrics > > > > A second copy of comctl32 then tries to use that address to call > > GetSystemMetrics > > > > Unfortunately the second process has user32 mapped > somewhere else and so the > > call goes somewhere weird and things fall over. > > > > Any ideas as to what we can do about it? > > That's a common problem with Win9x dlls. It cannot be completely fixed > because we don't control the layout of our address space; there are > some hacks that could be done in the loader to make it less likely to > happen, but I'm not convinced it is worth the trouble. Our efforts > would probably be better spent making sure the builtin versions of the > offending dlls work properly. > > -- > Alexandre Julliard > julliard(a)winehq.com > Thanks Alexandre. I guess the lesson is to use NT dlls wherever possible. Bill

July 10, 2002

Re: winedbg font selection?

by Andreas Mohr

On Wed, Jul 10, 2002 at 03:45:27PM -0400, Michael Cardenas wrote: > Andreas Mohr wrote: > >Of course you're aware of the fact that wineconsole has a context menu, > >right ? > > > >;-)) > > > >Andreas "Why does nobody ever realize simple things" Mohr > > > > > Well, that's the problem with context menus, by definition, they're > hidden. Although, since xterm has one, I guess I should've figured that > one out too. But do you really want to change the size every time it > launches? not if you're actually doing some debugging. Hmm, I could be mistaken, but AFAIK wineconsole is supposed to keep its settings. Seems like that is broken, though, of course. It's on my ToDo list, but feel free to fix it. > and I've read the debugger documentation on winehq, and I don't recall > that menu being mentioned. Err, well, it's not a winedbg thing. It's a *wineconsole* thing. But it's probably not even documented for wineconsole... Feel free to fix that ! :) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://mohr.de.tt

July 10, 2002