September 2003 - Wine-Devel

Re: FAQ: How much ram do I need #2
by Alexandre Julliard Sept. 17, 2003

Sept. 17, 2003

Tom <twickline(a)skybest.com> writes: > Andreas suggested that 128 is the minimum memory requirements for wine > to work in a useable fashion. So I will leave the content of this entry > in place and just change the 256 to 128. I haven't really seen any evidence that Wine memory requirements have suddenly been multiplied by 4. It all depends on the application you are running anyway, so I don't think there's much point in trying to give specific requirements. I'd suggest rewriting the whole thing to simply say that you need basically the same amount of memory than under Windows to run the same apps. -- Alexandre Julliard julliard(a)winehq.com

1 0

More DOS regressions due to instruction emulation changes
by Jukka Heinonen Sept. 17, 2003

Sept. 17, 2003

In addition to breaking protected mode programs, instruction emulation changes have also broken many real mode programs. Instruction emulation code was previously used to emulate not only protected mode instructions but also some real mode instructions. For example, ioport instructions (inb,outb,...) were emulated using that code. Now, these instructions raise an exception that will not be caught by any handler because real mode code may not have been called via K32WOWCallback16Ex, which seems to be the place where instruction emulation hooks in. There are many different ways of fixing these problems, one possibility is to make K32WOWCallback16Ex call VM86 stuff from NTDLL when special magic parameter is passed to it so it can install the correct exception handler. Another is to export instruction emulation hook or exception handler from kernel. Anyway, this is something I don't probably want to decide, even if I had more time available for this. A better fix for protected mode programs would be welcome, too. -- Jukka Heinonen <http://www.iki.fi/jhei/>

1 0

A useful resource for all windows API trivia
by Mike Hearn Sept. 17, 2003

Sept. 17, 2003

http://blogs.gotdotnet.com/raymondc/ That guy did a lot of work on the Windows APIs, in particular in the GUI and shell areas. He routinely posts interesting, and often funny, accounts of why things in Windows are as they are, as well as occasional links to internal docs on the semantics of particular APIs/constructs/types etc. Well worth reading if you are feeling bored ;) thanks -mike

1 0

API DB scripts available - help wanted populating the apps table
by Dave Miller Sept. 17, 2003

Sept. 17, 2003

I have placed all of the scripts used in creating the API DB at http://24.229.94.2 in a .tar.gz available here: http://24.229.94.2/winedb.tar.gz in case anyone is interested. Yes, they are ugly. I'll gladly accept any improvements or ideas. :) One of the scripts (dump_app_imports) dumps the apis used by a given program. Another can query the database from a web form to find missing apis for a given app. If anyone is interested in finding what apis are missing for particular apps please run dump_app_imports on the install directory as follows: dump_app_imports.pl -p path-to-app -f appname-and-version and email me the resulting appname.ref file. I will then add it to the database. The script which does the queries still needs some work but I am ready to add applications now.

1 0

Numeric data problems on wine
by Hengga Sept. 17, 2003

Sept. 17, 2003

Hi..., It's my first experience with wine. I got wine installed on my computer. It runs Xandros Desktop 1.0 based on Debian distro. I am about to run my applications created on windows platform. The applications created by Sybase Power Builder 7.0. When I run the applications, if I put the numeric data (integer, long integer, etc.), e.g.: 1 it will appears +.. 11 it will appears +..1 111 it will appears +.1.1 123 it will appears +.2.3 When I try to run it on windows, everything fine. What's wrong with it? Anyone have the experience. Help me please. BTW, my wine package is wine-20030911.tar.gz Thanks. Hengga

2 1

Re: Trivial compile patch for dlls/winmm/winealsa/midi.c
by Stefan Leichter Sept. 16, 2003

Sept. 16, 2003

On Tuesday 16 September 2003 07:16, Pavel Roskin wrote: > ChangeLog: > > * dlls/winmm/winealsa/midi.c: Set WINE_DEFAULT_DEBUG_CHANNEL > unconditionally. > > There are TRACE calls below corresponding #endif. Hello, your patch is fine for me. It fixes the first compile error for me, but did you fix also this one? make[2]: Entering directory `/usr/src/wine/wine-build/dlls/winmm/winealsa' gcc -shared -Wl,-Bsymbolic,-z,defs winealsa.drv.spec.o audio.o audio_05.o alsa.o midi.o winealsa.drv.dbg.o -o winealsa.drv.so -L../../../dlls -L../../../libs/wine -lwine -L../../../libs/uuid -lwine_uuid -lasound -L../../../libs/port -lwine_port -lm -lc alsa.o: In function `ALSA_DriverProc': /home/sle/src/wine/wine-build/dlls/winmm/winealsa/../../../../wine/dlls/winmm/winealsa/alsa.c:77: undefined reference to `ALSA_MidiInit' collect2: ld returned 1 exit status make[2]: *** [winealsa.drv.so] Error 1 make[2]: Leaving directory `/usr/src/wine/wine-build/dlls/winmm/winealsa' make[1]: *** [winmm/winealsa] Error 2 make[1]: Leaving directory `/usr/src/wine/wine-build/dlls' make: *** [dlls] Error 2 The attached patch fixes the problem for me but i am not sure if it is the right fix. My system has only alsa 0.5 installed. Comments please. Bye Stefan

