January 2003 - Wine-Devel - list.winehq.org

building a windows API database

by Dave Miller

Francois, I am interested in taking on the "build a database of windows APIs and dependencies" task. I have started work on scripts to scan a windows system and list import/export information. So far I can gather a list of dlls and run dumpbin on them, then parse imports (mostly, I think). I've started with simply printing the parsed output in three columns. The first is the DLL being scanned, the second is the DLL being imported, and the third is API imported. I am unsure of one thing. There is a 1 - 3 character hexadecimal number preceding almost every API. What is it, and should it be included in the output? Here is an example of what I am referring to: The hexadecimal number, in the third column. c:\windows\system32/atiiiexx.dll KERNEL32.dll 1AD InterlockedDecrement c:\windows\system32/atiiiexx.dll KERNEL32.dll 1B0 InterlockedIncrement c:\windows\system32/atiiiexx.dll KERNEL32.dll 126 GetModuleHandleA c:\windows\system32/atiiiexx.dll USER32.dll 2AC wsprintfA c:\windows\system32/atiiiexx.dll USER32.dll 1DE PostMessageA c:\windows\system32/atiiiexx.dll USER32.dll 15E GetWindowTextA Also I could use some direction on what the goals of this task are. Do we want text output? That makes a very large text file when listing all imported/exported APIs. Do we actually want a database for this?

Jan. 28, 2003

Re: dlls/comcat Makefile.in version.rc include/wine wine_common_ver.rc

by John K. Hohm

> Changelog: > John K. Hohm <jhohm(a)acm.org> > Added optional OLESelfRegister to wine_common_ver.rc, used in dlls/comcat. This apparently was not applied; was it flawed, or simply missed?

Jan. 27, 2003

WWN interview idea

by Brian Vincent

For a while now I've kicked around adding interviews to the Wine Weekly News. Basically how it would work is I'll email a bunch of you some questions, you can answer as many as you'd like, and I'll include the interview in the Wine Weekly News. More than likely there will be a bit of an email exchange so I can put some detail into it. (For instance, I never liked the interviews that were done on kde.org but the ones on kerneltrap.org are excellent.) What I'd like to do is get about ten of them completed first and publish them one at a time. They'll focus mostly on your involvement with Wine and the parts you've worked on. With a little luck they'll get into some of the technical details that someone wouldn't normally see discussed on the mailing list. I guess I'm more interested to hear from you if you _don't_ want to take part. Otherwise I'll assume you're a target. If you have any questions/comments/gripes or any other suggestions for the Wine Weekly News let me know. -Brian vinn(a)theshell.com

Jan. 27, 2003

