March 2008 - Wine-devel - list.winehq.org

Testing service/driver install via setupapi
by Paul Vriens 20 Mar '08

20 Mar '08

Hi, I'm looking into bug 12030 (http://bugs.winehq.org/show_bug.cgi?id=12030) The driver service is not installed by our InstallHinfSection function. I'm first trying to come up with a test before even trying to do the implementation. The question I'm having is whether I should be doing the test with InstallHinfSection and/or SetupInstallServicesFromInfSection[Ex]? The current setupapi tests only test InstallHinfSection. But in the end SetupInstallFromInfSection will be called from within InstallHinfSection. Should I take the same approach for the services piece?. So, 1) Implement in SetupInstallServicesFromInfSection[Ex] 2) Test via InstallHinfSection -- Cheers, Paul.

1 0

The Linux/BSD DF kernel bug
by Francois Gouget 20 Mar '08

20 Mar '08

So I've just read the following article: GCC 4.3.0 exposes a kernel bug http://lwn.net/SubscriberLink/272048/ecf14f359bcdcd15/ And my question is: could this be relevant to Wine? And I don't mean about GCC 4.3.0 but about MSVC. Here's the core of the issue: The problem revolves around the x86 direction flag (DF), which governs whether block memory operations operate forward through memory or backwards. GCC [...] 4.3.0, assumes that the direction flag has been cleared [...] at the entry of each function, as is specified by the ABI [...] Prior to 4.3, GCC would emit a cld (clear direction flag) opcode before doing inline string or memory operations. So any compiler that not clear the direction flag at the start of each function can cause kernel crashes when running on a buggy Linux or BSD kernel. So the questions are: Does anyone know if MSVC does a cld in the right places? What about other popular compilers used to compile Windows applications? Mac OS X being (loosely) based on the BSD kernels, does it have this issue too? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY

4 12

re: First steps to make Win32 app running under Wine
by Dan Kegel 20 Mar '08

20 Mar '08

Martin Hinner wrote: > I am solving problem how to get one Win32 app (for which I have > source code) running under Wine. The biggest issue is drivers and > ioctls. Linux has driver support for what we need and provides similar > ioctls for some stuff, but it differs from Windows. What drivers and ioctls, exactly? Which driver framework are you using? http://en.wikipedia.org/wiki/User-Mode_Driver_Framework might be easier for us to directly support... - Dan

1 0

Google Summer of Code Test Suite project
by Corey McClymonds 20 Mar '08

20 Mar '08

I would like to work on the Regression Suite project, but I'm not quite sure of the scope. Would I be choosing a good 30 or 40 applications that run well on wine, using wpkg to install them, and then test for failures? Because that would seem as though I am only doing installer testing, instead of actual application testing. I would also like to do some sort of automated regression testing for actual features you can easily test, if that would be possible. Corey

4 4

Re: wineboot: Add the Romanian translation.
by Dimi Paun 20 Mar '08

20 Mar '08

On Wed, 2008-03-19 at 23:57 +0100, Michael Stefaniuc wrote: > + LTEXT "O îeșire sau oprire simulată este în curs dar > acest proces nu răspunde.", This should be "O ieșire" not "O îeșire", no? -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

2 1

First steps to make Win32 app running under Wine
by Martin Hinner 20 Mar '08

20 Mar '08

Hi, I am solving problem how to get one Win32 app (for which I have source code) running under Wine. The biggest issue is drivers and ioctls. Linux has driver support for what we need and provides similar ioctls for some stuff, but it differs from Windows. The difference is *so big* that I would prefer to modify our source code to use different pieces of code when it detects Wine. I understand, that this is *against* Wine policy and generally should not be used. But writing built-in replacement for some DLLs (hack Linux-style drivers into Windows-style) would be a nightmare, so having small mods to Win code would be much easier. I am not talking about "generic" functions, but about specific drivers/etc. Imagine this: Under windows you get usb driver with some ioctl-based interface, sometimes with DLL or without it (vendor provides only .lib file that gets statically linked). Under Linux there is libusb used. Difference between these two ways of driver implementation is *huge* and making libusb driver compatible with Win32 driver is almost impossible (in Win you have a real file handle, under libusb only pointer, etc.). It would greatly help for this case to be able to: - detect wine and platform from Win32 app (.exe) - load native Linux library and perform ioctls (ioctl(2), not Windows IOCTL!) on file handles - get somehow access to files in Linux filesystem (i.e. in /dev) This would allow to easily modify our source code in a few places (i.e. hardware routines) and get it quickly running under Linux. I can do all above by writing some built-in dll that would work just for my case, but I think *maybe* it's worth it to provide some generic interface in Wine?? Martin

