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

WINE Performance tweaking and known bottlenecks

by Adam Luchjenbroers

What options/tricks/techniques can I use to enhance performance under WINE. I am trying to get Total Annihilation to run smoothly on a K6-2 233MHz machine, it runs and is getting close to playable. The only unusual thing is that the framerate is the same at 1024x768 as in 640x480. What is likely to be the bottleneck and what can I do about it? I'm willing to go into the code if neccessary. I have limited programming ability but I am an exceptionally fast learner.

June 24, 2002

[help] GDI text fonts

by leanne

Dear all, When we are working on the Chinese support on WINE using Lotus Notes r5, we found that the fonts display for the interface is very ugly (attached the screepshot). I would like to change to have different font when detected English or Chinese. Could somebody point me where I could start with? Also, for a text document, the gdi text and font are used to store them, I would like to ask where can I find the structure to store and the code to manipulate it (e.g. send for display/print (pExtTextOut? but where called pExtTextOut))? Thanks. Leanne

June 24, 2002

RtlGetNtVersionNumbers

by Joshua Thielen

Hello everybody, I was searching Google for info about RtlGetNtVersionNumbers and I came across this message, http://www.winehq.com/hypermail/wine-users/2001/12/0488.html, posted on wine-users. Unfortunately, the attachment is not there. Does anyone know what happened to this patch? It doesn't appear to have been sent to wine-patches nor did it make it into the CVS. Perhaps the patch was incorrect as he said his implementation might be off. If this is the case, does anyone have more info about RtlGetNtVersionNumbers? Thanks, Josh

June 24, 2002

Re: Getting CUPS printer to work in wine

by Joshua Thielen

