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

Regedit
by Ivan Leo Murray-Smith Sept. 15, 2003

Sept. 15, 2003

Hi list, I'm translating regedit to italian, and I wanted to make it as similar as possible to the windows regedit. The only problem is that the wine regedit is based on the english m$ regedit, but m$ has written the italian version in a slightly different way. For example, what in the m$ english version and in the wine version is import registry file in the m$ italian version is translated into import file of the configuration registry Now I'm not sure if I should base the italian translation of the wine registry on the english version of the registry(I suppose it would be more consistent with other translations), or if I should translate it as m$ has done(What I think is best, as any user coming from an italian windows installation would find familiar menus), any advice would be greatly appreciated.

2 1

keyboard broken in DOS (real mode)
by Michael Stefaniuc Sept. 14, 2003

Sept. 14, 2003

Hello, the installer of the free IDA pro version (http://www.simtel.com/pub/pd/27629.html) dosn't work with wine due missing keyboard input. Pressing some keys makes wine to spit out following error: err:int:DOSVM_Int09SendScan keyboard queue overflow The emulated hardware keyboard buffer overflows because the keys don't make it to the emulated BIOS keyboard buffer. DOSVM_Int09SendScan queues an event for IRQ1 but no handler for int 09 is ever called (the int 09 handler copies the keys from the hardware to the BIOS keyboard buffer). (Thx to Ove for the explanation how things should work) >From the +int,+int21,+relay debug output it seems like the event queued by DOSVM_Int09SendScan is stuck in the queue. I had a look at DOSVM_QueueEvent and the other dosvm and interrupt functions but i didn't see the light of how this stuff works and why the queued event is never processed. Some help with that would be grateful. Btw the keyboard input seems to work in protected mode (tested with the setup program of Imperium Romanum using the DOS32A extender). bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

1 0

load library problem
by Dimitrie O. Paun Sept. 14, 2003

Sept. 14, 2003

Hi folks, I have flagged this before, but got no answer. Once again, this a C++ Winelib app (one of the wxWindows samples): [dimi(a)dimi calendar]$ ls calendar* calendar calendar_calendar.o calendar.cpp calendar.exe.so calendar.o calendar.rc calendar-wrap.dll.so calendar.bkl calendar_calendar_rc.o calendar.dsp calendarM5.xml calendar.pro calendar_resources.o [dimi(a)dimi calendar]$ export WINEDLLPATH=`pwd` [dimi(a)dimi calendar]$ echo $WINEDLLPATH /home/dimi/dev/wine/wxWindows/samples/calendar [dimi(a)dimi calendar]$ wine --debugmsg +module,+loaddll calendar.exe.so 2>log [dimi(a)dimi calendar]$ tail log trace:module:GetModuleFileNameW L"F:\\dev\\wine\\wxWindows\\samples\\calendar\\calendar.exe" trace:module:GetModuleFileNameW L"F:\\dev\\wine\\wxWindows\\samples\\calendar\\calendar.exe" trace:module:MODULE_GetLoadOrder looking for C:\WINDOWS\SYSTEM\calendar-wrap.dll trace:module:GetModuleFileNameW L"F:\\dev\\wine\\wxWindows\\samples\\calendar\\calendar.exe" trace:module:open_app_key searching 'calendar-wrap' in AppDefaults\calendar.exe\DllOverrides trace:module:MODULE_GetLoadOrder got standard wildcard "b,n" for "calendar-wrap.dll" trace:module:load_dll Trying built-in 'C:\WINDOWS\SYSTEM\calendar-wrap.dll' trace:module:load_dll Trying native dll 'C:\WINDOWS\SYSTEM\calendar-wrap.dll' warn:module:load_dll Failed to load module 'C:\WINDOWS\SYSTEM\calendar-wrap.dll'; status=c000000f Error: Could not load the application's module calendar-wrap.dll (126) The piece of code that fails is from the automatically generated wrapper[1]. Here is the part that fails: LoadLibrary("calendar-wrap.dll"); I have the WINEDLLPATH set, what gives? Alexandre, I can't really track this easily back, but I have a gut feeling it got triggered by one of the reorganizations that you did around the loader... [1] That is how the app was linked: [dimi(a)dimi calendar]$ winewrap -v -k -mgui -C -o calendar.exe calendar_calendar.o calendar_calendar_rc.o -L../../lib -lwx_msw-2.5 -lwxexpat -lz -lrpcrt4 -loleaut32 -lole32 -lwine_uuid -lwinspool -lwinmm -lshell32 -lcomctl32 -lcomdlg32 -lctl3d32 -ladvapi32 -lwsock32 -lgdi32 -lpng -ljpeg -ltiff -lcomdlg32 -ladvapi32 -lshell32 Creating file /tmp/wapp9rVK4g.spec winebuild -o /tmp/wapp9rVK4g.spec.c -F calendar-wrap.dll --spec /tmp/wapp9rVK4g.spec -L/usr/local/lib/wine -L../../lib -lrpcrt4 -loleaut32 -lole32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lcomdlg32 -lctl3d32 -ladvapi32 -lwsock32 -lgdi32 -lcomdlg32 -ladvapi32 -lshell32 -lgdi32 -luser32 -lkernel32 calendar_calendar.o calendar_calendar_rc.o ../../lib/libwx_msw-2.5.a ../../lib/libwxexpat.a /usr/lib/libz.a /usr/local/lib/libwine_uuid.a ../../lib/libpng.a ../../lib/libjpeg.a ../../lib/libtiff.a gcc -fPIC -o /tmp/wapp9rVK4g.spec.o -c /tmp/wapp9rVK4g.spec.c g++ -shared -Wl,-Bsymbolic,-z,defs -lwine -lm -L/usr/local/lib/wine -L../../lib -o calendar-wrap.dll.so /tmp/wapp9rVK4g.spec.o calendar_calendar.o ../../lib/libwx_msw-2.5.a ../../lib/libwxexpat.a /usr/lib/libz.a /usr/local/lib/libwine_uuid.a ../../lib/libpng.a ../../lib/libjpeg.a ../../lib/libtiff.a Creating file /tmp/wwrpBOB32M.c gcc -fPIC -I/usr/local/include/wine/windows -o /tmp/wwrpBOB32M.o -c /tmp/wwrpBOB32M.c winebuild -o /tmp/wwrpBOB32M.spec.c --exe calendar.exe -mgui /tmp/wwrpBOB32M.o -L/usr/local/lib/wine -L../../lib -lrpcrt4 -loleaut32 -lole32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lcomdlg32 -lctl3d32 -ladvapi32 -lwsock32 -lgdi32 -lcomdlg32 -ladvapi32 -lshell32 -lgdi32 -luser32 -lkernel32 gcc -fPIC -o /tmp/wwrpBOB32M.spec.o -c /tmp/wwrpBOB32M.spec.c g++ -shared -Wl,-Bsymbolic,-z,defs -lwine -ldl -o calendar.exe.so /tmp/wwrpBOB32M.spec.o /tmp/wwrpBOB32M.o Creating file calendar [dimi(a)dimi calendar]$ cat /tmp/wapp9rVK4g.spec @ stdcall WinMain(ptr long ptr long) WinMain [dimi(a)dimi calendar]$ cat /tmp/wwrpBOB32M.c /* * Copyright 2000 Francois Gouget <fgouget(a)codeweavers.com> for CodeWeavers * Copyright 2002 Dimitrie O. Paun <dpaun(a)rogers.com> */ #include <stdio.h> #include <windows.h> /* * Describe the wrapped application */ /* The app name */ #define APPNAME "calendar" /** * This is either 0 for a console based application or * 1 for a regular windows application. */ #define GUIEXE 1 /** * This is the name of the library containing the application, * e.g. 'hello-wrap.dll' if the application is called 'hello.exe'. */ static char* appName = APPNAME "-wrap.dll"; /** * This is the name of the application's Windows module. If left NULL * then appName is used. */ static char* appModule = NULL; /** * This is the application's entry point. This is usually 'WinMain' for a * gui app and 'main' for a console application. */ #if GUIEXE static char* appInit = "WinMain"; #else static char* appInit = "main"; #endif /** * This is either non-NULL for MFC-based applications and is the name of the * MFC's module. This is the module in which we will take the 'WinMain' * function. */ static char* mfcModule = NULL; void error(const char *format, ...) { va_list ap; char msg[4096]; va_start(ap, format); vsnprintf(msg, sizeof(msg), format, ap); fprintf(stderr, "Error: %s\n", msg); /*MessageBox(NULL, msg, "Error", MB_OK);*/ va_end(ap); exit(1); } #if GUIEXE typedef int WINAPI (*WinMainFunc)(HINSTANCE hInstance, HINSTANCE hPrevInstance, PSTR szCmdLine, int iCmdShow); #else typedef int WINAPI (*MainFunc)(int argc, char** argv, char** envp); #endif #if GUIEXE int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, PSTR szCmdLine, int iCmdShow) #else int WINAPI main(int argc, char** argv, char** envp) #endif { HINSTANCE hApp = 0, hMFC = 0, hMain = 0; void* appMain; int retcode; /* Then if this application is MFC based, load the MFC module */ if (mfcModule) { hMFC = LoadLibrary(mfcModule); if (!hMFC) error("Could not load the MFC module %s (%d)", mfcModule, GetLastError()); /* For MFC apps, WinMain is in the MFC library */ hMain = hMFC; } /* Load the application's module */ if (!appModule) appModule = appName; hApp = LoadLibrary(appModule); if (!hApp) error("Could not load the application's module %s (%d)", appModule, GetLastError()); if (!hMain) hMain = hApp; /* Get the address of the application's entry point */ appMain = GetProcAddress(hMain, appInit); if (!appMain) error("Could not get the address of %s (%d)", appInit, GetLastError()); /* And finally invoke the application's entry point */ #if GUIEXE retcode = (*((WinMainFunc)appMain))(hApp, hPrevInstance, szCmdLine, iCmdShow); #else retcode = (*((MainFunc)appMain))(argc, argv, envp); #endif /* Cleanup and done */ FreeLibrary(hApp); FreeLibrary(hMFC); return retcode; } -- Dimi.

4 8

Re: [comctl32] Fix listview item activate
by Dimitrie O. Paun Sept. 14, 2003

Sept. 14, 2003

On September 14, 2003 09:36 am, Maxime Bellengé wrote: > + nmia.uNewState = 0; > + nmia.uOldState = 0; > + nmia.uChanged = 0; > + nmia.lParam = 0; > + nmia.uKeyFlags = 0; What about these flags, shouldn't we fill these in as well? At the very least we need an entry in the TODO list at the top of the file... -- Dimi.

1 0

Link winlib with windows DLL help????
by Kevin Atkinson Sept. 14, 2003

Sept. 14, 2003

I am having a hell of a time getting a simple program to link with a windows dll. I am really sorry for the newbie question but I can't seam to find an answer anywhere and the mailing list archive is not searchable. Here is what I got: avs2yuv4mpeg.cpp - the main program avisynth_c.h - header for DLL I need to link with avisynth_c.lib - lib " " " And I want to compile this into an executable avs2yuv4mpeg 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. Please help. Once again really sorry. But the mailing list is not searchable AND the winlib docs are really confusing and do not specially cover this situation. -- http://kevin.atkinson.dhs.org

3 8

Re: wineproc: a new wine utility
by Dimitrie O. Paun Sept. 14, 2003

Sept. 14, 2003

On September 3, 2003 03:53 pm, Eric Pouech wrote: > any comment welcomed!! Sorry for the late reply -- I just got a chance to look into it. It looks good, I hope to see (some version of) it in the tree soon. One thing that bug me were the refreshes -- too much flicker, loss of selection etc. I think we need to be smarter and not change the display if nothing changed. But of course, this can happen once we have something integrated into the tree... -- Dimi.

1 0

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith Sept. 14, 2003

Sept. 14, 2003

>On Thu, 11 Sep 2003, Ivan Leo Murray-Smith wrote: > >> The original sentence that started this is >> >The following list are the x86 operating systems supported by >[...] >> "The list is current as of XX/XX/XXXX" is a solution that should make everybody >> happy. > >Not really because as the above clearly illustrates, this is not what >the original sentence said or meant to say. I really don't know why >everyone focused on this 'up-to-date' thing. > >*Sigh* This is just getting so boring, just use "The following lists the x86 operating systems supported by" and that can be the end of that (Hoping nobody starts discussing again about there great knowledge of slang and ignorance of english...)

2 1

Kernel pipe test segfaults?
by Rolf Kalbermatter Sept. 13, 2003

Sept. 13, 2003

Mike Hearn <mike(a)theoretic.com> wrote: >Maybe this is a known issue, I haven't really followed the test case >work up until now, but does the kernel32 pipe test segfault for anybody >else? I have problems, too. It used to crash somewhere in kernel32 with processes and now with pipes, where the test hangs for several minutes and then is aborted with returning an error 139. This is with Suse 8.2 and an Athlon optimized 2.4.20 Standard Suse kernel. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:rolf.kalbermatter(a)citeng.com

1 0

Really slow named pipes
by Duane Clark Sept. 13, 2003

Sept. 13, 2003

This is a bit old, from May, but anyhow... The patch to implement anonymous pipes on top of named pipes: http://www.winehq.com/hypermail/wine-cvs/2003/05/0305.html along with a corresponding bug fix: http://www.winehq.com/hypermail/wine-cvs/2003/06/0123.html causes Xilinx ISE to run really, really slow. It has a window to which messages are sent via a pipe, and what I see now is that one line comes out every 2/3 of a second or so, as regular as a clock at least by eye. I can revert those two patches, and it goes back to spitting out the messages very fast. Since there are a lot of messages being sent, the current version slows the app down to a crawl. It does not look like the patch itself is the problem; I am guessing that it is the underlying named pipe implementation that is the problem, which was exposed by the patch. Also, reverting to the full CVS 5/20, just after the pipe patches, has the same problem. So it appears that whatever is wrong with named pipes (if that really is the problem) was already there on 5/20, rather than it being something introduced since then. Any hints on what I could look for would be welcome.

4 10

Re: kernel32.GetProcessIoCounters basic implementation
by Eric Pouech Sept. 13, 2003

Sept. 13, 2003

Eric Pouech wrote: > TSIA > A+ oops, wrong file... use this one instead :-( A+ -- Eric Pouech Name: iocnt ChangeLog: Implemented GetIoProcessCounters License: X11 GenDate: 2003/09/13 12:50:39 UTC ModifiedFiles: dlls/kernel/kernel32.spec dlls/kernel/process.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/kernel/kernel32.spec,v retrieving revision 1.106 diff -u -u -r1.106 kernel32.spec --- dlls/kernel/kernel32.spec 11 Sep 2003 03:00:11 -0000 1.106 +++ dlls/kernel/kernel32.spec 13 Sep 2003 07:18:18 -0000 @@ -452,7 +452,7 @@ @ stdcall GetProcessFlags(long) @ stdcall GetProcessHeap() @ stdcall GetProcessHeaps(long ptr) -@ stub GetProcessIoCounters +@ stdcall GetProcessIoCounters(long ptr) @ stdcall GetProcessShutdownParameters(ptr ptr) @ stdcall GetProcessTimes(long ptr ptr ptr ptr) @ stdcall GetProcessVersion(long) Index: dlls/kernel/process.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/dlls/kernel/process.c,v retrieving revision 1.4 diff -u -u -r1.4 process.c --- dlls/kernel/process.c 5 Sep 2003 23:08:37 -0000 1.4 +++ dlls/kernel/process.c 13 Sep 2003 07:17:56 -0000 @@ -424,6 +424,16 @@ return !status; } +/****************************************************************** + * GetProcessIoCounters (KERNEL32.@) + * + * + */ +BOOL WINAPI GetProcessIoCounters(HANDLE hProcess, PIO_COUNTERS ioc) +{ + memset(ioc, 0, sizeof(ioc)); + return TRUE; +} /*********************************************************************** * RegisterServiceProcess (KERNEL.491)

1 0

Here is one - Linux on Cygwin on Linux
by Steven Edwards Sept. 13, 2003

Sept. 13, 2003

Here is a good one for someone to test. The User Mode Linux people have done it. They are working on a port of User Mode Linux to Win32. This has been something I have been wanting to see for a while so we can use Linux as our Posix subystem in ReactOS by moving parts of UMLwin32 in to back to kernel mode. Right now you still need cygwin but if someone wants to try running it under Cygwin on WINE here is the url: http://umlwin32.sourceforge.net Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

3 2

Re: Word-splitting in the FAQ
by Dan Kegel Sept. 13, 2003

Sept. 13, 2003

On the general subject of spellchecking, there are a few typo lists and spellcheckers at http://www.kegel.com/kerspell/ which specialize in typos in C program comments... might be of some interest. One of them was contributed by Francois and has already been run on the Wine tree, I think... -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith Sept. 13, 2003

Sept. 13, 2003

The original sentence that started this is >The following list are the x86 operating systems supported by from twickline_at_skybest.com http://www.winehq.org/hypermail/wine-devel/2003/09/0356.html He claims he knows 3 types of slang, and is from west virginia, but he never claimed to be "A native english speaker", so you don't have (Such a big) reason to be bothered. I was the first to claim a native english speaker (As far as I know) and I have tried explaining to Tom that there is a thing called grammar, but he had a few problems understanding that. "The list is current as of XX/XX/XXXX" is a solution that should make everybody happy.

2 1

ikernel.exe error still not fix in 11_9_03.tar.gz
by lineric＠qwest.net Sept. 12, 2003

Sept. 12, 2003

1 0

Re: [ros-kernel] an interesting idea
by Steven Edwards Sept. 12, 2003

Sept. 12, 2003

This is what I have been thinking. We can move parts of UML back to a subsytem mode and them implement a Xsever in to Win32k.sys/GDI32. You wouldnt even need to recompile X applications provided we implement X properly. All that would be needed is a modded Xserver and X libs. The client libs should still work using X protocal and Xtenstions. This type of hybrid system could then run any application Windows or Linux and would not suffer from the same problems WINE does because it would be a real Linux Kerenl and GLIBC running. Thanks Steven --- Jonathan Wilson <jonwil(a)tpgi.com.au> wrote: > Something we could do (once we get UML going without cygwin and down into > the kernel) is to build a Linux subsystem (mabie even with ports of > GTK/QT/X/etc on top of GDI) that could run linux apps just as easily as it > can run windows apps. > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

Re: [winecfg 8] Complete drive edit dialog, warn on lack of C drive, implement drive delete, code cleanups
by Dimitrie O. Paun Sept. 12, 2003

Sept. 12, 2003

On 11 Sep 2003, Mike Hearn wrote: > ChangeLog: > - All settings in the drive edit dialog are now instant apply This is a cool feature, but we should keep it optional. Our primary audience are Windows users, and they are not used to that. Heck, even I am not used to it, I am used to be able to play around with stuff in dialogs, and than press CANCEL. In fact, KDE is not instant apply, so I would argue that even most Linux users are used to that. I'd argue that we need to support instant apply to integrate with GNOME, but to default to the classic OK/CANCEL for now, until we can figure how and when to enable one or the other behaviour. -- Dimi.

5 8

Kernel pipe test segfaults?
by Mike Hearn Sept. 12, 2003

Sept. 12, 2003

Maybe this is a known issue, I haven't really followed the test case work up until now, but does the kernel32 pipe test segfault for anybody else? thanks -mike

2 1

Re: WIne help - get rid of W->A calls
by Eric Pouech Sept. 12, 2003

Sept. 12, 2003

hatky wrote: > My first patch, so a deep check is welcome > > Change log: > - Remove W->A call from WineHelpA/W > - This patch is dedicated to dimi that guided me I'm afraid the patch is wrong. the current implentation of WinHelp, which sends data from any app to the program winhelp, requires that the data block passed between those two apps encodes strings in ASCII, not unicode. Your patch modifies the sender so that it encodes in Unicode, but the receiver is left untouched. I'd suggest anyway that we remain as close as possible as Windows do. - we don't completly handle this protocol as Windows do (Windows send a WM_HELP - registered - message, we only use a WM_COPYDATA), but the format of the message (parameter block) is quite the same (we just add some extra fields to ensure that we don't mess with a spurious WM_COPYDATA message in winhelp). - as Windows encode strings in this message block in ASCII, I'd suggest keeping the encoding of strings inside the message as ASCII. A+ -- Eric Pouech

3 2

configure new wine
by eric Sept. 12, 2003

Sept. 12, 2003

Dear cvs wine users: By reading the doc's install page, I success uninstall cvs 's wine reinstall 8/13' wine, then test again, it indeed repeat the ikernel problem, but it at least configure correct by default. So I copy /root/.wine/config to /root/oldwineconfig. Then uninstall it again as doc indicate, then install cvs again, after that I cp oldwineconfig /etc/wine/config and /root/.wine/config then run my app, it still show segmentation fault please help, thanks in advance Sincerely Eric

1 0

Can not uninstall CVS wine
by eric Sept. 12, 2003

Sept. 12, 2003

Dear Wine users: After I install CVS wine, and find it is not work, it type rpm -e wine reinstall my old wine, then if I did not do it by force, it showed error ------------------ [root(a)localhost x86]# rpm -vhi /root/wine-2* Preparing... ########################################### [100%] file /usr/bin/widl from install of wine-20030813-1rh9winehq conflicts with file from package wine-cvs-unstripped-20030911-1 file /usr/bin/wine from install of wine-20030813-1rh9winehq conflicts with file from package wine-cvs-unstripped-20030911-1 ------------------ if I use force to install old package, it still can not run my app, segmentation fault, and I check rpm -q wine, it reponse wine package in not installed highly appreciate any help to remove that CVS's wine throughly and thanks in advance Sincerely Eric

1 0

openbsd supports MAP_FIXED too
by Ted Unangst Sept. 12, 2003

Sept. 12, 2003

sorry no patch. i'm not sure what the status of wine on openbsd is, although i came across a notice that wine was capable of using MAP_FIXED. i committed what amounted to todd's (netbsd) patch to openbsd shortly after it went into netbsd. don't know if this helps / who cares, but fyi. patch below could probably be || defined (__OpenBSD__) as well. http://www.winehq.org/hypermail/wine-patches/2003/08/0278.html -- someone's writing down your mistakes someone's documenting your downfall

1 0

scheduler related complete breakage on FreeBSD
by Gerald Pfeifer Sept. 12, 2003

Sept. 12, 2003

On FreeBSD 4.8 (using -lc_r instead of -lc to get pthreads) Wine crashes upon startup: /sw/test/wine% wine FIXME:pthread_cond_init Segmentation fault (core dumped) % gdb53 miscemu/wine wine.core GNU gdb 5.3 (FreeBSD) Reading symbols from /sw/test/wine/dlls/libntdll.dll.so...done. Loaded symbols for /sw/wine/dlls/libntdll.dll.so Reading symbols from /sw/test/wine/libs/libwine.so.1...done. Loaded symbols for /sw/test/wine/libs/libwine.so.1 Reading symbols from /sw/test/wine/libs/libwine_unicode.so.1...done. Loaded symbols for /sw/test/wine/libs/libwine_unicode.so.1 Reading symbols from /usr/lib/libc.so.4...done. Loaded symbols for /usr/lib/libc.so.4 Reading symbols from /usr/lib/libm.so.2...done. Loaded symbols for /usr/lib/libm.so.2 Reading symbols from /usr/lib/libc_r.so.4...done. Loaded symbols for /usr/lib/libc_r.so.4 Reading symbols from /sw/test/wine/dlls/kernel32.dll.so...done. Loaded symbols for /sw/test/wine/dlls/kernel32.dll.so Reading symbols from /usr/libexec/ld-elf.so.1...done. Loaded symbols for /usr/libexec/ld-elf.so.1 (gdb) bt #0 0x5c251aac in .cerror () from /usr/lib/libc.so.4 #1 0x5c2feca6 in flock () from /usr/lib/libc_r.so.4 #2 0x5c231919 in _yp_dobind () from /usr/lib/libc.so.4 #3 0x5c231fa8 in yp_match () from /usr/lib/libc.so.4 #4 0x5c215c12 in endpwent () from /usr/lib/libc.so.4 #5 0x5c2153b8 in getpwuid () from /usr/lib/libc.so.4 #6 0x5c0d06d1 in init_paths () at config.c:112 #7 0x5c0d0a4e in wine_get_server_dir () at config.c:191 #8 0x5c07e5ae in CLIENT_InitServer () at ../../scheduler/client.c:641 #9 0x5c07f4f4 in process_init (argv=0xbfbff690) at ../../scheduler/process.c:306 #10 0x5c07fa19 in __wine_process_init (argc=1, argv=0xbfbff690) at ../../scheduler/process.c:480 #11 0x5c0d21c4 in wine_init (argc=1, argv=0xbfbff690, error=0xbfbff240 "", error_size=1024) at loader.c:428 #12 0x3c000621 in main (argc=1, argv=0xbfbff690) at main.c:33 #13 0x3c000566 in _start () Any help will be appreciated. Gerald

1 1

FIXME:pthread_cond_init
by Gerald Pfeifer Sept. 12, 2003

Sept. 12, 2003

When building Wine on FreeBSD with libc_r (r for reentrant) instead of libc, I now trigger the following FIXME in scheduler/pthread.c: /***** CONDITIONS *****/ /* not implemented right now */ int __pthread_cond_init(pthread_cond_t *cond, const pthread_condattr_t *cond_attr) { P_OUTPUT("FIXME:pthread_cond_init\n"); return 0; } What's the proper way to address this? (I'm afraid, it's beyond what I'll be able to implement, though.) Gerald

