May 2003 - Wine-devel - list.winehq.org

x11drv
by Oliver Sampson 05 May '03

05 May '03

Howdy, I was trying to do a new wine update to the latest CVS, and when cvs update gets to windows/x11drv, it just hangs. I tried deleting the windows directory and I'm using "-Pd." Is there a simple solution to this? Thanks, -- Oliver Sampson olsam(a)quickaudio.com http://www.oliversampson.com

8 8

Problem in ole32.CoCreateInstance ?
by Sylvain Petreolle 05 May '03

05 May '03

Trying to run dxdiag for testing DirectPlay , get a read at 0x0 in CoCreateInstance at line 1355 (dlls/ole32/compobj.c): 1355 hres = IClassFactory_CreateInstance(lpclf, pUnkOuter, iid, ppv); This cant work since lpcf is always 0 and this function is defined as a macro in include/unknwn.h : ./include/unknwn.h:160:#define IClassFactory_CreateInstance(p,a,b,c) (p)->lpVtbl->CreateInstance(p,a,b,c) Should we rewrite this as a function or is lpclf assumed to be non NULL ? ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 4

Ole32 16/32 questions
by Steven Edwards 05 May '03

05 May '03

Hello, I need to break some of the Win16/32 and non winapi calls apart in ole32 for our work on ReactOS and I dont know what the best method will be. Without ole32 we cant make much use of anything else so I'm going to start working on this soon. Ole16 and ole2 look like good starting points for moving code around but I would like the help of someone that has worked on this code. I will start by making a list of all of the non-win32 functions I can compile out while still leaving ole32 in a usable state, maybe this help give you a idea as to where we can move code around. Thanks Steven

1 0

MSVCRT calling convention issue
by us＠the-edmeades.demon.co.uk 05 May '03

05 May '03

While debugging a game which only installs if we use the windows msvcrt, I have identified the problem but dont know how to fix it! The problem revolves around the function MSVCRT_type_info_raw_name. This is defined as stdcall, but disassembling the windows version, it clearly shows use of a calling convention I had never heard of, 'thiscall'. According to the MSDN, thiscall is stdcall BUT the 'this' pointer on x86 machines is stored in the ECX register. How can we fix this? My thought: Change the definition to not take a ptr arg, and define a local, this as being in the ECX register, but (a) I dont know how to do this, and (b) is not a solution for winelib applications. For now I can continue having put the msvcrt.dll from another machine in, but it would be nice to solve this issue. I'd also guess it affects more than just that one function. Regards, Jason

2 4

-pthread ??
by Davide Giannotti 05 May '03

05 May '03

I noticed this bug (well.. not sure if it's a bug but it looks like) when compiling from current csv: the make depend command exits with an error like "-pthread unknown option" when processing the directory {wineroot}/dlls/winmm/winearts. I removed the -pthread flag from the Makefile and everything went fine. I'm using a strong customized redhat 8.0 with glibc 2.3.1. Do i miss something or is it an error? Another question: if i compile with nptl i can't get it to work fine. I have to use the LD_ASSUME_KERNEL=2.2.5 before configure and at runtime. bye -- Davide Giannotti ITS Planet s.n.c davide.giannotti(a)itsplanet.com www.itsplanet.com

1 0

Request: Using our spec files for snoop like debugging on known native DLLs
by Uwe Bonnes 05 May '03

05 May '03

Hallo, snoopdebugging is a great thing, but sometimes the arguments are not found and lots of exceptions are generated while wine tries to decipher the arguments. What would it take to use our spec file and build stub dlls that could print out the arguments and then jump to the native dll entries? Any takers? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Re: Mac OS X Support : Signals support
by Steven Edwards 05 May '03

05 May '03

--- Pierre d'Herbemont <stegefin(a)free.fr> wrote: > Hi, > This patch add in signal_powerpc.c of ntdll support for darwin signal. > Cheers, > > Pierre > > Modified files: > dlls/ntdll/signal_powerpc.c > > ChangeLog: > Add support for Darwin's signals. Please dont use C++ style comments. Thanks Steven __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

1 0

Callbacks while app is looping
by Mark Westcott 05 May '03

05 May '03

Hi all, I've been working on fixing the crash in 'Gens' when trying to reassign keys. The app basically does a: while (1) { IDIRECTINPUTINTERFACE::GetDeviceState(); } Until it notices a key has been pressed. DirectInput hooks onto system keyboard events with SetWindowsHookEx(WH_KEYBOARD_LL........), but while the app is doing its nasty while(1) loop, DirectInput's callback procedure never gets called. This is as far as I can get (new to wine) - any ideas anyone? I threw a test case app that illustrates the problem (btw, the WH_KEYBOARD_LL hook has the note 'should use SendMessage instead', but I don't get what this means or know if using SendMessage instead would have anything to do with fixing this problem) -------- Mark Westcott

4 4

WinZip registry patch
by Nick Brereton 04 May '03

04 May '03

Attachment is a windows registry file. Integration of this file directs WinZip to not use the Rich Edit control when displaying comments in Zip files by changing a flag that WinZip read from the registry. This means that it will work with all zip files rather than crashing out on zip files with comments. Should I post this anywhere else? eg the wine-patch list? Any comments would be appreciated. Regards, Nick Brereton

3 2

Re: How to add a new DLL?
by Gerhard W. Gruber 04 May '03

04 May '03

On Sun, 4 May 2003 00:43:13 +0200, Joerg Mayer <jmayer(a)loplof.de> wrote: >So what you have to to is add the new Makefile to configure.ac - search for >AC_CONFIG_FILES([ >Then you need to run autoconf (no arguments required but we require a version >>=2.53). After that you need to rerun ./configure <options> (or >./config-status --recheck && ./config.status). Ok. So I did add it to configure.ac and ran autoconf. I could see that it was added to configure and it also created the makefile. But when I run the makefile I always get this error: make: *** No rule to make target `../../configure', needed by `Makefile'. Stop. The Makefile.in looks like this: TOPSRCDIR = @top_srcdir@ TOPOBJDIR = ../.. SRCDIR = @srcdir@ VPATH = @srcdir@ MODULE = w95inf32.dll IMPORTS = ALTNAMES = EXTRALIBS = $(LIBUNICODE) LDDLLFLAGS = @LDDLLFLAGS@ SYMBOLFILE = $(MODULE).tmp.o C_SRCS = w95inf32_main.c @MAKE_DLL_RULES@ ### Dependencies: ------------------------------------ I took it from lzexpand and only removed the imports and altnames. Also the C_SRCS16 because I don't have 16bit files. Or are they always needed also when it is just a 32 bit DLL? Another questions is how I can create the sources from the spec file? -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

1 0