wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

w2k Explorer makes wine crash in RtlRaiseException [Virus checked]
by thomas.mertes＠t-mobile.at 30 Jan '03

30 Jan '03

Hello On my Suse 7.3 Linux (Kernel 2.4.4) I tried to start the w2k Explorer (Version 5.0 (Build 2195: Service Pack 3) using wine-20030115 with just buildin dlls. tm@penguin:~/c/w2k > winedbg explorer For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE fixme:console:SetConsoleCtrlHandler (0x404c3340,1) - no error checking or testing yet For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_AT - 0C07; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE fixme:shell:SHLWAPI_437 (0x00000004) stub fixme:process:SetProcessShutdownParameters (00000002, 00000000): partial stub. fixme:shell:FileIconInit (true) fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x406b2e08): stub fixme:ntdll:NtQueryInformationToken (0xcafe,10,0x406b2dc4,56,0x406b2dfc): stub Copied by hand from the winedbg window: 0011: sel=008f base=401145e0 limit=00000fff 32-bit rw- Backtrace: =>0 0x400c3de5 (RaiseException+0x75(code=0xc06d007f, flags=0x0, nbargs=0x1, args=0x406b2df8) [except.c:84] in libntdll.dll.so) (ebp=406b2da8) 1 0x0040de7f (explorer.exe.EntryPoint+0xc8d7 in C:\w2k\explorer.exe) (ebp=406b2df0) 2 0x0040a30f (explorer.exe.EntryPoint+0x8d67 in C:\w2k\explorer.exe) (ebp=406b2e3c) 3 0x00401621 (explorer.exe.EntryPoint+0x79 in C:\w2k\explorer.exe) (ebp=406b2e9c) 4 0x400ba038 (start_process+0x248 [process.c:564] in libntdll.dll.so) (ebp=406b2f38) 5 0x400beb3d (call_on_thread_stack+0x1d(func=0x400b9df0) [sysdeps.c112] in libntdll.dll.so) (ebp=406b2ff4) 6 0x400bece4 (SYSDEPS_CallOnStack+0x14 in libntdll.dll.so) (ebp=00000000) 0x400c3de5 (RaiseException+0x75 [except.c84] in libntdll.dll.so): leal 0xffffffa8(%ebp),%esp 84 RtlRaiseException( &record ); This seems to be an error in the wine exception handling. Is this right? What can be done about that? Greetings Thomas Mertes

4 6

Re: Patch for crash caused by XIM and make XIM functions properly (2ed)
by Alexandre Julliard 30 Jan '03

30 Jan '03

