- Wine-Devel - list.winehq.org

building a windows API database
by Dave Miller Jan. 28, 2003

Jan. 28, 2003

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?

1 0

Re: dlls/comcat Makefile.in version.rc include/wine wine_common_ver.rc
by John K. Hohm Jan. 27, 2003

Jan. 27, 2003

> 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?

1 0

WWN interview idea
by Brian Vincent Jan. 27, 2003

Jan. 27, 2003

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

1 0

App works almost perfectly, but one MDI screen won't draw
by Dan Kegel Jan. 27, 2003

Jan. 27, 2003

Installing my company's app is still a bear -- the only way I've found to avoid the dreaded "object reference not set" is to run with --debugmsg +ole and redirect to a file (not to the screen, and not to /dev/null). Once installed, the app runs quite well... except for one screen, which remains nearly blank. The MDI frames draw fine, but the contents (which include a hex memory dump area and a tree control) remain blank. Since there were a few richtext fixmes, I threw in native richtext dlls, and that got rid of lots of fixmes, but didn't help the display. Here's the Wine log file, passed through uniq -c: 1 fixme:win32:PE_CreateModule Security directory ignored 1 err:win32:PE_fixup_imports No implementation for WSOCK32.dll.1141 imported from blahblah.dll, setting to 0xdeadbeef 1 fixme:ole:CoRegisterMessageFilter stub 1 fixme:commdlg:GetFileName95 Flags 0x00800002 not yet implemented 1 fixme:winsock:WS_bind Setting WS_SO_REUSEADDR on socket before we binding it 2 fixme:mdi:MDIRefreshMenu partially function stub 1 fixme:dc:LockWindowUpdate ((nil)), partial stub! 3 fixme:mdi:MDIRefreshMenu partially function stub 1 fixme:winsock:WS_bind Setting WS_SO_REUSEADDR on socket before we binding it 8 fixme:mdi:MDIRefreshMenu partially function stub 1 fixme:ole:CoRegisterMessageFilter stub Grr. Nothing's really obvious to this non-windows-programmer, and the guy who wrote this program is on vacation, so I can't pick his brains. Anyone have suggestions for what to try next? Thanks, Dan p.s. FWIW, here's sort | uniq -c of the log file before I threw in the native DLLs: 1 err:win32:PE_fixup_imports No implementation for WSOCK32.dll.1141 imported from blahblah.dll, setting to 0xdeadbeef 1 fixme:dc:LockWindowUpdate ((nil)), partial stub! 9 fixme:mdi:MDIRefreshMenu partially function stub 2 fixme:ole:CoRegisterMessageFilter stub 1 fixme:richedit:RICHED32_WindowProc Unknown message 0x24 Passed to default hwnd=0x110023, wParam=00000000, lParam=40791e18 622 fixme:richedit:RICHED32_WindowProc Unknown message 0x363 Passed to default hwnd=0x110023, wParam=00000001, lParam=00000000 1 fixme:win32:PE_CreateModule Security directory ignored 2 fixme:winsock:WS_bind Setting WS_SO_REUSEADDR on socket before we binding it

5 11

qpro200.dll is its own little DLL hell
by Dan Kegel Jan. 27, 2003

