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

Re: More common control fixies
by Alexandre Julliard Sept. 16, 2003

Sept. 16, 2003

"Filip Navara" <xnavara(a)volny.cz> writes: > - Included wtypes.h in dlls/comctl32/trackbar.c for compilation > with w32api. Why is wtypes.h needed with w32api and not with the Wine headers? -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: shell32 (part3): Make sure the bind context is forwarded in ShellFolder_ParseDisplayName
by Alexandre Julliard Sept. 16, 2003

Sept. 16, 2003

"Rolf Kalbermatter" <rolf.kalbermatter(a)citengineering.com> writes: > - dlls/shell32/shell32_main.h > Add inline functions to convert ANSI strings to Unicode strings using the heap > for A->W function calls. I do believe we shouldn't link shell32 to ntdll so the > Rtl.. functions seem no option here. If this is wrong I would rather like to > call those. There's no reason not to use ntdll functions if they are more convenient. Most of our dlls import ntdll already, and shell32 can perfectly do that too. -- Alexandre Julliard julliard(a)winehq.com

1 0

How do I find out what a program uses to identify a screen mode
by hatky Sept. 15, 2003

Sept. 15, 2003

I am trying to get some code contributes to wine but after trying 2 w->a converts and then getting the response of "Thats to complicated, leave it to me" I decided to more on.... I have a few games that are failing logically identifying a screen mode (one actually fails at detecting a 3d card) I searched msdn and the code and traces of their runs and yet couldn't find that procedure gives them that wrong info. Can some directX/x11drv guru help me find and fix the problem, I assume it is something that either is stubbed or doesn't check the wine config correctly.... Trying to start on some real contribution to wine, Thanks in advance, Hatky. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 2

Unable to cimpile wineproc
by BiGgUn Sept. 15, 2003

Sept. 15, 2003

Hi all When i try to compile wineproc , i got the following error: In file included from system.c:3: ../../include/psapi.h:25: parse error before "LPVOID" ../../include/psapi.h:25: warning: no semicolon at end of struct or union (...) and many ohter like this. What did i do in the wrong way ? TIA, Stephan

8 19

Ventril Howto coming
by Kristoffer Ericson Sept. 15, 2003

Sept. 15, 2003

Greetings, Due to popular demand and my lack of mail time, i've decided to write an howto concerning getting Ventrilo to work with Wine. I do this cause 1) helping people is fun, 2) you guys are spamming my mailbox. I will send the link when the howto is completed. Best wishes Kristoffer

2 2

PeekNamedPipe
by Marcelo Bezerra Sept. 15, 2003

Sept. 15, 2003

Hello, I've been trying to run Valve's Steam under winex and has not achieved success. Aparently it depends on PeekNamedPipe, wich is only a stub and is a kernel32 function, so no native dll would help. I would like some help in implementing this function, google sugested using recvfrom with MSG_PEEK flag set but I have some doubts about it. Where is HANDLE struct defined? How to relate it to the actual file descriptor in unix? How to find out the pipemode of such HANDLE? If I make it return true inconditionaly and set all args to 1, Steam will even show up (with most text impossible to read, but will most likely work when implemented correclty). Anyone able to help?

4 3

Conformance tests compile progress with MSVC
by Jakob Eriksson Sept. 15, 2003

Sept. 15, 2003

