October 2004 - Wine-devel - list.winehq.org

Re: Fix regression in CreateProcess
by Mike McCormack 24 Oct '04

24 Oct '04

Eric Pouech wrote: > As Mike reported, there was a bug in CreateProcess introduced with the > runtime info handling. > This patch should take care of it. > A+ Hi Eric, This patch fixes the problem! thanks for your help! Mike

1 0

The wine user guide: an idea
by Noam Raphael 23 Oct '04

23 Oct '04

Hello, First, let me apologize: I am not familiar with wine, and I didn't make a decent research before I posted this message. I just read through the wine user guide, and though of something that could be nice for a user as lazy as I am. Since the introduction asked for comments, I comment. What I would like is a section with common use cases of wine and step-by-step instructions for each of them. It shouldn't be long - it should be mostly links to other parts of the user guide. I think of something like that: CASE: I have a working windows machine, and I would like to use the installed programs from linux. (which happens to be my situation...) WHAT TO DO: 1. Install wine (see ...) 2. Copy all files into your home dir, for example, ~/wine/C 3. Run winecfg (see ...) ... This would give the users (or at least me) a nice warm feeling that what I want to do was already done and isn't so complicated (I hope - I haven't tried it yet). Have a good week, Noam Raphael P.S. if you reply, can you please CC me? I'm not a member of wine-devel.

1 0

Re: wine devel documentation reorganization
by Mike Hearn 23 Oct '04

23 Oct '04

Spiffy. As part of my ongoing quest to make Wine hacking less scary, I've written some docs on SEH. I'll submit them to the kernel modules section when I get net access back. Just a heads up in case anybody else was thinking of covering that topic. Eric Pouech wrote: > As posted on wine-devel, here's a patch to reorganize the Wine > Developer's Guide. > It's gzip:ed because of the size (160KB). > Here's the changelog for those who don't want to open the gzip: > > A+ > Reorganizing wine-devel: > - killing the advanced part > (and moving its chapters in both developing Wine and Wine > archi parts) > - creating a new book on coding practices > from i18n.sgml, patches.sgml and porting.sgml (developing > Wine) > - creating a new book on some debugging strategies > from the old advanced book and cvs-regression.sgml > (developing Wine) > - creating a new book on the kernel modules (NTDLL & KERNEL32) > from architure.sgml / related DLLs and > address-space.sgml, console.sgml, threading.sgml > - creating a new book on the windowing > from architure.sgml / USER32 and related > - creating a new book on the graphical parts > from architure.sgml / GDI32 and related > Other changes: > - removed list of DLLs and their role (from the > modules overview) > - removed in X11 keyboard mapping section the part related > to submit a patch

2 1

Re: Fully Revised Wine User Guide Introduction
by Francois Gouget 23 Oct '04

23 Oct '04

On Fri, 22 Oct 2004, Scott Ritchie wrote: > The version 0.9 todo list (bug 85) specifies the need for a rewritten > intro to the Wine User Guide. > > This patch is that rewritten intro. It rewords things to make Wine > easier to understand for the new user, gives it a more professional > look, and removes some outdated information. Unlike my previous patch, > this one should be properly formatted, It still has awfully long lines. Are you sure you sent the right patch? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly.

1 0

Program To Check System Metrics
by William Poetra Yoga H 23 Oct '04

23 Oct '04

Hi guys (& gals), if you remember I was working on the caption buttons. I haven't submitted the patch yet (it's still in progress) and I wish to know the relations between system metrics, because I think they are very closely related to drawing on the screen, like borders, sizes, etc. I'm writing an app here, called metrics, but since this is my first Win32 program, I've encountered many problems (and solved only a few :-P). I've read bits of theForge's Win32 tutorial at www.winprog.org (I got the link from Wine), but I just can't figure out how to handle the "Refresh" and "Save" buttons properly. "Refresh" is for refreshing (regetting) the metric values, and save is for saving the values to a file. Please help me with this, and be informed that this is my first Win32 app, so bear with me... File is attached. _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

1 0

IE6 install Regression
by Mike McCormack 23 Oct '04

23 Oct '04