Joshua Thielen wrote: > After updating to the current CVS I get the following error message: > > trace:psdrv:PSDRV_CreateDC (WINEPS Printer LPT1: (nil)) > To use WINEPS you need to install some AFM files. > > I believe this may be why I can't get printing to work. But do I > really need AFM files to get printing to work? The printing doc says > you don't need them for type 1 fonts. > > I've attached a trace of the printing errors just in case this isn't > the cause of the problem. > > TIA for the help, > > Josh > Well, first I forgot to attach the trace and then when I resent it with the attachment it was too big (> 20 K). If anyone is interested in looking at it, just let me know. Otherwise, I will debug it on my own (if it isn't related to needing AFM files). Thanks again, Josh

June 24, 2002

(PATCH) SPI_GETDESKWALLPAPER Implementation

by Philipp Wollermann

Hello, this is my first real patch for Wine. It implements the SystemParametersInfo SPI_GETDESKWALLPAPER action and fixes SPI_SETDESKWALLPAPER so it updates the Wallpaper entry in the registry. (Wine Bug-Tasklet #461) I've also included a simple test for these two actions. Please tell me if something is wrong so I can fix it. :-) ChangeLog: * windows/sysparams.c: Implemented SPI_GETDESKWALLPAPER action, fixed SPI_SETDESKWALLPAPER * dlls/user/tests/sysparams.c Added test for wallpaper actions License: X11 / LGPL Philipp Wollermann

June 23, 2002

Re: Infinite loop in winedebug

by Eric Pouech

Duane Clark a écrit : > > During an installation, wine crashed and went into the debugger, which > proceeded to go into an infinite loop. This is with current CVS. Oddly, > it only goes into the infinite loop if I have: > "UseXTerm"=dword:00000000 > Allowing winedebug to use its own xterm, the debugger works fine. Here > is one iteration of the loop. basically, it seems the debugger (or in this case any console base program) cannot get a decent input stream and gets a bit confused about it. asking the debugger not to use any inherited input stream (UseXTerm = 1) is the preferred way to handle this. the attached patch should prevent the loop in debugger input A+ Index: debugger/debug.l =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/debugger/debug.l,v retrieving revision 1.27 diff -u -r1.27 debug.l --- debugger/debug.l 13 Jun 2002 21:37:41 -0000 1.27 +++ debugger/debug.l 23 Jun 2002 08:54:29 -0000 @@ -29,7 +29,7 @@ #undef YY_INPUT #define YY_INPUT(buf,result,max_size) \ - if ( (result = DEBUG_ReadLine("Wine-dbg>", (char *) buf, max_size, TRUE, TRUE )) < 0 ) \ + if ( (result = DEBUG_ReadLine("Wine-dbg>", (char *) buf, max_size, TRUE, TRUE )) <= 0 ) \ YY_FATAL_ERROR( "read() in flex scanner failed" );

June 23, 2002

Re: Regression Bug in Wine MM (Bug #817)

by Eric Pouech

> > I have reported what appears to be a regression bug in Wine's > > multimedia subsystem (Bug #817). > > Correction: that should be Bug #818 does the attached patch cures the regression ? A+ Name: ps5 ChangeLog: fixed flags handling in sndPlaySound License: X11 GenDate: 2002/06/23 08:42:11 UTC ModifiedFiles: dlls/winmm/mmsystem.c AddedFiles: =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/winmm/mmsystem.c,v retrieving revision 1.59 diff -u -u -r1.59 mmsystem.c --- dlls/winmm/mmsystem.c 4 Jun 2002 00:51:38 -0000 1.59 +++ dlls/winmm/mmsystem.c 23 Jun 2002 08:40:22 -0000 @@ -690,7 +690,7 @@ */ BOOL WINAPI sndPlaySoundA(LPCSTR pszSoundA, UINT uFlags) { - uFlags &= ~(SND_ASYNC|SND_LOOP|SND_MEMORY|SND_NODEFAULT|SND_NOSTOP|SND_SYNC); + uFlags &= SND_ASYNC|SND_LOOP|SND_MEMORY|SND_NODEFAULT|SND_NOSTOP|SND_SYNC; return MULTIMEDIA_PlaySound(pszSoundA, 0, uFlags, FALSE); } @@ -699,7 +699,7 @@ */ BOOL WINAPI sndPlaySoundW(LPCWSTR pszSound, UINT uFlags) { - uFlags &= ~(SND_ASYNC|SND_LOOP|SND_MEMORY|SND_NODEFAULT|SND_NOSTOP|SND_SYNC); + uFlags &= SND_ASYNC|SND_LOOP|SND_MEMORY|SND_NODEFAULT|SND_NOSTOP|SND_SYNC; return MULTIMEDIA_PlaySound(pszSound, 0, uFlags, TRUE); }

June 23, 2002

Getting CUPS printer to work in wine

by Joshua Thielen

After updating to the current CVS I get the following error message: trace:psdrv:PSDRV_CreateDC (WINEPS Printer LPT1: (nil)) To use WINEPS you need to install some AFM files. I believe this may be why I can't get printing to work. But do I really need AFM files to get printing to work? The printing doc says you don't need them for type 1 fonts. I've attached a trace of the printing errors just in case this isn't the cause of the problem. TIA for the help, Josh

June 23, 2002

Re: Updated patch for PROFILE_GetString

by Dmitry Timoshkov

"Joshua Thielen" <thielen(a)netprince.net> wrote: > >Joshua, very simple question: how about Profile APIs regression test? > > > OK, I'll do it. I had already thought about doing this, but it was just > a thought. I guess I'll have to take a look at some of the tests to see > how this is done. Thanks for at least looking at it! > Man, I just wish I had more time. The thing we all are just dreaming about :-) -- Dmitry.

June 23, 2002

Re: Updated patch for PROFILE_GetString

by Joshua Thielen

Dmitry Timoshkov wrote: > >Joshua, very simple question: how about Profile APIs regression test? > OK, I'll do it. I had already thought about doing this, but it was just a thought. I guess I'll have to take a look at some of the tests to see how this is done. Man, I just wish I had more time. Josh

June 23, 2002