Jan. 27, 2003

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. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 080f0590:Call kernel32.GetModuleHandleA(411021b0 "C:\\WINDOWS\\SYSTEM\\qpro200.dll") ret=41160128 080f0590:Ret kernel32.GetModuleHandleA() retval=00000000 ret=41160128 080f0590:Call kernel32.LoadLibraryExA(411021b0 "C:\\WINDOWS\\SYSTEM\\qpro200.dll",00000000,00000002) ret=4116013c 080f0590:Ret kernel32.LoadLibraryExA() retval=00000000 ret=4116013c 080f0590:Call kernel32.LoadLibrary16(411021b0 "C:\\WINDOWS\\SYSTEM\\qpro200.dll") ret=41160354 080f0590:CallTo16(func=02e7:00fb,ds=0417) ss:sp=0267:1530 ax=0000 bx=0000 cx=0800 dx=0000 si=0000 di=0416 bp=155a es=0417 fs=0000 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) 3 0x40075b9a (MODULE_LoadModule16+0x10e(libname=0x411021b0, implicit=0x0, lib_only=0x1) [module.c:999] in libntdll.dll.so) (ebp=41101c60) 4 0x40075e23 (LoadModule16+0xc3(name=0x411021b0, paramBlock=0xffffffff) [module.c:1084] in libntdll.dll.so) (ebp=41101c84) 5 0x400761f2 (LoadLibrary16+0x1a(libname=0x411021b0) [module.c:1245] in libntdll.dll.so) (ebp=41101c98) 6 0x4009ac27 (.L119+0x4 [relay386.c] in libntdll.dll.so) (ebp=41101cac) 7 0x4009aeb8 (RELAY_CallFrom32+0x68(ret_addr=0x41160354) [relay386.c:426] in libntdll.dll.so) (ebp=41101d30) 8 0x40a4f02d (KERNEL32.DLL.LoadLibrary16+0x5 in kernel32.dll.so) (ebp=41101d58) 9 0x41160815 (GetFileVersionInfoA+0x85(filename=0x411021b0, handle=0x0, datasize=0x3e8, data=0x40274cc8) [info.c:524] in ver.dll.so) (ebp=41101d7c) 10 0x4116155e (_fetch_versioninfo+0x3e [install.c] in ver.dll.so) (ebp=41101da0) 11 0x41161952 (VerInstallFileA+0x2fa(flags=0x2, srcfilename=0x4026297c, destfilename=0x4026270a, srcdir=0x402619ae, destdir=0x40262a1a, curdir=0x402628de, tmpfile=0x40262840, tmpfilelen=0x411022f4) [install.c:445] in ver.dll.so) (ebp=411022cc) 12 0x4115f75d (VerInstallFile16+0x31(flags=0x2, lpszSrcFilename=0x4026297c, lpszDestFilename=0x4026270a, lpszSrcDir=0x402619ae, lpszDestDir=0x40262a1a, lpszCurDir=0x402628de, lpszTmpFile=0x40262840, lpwTmpFileLen=0x40262c06) [ver16.c:80] in ver.dll.so) (ebp=411022fc) 13 0x4115f5b6 (__wine_ver_dll_CallFrom16_p_long_wtttttpp+0xa6(proc=0x4115f72c, args=0x402626e8) [ver.spec.c:138] in ver.dll.so) (ebp=4110232c) 14 0x400b9cf5 (__wine_call_from_16_long+0x8d [relay16.s] in libntdll.dll.so) (ebp=41102364) 15 0x025f:0x250a (bp=1a8c) 16 0x025f:0x1f89 (bp=1ae2) 17 0x00f7:0x0000 (bp=1b1c, far call assumed) 18 0x4009ac30 (.L120+0x7 [relay386.c] in libntdll.dll.so) (ebp=4110237c) 19 0x4009aeb8 (RELAY_CallFrom32+0x68(ret_addr=0x40888153) [relay386.c:426] in libntdll.dll.so) (ebp=41102400) 20 0x40a5336d (KERNEL32.DLL.wine_call_to_16_regs_short+0x5 in kernel32.dll.so) (ebp=4110270c) 21 0x4089f1cc (SendMessage16+0xe8(hwnd16=0x21, msg=0x720, wparam=0x0, lparam=0x0) [msg16.c:72] in user32.dll.so) (ebp=41102778) 22 0x40834b02 (__wine_user_exe_CallFrom16_p_long_wwwl+0x1a(proc=0x4089f0e4, args=0x40262caa) [user.exe.spec.c:1449] in user32.dll.so) (ebp=41102790) 23 0x400b9cf5 (__wine_call_from_16_long+0x8d [relay16.s] in libntdll.dll.so) (ebp=411027c8) 24 0x025f:0x1f4a (bp=1b7e) 25 0x00f7:0x0000 (bp=1bb8, far call assumed) 26 0x4009ac30 (.L120+0x7 [relay386.c] in libntdll.dll.so) (ebp=411027e0) 27 0x4009aeb8 (RELAY_CallFrom32+0x68(ret_addr=0x40888153) [relay386.c:426] in libntdll.dll.so) (ebp=41102864) 28 0x40a5336d (KERNEL32.DLL.wine_call_to_16_regs_short+0x5 in kernel32.dll.so) (ebp=41102b70) 29 0x4089f787 (DispatchMessage16+0xaf(msg=0x40262e70) [msg16.c:301] in user32.dll.so) (ebp=41102bb8) 30 0x408347ba (__wine_user_exe_CallFrom16_p_long_p+0x2e(proc=0x4089f6d8, args=0x40262d46) [user.exe.spec.c:1288] in user32.dll.so) (ebp=41102bc8) 31 0x400b9cf5 (__wine_call_from_16_long+0x8d [relay16.s] in libntdll.dll.so) (ebp=41102c00) 32 0x025f:0x1e15 (bp=1cfc) 33 0x025f:0x00d2 (bp=1d0a)

3 4

open_master_socket ???
by Auge Mike Jan. 27, 2003

Jan. 27, 2003

/* 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()? Thanx _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

2 1

trouble with spy++
by Dan Kegel Jan. 27, 2003

Jan. 27, 2003

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? Thanks, Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 1

Bug #416 - Missings exports in winsocks
by Andrew John Hughes Jan. 26, 2003

Jan. 26, 2003

License: LGPL Changelog: - Provides stub implementations of functions listed in Bug #416 - GetTypeByNameA and SetServiceA This were previously sent, but I received no comment on the patch and it wasn't applied. Please let me know if there's something wrong with it. -- Andrew :-) Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html

2 1

Definitions of wine Exec files
by Tom Wickline Jan. 26, 2003

Jan. 26, 2003

I am in the process of updating section 3.1. ( Wine Static and Shareable Files ) of the Packagers Guide : http://www.winehq.com/Docs/wine-pkg/pkg-components.shtml#PKG-STATIC Below is a list of what I have so far. This list is by no means done or correct . I would like to submit it here for overview. If you are aware of something that is out of place, incorrect, or just out right wrong could you please give feed back on it. This could also serve to start as a mini Wine Dictionary :)) That is not my current goal but if others think it could be of use I could spend some time on one after the Packagers Guide is updated. Tom -------------------------------------------- -- = files that are listed in this Doc but are not installed on my system. * = files are in this Doc and on my system @ = files that are on my system but not in the Doc # = files that are not in the Doc or on my System ( wineboot ) -- dosmod : Deleted as of Jan 2001. -- fnt2bdf : Discussed on Wine-Devel ( practically obsolete ) @ notepad : The windows Notepad replacement @ progman : Program Manager for WINE. @ regedit : A tool to browse/edit your regestory or for exporting a windows registory to Wine. @ regsvr32 : A program to register .DLL's and .OCX files ? @ uninstaller: A Winelib program to uninstall installed Windows programs. @ wcmd : Wine's command line interpreter @ widl : Wine IDL compiler ??? * wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries. # wineboot : A Winelib application that's executed by Wine on startup of the first wine process of a particular user. * wininit.ini processing * registry RenameFiles entries * RunServices* / RunOnce* / Run registry keys * win.ini Load= / Run= entries * StartUp folder processing -- winebootup : Now wineboot...... * winebuild : Winebuild is a tool used for Winelib applications (and by Wine itself) to allow a developer to compile a .spec file into a .spec.c file. * wineclipserv : The Wine Clipboard Server is a standalone XLib application whose purpose is to manage the X selection when Wine exits. @ wineconsole : a console program for wine,,, For running CUI executables (Windows console programs), use wineconsole instead of wine run). Not using wineconsole for CUI programs will only provide very limited console support, and your program might not function properly. * winedbg : Winedbg is the Wine built in debugger. @ winedump : A NE and PE file dumper @ winefile : A clone of the win3x filemanager @ winegcc : Wrapper for gcc to build winelib binaries * winelauncher : A wine wrapper shell script that intelligently handles wine invocation by informing the user about what's going on, among other things. To be found in tools/ directory. Use of this wrapper script instead of directly using wine is strongly encouraged, as it not only improves the user interface, but also adds important functionality to wine, such as session bootup/startup actions. If you intend to use this script, then you might want to rename the wine executable to e.g. wine.bin and winelauncher to wine. the WINECONFDIR/config file. winemaker : Winemaker is a perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do thisit will go analyze your code, fixing the issues listed above and generate autoconf-based Makefiles. @ winemine : A winmine clone "Windows Minesweeper" ??? @ winepath : Specifies the path(s) in which to search for builtin dlls and Winelib applications. * wineserver : The Wine server is critical to Wine; it is the process that coordinates all shared Windows resources. -- winesetup : This is a Tcl/Tk based front end that provides a user friendly tool to edit and configure the WINECONFDIR/config file. * wineshelllink : This shell script can be called by Wine in order to propagate Desktop icon and menu creation requests out to a GNOME or KDE (or other Window Managers). @ winewrap : Adds Visual Basic compatible scripting to Windows applications. (depends on gcc) ??? @ winhelp : For viewing windows help files * wmc : Wine Message Compiler it allows Windows message files to be compiled into a format usable by Wine. * wrc : Wine Resource Compiler. It allows Winelib programmers (and Wine itself) to compile Windows style resource files into a form usable by Wine.

2 1

bitblt fails to handle transparent bg
by Marko Kreen Jan. 26, 2003

Jan. 26, 2003

You can download the application here: http://www.smart-games.com/igowin.html wine draws the buttons background wrong. -- marko

1 0