- Wine-devel - list.winehq.org

ITypeInfo_fnGetContainingTypeLib
by lawson_whitney＠juno.com 25 Nov '01

25 Nov '01

Good day! Anyone like to take a swat at this? I don't normally shy from a page fault, but frankly, ICOM confuses me. Anyway, maybe Ove can spot it in a second. If I have to do it it may take weeks. Backtrace attached. Wineconsole seems to be working nicely, as long as the resolution is good and high. I wanted to include a typelib trace, but that crashes at an earlier spot. I haven't really looked at that one yet; I can send it along if anyone is interested. At least Wine is starting to get its teeth into InstallSh**** and its confounded IKernel.exe. Regards Lawson ---oof---

3 5

Re: Crashing menus, event handling broken?
by Alexandre Julliard 25 Nov '01

25 Nov '01

Jukka Heinonen <jhei(a)iki.fi> writes: > The reason for this is that raw hardware messages get processed > before menu event loop starts. Raw event processing turns raw events > into cooked events and because menu event loop has not started yet, > game window is not capturing events and thus clicks on menu bar > are turned into nonclient messages. These cooked messages are > put back into message queue. Raw messages are not supposed to get processed while there is a cooked message in the queue. Is the app filtering messages in GetMessage? Could you please do a +server trace showing the problem? -- Alexandre Julliard julliard(a)winehq.com

3 3

Re: ttydrv fix (adds missing ShowWindow function)
by lawson_whitney＠juno.com 25 Nov '01

25 Nov '01

On Thu, 22 Nov 2001, Eric Laforest wrote: > tydrv/ttydrv.spec > =================================================================== > RCS file: /cvsroot/winex/wine/dlls/ttydrv/ttydrv.spec,v > retrieving revision 1.1.1.8 > diff -r1.1.1.8 ttydrv.spec > 71a72 > > @ cdecl ShowWindow(long long) TTYDRV_ShowWindow > Index: dlls/ttydrv/wnd.c > =================================================================== > RCS file: /cvsroot/winex/wine/dlls/ttydrv/wnd.c,v > retrieving revision 1.1.1.10 > diff -r1.1.1.10 wnd.c > 648a649,809 > > I think it is worth reading <wine>/README all the way to the end, where you will see: If you add something, or fix a bug, please send a patch ('diff -u' format preferred) to julliard(a)winehq.com or to the wine-patches(a)winehq.com mailing list for inclusion in the next release. -- Alexandre Julliard julliard(a)winehq.com Is it asking too much to use diff -u? Would you like to get patches from all over the world against who knows which version of wine in random formats? I think -u is the only format suitable for an open-source project. Regards, Lawson ---oof---

1 1

Re: wineconsole compile error
by Gerard Patel 24 Nov '01

24 Nov '01

At 06:59 PM 24/11/2001 +0100, you wrote: >make[1]: Entre dans le répertoire `/home/wine/programs/wineconsole' >gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -DSTRICT -DUNICODE -D_REENTRANT -I/usr/X11R6/include -o >dialog.o dialog.c >dialog.c: In function `WCUSER_GetProperties': >dialog.c:492: structure has no member named `u' <snip> Yes, me too. Does the patch posted on Wine-patches by Chris Green not fix it for you ? Gerard

3 2

Re: mmsystem should be loaded at startup
by eric pouech 24 Nov '01

24 Nov '01

Joshua Thielen wrote: > > Note: I'm not sure if I should have called ExitProcess if mmsystem.dll > can't be loaded not needed, if it couldn't be loaded, then no need to free it > and if I needed to call FreeLibrary. I just took the > LoadLibrary("user32") as an example. well, error reporting for 16 bit DLL is a bit different (see below) > + if(!(mmsystem = LoadLibrary16("mmsystem.dll"))) the correct test should be > + if((mmsystem = LoadLibrary16("mmsystem.dll")) < 32) (the other values (< 32) are the error codes) A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

1 0

mmsystem should be loaded at startup
by Joshua Thielen 24 Nov '01

24 Nov '01

Hello everybody, Finale expects mmsystem to be present without having to call LoadLibrary on it. It does a GetModuleHandle on mmsystem.dll to find out if the mm extensions are available. I checked out windows 95, and it has mmsystem and winmm loaded when no apps are runing besides the desktop / explorer. This patch links wine with winmm andmakes winmm load mmsystem on init. Finale gets by this ok now. I don't know if this the correct approach, though. Could someone (Eric or Alexandre?) please take a look at it before I send it to wine-patches? TIA, Josh Thielen Index: wine/miscemu/wine.spec =================================================================== RCS file: /home/wine/wine/miscemu/wine.spec,v retrieving revision 1.3 diff -u -r1.3 wine.spec --- wine/miscemu/wine.spec 2000/12/15 03:38:11 1.3 +++ wine/miscemu/wine.spec 2001/11/23 19:11:47 @@ -4,3 +4,4 @@ init wine_initial_task import ntdll.dll +import winmm.dll Index: wine/dlls/winmm/mmsystem.c =================================================================== RCS file: /home/wine/wine/dlls/winmm/mmsystem.c,v retrieving revision 1.46 diff -u -r1.46 mmsystem.c --- wine/dlls/winmm/mmsystem.c 2001/11/13 21:58:32 1.46 +++ wine/dlls/winmm/mmsystem.c 2001/11/23 19:11:59 @@ -114,6 +114,7 @@ */ BOOL WINAPI WINMM_LibMain(HINSTANCE hInstDLL, DWORD fdwReason, LPVOID fImpLoad) { + HINSTANCE16 mmsys16; TRACE("0x%x 0x%lx %p\n", hInstDLL, fdwReason, fImpLoad); switch (fdwReason) { @@ -124,9 +125,15 @@ MULTIMEDIA_DeleteIData(); return FALSE; } + mmsys16 = LoadLibrary16("mmsystem.dll"); + if (!mmsys16) { + ERR("Could not load sibling mmsystem.dll\n"); + return FALSE; + } break; case DLL_PROCESS_DETACH: MULTIMEDIA_DeleteIData(); + if(mmsys16) FreeLibrary16(mmsys16); break; case DLL_THREAD_ATTACH: case DLL_THREAD_DETACH: @@ -2549,7 +2556,7 @@ TRACE("(%d, %p, %d);\n", uDeviceID, lpCaps, uSize); if ((wmld = MMDRV_Get(uDeviceID, MMDRV_MIDIIN, TRUE)) == NULL) - return MMSYSERR_INVALHANDLE; + return MMSYSERR_BADDEVICEID; return MMDRV_Message(wmld, MIDM_GETDEVCAPS, (DWORD)lpCaps, uSize, TRUE); }

3 3

Re: mmsystem should be loaded at startup
by Alexandre Julliard 24 Nov '01

24 Nov '01

Joshua Thielen <thielen(a)netprince.net> writes: > Finale expects mmsystem to be present without having to call LoadLibrary > on it. It does a GetModuleHandle on mmsystem.dll to find out if the mm > extensions are available. I checked out windows 95, and it has mmsystem > and winmm loaded when no apps are runing besides the desktop / > explorer. This patch links wine with winmm andmakes winmm load mmsystem > on init. Finale gets by this ok now. I don't know if this the correct > approach, though. Could someone (Eric or Alexandre?) please take a look > at it before I send it to wine-patches? It would be better to do the LoadLibrary16("mmsystem") in wine_initial_task, this way it only impacts 16-bit applications. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: wineconsole compile error
by Alexandre Julliard 24 Nov '01

24 Nov '01

Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> writes: > dialog.o dialog.c > dialog.c: In function `WCUSER_GetProperties': > dialog.c:492: structure has no member named `u' > dialog.c:496: structure has no member named `u' > dialog.c:500: structure has no member named `u' > dialog.c:509: structure has no member named `u3' > > This is happening on gcc 3.0.2 (nameless union support, I suppose). It should be fixed now. -- Alexandre Julliard julliard(a)winehq.com

1 0

wineconsole compile error
by Andreas Mohr 24 Nov '01

24 Nov '01

Hi all, people get make[1]: Entre dans le répertoire `/home/wine/programs/wineconsole' gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -DSTRICT -DUNICODE -D_REENTRANT -I/usr/X11R6/include -o dialog.o dialog.c dialog.c: In function `WCUSER_GetProperties': dialog.c:492: structure has no member named `u' dialog.c:496: structure has no member named `u' dialog.c:500: structure has no member named `u' dialog.c:509: structure has no member named `u3' This is happening on gcc 3.0.2 (nameless union support, I suppose). On my system, this file compiles painlessly: root(a)andi:/root# gcc -v Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20010902 (Debian prerelease) (no nameless union support, I suppose) I told this guy to replace .u. and .u3. in dialog.c with DUMMYUNIONNAME and DUMMYUNIONNAME3, respectively. This caused: dialog.c:492: parse error before `.' dialog.c:496: parse error before `.' dialog.c:500: parse error before `.' dialog.c:509: parse error before `.' I thought that this particular error was caused by a missing #include "winnt.h", but adding this didn't help either. Please fix this "mess" ASAP (in an appropriate way, one that I seem to not be able to find out :-\). Thank you ! -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany "Point is, nothing here is unfamiliar or unexpected. How long does it take before there's general recognition that Microsoft software has no business on the Internet? - Dennis E. Powell re: Code Red

1 0

Re: Where are we going on multiuser?
by Alexandre Julliard 24 Nov '01

24 Nov '01

"Bill Medland" <medbi01_1(a)accpac.com> writes: > What is our vision on support for multiple users on a single computer? > > I know that WINEPREFIX allows us to use something other than $HOME/.wine for > the base of everything but as far as I can see the whole design still > requires a different WINEPREFIX for each user. (e.g. the socket is in > wine-server-<hostname> and there is no apparent support for the system.reg, > user.reg and userdef.reg being in different places). You need one WINEPREFIX per user yes. You can use global registry files by creating symlinks to global files in the user WINEPREFIX. The usual way is to wrap your app in a shell script that will populate the user's WINEPREFIX if it doesn't exist yet. There are plans for splitting registry files into separate sections with some kind of include mechanism, but nothing implemented yet. -- Alexandre Julliard julliard(a)winehq.com

1 0