1 0

WM_MDICREATE failing
by Shachar Shemesh Sept. 16, 2003

Sept. 16, 2003

Hi all, I have an application that does "SendMessageA" WM_MDICREATE, and this call FAILS. I'm currently running this under crossover office 2.0.1 (the only environment that would install it). I'm quite capable of hunting this down on my own, but I was wondering whether anyone has had similar experience in the past. I would also like to know who is our "official" MDI maintainer. Also, I noticed that this application registered two Windows hooks. I wasn't aware that these worked, but the app seems happy. Do we or don't we have working hooks support? Shachar P.S. I have been a Win32 programmer for five years, and managed to go without writing any UI more complicated than a single dialog and a progress bar. Since I have been involved in Wine, I have tweaked the Font dialog, tracked the Text printing functions, did more OLE than I would normally want, keyboard input, and even some Direct X (a little). I find it ironic that I had to move my skills to Linux before I had to touch any of these. -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

3 3

Re: Conformance tests compile progress with MSVC
by Rolf Kalbermatter Sept. 16, 2003

Sept. 16, 2003

On September 11, 2003 12:24 pm, Jakob Eriksson wrote: >> This means with VC++ and MSVC headers 12 EXEs compile, with VC++ and >> MinGW headers 16 EXEs compile. Crosscompiling tests from Linux is still >> somewhat >> broken as per current CVS, but still 18 EXEs compile! >> >> So crosscompiling gets us the most tests compiled. >> >> >> Errors with MSVC headers: > >This may help a little. > >ChangeLog > Use winnt.h instead of ntstatus.h where we can. Why is it that I can just remove the #include <ntstatus.h> and everything compiles fine both under wine as well as MSVC? <winnt.h> seems not necessary at all because some other header seems to include it, possibly unintentionally. Rolf Kalbermatter

3 2

[DXT3] menu in Tribunal now vanishes (regression?)
by MichaelGuennewig＠gmx.de Sept. 16, 2003

Sept. 16, 2003

Hallo, with the following 2 patches the menu in "The Elder Scrolls III: Tribunal Morrowind Expansion Pack" version 1.4.1313 german only shows white blocks instead of the menuitems as before. When IDirect3DImpl_CheckDeviceFormat reports that D3DFMT_DXT3 isn't supported the menuitems will draw correct. When IDirect3DImpl_CheckDeviceFormat reports that D3DFMT_DXT3 is supported then white blocks appear instead of the menuitems and glCompressedTexImage2D returns the error code 0x502 (GL_INVALID_OPERATION). Using NVIDIA drivers 1.0-4349 and updating to 1.0-4496 doesn't solve the problem. Is it the OpenGL implementation which is buggy or the way how wine uses it? I have attached a log of "wine -debugmsg +loaddll,+d3d_surface Morrowind.exe". The binary is a no-cd version, but the original one behaves the same. Some parts from my config: ,----- | ... | | [Version] | "Windows" = "win98" | ;"DOS" = "6.22" | | [x11drv] | "AllocSystemColors" = "100" | "PrivateColorMap" = "N" | "UseDGA" = "N" | "UseXShm" = "Y" | "UseXVidMode" = "Y" | "UseTakeFocus" = "Y" | "DXGrab" = "N" | "DesktopDoubleBuffered" = "Y" | "TextCP" = "0" | "Synchronous" = "N" | | [WinMM] | "Drivers" = "wineoss.drv" | ; ... | | ;; Debug, dsound, network are empty | | [DllOverrides] | "*" = "builtin, native" | "msvideo" = "native, builtin" | "msvfw32" = "native, builtin" | "ole32" = "native, builtin" | "oleaut32" = "native, builtin" | "quartz" = "native, builtin" | "rpcrt4" = "native, builtin" | | ... `----- Will send more details if someone wish. Michael

2 3

Re: resend - system tray support
by Alexandre Julliard Sept. 16, 2003

Sept. 16, 2003

Mike Hearn <mike(a)theoretic.com> writes: > I'm going to keep sending this flipping patch until it gets in, or I > find out what the next problem is you know. There's no escape! :) Well, at least the critical section handling is broken, but the real problem is that all this stuff doesn't belong in shell32. We should really redesign it to get rid of the internal WS_EX_TRAYWINDOW flag and have a separate process to manage the tray window (plus other background tasks like the progman DDE interface, and maybe the desktop window too). -- Alexandre Julliard julliard(a)winehq.com

3 7