1 1

BuildCommDCB conformance test
by Kevin Groeneveld Sept. 12, 2003

Sept. 12, 2003

Here is my first attempt at a conformance test for the BuildCommDCB functions. It does not cover very many cases yet, but I thought I would post what I have so far in case I am going about this the wrong way. I compiled this with MSVC and it ran with no errors on both Windows 95 and Windows 2000. It also compiles with libwine in Linux, but for this to work you need to add a missing member to the DCB structure in winbase.h. If I run this test with the existing implementation of BuildCommDCB it page faults, probably because it is writing to a constant string. If my previous patch to BuildCommDCB is applied, then the test runs ok. Kevin diff -urN wine-20030813/dlls/kernel/tests/Makefile.in wine-20030813.patched/dlls/kernel/tests/Makefile.in --- wine-20030813/dlls/kernel/tests/Makefile.in 2003-08-23 23:12:31.000000000 -0400 +++ wine-20030813.patched/dlls/kernel/tests/Makefile.in 2003-09-10 23:31:59.000000000 -0400 @@ -8,6 +8,7 @@ CTESTS = \ alloc.c \ atom.c \ + build_dcb.c \ codepage.c \ console.c \ directory.c \ diff -urN wine-20030813/dlls/kernel/tests/build_dcb.c wine-20030813.patched/dlls/kernel/tests/build_dcb.c --- wine-20030813/dlls/kernel/tests/build_dcb.c 1969-12-31 19:00:00.000000000 -0500 +++ wine-20030813.patched/dlls/kernel/tests/build_dcb.c 2003-09-11 01:00:19.000000000 -0400 @@ -0,0 +1,171 @@ +/* Unit test suite for BuildCommDCBA/W & BuildCommDCBAndTimeoutsA/W + * + * Copyright 2003 Kevin Groeneveld + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + */ + +#include "wine/test.h" +#include "winbase.h" + +typedef struct +{ + char *string; + BOOL result; + DCB dcb1, dcb2; + COMMTIMEOUTS timeouts1, timeouts2; +} TEST; + +TEST test[] = +{ + { + "baud=9600", + TRUE, + { 0x00000000, 9600, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0x00000, 0x0000, 0x0000, 0x0000, 0x00, 0x00, 0x00, (char)0x00, (char)0x00, (char)0x00, (char)0x00, (char)0x00, 0x0000 }, + { 0xffffffff, 9600, 1, 1, 1, 1, 3, 1, 1, 1, 1, 1, 1, 3, 1, 0x1ffff, 0xffff, 0xffff, 0xffff, 0xff, 0xff, 0x00, (char)0xff, (char)0xff, (char)0xff, (char)0xff, (char)0xff, 0xffff }, + { 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 }, + { 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff } + }, + { + " baud=9600", + FALSE, + { 0x00000000, 0x00000000, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0x00000, 0x0000, 0x0000, 0x0000, 0x00, 0x00, 0x00, (char)0x00, (char)0x00, (char)0x00, (char)0x00, (char)0x00, 0x0000 }, + { 0xffffffff, 0xffffffff, 1, 1, 1, 1, 3, 1, 1, 1, 1, 1, 1, 3, 1, 0x1ffff, 0xffff, 0xffff, 0xffff, 0xff, 0xff, 0xff, (char)0xff, (char)0xff, (char)0xff, (char)0xff, (char)0xff, 0xffff }, + { 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 }, + { 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff } + }, + { + "to=on", + TRUE, + { 0x00000000, 0x00000000, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0x00000, 0x0000, 0x0000, 0x0000, 0x00, 0x00, 0x00, (char)0x00, (char)0x00, (char)0x00, (char)0x00, (char)0x00, 0x0000 }, + { 0xffffffff, 0xffffffff, 1, 1, 1, 1, 3, 1, 1, 1, 1, 1, 1, 3, 1, 0x1ffff, 0xffff, 0xffff, 0xffff, 0xff, 0xff, 0x00, (char)0xff, (char)0xff, (char)0xff, (char)0xff, (char)0xff, 0xffff }, + { 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x0000EA60 }, + { 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x0000EA60 } + }, +}; + +#define TEST_COUNT (sizeof(test) / sizeof(TEST)) + +void check_result(char *function, char *string, int initial_value, BOOL result1, BOOL result2) +{ + DWORD LastError = GetLastError(); + DWORD CorrectError = (result2 ? 0xdeadbeef : ERROR_INVALID_PARAMETER); + + ok(LastError == CorrectError, "%s(\"%s\"), 0x%02x: GetLastError() returned 0x%08lx, should be 0x%08lx", function, string, initial_value, LastError, CorrectError); + ok(result1 == result2, "%s(\"%s\"), 0x%02x: return value should be %s", function, string, initial_value, result2 ? "TRUE" : "FALSE"); +} + +#define check_dcb_member(a,b) ok(pdcb1->a == pdcb2->a, "%s(\"%s\"), 0x%02x: "#a" is "b", should be "b, function, string, initial_value, pdcb1->a, pdcb2->a); + +void check_dcb(char *function, char *string, int initial_value, DCB *pdcb1, DCB *pdcb2) +{ + /* DCBlength is a special case since Win 9x sets it but NT does not. + We will accept either as correct. */ + ok(pdcb1->DCBlength == pdcb2->DCBlength || pdcb1->DCBlength == sizeof(DCB), "%s(\"%s\"), 0x%02x: DCBlength is %lu, should be %lu or %lu", function, string, initial_value, pdcb1->DCBlength, pdcb2->DCBlength, (DWORD)sizeof(DCB)); + + /* Check all other DCB members */ + check_dcb_member(BaudRate, "%lu"); + check_dcb_member(fBinary, "%u"); + check_dcb_member(fParity, "%u"); + check_dcb_member(fOutxCtsFlow, "%u"); + check_dcb_member(fOutxDsrFlow, "%u"); + check_dcb_member(fParity, "%u"); + check_dcb_member(fOutxCtsFlow, "%u"); + check_dcb_member(fOutxDsrFlow, "%u"); + check_dcb_member(fDtrControl, "%u"); + check_dcb_member(fDsrSensitivity, "%u"); + check_dcb_member(fTXContinueOnXoff, "%u"); + check_dcb_member(fOutX, "%u"); + check_dcb_member(fInX, "%u"); + check_dcb_member(fErrorChar, "%u"); + check_dcb_member(fNull, "%u"); + check_dcb_member(fRtsControl, "%u"); + check_dcb_member(fAbortOnError, "%u"); + check_dcb_member(fDummy2, "%u"); + check_dcb_member(wReserved, "%u"); + check_dcb_member(XonLim, "%u"); + check_dcb_member(XoffLim, "%u"); + check_dcb_member(ByteSize, "%u"); + check_dcb_member(Parity, "%u"); + check_dcb_member(StopBits, "%u"); + check_dcb_member(XonChar, "%d"); + check_dcb_member(XoffChar, "%d"); + check_dcb_member(ErrorChar, "%d"); + check_dcb_member(EofChar, "%d"); + check_dcb_member(EvtChar, "%d"); + check_dcb_member(wReserved1, "%u"); +} + +#define check_timeouts_member(a) ok(ptimeouts1->a == ptimeouts2->a, "%s(\"%s\"), 0x%02x: "#a" is %lu, should be %lu", function, string, initial_value, ptimeouts1->a, ptimeouts2->a); + +void check_timeouts(char *function, char *string, int initial_value, COMMTIMEOUTS *ptimeouts1, COMMTIMEOUTS *ptimeouts2) +{ + check_timeouts_member(ReadIntervalTimeout); + check_timeouts_member(ReadTotalTimeoutMultiplier); + check_timeouts_member(ReadTotalTimeoutConstant); + check_timeouts_member(WriteTotalTimeoutMultiplier); + check_timeouts_member(WriteTotalTimeoutConstant); +} + +void test_BuildCommDCBA(char* string, BOOL expected_result, DCB *pexpected_dcb, int initial_value) +{ + BOOL result; + DCB dcb; + + /* set initial conditions */ + memset(&dcb, initial_value, sizeof(DCB)); + SetLastError(0xdeadbeef); + + result = BuildCommDCBA(string, &dcb); + + /* check results */ + check_result("BuildCommDCBA", string, initial_value, result, expected_result); + check_dcb("BuildCommDCBA", string, initial_value, &dcb, pexpected_dcb); +} + +void test_BuildCommDCBAndTimeoutsA(char* string, BOOL expected_result, DCB *pexpected_dcb, COMMTIMEOUTS *pexpected_timeouts, int initial_value) +{ + BOOL result; + DCB dcb; + COMMTIMEOUTS timeouts; + + /* set initial conditions */ + memset(&dcb, initial_value, sizeof(DCB)); + memset(&timeouts, initial_value, sizeof(COMMTIMEOUTS)); + SetLastError(0xdeadbeef); + + result = BuildCommDCBAndTimeoutsA(string, &dcb, &timeouts); + + /* check results */ + check_result("BuildCommDCBAndTimeoutsA", string, initial_value, result, expected_result); + check_dcb("BuildCommDCBAndTimeoutsA", string, initial_value, &dcb, pexpected_dcb); + check_timeouts("BuildCommDCBAndTimeoutsA", string, initial_value, &timeouts, pexpected_timeouts); +} + +void do_test(TEST *ptest) +{ + test_BuildCommDCBA(ptest->string, ptest->result, &ptest->dcb1, 0x00); + test_BuildCommDCBA(ptest->string, ptest->result, &ptest->dcb2, 0xFF); + test_BuildCommDCBAndTimeoutsA(ptest->string, ptest->result, &ptest->dcb1, &ptest->timeouts1, 0x00); + test_BuildCommDCBAndTimeoutsA(ptest->string, ptest->result, &ptest->dcb2, &ptest->timeouts2, 0xFF); +} + +START_TEST(build_dcb) +{ + int i; + + for(i = 0; i < TEST_COUNT; i++) + do_test(&test[i]); +} diff -urN wine-20030813/include/winbase.h wine-20030813.patched/include/winbase.h --- wine-20030813/include/winbase.h 2003-08-23 23:12:51.000000000 -0400 +++ wine-20030813.patched/include/winbase.h 2003-09-08 20:19:39.000000000 -0400 @@ -976,6 +976,7 @@ char ErrorChar; char EofChar; char EvtChar; + WORD wReserved1; } DCB, *LPDCB; typedef struct tagCOMMCONFIG {

4 4

Re: missing ordinals in avifil32
by Alexandre Julliard Sept. 12, 2003

Sept. 12, 2003

Dave Miller <compsol(a)ptd.net> writes: > The first 59 ordinals seem to match in all windows versions. Add > ordinals to avifil32.spec to match windows. Unless ordinals are actually needed, it's better not to add them. In that case the functions are sorted so it's very likely that Windows is using automatic allocation too. -- Alexandre Julliard julliard(a)winehq.com

3 3