liu spider <liuspider(a)yahoo.com> writes: > ChangLog: > - controls/edit.c > new message type WM_IME_CHAR to handle XIM input. > - dlls/x11drv/keyboard.c > new function XIM_KeyEvent to process XIM key events. > - dlls/x11drv/window.c > new attributs added when creating a IC > - dlls/x11drv/x11drv_main.c > exchange the order of XCloseDisplay and XCloseIM > (otherwise it will crash when closed) > > (What's wrong with this patch? It seems to be ignored.) It's not ignored, but I'm currently working in this area, and we also have some related stuff in the Crossover tree, and I'm trying to bring everything together into a coherent whole; so it will eventually be committed in one form or another, but I have to spend a bit more time on this first. -- Alexandre Julliard julliard(a)winehq.com

2 1

japanese fonts
by Scott Jackson 30 Jan '03

30 Jan '03

My japanese fonts seem to make wine crash, even apart from that, they also don't work in wine ;-) ------------- wine output on wine hl.exe -------- ---------- cut out a couple thousand lines------- err:font:XFONT_BuildMetrics failed to load -kappa-fixed-bold-r-normal--20-190-75-75-c-100-jisx0201.1976-0 Font metrics: 92.2% done fixme:font:LFD_InitFontInfo font '-kappa-fixed-bold-r-normal--20-190-75-75-c-100-muleipa-1' has unknown registry 'muleipa' and character encoding '1' X Error of failed request: 82 Major opcode of failed request: 45 (X_OpenFont) Serial number of failed request: 10964 Current serial number in output stream: 10965 ----------------------- end --------------------- Why? I don't know. they work fine in everything else... -- "De-fault! The two sweetest words in the English language." -- Homer Simpson Get Gaim for unix or win32 systems! gaim.sourceforge.net Scott "Action" Jackson - scott_j(a)ajackson.org

1 0

Re: wrc: drop header file generation
by Alexandre Julliard 30 Jan '03

30 Jan '03

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > Not so. Looking at the header file generated by wrc, > it occured to me that it is exporting symbols that it > shouldn't be exporting in the first place. I think the > options where added long ago for compatibility with the > old resource compiler. No, it's exporting symbols to reference the resource data directly, in case you don't want to go to the trouble of parsing the resource directory and you just want the data. It's true that the header is not really useful since you can add extern statements in the code that uses the data; I think we should keep the -g option though, otherwise in asm mode you are forced to parse the resource descriptor which isn't much fun. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: some ntdll functions [Virus checked]
by thomas.mertes＠t-mobile.at 30 Jan '03

30 Jan '03

"Dmitry Timoshkov" <dmitry(a)baikal.ru> wrote: > > /************************************************************************** > > + * RtlUpperChar (NTDLL.@) > > + */ > > +CHAR WINAPI RtlUpperChar( CHAR ch ) > > +{ > > + return toupper(ch); > > +} > > It's better to avoid using locale dependent functions from an underlying > system because Wine internal code page almost always is different from OS > locale. The way to go is convert to unicode, do desired things, and convert > the result back to ansi. The implementation of RtlUpperString in rtlstr.c gave me the idea to use toupper: /************************************************************************** * RtlUpperString (NTDLL.@) */ void WINAPI RtlUpperString( STRING *dst, const STRING *src ) { unsigned int i, len = min(src->Length, dst->MaximumLength); for (i = 0; i < len; i++) dst->Buffer[i] = toupper(src->Buffer[i]); dst->Length = len; } The docu of RtlUpperChar says: RtlUpperChar returns the uppercase version of the specified character or returns the value specified by the caller for Character if the specified character cannot be converted. RtlUpperChar returns the input Character unconverted if it is the lead byte of a multibyte character or if the uppercase equivalent of Character is a double-byte character. To convert such characters, use RtlUpcaseUnicodeChar. --- End of docu -- IMHO RtlUpperChar has nothing to do for unicode chars. Is there a way to use Wine internal code page to do the conversion without converting to unicode and back? BTW: If it is not ok to use toupper several other places in wine have a problem: $ grep toupper */*.c */*/*.c */*/*/*.c | grep -v toupperW | grep -v str_toupper in wine-20030115 gives a longer list of usages of toupper. Specially msvcrt toupper seems also to use the function from libc. Greetings Thomas Mertes

2 1

RE: w2k Explorer makes wine crash in RtlRaiseException
by Robert Shearman 30 Jan '03

30 Jan '03

> To: wine-devel(a)winehq.com > From: thomas.mertes(a)t-mobile.at > Date: Wed, 29 Jan 2003 14:26:27 +0100 > Subject: w2k Explorer makes wine crash in RtlRaiseException > [Virus checked] > > Hello > > On my Suse 7.3 Linux (Kernel 2.4.4) I tried to start the > w2k Explorer (Version 5.0 (Build 2195: Service Pack 3) > using wine-20030115 with just buildin dlls. > > tm@penguin:~/c/w2k > winedbg explorer > Copied by hand from the winedbg window: > 0011: sel=008f base=401145e0 limit=00000fff 32-bit rw- > Backtrace: > =>0 0x400c3de5 (RaiseException+0x75(code=0xc06d007f, flags=0x0, > nbargs=0x1, > args=0x406b2df8) [except.c:84] in libntdll.dll.so) (ebp=406b2da8) > 1 0x0040de7f (explorer.exe.EntryPoint+0xc8d7 in C:\w2k\explorer.exe) > (ebp=406b2df0) > This seems to be an error in the wine exception handling. Is this right? > What can be done about that? No, it is not. It is a software exception raised by explorer itself (you can get the same effect by running Win98 explorer on Win2k). I have seen the same problem myself and managed to fix it, though I can't remember how. I have submitted quite a few patches specific to getting Win2k explorer running on Wine, but they haven't been accepted so far. For a start you could try --dll shlwapi=b and copying over the native shdocvw.dll and browseui.dll and running regsvr32 on them both. Try running with --dll ole32=b to see if it is a COM class that isn't registered and finally try using some of my shell32 and shlwapi patches :) Hope this helps, Rob BTW I have got explorer loaded and displaying a folder but there are no items in the folder view apart from 'Desktop'. I am still trying to work out exactly why this is.

1 0

Re: App works almost perfectly, but one MDI screen won't draw
by Dan Kegel 30 Jan '03

30 Jan '03

I've played with our MDI application a bit more, and have observed two kinds of bugs under cvs wine: First type: things not drawing, probably because of missing messages (we know the WM_NCPAINT message is AWOL, but it might be something else); 1. One of the "documents" has blank client areas (mentioned previously); these don't ever get drawn. 2. Another of the "documents" has a blank pane initially, but if you diddle around a bit, it does draw. 3. Maximizing any of the "documents" is supposed to make a minimize/maximize/close widget appear on the right-hand side of the toolbar, but it doesn't. Second type: things drawing in the wrong place: 4. The text box at the bottom of a three-panel window has its upper left corner in the right place, but its lower right corner is exactly one scrollbar width inset too far. The scrollbars are inset by that amount, too. That leaves the area where the scrollbars ought to be totally undrawn. Duane Clark is looking at the missing message problem in this and another app. Also, I'm setting up Linux and Wine for the guy who wrote our app so he can poke around and look for these problems himself; if nothing else, he can put together a minimal test case. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

4 3

Registry Files & Windows Dynamic Link Libraries
by Tom Wickline 29 Jan '03

29 Jan '03

I'm looking into updating section 3.3 of the Packagers Guide. I am not toatly sure about all the info that I have if you are aware of something out of place could you let me know. Thanks Tom ---------- Windows 95 to ME ) Registry Files /windows/system.dat /windows/user.dat /windows/win.ini The Registry consists of two local files, System.dat and User.dat. System.dat contains information on software and hardware settings and is located in the Windows folder. User.dat contains user-specified configurations for the GUI and shell. It is located in the Windows folder unless the system is set up for multiple users, in which case each user will have a separate User.dat file located in Windows\Profiles\username (where username is the name of the user). Windows Dynamic Link Libraries /windows/system ( Windows NT ) Registry Files /winnt/profiles/(username)/ntsystem.dat /winnt/profiles/(username)/ntuser.dat /windows/win.ini -- for 16-bit app compatibility If there are multiple profiles on one machine (one local, one as part of a domain, etc.), then the user directory will be the user name plus a number. Windows Dynamic Link Libraries /winnt/system -- 16-bit compat ? /winnt/system32 ( Win2K / XP ) /documents and settings/(username)/ntsystem.dat /documents and settings/(username)/ntuser.dat /windows/win.ini -- for 16-bit app compatibility If there are multiple profiles on one machine (one local, one as part of a domain, etc.), then the user directory will be the user name plus a number. Windows Dynamic Link Libraries /winnt/system -- 16-bit compat ? /winnt/system32

1 0

Re: README translated to Portuguese
by Dimitrie O. Paun 29 Jan '03

29 Jan '03

On January 24, 2003 09:04 pm, Tom Wickline wrote: > www: Uma grande quantidade de informação acerca do Wine está disponivel > pelo WineHQ em http://www.winehq.com/ : varios guias Wine, base de > dados de aplicações, localizaçao de erros. Isto é provavelmente o > melhor ponto de começo. > > FAQ: A Wine FAQ está localizada em http://www.winehq.com/FAQ > > Usenet Tu podes discutor tópicos relacionados de Wine e obter ajuda em > comp.emulators.ms-windows.wine. > > Bugs: Ajuda online está disponivel em #WineHQ on irc.freenode.net. > > IRC: O currente desenvolvimento do Wine está disponivel por CVS. > Vai a http://www.winehq.com/development/ para mais informação. > > Mailing Lists: > Há algumas mailing list para responsaveis pelo desenvolvimento > Wine; ver em http://www.winehq.com/development/#ml para mais informação. Can we please switch these www.winehq.com references to www.winehq.org? Any volunteer to update our documentation? -- Dimi.

4 4

Spanish Documentation Project
by Javier Canovas 29 Jan '03

29 Jan '03

hi, this is my first message on this mailing list... HI! I am a spanish user of wine, and I am going to translate the english documentation of wine (I manage the project). I am creating the project (cvs, bugzilla...) in Lucas (es.tldp.org) but I cant do it alone. I am meeting people to work in this, somebody can help us? Thks PD: Im sorry Shachar...

3 2

Re: some ntdll functions [Virus checked]
by thomas.mertes＠t-mobile.at 29 Jan '03

29 Jan '03

"Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > It seems the patch got wrapped. Turn off automatic wrapping in your > mail client before resending it. My mail client is Lotus Notes (company decision, not mine). Strange: Here the mail looks ok. Do you know how to turn line wrapping of in Lotus Notes. If not I will send the next patch as attatchment. Greetings Thomas Mertes

1 0

spyxx from msvc6.0 crashes on exit...
by Dan Kegel 29 Jan '03

29 Jan '03

spyxx from msvc6.0 crashes repeatably. Here's the recipe: $ wine spyxx.exe click the minimize widget on the client document click the quit widget on the app Bingo, unhandled exception. The traceback looks uninformative, so either the stack is corrupt or it's crashing in the very outer routine. Here's the output of +relay and the backtrace (ah, I love it now that the debugger just uses the terminal I started wine with!!): 08076498:Call kernel32.TlsGetValue(00000000) ret=78001322 08076498:Ret kernel32.TlsGetValue() retval=408e0f70 ret=78001322 08076498:Call kernel32.SetLastError(00000000) ret=7800132f 08076498:Ret kernel32.SetLastError() retval=00000000 ret=7800132f 08076498:Call kernel32.GetLastError() ret=78001314 08076498:Ret kernel32.GetLastError() retval=00000000 ret=78001314 08076498:Call kernel32.TlsGetValue(00000000) ret=78001322 08076498:Ret kernel32.TlsGetValue() retval=408e0f70 ret=78001322 08076498:Call kernel32.SetLastError(00000000) ret=7800132f 08076498:Ret kernel32.SetLastError() retval=00000000 ret=7800132f 08076498:Call kernel32.UnhandledExceptionFilter(40440900) ret=7800f914 wine: Unhandled exception, starting debugger... Unhandled exception: page fault on read access to 0x00000040 in 32-bit code (0x0041e214). In 32-bit mode. 0x0041e214 (spyxx.exe..text+0x1d214 in F:\spy\spyxx.exe): movl 0x40(%eax),%edi Wine-dbg> bt Backtrace: =>0 0x0041e214 (spyxx.exe..text+0x1d214 in F:\spy\spyxx.exe) (ebp=0001002f) Wine-dbg> quit WineDbg terminated on pid 8072e48 -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

Re: some ntdll functions [Virus checked]
by Dmitry Timoshkov 29 Jan '03

29 Jan '03

<thomas.mertes(a)t-mobile.at> wrote: > --- old_wine-20030115/dlls/ntdll/rtlstr.c Tue Nov 12 03:17:34 2002 > +++ new_wine-20030115/dlls/ntdll/rtlstr.c Sun Jan 26 00:03:56 2003 > @@ -516,6 +516,15 @@ > */ > > > /************************************************************************** > + * RtlUpperChar (NTDLL.@) > + */ > +CHAR WINAPI RtlUpperChar( CHAR ch ) > +{ > + return toupper(ch); > +} It's better to avoid using locale dependent functions from an underlying system because Wine internal code page almost always is different from OS locale. The way to go is convert to unicode, do desired things, and convert the result back to ansi. -- Dmitry.

1 0

Re: some ntdll functions [Virus checked]
by Dimitrie O. Paun 29 Jan '03

29 Jan '03

On January 28, 2003 04:11 am, thomas.mertes(a)t-mobile.at wrote: > +NTSTATUS WINAPI RtlIntegerToUnicodeString(ULONG value, ULONG base,const > UNICODE_STRING *str); Thomas, It seems the patch got wrapped. Turn off automatic wrapping in your mail client before resending it. -- Dimi.

1 0

Re: [dx8 patch 12]: huge cleanup + split
by Andrew John Hughes 28 Jan '03

28 Jan '03

On Sat, 25 Jan 2003 01:14:15 +0100 Raphaël Junqueira <fenix(a)club-internet.fr> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > it seems a big patch, but it's only simple cleanups/splits ;) > > it's the first and bigger patch for splitting d3d8 from the future d3d7/d3d8/d3d9 comon code > > Changelog: > - some needed cleanups for future dx9 and d3d common layer support: > - stateblocks to IDirect3DStateBlockImpl interface and moving into a new file (stateblock.c) > - shaders to IDirect3D*ShaderImpl interfaces > - splitting vshader and vshader declaration as in dx9 into 2 interfaces (for future common layer use) > - vshader declaration code to a new file (vsaderdeclaration.c) > - device calls to new interfaces (redirect stubs) > - simple texture fix for a little regression after last jason patches > - some caps code using the GL/glext.h defines (GL_VERSION_*) > > Todo: > - renaming IDirec3DDevice8Impl::StateBlock to IDirec3DDevice8Impl::startupStateBlock > - moving IDirec3DDevice8Impl d3d generic code to a "common layer" interface (maybe IDirec3DDeviceImpl) > - merging new DrawPrimitive prototype (using ddraw code) with current code > - splitting d3d8_private.h into 2 headers (d3d8 specific header, and common layer header) > - merging the hal base prototype > > Raphael > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQE+MdbYp7NA3AmQTU4RAg3DAJ94zf6kzopk2WH95+Nvq/BcH26dogCdEhf2 > UASOhtqMDLoJocMODUtZZv8= > =5SNm > -----END PGP SIGNATURE----- > Including glext.h appears to break the DLL for me. NVidia's GL headers (gl.h) already define some of the types specified in glext.h. I presume X installs glext.h, but I've not had a conflict between the two headers before. In file included from d3d8_private.h:30, from device.c:35: /usr/local/include/GL/glext.h:3142: conflicting types for `glCopyTexSubImage3DEXT' /usr/local/include/GL/gl.h:2486: previous declaration of `glCopyTexSubImage3DEXT' /usr/local/include/GL/glext.h:3566: conflicting types for `glColorSubTableEXT' /usr/local/include/GL/gl.h:2446: previous declaration of `glColorSubTableEXT' /usr/local/include/GL/glext.h:4372: conflicting types for `glTbufferMask3DFX' /usr/local/include/GL/gl.h:2984: previous declaration of `glTbufferMask3DFX' /usr/local/include/GL/glext.h:4406: conflicting types for `glTextureColorMaskSGIS' /usr/local/include/GL/gl.h:3050: previous declaration of `glTextureColorMaskSGIS' -- Andrew :-) Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html "Windows is the one true OS. MS invented the GUI. MS invented the 32 bit OS. MS is open and standard. MS loves you. We have always been at war with Oceania."

3 4

Re: Bug #540: DLL Separation of user32 from x11drv (clipboard)
by Vincent Béron 28 Jan '03

28 Jan '03

Andrew John Hughes a écrit: > License: LGPL > > Changelog: > Removes calls to CLIPBOARD_IsPresent, CLIPBOARD_EmptyCache and CLIPBOARD_GetFormatName. > Something's missing... Vincent

1 0

Guess who's back, back again... :)
by Dimitrie O. Paun 28 Jan '03

28 Jan '03

Hi folks, My ski vacation was a blast, good snow, good skiing, good people... You guys have been busy this past week judging by the number of messages I had to go through :) It's good to be back! -- Dimi.

3 2

Re: PATCH: glibc 2.3.x and errno
by Dan Kegel 28 Jan '03

28 Jan '03

Ulrich Weigand wrote: > On the other hand, maybe it would now be possible to implement Wine > threads on top of regular pthreads; at least some of the inhibitors > should be gone now, e.g. you can have thread stacks at arbitrary locations > and sizes, and there is no master thread any more ... Unfortunately I > don't quite remember the full list of problems we had with pthreads ;-/ It occurs to me that implementing Wine threads on top of pthreads would probably get rid of a few of the problems keeping us from running Wine under Valgrind. Short of getting the Stanford Checker guys interested in the Wine source tree, I can't think of an cooler way to look for stupid memory bugs in Wine... - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 2

mkdir, copy, etc.
by Jon Bright 28 Jan '03

28 Jan '03

Hi, I'm trying to build OpenSSL using Borland Builder 5 within wine. Installation of Builder has gone fine, ActiveState Perl went on after a bit of fiddling, but I've now hit a small problem. The makefile for OpenSSL attempts to run mkdir, copy, etc. - this results in Borland's make attempting to run (after trying to find copy.exe/com/bat/cmd), the command interpreter found in COMSPEC. But wcmd is only a unix command - there is no windows\system\wcmd.exe Is there already a workaround for this, or can someone point me in the right direction to look at fixing it? -- Jon Bright Lead Programmer, Silicon Circus Ltd. http://www.siliconcircus.com/

3 2

pshpack8.h:47:6: warning: #warning "8 as alignment
by Gerald Pfeifer 28 Jan '03

28 Jan '03

On all platforms I have access to (GNU/Linux, FreeBSD) I have been seeing the following for quite some time now: ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" ../../include/pshpack8.h:47:6: warning: #warning "8 as alignment is not supported" Is this really useful, resp. couldn't we avoid that somehow? Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.pfeifer.com/gerald/

1 0

Re: Windows API database
by Dave Miller 28 Jan '03

28 Jan '03

So for starters, we want something like this? It doesn't look very impressive. :) http://home.ptd.net/~compsol/imported_dll.txt However, my system is by no means a clean install of WinXP home so most of thos DLLs probably don't belong to windows. -----Original Message----- From: Dan Kegel [mailto:dank@kegel.com] Sent: Thursday, January 23, 2003 5:20 PM To: Dave Miller Cc: wine-devel(a)winehq.com Subject: Re: Windows API database Oh, ok. Cross-referencing DLL imports and exports. Yeah, that sounds like a job for a simple perl script. All you need to output is DLL name and what DLLs it imports from. Just generate a flat text file for starters, then later postprocess that into an ascii tree or graph. It's going to be a messy little graph, I bet. - Dan Dave Miller wrote: > The project I am considering is mentioned on the contributing page here: > http://fgouget.free.fr/wine/contributing-en.shtml. (Build a database of > Windows APIs and dependencies) It sounds like less work to simply create > text files containing the imports and exports, although I think the point is > partially for the results to be easily cross referenced by developers. > Hence the suggestion of a database of some kind. I've considered scanning > applications as well. If I have any success with the Windows APIs I may try > tackling that at some point as well. > > ----- Original Message ----- > From: "Dan Kegel" <dank(a)kegel.com> > To: "David Miller" <compsol(a)ptd.net> > Cc: <wine-devel(a)winehq.com> > Sent: Thursday, January 23, 2003 3:38 PM > Subject: Re: Windows API database > > > >>David Miller wrote: >> >>>I would be interested in knowing more about the goals of this project. >>>Don't consider me officially working on such a thing just yet. I have >>>no real perl experience, but would like to learn. First I'd like to >>>know more about what I'm up against. >> >>I'm not sure what project you're talking about, but I can make a few >>wild guesses... >> >> >>>1. Is there a specific set of dll's and exe's we want included in the >>>database or does it need to scan and gather a list of all dll and exe >>>files? That would suggest a clean OS install is necessary. >> >>Sure, a clean OS install is probably good. Many of the >>APIs exposed by even the clean OS install may not be >>needed if no application calls them, but it's hard to know >>that in advance. >> >>We might want to also scan applications to see what APIs >>they actually use, but that's real hard. >> >> >>>2. What information should be in the database? (OS ver, name of dll or >>>exe, name of imported dll, APIs and whether they are imported or >>>exported, etc.) >> >>Maybe use the same format as we use in the souce tree? e.g. >>scanning advapi32.dll should produce something that looks very >>much like > > http://cvs.winehq.com/cvsweb/wine/dlls/advapi32/advapi32.spec?rev=1.32 > >>>3. Will a single MySQL table do or does it need to be a relational >>>database with multiple tables? >> >>IMHO no SQL is needed. The database should be plain text >>files checked into CVS. >> >> >>>4. Anything else you can tell me about this task? >> >>Compare with other standards which provide lists of API's, for example: >>http://www.linuxbase.org/spec/ >>http://www.unix.org/ >>http://www.ecma.ch/ecma1/STAND/ECMA-234.HTM >>to get some ideas. Of course, these are formatted all fancily, >>and cover different operating systems, but the goal is similar: >>to provide an authoritative list of APIs. >>Ideally, the result could be part of a submission to a >>standards body. >>(See also http://www.kegel.com/remedy/remedy2.html#fix.info ) >>- Dan >> >>-- >>Dan Kegel >>http://www.kegel.com >>http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 >> >> >> > > > > -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 1

Re: PATCH: dlls/ole32/storage.c
by Dan Kegel 28 Jan '03

28 Jan '03

Gerald Pfeifer wrote: > - int lastblocknr; > + int lastblocknr=-1; FWIW, some compilers will complain on that line (though only us K&R vets remember why). Safer to use whitespace between the = and the -, e.g. > - int lastblocknr; > + int lastblocknr = -1; - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

building a windows API database
by Dave Miller 28 Jan '03

28 Jan '03

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 27 Jan '03

27 Jan '03

> 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 27 Jan '03

27 Jan '03

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel