May 2003 - Wine-Devel - list.winehq.org

Idea: Combine libSDL with the Wine project

by erwin wolff

I have an idea: Combine the SDL project with the Wine DirectX code. It is a great way to catch up with the winex project and SDL has also network code to begin working with the RASAPI32 DLL (used by various instant messengers). Since SDL is ported to every platform out there it is also good for the portability of Wine. I only hope that the license of SDL doesn't give any problems. Have a nice day ECF Wolff erwinwolffnl(a)microformatica.com

May 3, 2003

Re: More checks when loading the driver

by Uwe Bonnes

>>>>> "Eric" == Eric Pouech <pouech-eric(a)wanadoo.fr> writes: Eric> Uwe Bonnes wrote: >> Changelog: wine/dlls/winmm/lolvldrv.c: MMDRV_Install Check for >> failing DRIVER_FindFromHDrvr Eric> this doesn't seem right to me: either the loading fails and we Eric> shouldn't get a valid handle, or it succeeds and we should be able Eric> to find it there's must be something wrong elsewhere could you Eric> please send a -debugmsg +driver,+module,+winmm to see what happens Eric> ? Sorry, the error no longer exists. I guess some registry entry was corrupt and a successfull run corrected it later. However I see a lot of check after DRIVER_FindFromHDrvr() in other parts of the code... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

May 3, 2003

Re: More checks when loading the driver

by Eric Pouech

Uwe Bonnes wrote: > Changelog: > wine/dlls/winmm/lolvldrv.c: MMDRV_Install > Check for failing DRIVER_FindFromHDrvr this doesn't seem right to me: either the loading fails and we shouldn't get a valid handle, or it succeeds and we should be able to find it there's must be something wrong elsewhere could you please send a -debugmsg +driver,+module,+winmm to see what happens ? TIA -- Eric Pouech

May 3, 2003

Re: Solaris Update Patch 02052003

by Robert Lunnon

On Saturday 03 May 2003 04:06, Dimitrie O. Paun wrote: > On Fri, 2 May 2003, Robert Lunnon wrote: > > OOPS forgot to attach the patch here it is > > This pcontext() thing is very ugly: > No need to be rude... Ugly it might be but something like this is necessary since with the signal handling fix gdb/mdb can no longer be used for debugging. There is a need then to determine the source of any unexpected exceptions. > +static void pcontext ( CONTEXT *context, int trap_code, void *cr2, int > err_code){ > > Please do a > const char *dbg_context ( CONTEXT *context ); > function which converts the context to a string, and then use directly > TRACEs instead of pcontext. There are examples in the code on how to > do so via the wine_dbg_sprintf() function. See ./dlls/x11drv/xvidmode.c > around line 460, in the _CDS_flags() function. I don't know a lot of detail about wine innards, but given you have pointed me in the right direction I'll adjust the code next time around. Will come with the libaudioio patch within the next couple of weeks. Besides its only a temporary measure until I get around to doing a ptrace emulation when It can go. Bob

May 3, 2003

Re: No console output?

by Juan Lang

Yeah. Still nothing. However, running wine rather than wineconsole worked :p Thanks for the suggestion! --Juan --- Eric Pouech <pouech-eric(a)wanadoo.fr> wrote: > Juan Lang wrote: > > I'm trying to run a console program with > wineconsole, > > and I see fixme output from the DLL I'm working > on, > > but no output from my program. > did you try: > wineconsole -- your_pgm your-args 2> /dev/null > > A+ > > -- > Eric Pouech > > __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

May 3, 2003

Re: iexplore 5.5.

by Mike Hearn

Hi KK, I'm afraid it's not that simple, IE provides a lot of functionality, it's not just the web browser control (though that is a large part of it). IE also extends the shell system a lot for favourites, history etc etc. Off the top of my head (got to go in a few mins, probably this list is too short) it provides: - MSHTML - BROWSEUI (internal) - SHDOCVW - IPHLPAPI - URLMON (url plugins) - JSCRIPT and a few other things, and of course that's all COM so you have to watch for unknown class factory fixmes..... thanks -mike On Fri, 2003-05-02 at 23:13, KK singh wrote: > hi, > I have tried ie5 installation on wine and failed, > I am trying to find workarounds for not using IE. > > Given a windows executable, can i detect which IE > dependent calls it is making ? > > Or exactly what calls both direct api's and COM > Interfaces are successful if IE5.5 is installed and > fails otherwise. > > any pointers shall be helpful to me... > > Regards > -kks > > PS: thanx for the earlier replies. > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com >

May 3, 2003

Re: With-* test in configure (was: wine and RedHat 9)

by Shachar Shemesh

This is a shot in the dark. Please let me know if the attached patch fixes your problem. Shachar Rob Hughes wrote: >On Fri, 2003-05-02 at 01:53, Shachar Shemesh wrote: > > >>Rob Hughes wrote: >> >> >> >>>Here's a screen shot from a debug message. I'm assuming this uses the >>>standard wine language code? >>> >>>On Thu, 2003-05-01 at 15:54, Sylvain Petreolle wrote: >>> >>> >>> >>> >>>>Huh ? English is the default lang for wine, it shouldnt happen. >>>>Could you give a precise example ? Im using fr_FR.UTF-8 on RH9. >>>> >>>> >>>> >>>> >>>> >>>>>Most of the pop up dialogs are showing this, but sometimes it's only >>>>>one >>>>>button or the other. LANG is set to >>>>> >>>>>LANG=LANG="en_US.UTF-8", which is the default in RH 8 and 9. >>>>> >>>>>Thanks, >>>>>Rob >>>>> >>>>> >>>>> >>>>> >>>>> >>I'm thinking of three possible explanations for this: >> >> 1. Tracing the specific dialog Rob showed, it calls "MessageBoxA", >> which calls "MessageBoxExA" with a language identifier >> "LANG_DEFAULT". According to >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winu… >> the langid parameter is "reserved". Can anyone confirm that there >> is any version of Windows that uses it? >> 2. Even if it did what it was supposed to do, shouldn't the paramter >> at windows/msgbox.c, line 347, say >> "MAKELANG(LANG_NEUTRAL,SUBLANG_DEFAULT)" instead of "LANG_DEFAULT"? >> 3. The English resource don't have "SUBLANG_DEFAULT" for something >> (does not appear to be the case in latest CVS). >> >>Rob - what version of Wine are you using? >>Also, can you please paste here the output of the command "locale"? >> >> > >I'm running CVS from this past Sunday. Locale output is: > >LANG=en_US.UTF-8 >LC_CTYPE="en_US.UTF-8" >LC_NUMERIC="en_US.UTF-8" >LC_TIME="en_US.UTF-8" >LC_COLLATE="en_US.UTF-8" >LC_MONETARY="en_US.UTF-8" >LC_MESSAGES="en_US.UTF-8" >LC_PAPER="en_US.UTF-8" >LC_NAME="en_US.UTF-8" >LC_ADDRESS="en_US.UTF-8" >LC_TELEPHONE="en_US.UTF-8" >LC_MEASUREMENT="en_US.UTF-8" >LC_IDENTIFICATION="en_US.UTF-8" >LC_ALL= > > > > -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/ Index: windows/msgbox.c =================================================================== RCS file: /home/sun/sources/cvs/wine/windows/msgbox.c,v retrieving revision 1.42 diff -u -r1.42 msgbox.c --- windows/msgbox.c 24 Jan 2003 00:54:58 -0000 1.42 +++ windows/msgbox.c 3 May 2003 09:47:52 -0000 @@ -344,7 +344,7 @@ */ INT WINAPI MessageBoxW( HWND hwnd, LPCWSTR text, LPCWSTR title, UINT type ) { - return MessageBoxExW(hwnd, text, title, type, LANG_NEUTRAL); + return MessageBoxExW(hwnd, text, title, type, MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT)); }

May 3, 2003

Re: Small DSound fix...

by Christian Costa

Lionel Ulmer wrote: >Replying in English :-) > >>A ce que je vois ton patch remplace le mien (qui n'a pas ete accepte >>d'ailleurs)... >> > >Did not remember that you submitted a patch for this... Was only aware of >the DInput one for ClassFactory, not the one on DSound. > You're completely right! I check into my mail box and realized I sent a patch with the title "[DSOUND] Fix argument passed to DirectSoundCreate8" just after the dinput's one but I attached the dinput diff a second time instead!!! No one noticed... Not even me... Arghhh! > >>P'tite curiosite.. :-) : >>Mais qu'est ce que ces foutues IIDs viennent faire a la place des GUID >>des devices ? >>C'est une bidouille ou bien DirectSoundCreate les acceptent vraiment ? >> > >>From what I know, it's about the same as out 'fake' GUIDs we have for >DirectX. Ie each driver has its own GUID so that a game can specifically ask >for one device (and when a game asks Wine to enumerate the DSound devices, >these 'fake' devices are actually returned => it works fine there). > >The problem is for games expecting the default driver being returned when >using the 'generic' GUID (ie without doing an enumeration and without using >the DefaultPlayback GUID). > > Lionel >

May 3, 2003

Re: No console output?

by Eric Pouech

Juan Lang wrote: > I'm trying to run a console program with wineconsole, > and I see fixme output from the DLL I'm working on, > but no output from my program. did you try: wineconsole -- your_pgm your-args 2> /dev/null A+ -- Eric Pouech

May 3, 2003

Re: New metabugs

by Shachar Shemesh

Francois Gouget wrote: >On Fri, 2 May 2003, hatky wrote: >[...] > > >>>Anyway, don't let me slow you down. Just remember that >>>bug tracking is a social issue, and you have to pay attention >>>to how the other developers feel about it. >>> >>> >>I am not sure what they realy think yes I only got 3 >>responces 2 of witch where positive :)... >>I guess I will have to wait for the next week to start >>when codewaver will return to flame me (or not) :) >> >> > >This is Wine's bugzilla so you don't need to worry about CodeWeavers >flaming you (or about the CodeWeavers' needs). However, as Dan said, >beware of the Wine developpers ;-). > >I know I used meta-bugs in the past and we used them too in our internal >CodeWeavers bugzilla database. But meta-bugs are not very practical in >the long term and it is worth considering alternatives. In particular: > > * Component field > Some developpers are specialized in a certain aspect of Wine. Havnig >specialists is good, it's certainly more efficient than having to learn >from scratch each time. So we need to provide a way for specialists to >find bugs in their area of expertise. > The 'Component' field is one way to do so. Let's say you're a >Direct3D specialist, you can find bugs in that area by querying Bugzilla >for all bugs tagged with 'Component=wine-directx'. > > * keywords > Keywords are another way to tag and query bugs. It's pretty flexible >and even lets you put multiple keywords on a bug. For instance you can >find all the bugs related to conformance testing by querying Bugzilla >for bugs that have the 'conformance' keyword. Similarly you can look for >all bugs related to programs for which the source is available by >searching for bugs with the 'source' keyword. > See http://bugs.winehq.com/describekeywords.cgi > > > >That being said, > > * Bugzilla queries don't appear to work. Newman do you know what's up? >Is it a database performance issue? Bugzilla bug? > > * Direct3D and DirectSound are pertty different areas. Maybe we should >split the wine-directx component into direct3d, directdraw, directsound >and the generic directx. > > * Maybe we need a 'wine-msvcrt' component. I know there are people >interested in msvcrt but looking at the component list I don't know >where such bugs would go. Or maybe we should be a bit more general and >have a 'wine-libc' so that it includes crtdll and potential future C++ >libraries, etc. > > * Maybe we should add more keywords. I'm not saying we should do it, >but adding 'game' keyword would provide the same functionality as the >current game meta-bug. If we go this way, I could see another useful >keyword: 'installer' to identify all bugs related to application >installers. But we have to be careful not to add frivolous keywords. > > * One useful things that can be done now is to inspect all new bugs to >make sure that: > - the component field is set correctly > - the download URL to the binary or source is provided if applicable > (in case of doubt ask the reporter) > - all applicable keywords are set > That said, things seem to be already pretty much in order (more so >for the component field than for keywords). > > While wer'e at it, can we add a "BiDi" keyword, or at least a "complex-lang" keyword? Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

May 3, 2003