Re: Missing WM_NCPAINT (was: Re: App works almost perfectly, but one MDI screen won't draw)

by Duane Clark

Dan Kegel wrote: > > That sounds like the problem my app is having, too. Now that I > have Spyxx.exe running, I see that a WM_NCPAINT message is sent > to that window in WinMe but not in Wine. NC messages affect the border that Windows (and Wine) add to a window. The border that you use to stretch or move the window, and that contains the window title. Since your problem is within the window client (content) area, it is probably unrelated. > Interestingly, a WM_NCPAINT *does* get sent to the parent > window ("AfxFrameOrView42") in wine. Is it supposed to > percolate down from that to its child area? > - Dan Generally, no they won't percolate. I am most of the way through a fix for the WM_NCPAINT messages in MDI apps, so that will probably come out this coming weekend. It turned out that finding where the fix went was fairly easy, but actually implementing it was slightly trickier than I expected.

Jan. 27, 2003

Re: qpro200.dll is its own little DLL hell

by Dmitry Timoshkov

"Dan Kegel" <dank(a)kegel.com> wrote: > The VB app I'm trying to bring up (Yardi) installs qpro200.dll. > Amusingly, their setup utility crashes on startup if > you run it again, in that dll's init routine. > Deleting it seems to fix things. Good old DLL hell. > Partial relay and traceback attached in case anyone's curious. > 080f0590:Call KERNEL.4: LOCALINIT(0417,0000,0800) ret=02e7:0120 ds=0417 > 080f0590:Ret KERNEL.4: LOCALINIT() retval=0001 ret=02e7:0120 ds=0417 > wine: Unhandled exception, starting debugger... > ... > Unhandled exception: privileged instruction in 16-bit code (02ef:00ab). > In 16-bit mode. > 0x02ef:0x00ab: ljmp *%ss:0x0020 > Wine-dbg>Backtrace: > =>0 0x02ef:0x00ab (bp=1528) > 1 0x02ef:0x0127 (bp=155a) > 2 0x4007951b (NE_InitDLL+0x113(pModule=0x402750b8) [segment.c:680] in libntdll.dll.so) (ebp=41101c30) Having a bit of spare time I have a found a copy of qpro200.dll using an Internet search. Although apparently it's not exactly the same version as yours (since it crashes at different address), but it crashes at the same address under both Wine and Windows 2000 somewhere in its LibMain and disassembly of the very first command looks exactly like in your trace. So, for me it looks like a bug in this DLL. I'm using simple 16-bit DLL loader written for my own needs which just does LoadLibrary/FreeLibrary. My copy of qpro200.dll has following strings in its VersionInfo record: CompanyName Crescent Software, Inc. FileDescription QuickPak Professional DLL FileVersion 3.24.000 InternalName QPRO200 LegalCopyright Copyrightй Crescent Software, Inc. 1991-1994 LegalTrademarks QuickPakо is a trademark of Crescent Software Inc. OriginalFilename QPRO200.DLL ProductName QuickPak Professional for Windows ProductVersion 3.24.000 I can send you my simple loader program if you wish to try it yourself. -- Dmitry.

Jan. 27, 2003

Re: Packagers Guide Update #5

by Tom Wickline

Tony Lambregts wrote: > LOL. So it seems that by default I am the current docbook "expert". > That's almost scary. Well you know alot more about this than I do :) > My vote (for what its worth ) if <wineconf> is not needed lets just get > rid of it. > Would # [wineconf] work ? If not I guess I would vote to remove it as well..... if it serves no purpose. Tom

Jan. 27, 2003

Re: Packagers Guide Update #5

by Tony Lambregts

Vincent Béron wrote: >Le dim 26/01/2003 à 15:38, Tony Lambregts a écrit : > > >>If we cannot replace the <> around wineconf the burning question for me >>is what is the directive to tell the make process ignore <wineconfig> >>Does anyone have an idea? Vincent...? >> >> > >Define it somewhere as a noop? I'm not familiar at all with writing >docbook, I only played with the executable tools. > > > LOL. So it seems that by default I am the current docbook "expert". That's almost scary. Oh well... This leaves us with two options. Both options require that we modifiy the config file. Option 1: Since AFAICT <wineconfig> is just a comment that serves no real purpose we just get rid of it. Option 2: wrap the config file in <![CDATA[ .... ]]> <! [CDATA[ is a directive to ignore all tags untill ]]>. Unfortunately this needs to be embeded in the document that uses it or it won't work. So we have two ways of doing this. one way is to modify the config file so that they are in it (ugly) or we use a configure script to wrap <![CDATA[ and ]]> around the config and create a new file. (This is not something I know how to do, but if it is nessesary I am willing to learn) My vote (for what its worth ) if <wineconf> is not needed lets just get rid of it. -- Tony Lambregts

Jan. 27, 2003

Re: open_master_socket ???

by Marcus Meissner

On Mon, Jan 27, 2003 at 01:00:46AM +0400, Auge Mike wrote: > > /* open the master server socket and start waiting for new clients */ > open_master_socket > > Who can explain for me the task of the above function in more words? > > Why we need to do fork() inside this function, although the parent of this > process will terminate after the child do call acquire_lock()? To daemonize the server process (detach it from the current session group), so it is not affect by signals or similar from it. See 'man setsid'. Ciao, Marcus

Jan. 27, 2003

Missing WM_NCPAINT (was: Re: App works almost perfectly, but one MDI screen won't draw)

by Dan Kegel

Duane Clark wrote: > Mike Hearn wrote: > >> Could you explain this to me please? I tried Kaleidograph and started >> looking at why the "Demo version only" dialog that pops up at the >> beginning wasn't blanking the background properly, which I decided was >> because the app didn't call BeginPaint but I am very much a novice. >> >> So, if you could explain how you tracked down these bugs I'd very much >> appreciate it! > > I ran the app under WinNT and Wine, and compared the messages generated > using SPY++. There are non-client (border) and background fill messages > missing. So then it becomes a matter of figuring out where they should > be generated. That sounds like the problem my app is having, too. Now that I have Spyxx.exe running, I see that a WM_NCPAINT message is sent to that window in WinMe but not in Wine. Interestingly, a WM_NCPAINT *does* get sent to the parent window ("AfxFrameOrView42") in wine. Is it supposed to percolate down from that to its child area? - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 27, 2003

Re: trouble with spy++

by Dan Kegel

Dan Kegel wrote: > I am trying out spy++, and it works great under Windows; > both the version from MSVC4.0 and MSVC6.0 can display > the Windows Messages apps receive on, say, getting focus. > > Unfortunately, spy++ doesn't seem to do diddly under > Wine. I see no messages, no matter what window I ask for > details about, or what I do to that window. > > Is there some trick to running spy++ under Wine? Found my problem. spy++ works a lot better with current cvs than with wine20020605! - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 27, 2003