2 2

Re: [1/2] reg: Implement basic 'reg add'.
by Dmitry Timoshkov 20 Mar '08

20 Mar '08

"Andrew Riedi" <andrewriedi(a)gmail.com> wrote: > +int reg_lstrncmpiW(const WCHAR *s1, const WCHAR *s2, size_t n) CompareString is better. > + const WCHAR hkcrW[] = {'h','k','c','r',0}; > + const WCHAR hkcuW[] = {'h','k','c','u',0}; > + const WCHAR hklmW[] = {'h','k','l','m',0}; > + const WCHAR hkuW[] = {'h','k','u',0}; > + const WCHAR hkccW[] = {'h','k','c','c',0}; > + const WCHAR hkddW[] = {'h','k','d','d',0}; You should make all const strings static. > + /* TODO: Remote registry editing. */ > + if (key_name[0] == '\\' && key_name[1] == '\\') > + { > + fprintf(stderr, "Remote registry editing not implemented.\n"); > + return 1; > + } Please use normal WINE_TRACE, WINE_ERR, etc instead of fprintf. -- Dmitry.

1 0

Questions regarding Summer of Code( and Dplay)
by Maarten Lankhorst 20 Mar '08

20 Mar '08

Hello Anurag, 2008/3/19, Anurag Mishra <mishra.anurag07(a)gmail.com>: > I am student at IIT Kanpur[1]. I have quite good knowledge about C > and have been tracking development of Wine over a period of 6 months > or so. I have good knowledge about C(and using it theoretically to > implement stacks, efficient structures and so on). However, I have > little real life experience about programming a project. I have little > experience about Window's API. > I was looking to participate in Wine development this summer. On SoC > page, the idea of Dplay was bought up. I am interested in trying hands > on that. Can anyone suggest what would be a good starting point? There are only a few important things to directplay as far as I know. The first one is find a game that runs in wine and uses it, and works reasonably well single player but not at all multiplayer or online because of the missing things (fixmes on dplay in console). After you played the game a little bit, think of a plan on how you want to tackle this problem. Have you managed to compile a git version of wine yet? Cheers, Maarten.

1 0

Questions regarding Summer of Code( and Dplay)
by Anurag Mishra 20 Mar '08

20 Mar '08

Hi, I am student at IIT Kanpur[1]. I have quite good knowledge about C and have been tracking development of Wine over a period of 6 months or so. I have good knowledge about C(and using it theoretically to implement stacks, efficient structures and so on). However, I have little real life experience about programming a project. I have little experience about Window's API. I was looking to participate in Wine development this summer. On SoC page, the idea of Dplay was bought up. I am interested in trying hands on that. Can anyone suggest what would be a good starting point? Thanks, Anurag Mishra. [1] http://www.iitk.ac.in

1 0

Proposed EM_Fontrange Patch
by James McKenzie 20 Mar '08

20 Mar '08

All: I would like to see the problems with EM_Fontrange be fixed. The attached patch is for comment/review and I would like SPECIFIC guidance on how to implement this patch as it relates to a Wine 1.0 bug (bug/issue 6254) and fixes the problem specified there. The conformance tests are already in tests/editor.c and all they involve is removing some todo_wine blocks related to this issue. The entire patch will do this. Sorry that the patch is in UNIX diff format, I could not get git to do what I wanted. The actual patch will be git format and use the daily git. Also, I would like to extend thanks to Tony Rollo, Lei Zhang and Eric Pouech for their guidance and prior fixes. I would like to thank Erich Pouech for moving some of the functionality that the original patch introduced into OLE handling. Please be BRUTAL as I feel we have a limited time period to get this in and other related issues that the patch will expose fixed before Wine 1.0. Thank you. James McKenzie

3 2