wine-devel September 2003

wine-devel@winehq.org

133 participants
342 discussions

Re: shell32 (part3): Make sure the bind context is forwarded in ShellFolder_ParseDisplayName
by Alexandre Julliard 16 Sep '03

16 Sep '03

"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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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 15 Sep '03

15 Sep '03

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

← Newer
1
...
14
15
16
17
18
19
20
...
35
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel September 2003