Hi Eric, The following patch causes the IE6 installer to crash. Thanks to Rob for figuring out which patch caused the problem very quickly :) Mike Log message: Eric Pouech <pouech-eric(a)wanadoo.fr> - msvcrt: the file descriptors are now inherited between parent/child processes - kernel32.CreateProcess: make use of the *reserved2 fields for C-RunTime data inheritance http://www.winehq.org/hypermail/wine-cvs/2004/09/0039.html ... 001f:Call kernel32.GetStartupInfoA(77adfca4) ret=500b34f6 001f:Ret kernel32.GetStartupInfoA() retval=77adfca4 ret=500b34f6 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x500b354f trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=780704e4 trace:seh:EXC_RtlRaiseException eax=00570000 ebx=77efd6e8 ecx=00000040 edx=77b004e0 esi=780704e4 edi=500c7ab8 trace:seh:EXC_RtlRaiseException ebp=77adfcec esp=77adfc98 cs=0073 ds=007b es=007b fs=0033 gs=0000 flags=00210 202 trace:seh:EXC_CallHandler calling handler at 0x77c0e240 code=c0000005 flags=0

2 3

Re: Fix for bug 824 - proper handling of REG_MULTI_SZ
by Alexandre Julliard 23 Oct '04

23 Oct '04

Randy Galbraith <randy.galbraith(a)cox.net> writes: > This proposed patch addresses the concern raised by bug 824. This > patch changes the handling of REG_MULTI_SZ from REG_SZ to REG_BINARY. Do you actually have an app that depends on this? I agree that in theory we should preserve the data exactly, but this means giving up on an easily editable registry format, so it should be done only if something really needs it. -- Alexandre Julliard julliard(a)winehq.org

3 5

Re: winapi_check and 16 bit -register functions
by Alexandre Julliard 23 Oct '04

23 Oct '04

Francois Gouget <fgouget(a)free.fr> writes: > Yesterday's winapi_check path warns about 32 bit -register functions > that are implemented by stdcall functions, but not about 16 bit > -register functions implemented by stdcall functions. The reason is > that for the latter the calling convention is set to 'pascal' or > 'pascal16' in winapi_check. However I suspect these too should be > implemented as cdecl. They could, but that will require some changes to the .spec.c code, right now the calling convention is based on the type specified in the spec file, so pascal register functions have to be WINAPI. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [dx9-12] Major change to desgin
by Alexandre Julliard 22 Oct '04

22 Oct '04

"Ann and Jason Edmeades" <us(a)the-edmeades.demon.co.uk> writes: > I have changed the design so only the Direct3D<interface><8/9> ones extend > IUnknown, and so there is no reference counting of the IWineD3D > objects. I don't think that's a good idea. If you are using COM interfaces then you need to use them the COM way, this means IWineD3D should derive from IUnknown and freeing it should be done through the Release method. If you don't want to use standard COM then don't declare COM interfaces at all, create your own mechanism. > Instead, when any Direct3D<interface><8/9> is Released to zero, then it > calls a Free method in its WineD3D equivalent interface. I also changed the > IWineD3D interface to contain, as a void *, a pointer to its 'parent' (by > which I mean the Direct3D8/9 interface) plus a function (GetParent) which > returns that pointer. This is bad too, you shouldn't use void*, you should use proper types, at the very least IUnknown*, but preferably define an IWineD3DUser interface or something like that. -- Alexandre Julliard julliard(a)winehq.org

2 4

Wine on OpenBSD
by Sascha Hanse 22 Oct '04

22 Oct '04

> >> I just tried to install the recent Wine-tarball (20041019) on my >> OpenBSD 3.6. First I had to remove kthread.c:275: the RFTHREAD flag. >> Then the'make depend && make' worked properly but the make install >> first fails with: >> >> /usr/bin/install -c serialui.dll.so >> /usr/local/lib/wine/serialui.dll.so cd `dirname setupapi/__install__` >> && make install gcc -g -O2 -o install install.c > >Your make tries to build the 'make install' target from install.c, >that won't work of course. I guess we'll have to rename that file, >unless OpenBSD make has an equivalent of the .PHONY target. > >-- >Alexandre Julliard >julliard_at_winehq.org Hi Julliard, thank you for your response. Could you tell me when or how this can be done? -- Anyone who considers arithmetical methods of producing random digits is, of course, in a state of sin. --John von Neumann (1951)

2 2