I have now managed to compile the tests with MSVC and MSVC headers. (Using Visual studio.NET) (Using instructions from http://winehq.com/site/docs/wine-devel/testing-windows ) propset.c, process.c, thread.c, wksta.c, env.c, error.c, generated.c, large_int.c, path.c, rtl.c, rtlbitmap.c, rtlstr.c, string.c and dpa.c did not compile however. 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: h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(42): error C2065: 'HDPA' : undeclared identifier h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(42): error C2146: syntax error : missing ';' before identifier 'dpa_ret' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(42): error C2144: syntax error : '<Unknown>' should be preceded by '<Unknown>' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(42): error C2144: syntax error : '<Unknown>' should be preceded by '<Unknown>' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(42): error C2143: syntax error : missing ';' before 'identifier' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(42): error C2065: 'dpa_ret' : undeclared identifier h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(43): error C2275: 'INT' : illegal use of this type as an expression h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(43): error C2146: syntax error : missing ';' before identifier 'int_ret' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(43): error C2144: syntax error : '<Unknown>' should be preceded by '<Unknown>' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(43): error C2144: syntax error : '<Unknown>' should be preceded by '<Unknown>' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(43): error C2143: syntax error : missing ';' before 'identifier' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(43): error C2065: 'int_ret' : undeclared identifier h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2275: 'CHAR' : illegal use of this type as an expression H:\program files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\Include\WinNT.h(239) : see declaration of 'CHAR' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2146: syntax error : missing ';' before identifier 'test_str0' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2144: syntax error : '<Unknown>' should be preceded by '<Unknown>' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2144: syntax error : '<Unknown>' should be preceded by '<Unknown>' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2143: syntax error : missing ';' before 'identifier' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2065: 'test_str0' : undeclared identifier h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(44): error C2059: syntax error : ']' h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(46): warning C4013: 'DPA_Create' undefined; assuming extern returning int h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(48): warning C4013: 'DPA_Search' undefined; assuming extern returning int h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(48): error C2065: 'DPAS_SORTED' : undeclared identifier h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(50): error C2065: 'DPAS_INSERTBEFORE' : undeclared identifier h:\work_dir\Wine\wine\dlls\comctl32\tests\dpa.c(52): error C2065: 'DPAS_INSERTAFTER' : undeclared identifier oleaut32_test error LNK2019: unresolved external symbol _IFont_QueryInterface referenced in function _func_olefont oleaut32_test fatal error LNK1120: 1 unresolved externals h:\work_dir\Wine\wine\dlls\ntdll\tests\string.c(27): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\rtlstr.c(28): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\rtlbitmap.c(26): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\rtl.c(27): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\path.c(24): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\large_int.c(27): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\generated.c(14): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\error.c(24): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\ntdll\tests\env.c(24): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\netapi32\tests\wksta.c(28): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\kernel\tests\thread.c(27): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\kernel\tests\process.c(27): fatal error C1083: Cannot open include file: 'ntstatus.h': No such file or directory h:\work_dir\Wine\wine\dlls\dsound\tests\propset.c(32): fatal error C1083: Cannot open include file: 'dsconf.h': No such file or directory

3 2

Linux Tribes
by Kristoffer Ericson Sept. 15, 2003

Sept. 15, 2003

Greetings, >From what i gather the "mouse gets no focus" problem is still there. Meaning that when tribes starts the standard mouse pointer is still active, while the tribes one is still in the uppe corner. No way to get focus. Lionell , any chance of checking this against the demo? Anyone running linux - Tribes? My wine-tribes has been broke since 3 months ago. Best wishes

2 1

Re: FAQ : How much ram do I need
by Andreas Mohr Sept. 15, 2003

Sept. 15, 2003

Hi, On Mon, Sep 15, 2003 at 07:15:34AM -0400, Tom wrote: > > Hi, > > I was reading over the faq and the minimum memory requirements > are extreamly low. So I just multiplied what we have by 4. 256 is much to high IMHO. Note that the paragraph talks about "working", not "working well". Case in point: I ran PowerPCB on Wine with 128MB RAM (P3/800), plus some other assorted programs (Mozilla (30MB), SETI (20MB), VNC server (5MB), ...), TODAY even. It did work pretty well, if only a bit slow (I didn't notice too much swapping on my 256MB swap partition, though). I'd rather change that paragraph to say that 64MB should be moderately usable if you use a very lightweight system environment (no KDE, Gnome, ... bloatware ;), 128MB is ok, and 256MB is pretty good. In fact IIRC the 64MB figure remains from times where Wine was a full-blown static binary. With todays DLL separation there should be no reason why we need more. At the least I'd change it to say 128MB only, but OTOH maybe we should simply specify 64MB as a minimum configuration and 256MB as "working well". -- Microsoft prepares new round of .doc office format lock-in (just forget about OpenOffice/StarOffice .doc interoperability then, ok?) http://news.com.com/2100-1012_3-5069246.html

1 0

Bad prefs that I'm planning on dropping
by Mike Hearn Sept. 15, 2003

Sept. 15, 2003

OK, so here is a basic list of settings that I can't be bothered doing UI for in winecfg. Before I start, I think I should make one thing clear - ultimately I believe winecfg should be removed entirely. Looking at the settings in the wine configuration really rams home how many simply should not be configurable by the user at all. Back during the 90s when the only people using Wine were happy and comfortable with computers, it was A-OK to have settings like "Use XSHM extension" and assume the users knew what it meant, or if they didn't, that they wouldn't fiddle with it to see what it did. But, Linux is changing, and we can't assume that sort of thing anymore. Worse, a lot of these settings could simply be autodetected, or are so obscure that the defaults would always suffice (we can auto detect the presence of XSHM, so why would you need to disable it?). Unfortunately, writing auto detect code is quite hard, a bit boring etc, so for now that'd have to be a long term project. Ultimately there's no reason why Wine should have to be configured at all - in the ideal world it would just get on with it, and the user doesn't have to think about it, maybe they don't even have to know what Wine is, in much the same way that users don't have to know what glibc or XFree is in order to use the latest distros. So, here's a quick hit list for now: [x11drv] * XSHM - can be autodetected, 99.9% of Wines users use XFree, which supports it. * Use DGA - enabling it apparently breaks wines keyboard input, rendering most games useless (and it's usually used for games). Difficult to know when to enable it short of trying. * Perfect Graphics - controls the use of optimized raster ops. What difference it makes in practice appears to be unknown. * Allocated system colors - in fact we still have UI for this in the latest version of the code, but I'm not sure what it's for, or what the best value is, I chose a default of 100 because that is what I happened to have in my config file * Private Color Map - the description for this setting is not helpful, "Use a private color map". I have no idea what this does, or what effect it'd have, so end users are probably just as clueless. * Synchronous mode - would this be better implemented as a command line switch? For most people who cannot debug problems in the Wine x11drv, it would just slow things down for no apparent reason. For those who can, it's easy to tell people to run wine with the --sync option, for instance, or do "export WINE_SYNCHRONOUS=1" * TextCP - description is "Code page used for captions in managed mode", which is fine, the problem is that there are no pointers to available codes and what they mean, other than zero meaning ANSI. Why can't this be auto detected? How do we explain how to set it? * XVideoPort - wow, this one is obscure. What is a video port when it's at home? Isn't that something X should take care of? * Use XRender/antialias control - this stuff should be controlled by fontconfig, there's no need to dupe settings here. [registry] All of them. The defaults seem sane enough: ;These are all booleans. Y/y/T/t/1 are true, N/n/F/f/0 are false. ;Defaults are read all, write to Home ; Where to find the global registries ;"GlobalRegistryDir" = "/etc"; ; Global registries (stored in /etc) "LoadGlobalRegistryFiles" = "Y" ; Home registries (stored in ~user/.wine/) "LoadHomeRegistryFiles" = "Y" ; Load Windows registries from the Windows directory "LoadWindowsRegistryFiles" = "Y" ; TRY to write all changes to home registries "WritetoHomeRegistryFiles" = "Y" ; Registry periodic save timeout in seconds ; "PeriodicSave" = "600" ; Save only modified keys "SaveOnlyUpdatedKeys" = "Y" Is there ever a reason why a user would want to change these? The last one in particular seems rather arcane - why would anybody want Wine to flush unchanged keys? Some of the global vs home stuff might be useful for administrators or packagers, but they should be OK with using a premade registry file and merging it in. [TweakLayout] I played around with these when I first started using Wine, and couldn't really figure out what they changed. Does this affect app compatability? Why would a user not want the latest layout? [Clipboard] >From the names it's only vaguely clear what they do - the defaults have always worked well for me, can anybody provide good use cases for when they need to be altered? That leaves the following things as user configurable, though really they probably shouldn't be one day: * Drive setup - I want to write some autodetect code for this, but I doubt people will want to have always autodetected anytime soon. * DSound - I can't understand any of these settings, but apparently they can't be easily autodetected??? * Ports setup - I don't know anything about these. They feel like we should be able to autodetect them, but I don't know how. * Debug - obviously, this has to be set by a human. But is a gui the best place? Perhaps have a switch to winecfg that enables the tab for "developer mode"? * Windows version. Well, real Windows users don't get to choose this :) Unfortunately while Wine is still imperfect, sometimes altering this can make things come good, so it's optional only in theory. * DLL overrides - ditto. Smarter defaults can't hurt here, for instance we have MSI only as stubs but we default to them anyway, which is dumb. As it is, some programs that saw the lack of MSI before and offered to helpfully install it, now crash :( * Desktop/managed mode. Well, desktop mode is maybe a pref for strange people (*cough*lionel*cough* ;), and managed mode is something that still must be sometimes tweaked for each app. Long term this could probably be made automatic so the user can just stick with managed/no-desktop by default and we select the right one as needed. I've probably missed some. Also, you may feel that a setting I marked as unnecessary, may actually be needed. If so, please tell me why *with reasoned arguments*, not just "well I happen to like tweaking that" or "application X needs it to be set". If a whole load of applications need it to be tweaked one way or the other then maybe, but really that's a bug and we should fix it.... thanks -mike

4 3

CreateBitmap fails
by Jarkko Lavinen Sept. 15, 2003

Sept. 15, 2003

I am trying to run Trace32 hardware debugging system with Wine. I would like to use the latest Wine version, but unfortunately some bitmap buttons are corrupted on recent Wine versions. Well, I think the problem started about a year ago and have simply used an old Wine 20020327 where the buttons are displayed correctly. Example of corrupted buttons with Wine 20030911 http://www.iki.fi/~jlavi/Wine/trace32-wine-20030911.gif and another example of same buttons looking ok on Wine 20020327 http://www.iki.fi/~jlavi/Wine/trace32-wine-20020327.gif When running Trace32 on Wine 20030911 I get 108 lines of following message: err:x11drv:X11DRV_CreateBitmap Trying to make bitmap with planes=1, bpp=4 And bitmap buttons on the main Trace32 window are corrupted but on subwindows they are ok. With Wine 20020327 I get the CreateBitmap message only once and the buttons are ok on both main window and on subwindows. Jarkko Lavinen

2 1

CreateProcessA and winboard
by erwin wolff Sept. 15, 2003

Sept. 15, 2003

Hey everyone, I think I got the reason why winlib's winboard doesn't work. The createprocessa function doesn't work on either the winlib compiled version or the native version. Although the winelib version of winboard works better than the windows version. This is the output I got from the windows version: fixme:process:CreateProcessA (C:\winboard\GNUChess.exe,...): CREATE_NEW_PROCESS_GROUP ignored fixme:console:SetConsoleCtrlHandler ((nil),1) - no error checking or testing yet It fired up GNUchess.exe and openend it in a window, but then it crashed >:(. The winelib counterpart gave me a more useful debug report: fixme:gdi:ExtCreatePen Hatches not implemented fixme:gdi:ExtCreatePen Hatches not implemented fixme:gdi:ExtCreatePen Hatches not implemented .... fixme:process:CreateProcessA (C:\winboard\GNUChess.exe,...): CREATE_NEW_PROCESS_GROUP ignored fixme:console:SetConsoleCtrlHandler ((nil),1) - no error checking or testing yet If you need the patch to compile and can't find it in the mail listing, just contact me :). I hope someone can fix it.

1 0

List of API functions and completeness.
by Jacobus Erasmus Sept. 15, 2003

Sept. 15, 2003

Hi I'm looking for a list of all the functions that would be displayed in a debug list. I'm feel like doing a fun project and am wondering if any body have pointers on how I can obtain the information I need. Basically I'm interested in writing a little script that would run through a debug output and pickup all the functions called with the execution of the Windows program in wine. I then want to match the functions called with a DB that tell me what the estimated completion level of each function is. The idea is to then is to calculate the probability that a program will function correctly with the current wine implementation. This is done using statistical data and estimation data for each function. (Like I say just for interest sake). What bothers me is the estimation of function completeness. How can I measure or alternatively collect this. Any suggestions would be appreciated. -- Jacobus Erasmus <jacobus(a)kewlconcepts.co.za> Kewlconcepts

2 1

Re: Taskmanger Relicense: Was Unable to cimpile wineproc
by thomas.mertes＠gmx.at Sept. 15, 2003

Sept. 15, 2003

Eric Pouech (pouech-eric_at_wanadoo.fr) wrote: > + Don't depend on msvcrt > - added wine only dumb macros for _ui64toa and _ultoa This is not necessary _ui64toa and _ultoa are defined in the ntdll. See ntdll.spec: @ cdecl _ui64toa(long long ptr long) @ cdecl _ultoa(long ptr long) and ntdll/string.c: char * __cdecl _ui64toa( ULONGLONG value, /* [I] Value to be converted */ char *str, /* [O] Destination for the converted value */ int radix) /* [I] Number base for conversion */ ...... char * __cdecl _ultoa( unsigned long value, /* [I] Value to be converted */ char *str, /* [O] Destination for the converted value */ int radix) /* [I] Number base for conversion */ ...... May be prototypes of _ui64toa and _ultoa should be added to winternl.h or some other ntdll specific include file. In the moment this prototypes are only defined in msvcrt/stdlib.h: char* _ui64toa(unsigned __int64,char*,int); char* _ultoa(unsigned long,char*,int); Greetings Thomas Mertes -- COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -------------------------------------------------- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post

1 0

Re: Link winlib with windows DLL help????
by Fabian Cenedese Sept. 15, 2003

Sept. 15, 2003

>I try "winemaker -iavisynth_c ." >But when making I get "could not open .def file for avisynth_c" > >And I am not sure how to create this .def file. Quite easy. It's a simple text file filled with the exported functions like DESCRIPTION 'My Special DLL' EXPORTS CMRegisterControl @1 CMUnregisterControl @2 CMGetCommandString @3 CMRegisterCommand @4 etc. I'm sure you will find more info about this on the net. bye Fabi

1 0