- wine-devel - winehq.org

IPersistFile::Load() broken ? + WineLib queries
by Subhobroto Sinha 22 Aug '03

22 Aug '03

Respected members of the forum, I have a few queries, which I have tabulated under: First: (1) With Windows apps doing smoothly on Wine, I had thought of creating a little program which would resolve Windows shortcut (.lnk) files. The program behaved perfectly with NO glitches whatsoever with the Wine package of <20030217-23> which came with my SuSE 8.2 as RPM. I had also downloaded the Wine20030408 tarball, which I duly patched upto v20030813 (the latest), removed the installed RPM package and wineinstalled the source for Wine20030813. (The improvements made was immediately apparent, and I could run Norton 2000 Update Agent as well as install my own .msi packages !) However, my program (which resolved shortcuts) failed to work anymore ! Previously, to compile the source using WineLib(from Wine<20030217-23>) I had to make the following changes in my source code: (1) Replace IShellLink with IShellLinkA (2) Include the header "shlguid.h" With the latest WineLib(from Wine20030813), I did NOT have to make ANY changes to the original source however, but though the source compiled without any issues, it failed at the IPersistFile::Load() call ! To make debugging easier for you folks, I have prepared a ZIP Package called "WineShellDriverPak.zip" which contains the following software: (1) The source code "WineShellDriver.cpp" . (This compiles on VC6 AND WineLib without ANY modification) (2) The VC6 compiled EXE file "WineShellDriver.EXE". To make this program work, just pass the .lnk filename as command line arg, and if successful, it will write out the resolved path in a text file called "WineWorksResolvedPath.dat" (This ALSO failed to work under Wine20030813) (3) The previous "working" (it does NOT work anymore..) WineLib form ("linkresolve.exe.so") of this code. This had been compiled using Wine<20030217-23> which came with SuSE 8.2. It used to work fine. (4) A shortcut (Notepad.lnk) file for testing. It should resolve to "C:\WINNT\notepad.exe" Is it due to a BUG in the latest release, or did I do something wrong ? Second: (2) How do I REDUCE the size of WineLib compiled apps ? Those source code which compile to ~35KB using VC6, compile to ~900KB using WineLib. Currently, I have to "strip" the WineLib compiled apps, but often, this breaks them ! Any suggestions ? (3) How do I log the output to a file say "Winelog.log" of a command like: "$ wine --debugmsg +all winelibapp.exe.so -- commandline args" Redirection (>>) or pipes (|less) only captues the output given by "winelibapp.exe.so" and NOT that given by Wine. (I currently run Wine from the commandline using XTerm) Thank you for your time. Please keep up the good work ! Cheers Subhobroto Sinha ---------------------------- Help us to free ourselves! __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

Re: [Foxgui-users]Re: Wine fixes (1)
by Dimitrie O. Paun 22 Aug '03

22 Aug '03

On August 21, 2003 12:07 am, jeroen wrote: > > Ha! Well, I can't say that I disagree with you; however, if you're > actually shipping applications for Windows, you'd better test on the > real thing..... One thing the emulation won't tell you is whether > any oddball device driver issues crop up. This particularly happens > with OpenGL. I have had to add special directives to avoid hardware > accelerated OpenGL on Windows so that broken drivers may be circumvented. > > Interactions with other applications also must be tested; for example, > clipboard support. You will discover the weirdest things... It's a nice compliment (thank you!) to assume that Wine is such a good implementation of the Win32 API that one would assume to do no testing on Windows :) Unfortunately, we haven't gone that far (yet ;) ). Wine is good enough at the moment to allow for some development, but you will definitely run into problems, and you _will_ need to test the result on Windows, as you say. But regardless of utility, I still maintain a Wine port would be cool :) -- Dimi.

1 0

Re: PATCH - winnt.h move non-standard language IDs to wine/port.h
by Jonathan Wilson 22 Aug '03

22 Aug '03

Looks good. This should enable apps like notepad to build out of the box on win32 with MingW or VC headers assuming port.h is copied over.

1 0

IPersistFile::Load() broken ? + WineLib queries
by Subhobroto Sinha 21 Aug '03

21 Aug '03

Respected members of the forum, I have a few queries, which I have tabulated under: First: (1) With Windows apps doing smoothly on Wine, I had thought of creating a little program which would resolve Windows shortcut (.lnk) files. The program behaved perfectly with NO glitches whatsoever with the Wine package of <20030217-23> which came with my SuSE 8.2 as RPM. I had also downloaded the Wine20030408 tarball, which I duly patched upto v20030813 (the latest), removed the installed RPM package and wineinstalled the source for Wine20030813. (The improvements made was immediately apparent, and I could run Norton 2000 Update Agent as well as install my own .msi packages !) However, my program (which resolved shortcuts) failed to work anymore ! Previously, to compile the source using WineLib(from Wine<20030217-23>) I had to make the following changes in my source code: (1) Replace IShellLink with IShellLinkA (2) Include the header "shlguid.h" With the latest WineLib(from Wine20030813), I did NOT have to make ANY changes to the original source however, but though the source compiled without any issues, it failed at the IPersistFile::Load() call ! To make debugging easier for you folks, I have prepared a ZIP Package called "WineShellDriverPak.zip" which contains the following software: (1) The source code "WineShellDriver.cpp" . (This compiles on VC6 AND WineLib without ANY modification) (2) The VC6 compiled EXE file "WineShellDriver.EXE". To make this program work, just pass the .lnk filename as command line arg, and if successful, it will write out the resolved path in a text file called "WineWorksResolvedPath.dat" (This ALSO failed to work under Wine20030813) (3) The previous "working" (it does NOT work anymore..) WineLib form ("linkresolve.exe.so") of this code. This had been compiled using Wine<20030217-23> which came with SuSE 8.2. It used to work fine. (4) A shortcut (Notepad.lnk) file for testing. It should resolve to "C:\WINNT\notepad.exe" Is it due to a BUG in the latest release, or did I do something wrong ? Second: (2) How do I REDUCE the size of WineLib compiled apps ? Those source code which compile to ~35KB using VC6, compile to ~900KB using WineLib. Currently, I have to "strip" the WineLib compiled apps, but often, this breaks them ! Any suggestions ? (3) How do I log the output to a file say "Winelog.log" of a command like: "$ wine --debugmsg +all winelibapp.exe.so -- commandline args" Redirection (>>) or pipes (|less) only captues the output given by "winelibapp.exe.so" and NOT that given by Wine. (I currently run Wine from the commandline using XTerm) Thank you for your time. Please keep up the good work ! Cheers Subhobroto Sinha ---------------------------- Help us to free ourselves! __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Can someone take a look at msvcmaker for me?
by Steven Edwards 21 Aug '03

21 Aug '03

I have tried using MSYS perl and ActiveState perl and both give me the following error: isolation@PH33R /g/src/wine-dev/wine $ ./tools/winapi/msvcmaker Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 52. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 116. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 440. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 1031. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 1091. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 1141. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 1180. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 1217. Global symbol "$wine_dir" requires explicit package name at ./tools/winapi/msvcm aker line 1234. Execution of ./tools/winapi/msvcmaker aborted due to compilation errors. isolation@PH33R /g/src/wine-dev/wine

1 0

Re: patch 6
by puoti＠inwind.it 21 Aug '03

21 Aug '03

My email will never change. My email provider is the biggest in Italy, and it's very improbable that it will ever close, and even if I don't use it as an ISP any more, I will never change my email until I can use my current one. Of course, if you don't want email addresses in the source, just ignore that part of the patch.

1 0

Re: Build broken due to -lpthread
by Gerald Pfeifer 21 Aug '03

21 Aug '03

On Thu, 21 Aug 2003, Ulrich Spoerlein wrote: >> So perhaps we ought to use -lc_r instead of -lc and omit -lpthread on >> FreeBSD (or use -pthread)? > The "best" solution IMHO would be to have configure look for -lpthread > and put the value into @PTHREAD_LIBS@. Then the Wine port can just > s/-lpthread/${PTHREAD_LIBS}/g configure in the post-patch-target Please keep in mind that Wine should build as is (in CVS) without any FreeBSD-specific changes. I have been investing a lot of time and effort to reach that state and would like to keep it that way (and Alexandre agrees with that, as far as I know). As far as I can see, the ideal approach might be: o Check whether -lphtread exits/works and use it only, if it does. o Check whether -lc_r exists/works, and if it does, use that instead of -lc. These two are independent, and should work in general, that is, portably. Gerald -- Gerald Pfeifer (Jerry) gerald(a)pfeifer.com http://www.pfeifer.com/gerald/

1 0

Re: patch 6
by Alexandre Julliard 21 Aug '03

21 Aug '03

"puoti\(a)inwind\.it" <puoti(a)inwind.it> writes: > Added my email next to my name in cmdlgtst /It.rc It's better to avoid putting email addresses in source files, they quickly become obsolete and nobody ever bothers to update them. Just put your name there, and people who want to mail you can look up your most recent address in the Changelog. -- Alexandre Julliard julliard(a)winehq.com

1 0

RFC: evolution of file management
by Eric Pouech 21 Aug '03

21 Aug '03

in the process of separating ntdll from kernel32, one of the next hurdle if the implementation of NtCreateFile. Since it's rather a core API, some thoughts are needed. Moreover, there are a few shortcomings in current file handling we might want to address. The goal of this small RFC is to: 1/ gather all known shortcomings of current file implementation 2/ propose some solutions and roadmaps for the implementation feel free to add your own remarks to these lists. 1/ shortcomings --------------- 1.1) no dynamicity in DOS drive management: user should be able, in his/her session(1), to either change the mapping of a DOS drive letter, or mount a SMB share somewhere...) 1.2) mounting should be done session wide and not process wide, and of course shared across processes 1.3) ntdll and kernel32 are not separated regarding file management 1.4) devices (vxd and DOS) management is still a hack 1.5) it may be necessary to introduce a notion of filesystem for some operations (open, read, write, seek, close, dir_enum, ioctl) in order to support several FS (unix, smb...) 1.6) poor management of ejectable devices 1.7) short/long file name conversion should be consistent (across several processes in the same session, across several sessions) Note: (1) a session is linked to a running instance of the wineserver 2/ proposal ----------- 2.1 "path gates" (target: 1.1, 1.2, 1.3/partly, 1.4/partly, 1.6/partly) all file names will be handled using the NT-style: + DOS paths (C:\foo\bar) into \??\C:\foo\bar + network paths (\\station\foo\bar) into \??\UNC\station\foo\bar + DOS device names (CON) into \??\CON + NT device names (\\.\PhysicalDrive0) into \??\PhysicalDrive0 + a VXD ?? (normally \\.\VFD) into \??\VFD the device concept will disappear and be replaced by a "path gate": in NT-Win32 name space, point where to convert from a NT-path to a Unix-path for example, assuming we have created a path-gate from \\??\c: to /mnt/windows, the NT-path \\??\c:\foo\bar will be transformed into the unix-path /mnt/windows/foo/bar the path-gate will hold the current options that the device currently does (case sensivity, fixed/removable...) path-gates will be stored in the server (they are session wide) management of VxD and devices could benefit from it: they could be path gates pointing to them selves (or nothing ?) 2.2 FS (target: 1.4/partly, 1.5/partly, 1.6/partly) I'm still wondering if we really need a FS (even a very simplistic one) in Wine 2.3 short/long file names (target 1.7) since current short file name management seems satisfactory, there's no need IMO to move short/long names conversion in the server -- Eric Pouech

5 8

GetLastError strangeness with FindClose
by Alex Pasadyn 21 Aug '03

21 Aug '03

Hi all, I observed a program that was bailing out with an absolutely baffling error message. I have traced it to its cause, but now I'm stuck. Basically, it was telling me that it had an error in FindNextFile of "success". I did a relay trace and found out that it was calling FindFirstFile, FindNextFile a bunch of times, FindClose, and then GetLastError. So, I put together a little test: #include <windows.h> #include <stdio.h> WIN32_FIND_DATA fd; HANDLE h; int main(int argc, char *argv[]) { h = FindFirstFile("*", &fd); if (h == INVALID_HANDLE_VALUE) { printf("Error finding first file: %d\n", GetLastError()); return 1; } printf("found file: %s\n", fd.cFileName); while (FindNextFile(h, &fd)) { printf("found file: %s\n", fd.cFileName); } FindClose(h); switch (GetLastError()) { case ERROR_NO_MORE_FILES: printf("all done!\n"); return 0; default: printf("Error finding next file: %d\n", GetLastError()); return 1; } return 1; } Now, on Windows, the output is: G:\testfnf>testfnf found file: . found file: .. found file: testfnf.cpp found file: testfnf.exe all done! And with Wine the output is: [ajp@toaster testfnf]$ ~/wine/wine testfnf.exe found file: . found file: .. found file: testfnf.cpp found file: testfnf.exe Error finding next file: 0 So, it looks like somewhere in FindClose Wine is resetting the last error. I started digging through there and the functions it calls but I was unable to find where it was getting reset. Can anyone shed some light on this? Is there any way to break on that value changing? Thanks, -ajp

6 10

Directx 8.1 sound bug
by puoti＠inwind.it 21 Aug '03

21 Aug '03

Anybody intrested may want to look at this http://bugs.winehq.com/show_bug.cgi?id=1670

1 0

Re: FAQ: When will Wine integrate an x86 CPU emulator?
by Mike Hearn 21 Aug '03

21 Aug '03

On Wed, 2003-08-20 at 21:42, Francois Gouget wrote: > + environment, Wine should only need minimal modifications. What > + performance you loose due to Wine running inside the emulator > + rather than natively, you gain in complexity inside of Wine. s/loose/lose/ - I'm not sure the second part of that sentance makes sense. What you lose in performance, you gain in complexity inside of wine? Shouldn't that be simplicity? Random tangent: at some point somebody needs to write an "msinterop" program that simply looks at the environment, the type of EXE file and then invokes: 1) Wine 2) Mono 3) Wine in QEMU 4) Wine and Mono in QEMU 5) Offers to download and install these programs if need be. Especially as we'll start seeing more and more programs that are partly unmanaged and partly managed (.net) code floating about, it's going to be harder to figure out what programs you need in order to make the exe run.

1 0

Re: stub for (undocumented) SHCreateLinks
by Dmitry Timoshkov 21 Aug '03

21 Aug '03

"Mike McCormack" <mike(a)codeweavers.com> wrote: > + 172 stdcall SHCreateLinks(long long long long long) > +HRESULT WINAPI SHCreateLinks( HWND hWnd, LPCSTR lpszDir, LPDATAOBJECT lpDataObject, > + UINT uFlags, LPITEMIDLIST *lppidlLinks) Then the spec entry should be 172 stdcall SHCreateLinks(long ptr ptr long ptr) -- Dmitry.

2 2

Re: patch 6
by Tom 21 Aug '03

21 Aug '03

puotiinwindit wrote: >this patch is licensed under the LGPL only (patch 5 is also LGPL only). >ChangeLog >Added Italian support to avifil32.dll >Fixed a typo in the english rc file in avifil32.dll > > > > > > Hi, umm.. the patches? :) Tom

1 0

Re: spec file syntax and automated generation
by Jon Griffiths 21 Aug '03

21 Aug '03

Hi Martin, > thanks for your info. I just wanted to forward my problem I posted on > wine-users - I do not know if wine-devel is the right place for this, so wine-devel is the place for any development issues, including problems with Winelib. Since someone may have the same problem(s) in the future, I'm also sending this to wine-devel (it serves as an issues archive for common problems). >I am currently having trouble building the DLLs of an application ported >from Win32 to Winelib - compiling, thanks to some hints from Dimi O. >Paun, now works fine, only(?) the final link __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Re: PATCH - some build fixes for w32api headers
by Alexandre Julliard 21 Aug '03

21 Aug '03

Steven Edwards <steven_ed4153(a)yahoo.com> writes: > Changelog: Fixes for building with w32api headers on Mingw Why do you need to add stdarg.h everywhere? AFAICS it should be already included by the headers that require it. As a general note, it's a very good thing to test with other headers, but make sure that the problem is really on the Wine side before making changes. Being compatible with w32api is not a goal in itself for Wine, we have to be compatible with Microsoft; and if the Wine code works with the Microsoft headers but not with w32api then the bug is in w32api and should be fixed there. And in the case where the bug is really in Wine, this means there's an incompatibility in the Wine headers, since it builds fine with them and it shouldn't. So this means we have to fix the Wine headers too, not only the C files. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: Small spanish keyboard fix
by Dmitry Timoshkov 21 Aug '03

21 Aug '03

"José Manuel Ferrer Ortiz" <jmfo1982(a)yahoo.es> wrote: > Hi again, attached you have a patch to the spanish > keyboard that adds support to write the Euro sign > using <Alt-GR> + <E>, as seen in newer spanish > keyboards. XFree86 4.3.0 has no this, which however should not prevent the Euro sign to work. Moreover, XFree86 project tends to leave only two characters per keysym for all keyboard layouts, not to add new ones. -- Dmitry.

1 0

uClibc and wine
by Felipe Wilhelms Damasio 20 Aug '03

20 Aug '03

Hi, I couldn't compile wine using the latest (0.9.20) version of uClibc. I installed the devel stuff and am using the /usr/i386-uClibc/gcc on my path, and then I get: gcc -c -I. -I. -I../include -I../include -g -O2 -Wall -mpreferred-stack-boundary=2 -gstabs+ -fPIC -D__WINESRC__ -DDLLDIR="\"/mnt/usr/lib/wine\"" -D_REENTRANT -o port.o port.c port.c:597: warning: type defaults to `int' in declaration of `wchar_t' port.c:597: syntax error before '*' token port.c: In function `wine_rewrite_s4tos2': port.c:601: `str4' undeclared (first use in this function) port.c:601: (Each undeclared identifier is reported only once port.c:601: for each function it appears in.) make[1]: *** [port.o] Error 1 make[1]: Leaving directory `/home/felipewd/elipse/cvs/wine-20030115/library' make: *** [library] Error 2 If I change my path to use the default gcc location, it compiles fine. Does anybody have any ideas? Thanks in advance, Felipe

2 1

Re: winegcc
by puoti＠inwind.it 20 Aug '03

20 Aug '03

I'm trying to compile the bidi test progam posted on this list by Shachar Shemesh, you can find his post and his program here: http://www.winehq.org/hypermail/wine-devel/2003/08/0175.html this mail also got to wine-users, sorry about that.

2 1

Re: FAQ: Will there be a Windows version of Wine?
by Steven Edwards 20 Aug '03

20 Aug '03

Thanks Francois, I have been meaning to update some of the docs to answer these questions for a while. You put it much better and more to the point then I would have =). Steven --- Francois Gouget <fgouget(a)free.fr> wrote: > > > Changelog: > > * documentation/faq.sgml > > Tweak 'Will there be a Windows version of Wine?': > - Add a pointer to the MinGW project > - Fix the ReactOS case > - Explain the rational behind these porting projects > > > Index: documentation/faq.sgml > =================================================================== > RCS file: /home/wine/wine/documentation/faq.sgml,v > retrieving revision 1.13 > diff -u -r1.13 faq.sgml > --- documentation/faq.sgml 28 Jul 2003 19:06:10 -0000 1.13 > +++ documentation/faq.sgml 20 Aug 2003 20:24:25 -0000 > @@ -485,19 +575,26 @@ > </question> > <answer> > <para> > - Some people are working on getting Wine code to compile on Windows. > + Some people are working on getting Wine code to compile on Windows > + using one of the following projects as a basis: > </para> > <itemizedlist spacing="compact"> > <listitem> > <para> > - Cygwin (<ulink url="http:/www.cygwin.com"> > - http://www.cygwin.com/</ulink>) > + Cygwin > + (<ulink url="http:/www.cygwin.com/">http://www.cygwin.com</>) > + </para> > + </listitem> > + <listitem> > + <para> > + MinGW > + (<ulink url="http:/www.mingw.org/">http://www.mingw.org</>) > </para> > </listitem> > <listitem> > <para> > - Reactos (<ulink url="http://www.reactos.com/"> > - http://www.reactos.com/</ulink>) > + ReactOS > + (<ulink url="http://www.reactos.com/">http://www.reactos.com</>) > </para> > </listitem> > </itemizedlist> > @@ -505,9 +602,21 @@ > There's some progress, so a Wine version that's usable on Windows > might be available at some time. > </para> > + <para> > + Part of the rational for these projects is to find out areas where > + Wine portability is lacking. This is especially true of the > + ReactOS project which is a reimplementation of the Windows kernel > + and should thus be able to reuse most of Wine dlls. > + </para> > + <para> > + Another reason for pursuing these projects is to be able to > + replace a single Windows dll with its Wine counterpart. Besides > + being a good test for the Wine dll, this lets us detect cases where > + we made incorrect assumptions about how the dlls interact. > + </para> > </answer> > </qandaentry> > - > + > </qandadiv> > <qandadiv id="What-do-I-need-in-order-to-use-Wine"> > <title>What do I need in order to use Wine?</title> > > > > -- > Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ > It really galls me that most of the computer power in the world > is wasted on screen savers. > Chris Caldwell from the GIMPS project > http://www.mersenne.org/prime.htm > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

PATCH try 2 - build libwine_unicode with w32api headers
by Steven Edwards 20 Aug '03

20 Aug '03

Ok now with clean w32api headers from CVS we can build unicode. This shouldnt break cross compiling or the *nix build but if it does please let me know. Also you can change WINVER >= 0x0500 to whatever as long as it is higher. Thanks Steven Changelog: Fix building libwine_unicode with w32api headers. Index: Makefile.in =================================================================== RCS file: /home/wine/wine/libs/unicode/Makefile.in,v retrieving revision 1.5 diff -u -r1.5 Makefile.in --- Makefile.in 27 Jun 2003 19:02:23 -0000 1.5 +++ Makefile.in 20 Aug 2003 06:13:25 -0000 @@ -4,7 +4,7 @@ VPATH = @srcdir@ LIBRARY = wine_unicode SOVERSION = 1 -EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT +EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT -DWINVER=0x0500 CODEPAGES = \ 037 \ Index: unicode.h =================================================================== RCS file: /home/wine/wine/include/wine/unicode.h,v retrieving revision 1.20 diff -u -r1.20 unicode.h --- unicode.h 27 Jun 2003 19:02:23 -0000 1.20 +++ unicode.h 20 Aug 2003 07:36:07 -0000 @@ -24,6 +24,7 @@ #include <stdarg.h> #include "windef.h" +#include "winbase.h" #include "winnls.h" /* code page info common to SBCS and DBCS */ __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 2

Re: spec file syntax and automated generation
by Jon Griffiths 20 Aug '03

20 Aug '03

Hi, <disclaimer> I havent read the wine-user posts.... >1. The winebuild manpage only mentions ptr, str, wstr, long and double >as valid Win32 function argument size information - is the amount and >kind of symbols really important, or is it just the amount of used stack >space? the type is used for dumping of parameters so its good to have it right. >I am not too familiar with assembler, but I would assume the first is >right, since two arguments are pushed on the stack, each using 32bit. Correct. Logical types are irrelevant, only the physical size matters. % __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

is anyone running windows 95, windows 98, windows ME or windows 2003?
by Jonathan Wilson 20 Aug '03

20 Aug '03

If so, I need you to run some kind of PE dumper that can dump exports (such as dumpbin from MS with the /exports switch on user32.dll and gdi32.dll from your version and send me the results, along with details of which version of windows you are running. I want this info because I am compiling a list of the different versions of windows and which functions are exported by user32.dll and gdi32.dll in each version.

4 3

Re: [Foxgui-users]Re: Wine fixes (1)
by Dimitrie O. Paun 20 Aug '03

20 Aug '03

On 20 Aug 2003, Doug Henry wrote: > > Added this one too. [As to why you'd want to run FOX under Wine while it > > runs natively under X11, I don't know....] > > > > If you cross-compile for windows under linux, it is useful to test under > wine. Its more convenient than rebooting or going to another machine > just for simple testing. Top 10 reasons you want Fox ported to Wine: 10. Windows sux 9. Microsoft is evil 8. Test windows features without rebooting (as Doug mentioned) 7. Keep development on Linux 6. Run valgrind on the Windows port 5. Make sure the Win32 part is portable to multiple implementations 4. Help find missing features/problems/etc. in Wine 3. Some people may prefer the Wine widgets to the GTK+ ones 2. wxWindows is already ported to Wine, Fox needs that too! ;) and the number one reason is: 1. It is just cool!!! (what geek can resist this sort of virtualization? :)) -- Dimi.

1 0

Re: winegcc
by puoti＠inwind.it 20 Aug '03

20 Aug '03

I've just updated via cvs, and I get this [ivan@my Wine]$ winegcc -mwindows 01-biditest.c /tmp/wappZjLo5B.spec.o(.text+0x1010a): In function `__wine_exe_main': : undefined reference to `WinMain' collect2: ld returned 1 exit status Error: gcc failed. Error: winewrap failed. [ivan@my Wine]$ winewrap returns a seg fault.

3 2

LPT1 support in DOSFS_OpenDevice
by E Lea 20 Aug '03

20 Aug '03

I'm trying to add LPT1 support to DOSFS_OpenDevice. The software that requires this functionality controls a parallel port plotter by sending LOGO-style ASCII commands. I have based my attempts heavily on the serial port support, although I don't think I really know what I'm doing. Can anyone explain to me what's required? I have tried to implement a server call to create a file descriptor to /dev/lp0 (read from ~/.wine/config) and return a handle to it, but after that (perhaps when wine starts using the handle) both the wine and wineserver processes die. I don't really understand handles and how they are used. Are more functions required other than a simple create_parallel()? How do handles work?

1 0

anyone here got the format of icons & cursors?
by Jonathan Wilson 20 Aug '03

20 Aug '03

I am asking this since WINE appears to support icons and cursors but I cant find the code or the info. What I am looking for is: 1.the format of *.cur files 2.the format of *.ico files 3.the format of RT_CURSOR resources 4.the format of RT_ICON resources 5.the format of RT_CURSOR_GROUP resources and 6.the format of RT_ICON_GROUP resources

1 0

Re: PATCH - build libwine_unicode with w32api headers
by Steven Edwards 20 Aug '03

20 Aug '03

Nevermind. Send this patch and email to /dev/null. My w32api headers were hosed. Sorry for the noise. Thanks Steven --- Steven Edwards <steven_ed4153(a)yahoo.com> wrote: > You can now rm -fr *.h in wine/include (exclude config.h) and then do > configure. This patch fixes unicode.dll. I didnt know if you had a problem with > defining the WINVER but a define the winnls.h is not included in mingw without this. Should > wines > winnls be changed also? here is what we get without the patch. I am not near a MS_VC install to > check how it is done with the headers there. > > gcc -c -I. -I. -I../../include -I../../include -D_REENTRANT -D__WINESRC__ -DNO_ > LIBWINE_PORT -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ - > Wpointer-arith -g -O2 -o wctomb.o wctomb.c > wctomb.c: In function `is_valid_sbcs_mapping': > wctomb.c:73: `WC_NO_BEST_FIT_CHARS' undeclared (first use in this function) > wctomb.c:73: (Each undeclared identifier is reported only once > wctomb.c:73: for each function it appears in.) > wctomb.c: In function `is_valid_dbcs_mapping': > wctomb.c:256: `WC_NO_BEST_FIT_CHARS' undeclared (first use in this function) > make: *** [wctomb.o] Error 1 > > Changelog: Fix building libwine_unicode with w32api headers. > > Index: Makefile.in > =================================================================== > RCS file: /home/wine/wine/libs/unicode/Makefile.in,v > retrieving revision 1.5 > diff -u -r1.5 Makefile.in > --- Makefile.in 27 Jun 2003 19:02:23 -0000 1.5 > +++ Makefile.in 20 Aug 2003 06:13:25 -0000 > @@ -4,7 +4,7 @@ > VPATH = @srcdir@ > LIBRARY = wine_unicode > SOVERSION = 1 > -EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT > +EXTRADEFS = -D__WINESRC__ -DNO_LIBWINE_PORT -DWINVER=0x0500 > > CODEPAGES = \ > 037 \ > > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

rpcrt4.dll from WINE in ReactOS
by Steven Edwards 20 Aug '03

20 Aug '03

Hello, Are we going to be able to make use of WINEs rpcrt4.dll on ReactOS? I can build 99% of the dll with Mingw but am having trouble because of WINEs exception handler and a few calls to gettimeofday. If we should be able to use it then I will work on porting it when I get back from vacation on the 8th. We need a semi functioning rpcrt4 to be able to port ole32 and shell32. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 2

winegcc
by puoti＠inwind.it 20 Aug '03

20 Aug '03

Hi list, I was compiling the bidi test to try the ICU libs, and got this error ivan@my Wine]$ winegcc 01-biditest.c wgcc.ygvnee.o(.text+0x91): In function `main': : undefined reference to `GetCharacterPlacementW' collect2: ld returned 1 exit status Error: gcc failed. Error: /usr/local/bin/winewrap failed. [ivan@my Wine]$ so I tried winewrap and got a segmentation fault I'm running wine cvs current, compiled on Mandrake 9.1 with gcc 3.2.2, and glibc 2.3, any help would be gratly appreciated, Ivan.

2 1

problem with apps in desktop mode
by Rok Mandeljc 19 Aug '03

19 Aug '03

When I try running InstallShield in windowed mode ("Desktop" = "640x480" as per default in config), window appears for a second and then dissapears printing this message: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 12 (X_ConfigureWindow) Serial number of failed request: 93 Current serial number in output stream: 98 Did latest modifications of x11drv break anything? -- Rok Mandeljc <rok.mandeljc(a)gimb.org> "All that is gold does not glitter, Not all those who wander are lost; The old that is strong does not wither, Deep roots are not reached by the frost. From the ashes a fire shall be woken, A light from the shadows shall spring; Renewed shall be blade that was broken, The crownless again shall be king." -- J.R.R. Tolkien

4 3

Re: REGRESSION: environment variables no longer possible
by Alexandre Julliard 19 Aug '03

19 Aug '03

"Dmitry Timoshkov" <dmitry(a)baikal.ru> writes: > Actually it's just the format of the Wine config has changed. Now all > environment variables should be surrounded by the percent signes (%HOME%), > and are handled by the normal registry code. Alexandre has changed the sample > config as well. Actually the format of the config has not really changed, most entries have been behaving that way for a long time already. I just made the drives part of the config behave like all the other entries. > Attached patch is rather useless, but however it makes the old profile > code be consistent with the new behaviour. A better approach is to > completely remove environment handling from profile.c. Yes, I think environment handling should be left to the application. -- Alexandre Julliard julliard(a)winehq.com

4 5

Parse error when trying to build imagehlp with the w32api headers
by Steven Edwards 19 Aug '03

19 Aug '03

Does anyone have any idea as to what is going on here. I dont really see why mingw has a problem. access.c: In function `ImageUnload': access.c:204: parse error before "LOADED_IMAGE" access.c:210: parse error before "LOADED_IMAGE" make1: *** [access.o] Error 1 Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

3 2

Re: Anyone having problems with Alsa ?
by Sylvain Petreolle 19 Aug '03

19 Aug '03

Yes, did it, thanks. And wine recompiling too (done daily with cvs update). Another user seems to have found a problem into dlls/winmm/winealsa/audio.c, related to the software silence duration setting. --- Jerry Jenkins <Jerry_J_Jenkins(a)hotmail.com> a écrit : > Did you restart service alsasound or your computer? Maybe recompiling > WINE > is also needed. ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: Fix treeview with checkboxes creation
by Dmitry Timoshkov 19 Aug '03

19 Aug '03

"Maxime Bellengé" <maxime.bellenge(a)laposte.net> wrote: > Changelog: > * Fix the creation of treeview with checkboxes. Now they display fine. The only real change in this patch is the following snippet. Could you retest and send only that chunk alone? @@ -4848,12 +4850,14 @@ DrawFrameControl(hdc, &rc, DFC_BUTTON, DFCS_BUTTONCHECK|DFCS_FLAT|DFCS_CHECKED); + SelectObject(hdc, hbmOld); nIndex = ImageList_AddMasked(infoPtr->himlState, hbm, GetSysColor(COLOR_WINDOW)); TRACE("chckbox index %d\n", nIndex); - SelectObject(hdc, hbmOld); -- Dmitry.

2 5

Re: [PATCH] Compiling GNU winboard completed
by Dimitrie O. Paun 19 Aug '03

19 Aug '03

On August 18, 2003 02:07 pm, erwin wolff wrote: > I have been busy with compiling GNU winboard (the win32 graphic > front-end for GNU chess). If these patches are applied, it compiles > without a single warning. Please note that the mmsystem.diff is intended > for wine/include/mmsystem.h. Here is a smaller patch against winboard which does the following: -- cygwin.mak: modify it to also support building under Wine. This way, we have only one makefile for cygwin/mingw/Wine, and therefore we run a much smaller risk of obsolesence. -- winboard.rc: make sure the case in filenames referenced from .rc file match the case of file on disk For the _popen problem, I have sent fixes for Wine. > I hope this doesn't break anything. The other two files are for the > winboard source tarball version 2.4.6. (ftp://ftp.gnu.org/gnu/winboard > ). Although it compiles and starts good, I cannot play against a > computer component (only against myself;() due the following fixme: Unfortunately, it doesn't even start in my case. Maybe the _popen stubs kill it, needs investigating. diff -u winboard/cygwin.mak winboard.dimi/cygwin.mak --- winboard/cygwin.mak 2001-12-03 02:09:44.000000000 -0500 +++ winboard.dimi/cygwin.mak 2003-08-19 08:23:08.000000000 -0400 @@ -17,17 +17,22 @@ gamelist.o pgntags.o wedittags.o wgamelist.o zippy.o \ wsockerr.o wbres.o wclipbrd.o woptions.o +ifndef WINE +CC = gcc +RC = windres +LDVARS = -Xlinker "-e" -Xlinker "_mainCRTStartup" +else +CC = winegcc +RC = wrc +endif # 2 Dec 2001 - the mingw libraries that I have right now # (not updated for a few months) have bugs in fileno and stat # that prevent WinBoard from working. -#cygwin= -mno-cygwin +cygwin= -mno-cygwin -CFLAGS= $(cdebug) -CVARS= -I. -mwindows $(cygwin) -CC = gcc $(CVARS) -WCC = $(CC) -mwindows -Xlinker "-e" -Xlinker "_mainCRTStartup" \ - $(linkdebug) $(cygwin) +CFLAGS= $(cdebug) -I. -mwindows $(cygwin) +WCC = $(CC) -mwindows $(LDVARS) $(linkdebug) $(cygwin) LD = ld all: $(proj).exe @@ -39,7 +44,7 @@ # Update the resource if necessary wbres.o: $(proj).rc $(proj).h resource.h - windres --use-temp-file $< -O coff -o $@ + $(RC) --use-temp-file $< -O coff -o $@ # Update the object files if necessary @@ -54,4 +59,4 @@ -o $(proj).exe clean: - rm *.o parser.c + rm -f *.o parser.c winboard diff -u winboard/winboard.rc winboard.dimi/winboard.rc --- winboard/winboard.rc 2002-02-02 02:09:33.000000000 -0500 +++ winboard.dimi/winboard.rc 2003-08-19 02:44:57.000000000 -0400 @@ -959,330 +959,330 @@ // Bitmap // -P21O BITMAP MOVEABLE PURE "bitmaps\\P21o.bmp" -N21O BITMAP MOVEABLE PURE "bitmaps\\N21o.bmp" -B21O BITMAP MOVEABLE PURE "bitmaps\\B21o.bmp" -R21O BITMAP MOVEABLE PURE "bitmaps\\R21o.bmp" -K21O BITMAP MOVEABLE PURE "bitmaps\\K21o.bmp" -Q21O BITMAP MOVEABLE PURE "bitmaps\\Q21o.bmp" -P21S BITMAP MOVEABLE PURE "bitmaps\\P21s.bmp" -N21S BITMAP MOVEABLE PURE "bitmaps\\N21s.bmp" -B21S BITMAP MOVEABLE PURE "bitmaps\\B21s.bmp" -R21S BITMAP MOVEABLE PURE "bitmaps\\R21s.bmp" -Q21S BITMAP MOVEABLE PURE "bitmaps\\Q21s.bmp" -K21S BITMAP MOVEABLE PURE "bitmaps\\K21s.bmp" -P21W BITMAP MOVEABLE PURE "bitmaps\\P21w.bmp" -N21W BITMAP MOVEABLE PURE "bitmaps\\N21w.bmp" -B21W BITMAP MOVEABLE PURE "bitmaps\\B21w.bmp" -R21W BITMAP MOVEABLE PURE "bitmaps\\R21w.bmp" -Q21W BITMAP MOVEABLE PURE "bitmaps\\Q21w.bmp" -K21W BITMAP MOVEABLE PURE "bitmaps\\K21w.bmp" -P25O BITMAP MOVEABLE PURE "bitmaps\\P25o.bmp" -N25O BITMAP MOVEABLE PURE "bitmaps\\N25o.bmp" -B25O BITMAP MOVEABLE PURE "bitmaps\\B25o.bmp" -R25O BITMAP MOVEABLE PURE "bitmaps\\R25o.bmp" -Q25O BITMAP MOVEABLE PURE "bitmaps\\Q25o.bmp" -K25O BITMAP MOVEABLE PURE "bitmaps\\K25o.bmp" -P25S BITMAP MOVEABLE PURE "bitmaps\\P25s.bmp" -N25S BITMAP MOVEABLE PURE "bitmaps\\N25s.bmp" -B25S BITMAP MOVEABLE PURE "bitmaps\\B25s.bmp" -R25S BITMAP MOVEABLE PURE "bitmaps\\R25s.bmp" -Q25S BITMAP MOVEABLE PURE "bitmaps\\Q25s.bmp" -K25S BITMAP MOVEABLE PURE "bitmaps\\K25s.bmp" -P25W BITMAP MOVEABLE PURE "bitmaps\\P25w.bmp" -N25W BITMAP MOVEABLE PURE "bitmaps\\N25w.bmp" -B25W BITMAP MOVEABLE PURE "bitmaps\\B25w.bmp" -R25W BITMAP MOVEABLE PURE "bitmaps\\R25w.bmp" -Q25W BITMAP MOVEABLE PURE "bitmaps\\Q25w.bmp" -K25W BITMAP MOVEABLE PURE "bitmaps\\K25w.bmp" -P29O BITMAP MOVEABLE PURE "bitmaps\\P29o.bmp" -N29O BITMAP MOVEABLE PURE "bitmaps\\N29o.bmp" -B29O BITMAP MOVEABLE PURE "bitmaps\\B29o.bmp" -R29O BITMAP MOVEABLE PURE "bitmaps\\R29o.bmp" -Q29O BITMAP MOVEABLE PURE "bitmaps\\Q29o.bmp" -K29O BITMAP MOVEABLE PURE "bitmaps\\K29o.bmp" -P29S BITMAP MOVEABLE PURE "bitmaps\\P29s.bmp" -N29S BITMAP MOVEABLE PURE "bitmaps\\N29s.bmp" -B29S BITMAP MOVEABLE PURE "bitmaps\\B29s.bmp" -R29S BITMAP MOVEABLE PURE "bitmaps\\R29s.bmp" -Q29S BITMAP MOVEABLE PURE "bitmaps\\Q29s.bmp" -K29S BITMAP MOVEABLE PURE "bitmaps\\K29s.bmp" -P29W BITMAP MOVEABLE PURE "bitmaps\\P29w.bmp" -N29W BITMAP MOVEABLE PURE "bitmaps\\N29w.bmp" -B29W BITMAP MOVEABLE PURE "bitmaps\\B29w.bmp" -R29W BITMAP MOVEABLE PURE "bitmaps\\R29w.bmp" -Q29W BITMAP MOVEABLE PURE "bitmaps\\Q29w.bmp" -K29W BITMAP MOVEABLE PURE "bitmaps\\K29w.bmp" -P33O BITMAP MOVEABLE PURE "bitmaps\\P33o.bmp" -N33O BITMAP MOVEABLE PURE "bitmaps\\N33o.bmp" -B33O BITMAP MOVEABLE PURE "bitmaps\\B33o.bmp" -R33O BITMAP MOVEABLE PURE "bitmaps\\R33o.bmp" -Q33O BITMAP MOVEABLE PURE "bitmaps\\Q33o.bmp" -K33O BITMAP MOVEABLE PURE "bitmaps\\K33o.bmp" -P33S BITMAP MOVEABLE PURE "bitmaps\\P33s.bmp" -N33S BITMAP MOVEABLE PURE "bitmaps\\N33s.bmp" -B33S BITMAP MOVEABLE PURE "bitmaps\\B33s.bmp" -R33S BITMAP MOVEABLE PURE "bitmaps\\R33s.bmp" -Q33S BITMAP MOVEABLE PURE "bitmaps\\Q33s.bmp" -K33S BITMAP MOVEABLE PURE "bitmaps\\K33s.bmp" -P33W BITMAP MOVEABLE PURE "bitmaps\\P33w.bmp" -N33W BITMAP MOVEABLE PURE "bitmaps\\N33w.bmp" -B33W BITMAP MOVEABLE PURE "bitmaps\\B33w.bmp" -R33W BITMAP MOVEABLE PURE "bitmaps\\R33w.bmp" -Q33W BITMAP MOVEABLE PURE "bitmaps\\Q33w.bmp" -K33W BITMAP MOVEABLE PURE "bitmaps\\K33w.bmp" -P37O BITMAP MOVEABLE PURE "bitmaps\\P37o.bmp" -N37O BITMAP MOVEABLE PURE "bitmaps\\N37o.bmp" -B37O BITMAP MOVEABLE PURE "bitmaps\\B37o.bmp" -R37O BITMAP MOVEABLE PURE "bitmaps\\R37o.bmp" -Q37O BITMAP MOVEABLE PURE "bitmaps\\Q37o.bmp" -K37O BITMAP MOVEABLE PURE "bitmaps\\K37o.bmp" -P37S BITMAP MOVEABLE PURE "bitmaps\\P37s.bmp" -N37S BITMAP MOVEABLE PURE "bitmaps\\N37s.bmp" -B37S BITMAP MOVEABLE PURE "bitmaps\\B37s.bmp" -R37S BITMAP MOVEABLE PURE "bitmaps\\R37s.bmp" -Q37S BITMAP MOVEABLE PURE "bitmaps\\Q37s.bmp" -K37S BITMAP MOVEABLE PURE "bitmaps\\K37s.bmp" -P37W BITMAP MOVEABLE PURE "bitmaps\\P37w.bmp" -N37W BITMAP MOVEABLE PURE "bitmaps\\N37w.bmp" -B37W BITMAP MOVEABLE PURE "bitmaps\\B37w.bmp" -R37W BITMAP MOVEABLE PURE "bitmaps\\R37w.bmp" -Q37W BITMAP MOVEABLE PURE "bitmaps\\Q37w.bmp" -K37W BITMAP MOVEABLE PURE "bitmaps\\K37w.bmp" -P40O BITMAP MOVEABLE PURE "bitmaps\\P40o.bmp" -N40O BITMAP MOVEABLE PURE "bitmaps\\N40o.bmp" -B40O BITMAP MOVEABLE PURE "bitmaps\\B40o.bmp" -R40O BITMAP MOVEABLE PURE "bitmaps\\R40o.bmp" -Q40O BITMAP MOVEABLE PURE "bitmaps\\Q40o.bmp" -K40O BITMAP MOVEABLE PURE "bitmaps\\K40o.bmp" -P40S BITMAP MOVEABLE PURE "bitmaps\\P40s.bmp" -N40S BITMAP MOVEABLE PURE "bitmaps\\N40s.bmp" -B40S BITMAP MOVEABLE PURE "bitmaps\\B40s.bmp" -R40S BITMAP MOVEABLE PURE "bitmaps\\R40s.bmp" -Q40S BITMAP MOVEABLE PURE "bitmaps\\Q40s.bmp" -K40S BITMAP MOVEABLE PURE "bitmaps\\K40s.bmp" -P40W BITMAP MOVEABLE PURE "bitmaps\\P40w.bmp" -N40W BITMAP MOVEABLE PURE "bitmaps\\N40w.bmp" -B40W BITMAP MOVEABLE PURE "bitmaps\\B40w.bmp" -R40W BITMAP MOVEABLE PURE "bitmaps\\R40w.bmp" -Q40W BITMAP MOVEABLE PURE "bitmaps\\Q40w.bmp" -K40W BITMAP MOVEABLE PURE "bitmaps\\K40w.bmp" -P45O BITMAP MOVEABLE PURE "bitmaps\\P45o.bmp" -N45O BITMAP MOVEABLE PURE "bitmaps\\N45o.bmp" -B45O BITMAP MOVEABLE PURE "bitmaps\\B45o.bmp" -R45O BITMAP MOVEABLE PURE "bitmaps\\R45o.bmp" -Q45O BITMAP MOVEABLE PURE "bitmaps\\Q45o.bmp" -K45O BITMAP MOVEABLE PURE "bitmaps\\K45o.bmp" -P45S BITMAP MOVEABLE PURE "bitmaps\\P45s.bmp" -N45S BITMAP MOVEABLE PURE "bitmaps\\N45s.bmp" -B45S BITMAP MOVEABLE PURE "bitmaps\\B45s.bmp" -R45S BITMAP MOVEABLE PURE "bitmaps\\R45s.bmp" -Q45S BITMAP MOVEABLE PURE "bitmaps\\Q45s.bmp" -K45S BITMAP MOVEABLE PURE "bitmaps\\K45s.bmp" -P45W BITMAP MOVEABLE PURE "bitmaps\\P45w.bmp" -N45W BITMAP MOVEABLE PURE "bitmaps\\N45w.bmp" -B45W BITMAP MOVEABLE PURE "bitmaps\\B45w.bmp" -R45W BITMAP MOVEABLE PURE "bitmaps\\R45w.bmp" -Q45W BITMAP MOVEABLE PURE "bitmaps\\Q45w.bmp" -K45W BITMAP MOVEABLE PURE "bitmaps\\K45w.bmp" -P49O BITMAP MOVEABLE PURE "bitmaps\\P49o.bmp" -N49O BITMAP MOVEABLE PURE "bitmaps\\N49o.bmp" -B49O BITMAP MOVEABLE PURE "bitmaps\\B49o.bmp" -R49O BITMAP MOVEABLE PURE "bitmaps\\R49o.bmp" -Q49O BITMAP MOVEABLE PURE "bitmaps\\Q49o.bmp" -K49O BITMAP MOVEABLE PURE "bitmaps\\K49o.bmp" -P49S BITMAP MOVEABLE PURE "bitmaps\\P49s.bmp" -N49S BITMAP MOVEABLE PURE "bitmaps\\N49s.bmp" -B49S BITMAP MOVEABLE PURE "bitmaps\\B49s.bmp" -R49S BITMAP MOVEABLE PURE "bitmaps\\R49s.bmp" -Q49S BITMAP MOVEABLE PURE "bitmaps\\Q49s.bmp" -K49S BITMAP MOVEABLE PURE "bitmaps\\K49s.bmp" -P49W BITMAP MOVEABLE PURE "bitmaps\\P49w.bmp" -N49W BITMAP MOVEABLE PURE "bitmaps\\N49w.bmp" -B49W BITMAP MOVEABLE PURE "bitmaps\\B49w.bmp" -R49W BITMAP MOVEABLE PURE "bitmaps\\R49w.bmp" -Q49W BITMAP MOVEABLE PURE "bitmaps\\Q49w.bmp" -K49W BITMAP MOVEABLE PURE "bitmaps\\K49w.bmp" -P54O BITMAP MOVEABLE PURE "bitmaps\\P54o.bmp" -N54O BITMAP MOVEABLE PURE "bitmaps\\N54o.bmp" -B54O BITMAP MOVEABLE PURE "bitmaps\\B54o.bmp" -R54O BITMAP MOVEABLE PURE "bitmaps\\R54o.bmp" -Q54O BITMAP MOVEABLE PURE "bitmaps\\Q54o.bmp" -K54O BITMAP MOVEABLE PURE "bitmaps\\K54o.bmp" -P54S BITMAP MOVEABLE PURE "bitmaps\\P54s.bmp" -N54S BITMAP MOVEABLE PURE "bitmaps\\N54s.bmp" -B54S BITMAP MOVEABLE PURE "bitmaps\\B54s.bmp" -R54S BITMAP MOVEABLE PURE "bitmaps\\R54s.bmp" -Q54S BITMAP MOVEABLE PURE "bitmaps\\Q54s.bmp" -K54S BITMAP MOVEABLE PURE "bitmaps\\K54s.bmp" -P54W BITMAP MOVEABLE PURE "bitmaps\\P54w.bmp" -N54W BITMAP MOVEABLE PURE "bitmaps\\N54w.bmp" -B54W BITMAP MOVEABLE PURE "bitmaps\\B54w.bmp" -R54W BITMAP MOVEABLE PURE "bitmaps\\R54w.bmp" -Q54W BITMAP MOVEABLE PURE "bitmaps\\Q54w.bmp" -K54W BITMAP MOVEABLE PURE "bitmaps\\K54w.bmp" -P58O BITMAP MOVEABLE PURE "bitmaps\\P58o.bmp" -N58O BITMAP MOVEABLE PURE "bitmaps\\N58o.bmp" -B58O BITMAP MOVEABLE PURE "bitmaps\\B58o.bmp" -R58O BITMAP MOVEABLE PURE "bitmaps\\R58o.bmp" -Q58O BITMAP MOVEABLE PURE "bitmaps\\Q58o.bmp" -K58O BITMAP MOVEABLE PURE "bitmaps\\K58o.bmp" -P58S BITMAP MOVEABLE PURE "bitmaps\\P58s.bmp" -N58S BITMAP MOVEABLE PURE "bitmaps\\N58s.bmp" -B58S BITMAP MOVEABLE PURE "bitmaps\\B58s.bmp" -R58S BITMAP MOVEABLE PURE "bitmaps\\R58s.bmp" -Q58S BITMAP MOVEABLE PURE "bitmaps\\Q58s.bmp" -K58S BITMAP MOVEABLE PURE "bitmaps\\K58s.bmp" -P58W BITMAP MOVEABLE PURE "bitmaps\\P58w.bmp" -N58W BITMAP MOVEABLE PURE "bitmaps\\N58w.bmp" -B58W BITMAP MOVEABLE PURE "bitmaps\\B58w.bmp" -R58W BITMAP MOVEABLE PURE "bitmaps\\R58w.bmp" -Q58W BITMAP MOVEABLE PURE "bitmaps\\Q58w.bmp" -K58W BITMAP MOVEABLE PURE "bitmaps\\K58w.bmp" -P64O BITMAP MOVEABLE PURE "bitmaps\\P64o.bmp" -N64O BITMAP MOVEABLE PURE "bitmaps\\N64o.bmp" -B64O BITMAP MOVEABLE PURE "bitmaps\\B64o.bmp" -R64O BITMAP MOVEABLE PURE "bitmaps\\R64o.bmp" -Q64O BITMAP MOVEABLE PURE "bitmaps\\Q64o.bmp" -K64O BITMAP MOVEABLE PURE "bitmaps\\K64o.bmp" -P64S BITMAP MOVEABLE PURE "bitmaps\\P64s.bmp" -N64S BITMAP MOVEABLE PURE "bitmaps\\N64s.bmp" -B64S BITMAP MOVEABLE PURE "bitmaps\\B64s.bmp" -R64S BITMAP MOVEABLE PURE "bitmaps\\R64s.bmp" -Q64S BITMAP MOVEABLE PURE "bitmaps\\Q64s.bmp" -K64S BITMAP MOVEABLE PURE "bitmaps\\K64s.bmp" -P64W BITMAP MOVEABLE PURE "bitmaps\\P64w.bmp" -N64W BITMAP MOVEABLE PURE "bitmaps\\N64w.bmp" -B64W BITMAP MOVEABLE PURE "bitmaps\\B64w.bmp" -R64W BITMAP MOVEABLE PURE "bitmaps\\R64w.bmp" -Q64W BITMAP MOVEABLE PURE "bitmaps\\Q64w.bmp" -K64W BITMAP MOVEABLE PURE "bitmaps\\K64w.bmp" -P72O BITMAP MOVEABLE PURE "bitmaps\\P72o.bmp" -N72O BITMAP MOVEABLE PURE "bitmaps\\N72o.bmp" -B72O BITMAP MOVEABLE PURE "bitmaps\\B72o.bmp" -R72O BITMAP MOVEABLE PURE "bitmaps\\R72o.bmp" -Q72O BITMAP MOVEABLE PURE "bitmaps\\Q72o.bmp" -K72O BITMAP MOVEABLE PURE "bitmaps\\K72o.bmp" -P72S BITMAP MOVEABLE PURE "bitmaps\\P72s.bmp" -N72S BITMAP MOVEABLE PURE "bitmaps\\N72s.bmp" -B72S BITMAP MOVEABLE PURE "bitmaps\\B72s.bmp" -R72S BITMAP MOVEABLE PURE "bitmaps\\R72s.bmp" -Q72S BITMAP MOVEABLE PURE "bitmaps\\Q72s.bmp" -K72S BITMAP MOVEABLE PURE "bitmaps\\K72s.bmp" -P72W BITMAP MOVEABLE PURE "bitmaps\\P72w.bmp" -N72W BITMAP MOVEABLE PURE "bitmaps\\N72w.bmp" -B72W BITMAP MOVEABLE PURE "bitmaps\\B72w.bmp" -R72W BITMAP MOVEABLE PURE "bitmaps\\R72w.bmp" -Q72W BITMAP MOVEABLE PURE "bitmaps\\Q72w.bmp" -K72W BITMAP MOVEABLE PURE "bitmaps\\K72w.bmp" -P80O BITMAP MOVEABLE PURE "bitmaps\\P80o.bmp" -N80O BITMAP MOVEABLE PURE "bitmaps\\N80o.bmp" -B80O BITMAP MOVEABLE PURE "bitmaps\\B80o.bmp" -R80O BITMAP MOVEABLE PURE "bitmaps\\R80o.bmp" -Q80O BITMAP MOVEABLE PURE "bitmaps\\Q80o.bmp" -K80O BITMAP MOVEABLE PURE "bitmaps\\K80o.bmp" -P80S BITMAP MOVEABLE PURE "bitmaps\\P80s.bmp" -N80S BITMAP MOVEABLE PURE "bitmaps\\N80s.bmp" -B80S BITMAP MOVEABLE PURE "bitmaps\\B80s.bmp" -R80S BITMAP MOVEABLE PURE "bitmaps\\R80s.bmp" -Q80S BITMAP MOVEABLE PURE "bitmaps\\Q80s.bmp" -K80S BITMAP MOVEABLE PURE "bitmaps\\K80s.bmp" -P80W BITMAP MOVEABLE PURE "bitmaps\\P80w.bmp" -N80W BITMAP MOVEABLE PURE "bitmaps\\N80w.bmp" -B80W BITMAP MOVEABLE PURE "bitmaps\\B80w.bmp" -R80W BITMAP MOVEABLE PURE "bitmaps\\R80w.bmp" -Q80W BITMAP MOVEABLE PURE "bitmaps\\Q80w.bmp" -K80W BITMAP MOVEABLE PURE "bitmaps\\K80w.bmp" -P87O BITMAP MOVEABLE PURE "bitmaps\\P87o.bmp" -N87O BITMAP MOVEABLE PURE "bitmaps\\N87o.bmp" -B87O BITMAP MOVEABLE PURE "bitmaps\\B87o.bmp" -R87O BITMAP MOVEABLE PURE "bitmaps\\R87o.bmp" -Q87O BITMAP MOVEABLE PURE "bitmaps\\Q87o.bmp" -K87O BITMAP MOVEABLE PURE "bitmaps\\K87o.bmp" -P87S BITMAP MOVEABLE PURE "bitmaps\\P87s.bmp" -N87S BITMAP MOVEABLE PURE "bitmaps\\N87s.bmp" -B87S BITMAP MOVEABLE PURE "bitmaps\\B87s.bmp" -R87S BITMAP MOVEABLE PURE "bitmaps\\R87s.bmp" -Q87S BITMAP MOVEABLE PURE "bitmaps\\Q87s.bmp" -K87S BITMAP MOVEABLE PURE "bitmaps\\K87s.bmp" -P87W BITMAP MOVEABLE PURE "bitmaps\\P87w.bmp" -N87W BITMAP MOVEABLE PURE "bitmaps\\N87w.bmp" -B87W BITMAP MOVEABLE PURE "bitmaps\\B87w.bmp" -R87W BITMAP MOVEABLE PURE "bitmaps\\R87w.bmp" -Q87W BITMAP MOVEABLE PURE "bitmaps\\Q87w.bmp" -K87W BITMAP MOVEABLE PURE "bitmaps\\K87w.bmp" -P95O BITMAP MOVEABLE PURE "bitmaps\\P95o.bmp" -N95O BITMAP MOVEABLE PURE "bitmaps\\N95o.bmp" -B95O BITMAP MOVEABLE PURE "bitmaps\\B95o.bmp" -R95O BITMAP MOVEABLE PURE "bitmaps\\R95o.bmp" -Q95O BITMAP MOVEABLE PURE "bitmaps\\Q95o.bmp" -K95O BITMAP MOVEABLE PURE "bitmaps\\K95o.bmp" -P95S BITMAP MOVEABLE PURE "bitmaps\\P95s.bmp" -N95S BITMAP MOVEABLE PURE "bitmaps\\N95s.bmp" -B95S BITMAP MOVEABLE PURE "bitmaps\\B95s.bmp" -R95S BITMAP MOVEABLE PURE "bitmaps\\R95s.bmp" -Q95S BITMAP MOVEABLE PURE "bitmaps\\Q95s.bmp" -K95S BITMAP MOVEABLE PURE "bitmaps\\K95s.bmp" -P95W BITMAP MOVEABLE PURE "bitmaps\\P95w.bmp" -N95W BITMAP MOVEABLE PURE "bitmaps\\N95w.bmp" -B95W BITMAP MOVEABLE PURE "bitmaps\\B95w.bmp" -R95W BITMAP MOVEABLE PURE "bitmaps\\R95w.bmp" -Q95W BITMAP MOVEABLE PURE "bitmaps\\Q95w.bmp" -K95W BITMAP MOVEABLE PURE "bitmaps\\K95w.bmp" -P108O BITMAP MOVEABLE PURE "bitmaps\\P108o.bmp" -N108O BITMAP MOVEABLE PURE "bitmaps\\N108o.bmp" -B108O BITMAP MOVEABLE PURE "bitmaps\\B108o.bmp" -R108O BITMAP MOVEABLE PURE "bitmaps\\R108o.bmp" -Q108O BITMAP MOVEABLE PURE "bitmaps\\Q108o.bmp" -K108O BITMAP MOVEABLE PURE "bitmaps\\K108o.bmp" -P108S BITMAP MOVEABLE PURE "bitmaps\\P108s.bmp" -N108S BITMAP MOVEABLE PURE "bitmaps\\N108s.bmp" -B108S BITMAP MOVEABLE PURE "bitmaps\\B108s.bmp" -R108S BITMAP MOVEABLE PURE "bitmaps\\R108s.bmp" -Q108S BITMAP MOVEABLE PURE "bitmaps\\Q108s.bmp" -K108S BITMAP MOVEABLE PURE "bitmaps\\K108s.bmp" -P108W BITMAP MOVEABLE PURE "bitmaps\\P108w.bmp" -N108W BITMAP MOVEABLE PURE "bitmaps\\N108w.bmp" -B108W BITMAP MOVEABLE PURE "bitmaps\\B108w.bmp" -R108W BITMAP MOVEABLE PURE "bitmaps\\R108w.bmp" -Q108W BITMAP MOVEABLE PURE "bitmaps\\Q108w.bmp" -K108W BITMAP MOVEABLE PURE "bitmaps\\K108w.bmp" -P116O BITMAP MOVEABLE PURE "bitmaps\\P116o.bmp" -N116O BITMAP MOVEABLE PURE "bitmaps\\N116o.bmp" -B116O BITMAP MOVEABLE PURE "bitmaps\\B116o.bmp" -R116O BITMAP MOVEABLE PURE "bitmaps\\R116o.bmp" -Q116O BITMAP MOVEABLE PURE "bitmaps\\Q116o.bmp" -K116O BITMAP MOVEABLE PURE "bitmaps\\K116o.bmp" -P116S BITMAP MOVEABLE PURE "bitmaps\\P116s.bmp" -N116S BITMAP MOVEABLE PURE "bitmaps\\N116s.bmp" -B116S BITMAP MOVEABLE PURE "bitmaps\\B116s.bmp" -R116S BITMAP MOVEABLE PURE "bitmaps\\R116s.bmp" -Q116S BITMAP MOVEABLE PURE "bitmaps\\Q116s.bmp" -K116S BITMAP MOVEABLE PURE "bitmaps\\K116s.bmp" -P116W BITMAP MOVEABLE PURE "bitmaps\\P116w.bmp" -N116W BITMAP MOVEABLE PURE "bitmaps\\N116w.bmp" -B116W BITMAP MOVEABLE PURE "bitmaps\\B116w.bmp" -R116W BITMAP MOVEABLE PURE "bitmaps\\R116w.bmp" -Q116W BITMAP MOVEABLE PURE "bitmaps\\Q116w.bmp" -K116W BITMAP MOVEABLE PURE "bitmaps\\K116w.bmp" -P129O BITMAP MOVEABLE PURE "bitmaps\\P129o.bmp" -N129O BITMAP MOVEABLE PURE "bitmaps\\N129o.bmp" -B129O BITMAP MOVEABLE PURE "bitmaps\\B129o.bmp" -R129O BITMAP MOVEABLE PURE "bitmaps\\R129o.bmp" -Q129O BITMAP MOVEABLE PURE "bitmaps\\Q129o.bmp" -K129O BITMAP MOVEABLE PURE "bitmaps\\K129o.bmp" -P129S BITMAP MOVEABLE PURE "bitmaps\\P129s.bmp" -N129S BITMAP MOVEABLE PURE "bitmaps\\N129s.bmp" -B129S BITMAP MOVEABLE PURE "bitmaps\\B129s.bmp" -R129S BITMAP MOVEABLE PURE "bitmaps\\R129s.bmp" -Q129S BITMAP MOVEABLE PURE "bitmaps\\Q129s.bmp" -K129S BITMAP MOVEABLE PURE "bitmaps\\K129s.bmp" -P129W BITMAP MOVEABLE PURE "bitmaps\\P129w.bmp" -N129W BITMAP MOVEABLE PURE "bitmaps\\N129w.bmp" -B129W BITMAP MOVEABLE PURE "bitmaps\\B129w.bmp" -R129W BITMAP MOVEABLE PURE "bitmaps\\R129w.bmp" -Q129W BITMAP MOVEABLE PURE "bitmaps\\Q129w.bmp" -K129W BITMAP MOVEABLE PURE "bitmaps\\K129w.bmp" +P21O BITMAP MOVEABLE PURE "bitmaps\\p21o.bmp" +N21O BITMAP MOVEABLE PURE "bitmaps\\n21o.bmp" +B21O BITMAP MOVEABLE PURE "bitmaps\\b21o.bmp" +R21O BITMAP MOVEABLE PURE "bitmaps\\r21o.bmp" +K21O BITMAP MOVEABLE PURE "bitmaps\\k21o.bmp" +Q21O BITMAP MOVEABLE PURE "bitmaps\\q21o.bmp" +P21S BITMAP MOVEABLE PURE "bitmaps\\p21s.bmp" +N21S BITMAP MOVEABLE PURE "bitmaps\\n21s.bmp" +B21S BITMAP MOVEABLE PURE "bitmaps\\b21s.bmp" +R21S BITMAP MOVEABLE PURE "bitmaps\\r21s.bmp" +Q21S BITMAP MOVEABLE PURE "bitmaps\\q21s.bmp" +K21S BITMAP MOVEABLE PURE "bitmaps\\k21s.bmp" +P21W BITMAP MOVEABLE PURE "bitmaps\\p21w.bmp" +N21W BITMAP MOVEABLE PURE "bitmaps\\n21w.bmp" +B21W BITMAP MOVEABLE PURE "bitmaps\\b21w.bmp" +R21W BITMAP MOVEABLE PURE "bitmaps\\r21w.bmp" +Q21W BITMAP MOVEABLE PURE "bitmaps\\q21w.bmp" +K21W BITMAP MOVEABLE PURE "bitmaps\\k21w.bmp" +P25O BITMAP MOVEABLE PURE "bitmaps\\p25o.bmp" +N25O BITMAP MOVEABLE PURE "bitmaps\\n25o.bmp" +B25O BITMAP MOVEABLE PURE "bitmaps\\b25o.bmp" +R25O BITMAP MOVEABLE PURE "bitmaps\\r25o.bmp" +Q25O BITMAP MOVEABLE PURE "bitmaps\\q25o.bmp" +K25O BITMAP MOVEABLE PURE "bitmaps\\k25o.bmp" +P25S BITMAP MOVEABLE PURE "bitmaps\\p25s.bmp" +N25S BITMAP MOVEABLE PURE "bitmaps\\n25s.bmp" +B25S BITMAP MOVEABLE PURE "bitmaps\\b25s.bmp" +R25S BITMAP MOVEABLE PURE "bitmaps\\r25s.bmp" +Q25S BITMAP MOVEABLE PURE "bitmaps\\q25s.bmp" +K25S BITMAP MOVEABLE PURE "bitmaps\\k25s.bmp" +P25W BITMAP MOVEABLE PURE "bitmaps\\p25w.bmp" +N25W BITMAP MOVEABLE PURE "bitmaps\\n25w.bmp" +B25W BITMAP MOVEABLE PURE "bitmaps\\b25w.bmp" +R25W BITMAP MOVEABLE PURE "bitmaps\\r25w.bmp" +Q25W BITMAP MOVEABLE PURE "bitmaps\\q25w.bmp" +K25W BITMAP MOVEABLE PURE "bitmaps\\k25w.bmp" +P29O BITMAP MOVEABLE PURE "bitmaps\\p29o.bmp" +N29O BITMAP MOVEABLE PURE "bitmaps\\n29o.bmp" +B29O BITMAP MOVEABLE PURE "bitmaps\\b29o.bmp" +R29O BITMAP MOVEABLE PURE "bitmaps\\r29o.bmp" +Q29O BITMAP MOVEABLE PURE "bitmaps\\q29o.bmp" +K29O BITMAP MOVEABLE PURE "bitmaps\\k29o.bmp" +P29S BITMAP MOVEABLE PURE "bitmaps\\p29s.bmp" +N29S BITMAP MOVEABLE PURE "bitmaps\\n29s.bmp" +B29S BITMAP MOVEABLE PURE "bitmaps\\b29s.bmp" +R29S BITMAP MOVEABLE PURE "bitmaps\\r29s.bmp" +Q29S BITMAP MOVEABLE PURE "bitmaps\\q29s.bmp" +K29S BITMAP MOVEABLE PURE "bitmaps\\k29s.bmp" +P29W BITMAP MOVEABLE PURE "bitmaps\\p29w.bmp" +N29W BITMAP MOVEABLE PURE "bitmaps\\n29w.bmp" +B29W BITMAP MOVEABLE PURE "bitmaps\\b29w.bmp" +R29W BITMAP MOVEABLE PURE "bitmaps\\r29w.bmp" +Q29W BITMAP MOVEABLE PURE "bitmaps\\q29w.bmp" +K29W BITMAP MOVEABLE PURE "bitmaps\\k29w.bmp" +P33O BITMAP MOVEABLE PURE "bitmaps\\p33o.bmp" +N33O BITMAP MOVEABLE PURE "bitmaps\\n33o.bmp" +B33O BITMAP MOVEABLE PURE "bitmaps\\b33o.bmp" +R33O BITMAP MOVEABLE PURE "bitmaps\\r33o.bmp" +Q33O BITMAP MOVEABLE PURE "bitmaps\\q33o.bmp" +K33O BITMAP MOVEABLE PURE "bitmaps\\k33o.bmp" +P33S BITMAP MOVEABLE PURE "bitmaps\\p33s.bmp" +N33S BITMAP MOVEABLE PURE "bitmaps\\n33s.bmp" +B33S BITMAP MOVEABLE PURE "bitmaps\\b33s.bmp" +R33S BITMAP MOVEABLE PURE "bitmaps\\r33s.bmp" +Q33S BITMAP MOVEABLE PURE "bitmaps\\q33s.bmp" +K33S BITMAP MOVEABLE PURE "bitmaps\\k33s.bmp" +P33W BITMAP MOVEABLE PURE "bitmaps\\p33w.bmp" +N33W BITMAP MOVEABLE PURE "bitmaps\\n33w.bmp" +B33W BITMAP MOVEABLE PURE "bitmaps\\b33w.bmp" +R33W BITMAP MOVEABLE PURE "bitmaps\\r33w.bmp" +Q33W BITMAP MOVEABLE PURE "bitmaps\\q33w.bmp" +K33W BITMAP MOVEABLE PURE "bitmaps\\k33w.bmp" +P37O BITMAP MOVEABLE PURE "bitmaps\\p37o.bmp" +N37O BITMAP MOVEABLE PURE "bitmaps\\n37o.bmp" +B37O BITMAP MOVEABLE PURE "bitmaps\\b37o.bmp" +R37O BITMAP MOVEABLE PURE "bitmaps\\r37o.bmp" +Q37O BITMAP MOVEABLE PURE "bitmaps\\q37o.bmp" +K37O BITMAP MOVEABLE PURE "bitmaps\\k37o.bmp" +P37S BITMAP MOVEABLE PURE "bitmaps\\p37s.bmp" +N37S BITMAP MOVEABLE PURE "bitmaps\\n37s.bmp" +B37S BITMAP MOVEABLE PURE "bitmaps\\b37s.bmp" +R37S BITMAP MOVEABLE PURE "bitmaps\\r37s.bmp" +Q37S BITMAP MOVEABLE PURE "bitmaps\\q37s.bmp" +K37S BITMAP MOVEABLE PURE "bitmaps\\k37s.bmp" +P37W BITMAP MOVEABLE PURE "bitmaps\\p37w.bmp" +N37W BITMAP MOVEABLE PURE "bitmaps\\n37w.bmp" +B37W BITMAP MOVEABLE PURE "bitmaps\\b37w.bmp" +R37W BITMAP MOVEABLE PURE "bitmaps\\r37w.bmp" +Q37W BITMAP MOVEABLE PURE "bitmaps\\q37w.bmp" +K37W BITMAP MOVEABLE PURE "bitmaps\\k37w.bmp" +P40O BITMAP MOVEABLE PURE "bitmaps\\p40o.bmp" +N40O BITMAP MOVEABLE PURE "bitmaps\\n40o.bmp" +B40O BITMAP MOVEABLE PURE "bitmaps\\b40o.bmp" +R40O BITMAP MOVEABLE PURE "bitmaps\\r40o.bmp" +Q40O BITMAP MOVEABLE PURE "bitmaps\\q40o.bmp" +K40O BITMAP MOVEABLE PURE "bitmaps\\k40o.bmp" +P40S BITMAP MOVEABLE PURE "bitmaps\\p40s.bmp" +N40S BITMAP MOVEABLE PURE "bitmaps\\n40s.bmp" +B40S BITMAP MOVEABLE PURE "bitmaps\\b40s.bmp" +R40S BITMAP MOVEABLE PURE "bitmaps\\r40s.bmp" +Q40S BITMAP MOVEABLE PURE "bitmaps\\q40s.bmp" +K40S BITMAP MOVEABLE PURE "bitmaps\\k40s.bmp" +P40W BITMAP MOVEABLE PURE "bitmaps\\p40w.bmp" +N40W BITMAP MOVEABLE PURE "bitmaps\\n40w.bmp" +B40W BITMAP MOVEABLE PURE "bitmaps\\b40w.bmp" +R40W BITMAP MOVEABLE PURE "bitmaps\\r40w.bmp" +Q40W BITMAP MOVEABLE PURE "bitmaps\\q40w.bmp" +K40W BITMAP MOVEABLE PURE "bitmaps\\k40w.bmp" +P45O BITMAP MOVEABLE PURE "bitmaps\\p45o.bmp" +N45O BITMAP MOVEABLE PURE "bitmaps\\n45o.bmp" +B45O BITMAP MOVEABLE PURE "bitmaps\\b45o.bmp" +R45O BITMAP MOVEABLE PURE "bitmaps\\r45o.bmp" +Q45O BITMAP MOVEABLE PURE "bitmaps\\q45o.bmp" +K45O BITMAP MOVEABLE PURE "bitmaps\\k45o.bmp" +P45S BITMAP MOVEABLE PURE "bitmaps\\p45s.bmp" +N45S BITMAP MOVEABLE PURE "bitmaps\\n45s.bmp" +B45S BITMAP MOVEABLE PURE "bitmaps\\b45s.bmp" +R45S BITMAP MOVEABLE PURE "bitmaps\\r45s.bmp" +Q45S BITMAP MOVEABLE PURE "bitmaps\\q45s.bmp" +K45S BITMAP MOVEABLE PURE "bitmaps\\k45s.bmp" +P45W BITMAP MOVEABLE PURE "bitmaps\\p45w.bmp" +N45W BITMAP MOVEABLE PURE "bitmaps\\n45w.bmp" +B45W BITMAP MOVEABLE PURE "bitmaps\\b45w.bmp" +R45W BITMAP MOVEABLE PURE "bitmaps\\r45w.bmp" +Q45W BITMAP MOVEABLE PURE "bitmaps\\q45w.bmp" +K45W BITMAP MOVEABLE PURE "bitmaps\\k45w.bmp" +P49O BITMAP MOVEABLE PURE "bitmaps\\p49o.bmp" +N49O BITMAP MOVEABLE PURE "bitmaps\\n49o.bmp" +B49O BITMAP MOVEABLE PURE "bitmaps\\b49o.bmp" +R49O BITMAP MOVEABLE PURE "bitmaps\\r49o.bmp" +Q49O BITMAP MOVEABLE PURE "bitmaps\\q49o.bmp" +K49O BITMAP MOVEABLE PURE "bitmaps\\k49o.bmp" +P49S BITMAP MOVEABLE PURE "bitmaps\\p49s.bmp" +N49S BITMAP MOVEABLE PURE "bitmaps\\n49s.bmp" +B49S BITMAP MOVEABLE PURE "bitmaps\\b49s.bmp" +R49S BITMAP MOVEABLE PURE "bitmaps\\r49s.bmp" +Q49S BITMAP MOVEABLE PURE "bitmaps\\q49s.bmp" +K49S BITMAP MOVEABLE PURE "bitmaps\\k49s.bmp" +P49W BITMAP MOVEABLE PURE "bitmaps\\p49w.bmp" +N49W BITMAP MOVEABLE PURE "bitmaps\\n49w.bmp" +B49W BITMAP MOVEABLE PURE "bitmaps\\b49w.bmp" +R49W BITMAP MOVEABLE PURE "bitmaps\\r49w.bmp" +Q49W BITMAP MOVEABLE PURE "bitmaps\\q49w.bmp" +K49W BITMAP MOVEABLE PURE "bitmaps\\k49w.bmp" +P54O BITMAP MOVEABLE PURE "bitmaps\\p54o.bmp" +N54O BITMAP MOVEABLE PURE "bitmaps\\n54o.bmp" +B54O BITMAP MOVEABLE PURE "bitmaps\\b54o.bmp" +R54O BITMAP MOVEABLE PURE "bitmaps\\r54o.bmp" +Q54O BITMAP MOVEABLE PURE "bitmaps\\q54o.bmp" +K54O BITMAP MOVEABLE PURE "bitmaps\\k54o.bmp" +P54S BITMAP MOVEABLE PURE "bitmaps\\p54s.bmp" +N54S BITMAP MOVEABLE PURE "bitmaps\\n54s.bmp" +B54S BITMAP MOVEABLE PURE "bitmaps\\b54s.bmp" +R54S BITMAP MOVEABLE PURE "bitmaps\\r54s.bmp" +Q54S BITMAP MOVEABLE PURE "bitmaps\\q54s.bmp" +K54S BITMAP MOVEABLE PURE "bitmaps\\k54s.bmp" +P54W BITMAP MOVEABLE PURE "bitmaps\\p54w.bmp" +N54W BITMAP MOVEABLE PURE "bitmaps\\n54w.bmp" +B54W BITMAP MOVEABLE PURE "bitmaps\\b54w.bmp" +R54W BITMAP MOVEABLE PURE "bitmaps\\r54w.bmp" +Q54W BITMAP MOVEABLE PURE "bitmaps\\q54w.bmp" +K54W BITMAP MOVEABLE PURE "bitmaps\\k54w.bmp" +P58O BITMAP MOVEABLE PURE "bitmaps\\p58o.bmp" +N58O BITMAP MOVEABLE PURE "bitmaps\\n58o.bmp" +B58O BITMAP MOVEABLE PURE "bitmaps\\b58o.bmp" +R58O BITMAP MOVEABLE PURE "bitmaps\\r58o.bmp" +Q58O BITMAP MOVEABLE PURE "bitmaps\\q58o.bmp" +K58O BITMAP MOVEABLE PURE "bitmaps\\k58o.bmp" +P58S BITMAP MOVEABLE PURE "bitmaps\\p58s.bmp" +N58S BITMAP MOVEABLE PURE "bitmaps\\n58s.bmp" +B58S BITMAP MOVEABLE PURE "bitmaps\\b58s.bmp" +R58S BITMAP MOVEABLE PURE "bitmaps\\r58s.bmp" +Q58S BITMAP MOVEABLE PURE "bitmaps\\q58s.bmp" +K58S BITMAP MOVEABLE PURE "bitmaps\\k58s.bmp" +P58W BITMAP MOVEABLE PURE "bitmaps\\p58w.bmp" +N58W BITMAP MOVEABLE PURE "bitmaps\\n58w.bmp" +B58W BITMAP MOVEABLE PURE "bitmaps\\b58w.bmp" +R58W BITMAP MOVEABLE PURE "bitmaps\\r58w.bmp" +Q58W BITMAP MOVEABLE PURE "bitmaps\\q58w.bmp" +K58W BITMAP MOVEABLE PURE "bitmaps\\k58w.bmp" +P64O BITMAP MOVEABLE PURE "bitmaps\\p64o.bmp" +N64O BITMAP MOVEABLE PURE "bitmaps\\n64o.bmp" +B64O BITMAP MOVEABLE PURE "bitmaps\\b64o.bmp" +R64O BITMAP MOVEABLE PURE "bitmaps\\r64o.bmp" +Q64O BITMAP MOVEABLE PURE "bitmaps\\q64o.bmp" +K64O BITMAP MOVEABLE PURE "bitmaps\\k64o.bmp" +P64S BITMAP MOVEABLE PURE "bitmaps\\p64s.bmp" +N64S BITMAP MOVEABLE PURE "bitmaps\\n64s.bmp" +B64S BITMAP MOVEABLE PURE "bitmaps\\b64s.bmp" +R64S BITMAP MOVEABLE PURE "bitmaps\\r64s.bmp" +Q64S BITMAP MOVEABLE PURE "bitmaps\\q64s.bmp" +K64S BITMAP MOVEABLE PURE "bitmaps\\k64s.bmp" +P64W BITMAP MOVEABLE PURE "bitmaps\\p64w.bmp" +N64W BITMAP MOVEABLE PURE "bitmaps\\n64w.bmp" +B64W BITMAP MOVEABLE PURE "bitmaps\\b64w.bmp" +R64W BITMAP MOVEABLE PURE "bitmaps\\r64w.bmp" +Q64W BITMAP MOVEABLE PURE "bitmaps\\q64w.bmp" +K64W BITMAP MOVEABLE PURE "bitmaps\\k64w.bmp" +P72O BITMAP MOVEABLE PURE "bitmaps\\p72o.bmp" +N72O BITMAP MOVEABLE PURE "bitmaps\\n72o.bmp" +B72O BITMAP MOVEABLE PURE "bitmaps\\b72o.bmp" +R72O BITMAP MOVEABLE PURE "bitmaps\\r72o.bmp" +Q72O BITMAP MOVEABLE PURE "bitmaps\\q72o.bmp" +K72O BITMAP MOVEABLE PURE "bitmaps\\k72o.bmp" +P72S BITMAP MOVEABLE PURE "bitmaps\\p72s.bmp" +N72S BITMAP MOVEABLE PURE "bitmaps\\n72s.bmp" +B72S BITMAP MOVEABLE PURE "bitmaps\\b72s.bmp" +R72S BITMAP MOVEABLE PURE "bitmaps\\r72s.bmp" +Q72S BITMAP MOVEABLE PURE "bitmaps\\q72s.bmp" +K72S BITMAP MOVEABLE PURE "bitmaps\\k72s.bmp" +P72W BITMAP MOVEABLE PURE "bitmaps\\p72w.bmp" +N72W BITMAP MOVEABLE PURE "bitmaps\\n72w.bmp" +B72W BITMAP MOVEABLE PURE "bitmaps\\b72w.bmp" +R72W BITMAP MOVEABLE PURE "bitmaps\\r72w.bmp" +Q72W BITMAP MOVEABLE PURE "bitmaps\\q72w.bmp" +K72W BITMAP MOVEABLE PURE "bitmaps\\k72w.bmp" +P80O BITMAP MOVEABLE PURE "bitmaps\\p80o.bmp" +N80O BITMAP MOVEABLE PURE "bitmaps\\n80o.bmp" +B80O BITMAP MOVEABLE PURE "bitmaps\\b80o.bmp" +R80O BITMAP MOVEABLE PURE "bitmaps\\r80o.bmp" +Q80O BITMAP MOVEABLE PURE "bitmaps\\q80o.bmp" +K80O BITMAP MOVEABLE PURE "bitmaps\\k80o.bmp" +P80S BITMAP MOVEABLE PURE "bitmaps\\p80s.bmp" +N80S BITMAP MOVEABLE PURE "bitmaps\\n80s.bmp" +B80S BITMAP MOVEABLE PURE "bitmaps\\b80s.bmp" +R80S BITMAP MOVEABLE PURE "bitmaps\\r80s.bmp" +Q80S BITMAP MOVEABLE PURE "bitmaps\\q80s.bmp" +K80S BITMAP MOVEABLE PURE "bitmaps\\k80s.bmp" +P80W BITMAP MOVEABLE PURE "bitmaps\\p80w.bmp" +N80W BITMAP MOVEABLE PURE "bitmaps\\n80w.bmp" +B80W BITMAP MOVEABLE PURE "bitmaps\\b80w.bmp" +R80W BITMAP MOVEABLE PURE "bitmaps\\r80w.bmp" +Q80W BITMAP MOVEABLE PURE "bitmaps\\q80w.bmp" +K80W BITMAP MOVEABLE PURE "bitmaps\\k80w.bmp" +P87O BITMAP MOVEABLE PURE "bitmaps\\p87o.bmp" +N87O BITMAP MOVEABLE PURE "bitmaps\\n87o.bmp" +B87O BITMAP MOVEABLE PURE "bitmaps\\b87o.bmp" +R87O BITMAP MOVEABLE PURE "bitmaps\\r87o.bmp" +Q87O BITMAP MOVEABLE PURE "bitmaps\\q87o.bmp" +K87O BITMAP MOVEABLE PURE "bitmaps\\k87o.bmp" +P87S BITMAP MOVEABLE PURE "bitmaps\\p87s.bmp" +N87S BITMAP MOVEABLE PURE "bitmaps\\n87s.bmp" +B87S BITMAP MOVEABLE PURE "bitmaps\\b87s.bmp" +R87S BITMAP MOVEABLE PURE "bitmaps\\r87s.bmp" +Q87S BITMAP MOVEABLE PURE "bitmaps\\q87s.bmp" +K87S BITMAP MOVEABLE PURE "bitmaps\\k87s.bmp" +P87W BITMAP MOVEABLE PURE "bitmaps\\p87w.bmp" +N87W BITMAP MOVEABLE PURE "bitmaps\\n87w.bmp" +B87W BITMAP MOVEABLE PURE "bitmaps\\b87w.bmp" +R87W BITMAP MOVEABLE PURE "bitmaps\\r87w.bmp" +Q87W BITMAP MOVEABLE PURE "bitmaps\\q87w.bmp" +K87W BITMAP MOVEABLE PURE "bitmaps\\k87w.bmp" +P95O BITMAP MOVEABLE PURE "bitmaps\\p95o.bmp" +N95O BITMAP MOVEABLE PURE "bitmaps\\n95o.bmp" +B95O BITMAP MOVEABLE PURE "bitmaps\\b95o.bmp" +R95O BITMAP MOVEABLE PURE "bitmaps\\r95o.bmp" +Q95O BITMAP MOVEABLE PURE "bitmaps\\q95o.bmp" +K95O BITMAP MOVEABLE PURE "bitmaps\\k95o.bmp" +P95S BITMAP MOVEABLE PURE "bitmaps\\p95s.bmp" +N95S BITMAP MOVEABLE PURE "bitmaps\\n95s.bmp" +B95S BITMAP MOVEABLE PURE "bitmaps\\b95s.bmp" +R95S BITMAP MOVEABLE PURE "bitmaps\\r95s.bmp" +Q95S BITMAP MOVEABLE PURE "bitmaps\\q95s.bmp" +K95S BITMAP MOVEABLE PURE "bitmaps\\k95s.bmp" +P95W BITMAP MOVEABLE PURE "bitmaps\\p95w.bmp" +N95W BITMAP MOVEABLE PURE "bitmaps\\n95w.bmp" +B95W BITMAP MOVEABLE PURE "bitmaps\\b95w.bmp" +R95W BITMAP MOVEABLE PURE "bitmaps\\r95w.bmp" +Q95W BITMAP MOVEABLE PURE "bitmaps\\q95w.bmp" +K95W BITMAP MOVEABLE PURE "bitmaps\\k95w.bmp" +P108O BITMAP MOVEABLE PURE "bitmaps\\p108o.bmp" +N108O BITMAP MOVEABLE PURE "bitmaps\\n108o.bmp" +B108O BITMAP MOVEABLE PURE "bitmaps\\b108o.bmp" +R108O BITMAP MOVEABLE PURE "bitmaps\\r108o.bmp" +Q108O BITMAP MOVEABLE PURE "bitmaps\\q108o.bmp" +K108O BITMAP MOVEABLE PURE "bitmaps\\k108o.bmp" +P108S BITMAP MOVEABLE PURE "bitmaps\\p108s.bmp" +N108S BITMAP MOVEABLE PURE "bitmaps\\n108s.bmp" +B108S BITMAP MOVEABLE PURE "bitmaps\\b108s.bmp" +R108S BITMAP MOVEABLE PURE "bitmaps\\r108s.bmp" +Q108S BITMAP MOVEABLE PURE "bitmaps\\q108s.bmp" +K108S BITMAP MOVEABLE PURE "bitmaps\\k108s.bmp" +P108W BITMAP MOVEABLE PURE "bitmaps\\p108w.bmp" +N108W BITMAP MOVEABLE PURE "bitmaps\\n108w.bmp" +B108W BITMAP MOVEABLE PURE "bitmaps\\b108w.bmp" +R108W BITMAP MOVEABLE PURE "bitmaps\\r108w.bmp" +Q108W BITMAP MOVEABLE PURE "bitmaps\\q108w.bmp" +K108W BITMAP MOVEABLE PURE "bitmaps\\k108w.bmp" +P116O BITMAP MOVEABLE PURE "bitmaps\\p116o.bmp" +N116O BITMAP MOVEABLE PURE "bitmaps\\n116o.bmp" +B116O BITMAP MOVEABLE PURE "bitmaps\\b116o.bmp" +R116O BITMAP MOVEABLE PURE "bitmaps\\r116o.bmp" +Q116O BITMAP MOVEABLE PURE "bitmaps\\q116o.bmp" +K116O BITMAP MOVEABLE PURE "bitmaps\\k116o.bmp" +P116S BITMAP MOVEABLE PURE "bitmaps\\p116s.bmp" +N116S BITMAP MOVEABLE PURE "bitmaps\\n116s.bmp" +B116S BITMAP MOVEABLE PURE "bitmaps\\b116s.bmp" +R116S BITMAP MOVEABLE PURE "bitmaps\\r116s.bmp" +Q116S BITMAP MOVEABLE PURE "bitmaps\\q116s.bmp" +K116S BITMAP MOVEABLE PURE "bitmaps\\k116s.bmp" +P116W BITMAP MOVEABLE PURE "bitmaps\\p116w.bmp" +N116W BITMAP MOVEABLE PURE "bitmaps\\n116w.bmp" +B116W BITMAP MOVEABLE PURE "bitmaps\\b116w.bmp" +R116W BITMAP MOVEABLE PURE "bitmaps\\r116w.bmp" +Q116W BITMAP MOVEABLE PURE "bitmaps\\q116w.bmp" +K116W BITMAP MOVEABLE PURE "bitmaps\\k116w.bmp" +P129O BITMAP MOVEABLE PURE "bitmaps\\p129o.bmp" +N129O BITMAP MOVEABLE PURE "bitmaps\\n129o.bmp" +B129O BITMAP MOVEABLE PURE "bitmaps\\b129o.bmp" +R129O BITMAP MOVEABLE PURE "bitmaps\\r129o.bmp" +Q129O BITMAP MOVEABLE PURE "bitmaps\\q129o.bmp" +K129O BITMAP MOVEABLE PURE "bitmaps\\k129o.bmp" +P129S BITMAP MOVEABLE PURE "bitmaps\\p129s.bmp" +N129S BITMAP MOVEABLE PURE "bitmaps\\n129s.bmp" +B129S BITMAP MOVEABLE PURE "bitmaps\\b129s.bmp" +R129S BITMAP MOVEABLE PURE "bitmaps\\r129s.bmp" +Q129S BITMAP MOVEABLE PURE "bitmaps\\q129s.bmp" +K129S BITMAP MOVEABLE PURE "bitmaps\\k129s.bmp" +P129W BITMAP MOVEABLE PURE "bitmaps\\p129w.bmp" +N129W BITMAP MOVEABLE PURE "bitmaps\\n129w.bmp" +B129W BITMAP MOVEABLE PURE "bitmaps\\b129w.bmp" +R129W BITMAP MOVEABLE PURE "bitmaps\\r129w.bmp" +Q129W BITMAP MOVEABLE PURE "bitmaps\\q129w.bmp" +K129W BITMAP MOVEABLE PURE "bitmaps\\k129w.bmp" GALACTIC BITMAP MOVEABLE PURE "bitmaps\\galactic.bmp" TIM BITMAP MOVEABLE PURE "bitmaps\\tim.bmp" -- Dimi.

1 0

spec file syntax and automated generation
by Martin Troester 19 Aug '03

19 Aug '03

Hi, apart from my desperate linking problems I mentioned in the wine-users list, I have some questions regarding the spec file for defining and wrapping exported symbols: 1. The winebuild manpage only mentions ptr, str, wstr, long and double as valid Win32 function argument size information - is the amount and kind of symbols really important, or is it just the amount of used stack space? 1a: Assuming a function taking two boolean parameters (or anything logically smaller than 32bit) like this: > void func(boolean a, boolean b) Do I specify it in the spec file as > @ stdcall func(long,long) or as > @ stdcall func(long) ? I am not too familiar with assembler, but I would assume the first is right, since two arguments are pushed on the stack, each using 32bit. 1b: What about structs? Do I have to give the size as multiples of 32bit? Assuming the following example: > typedef struct { > long var1; > double var2; > bool var3; >} test_struct; Assuming the function to be exported looks like > int test_func ( test_struct test ); Is the corresponding spec-file entry for 64bit stack space for function parameters > @ stdcall test_func(double,double) due to the fact that I just care about the absolute amount of stack-space used for the struct, or do I have to regard the size of each single member, thus pushing > @ stdcall test_func(long,double,long) on the stack? 1c: What about classes in C++-exported functions, as well as mangled names? I suppose I have to use the mangled name in the spec-file, but I am not sure about that. How do I calculate stack space for classes, or are they always put on the stack as references or pointers? If yes, I assume both take 32bit. 2. One question regarding the spec-file: The following questions arise since I wrote the .spec file myself. Is there any automation available in this field? Seems to be quite some work for several DLLs, and has a high potential to cause errors when done manually... What I did was extracting output from dumpbin for the original Win32 dll, replacing all decorated exported function names with stdcall, while using cdecl for the undecorated ones. Is this assumption right? Thanks in advance for your answers and help. Cheers, Martin--

1 0

REGRESSION: environment variables no longer possible
by Marcus Meissner 19 Aug '03

19 Aug '03

Hi, Apparently the changes from yesterday removed support of environment variables in registry keys (very useful for the "Path" keys in the "Drive" sections). Can it be readded? Or is there a rational behind it? Ciao, Marcus

1 0

Re: Spanish translation of winemine
by Marcelo Duarte 19 Aug '03

19 Aug '03

----- Original Message ----- From: "José Manuel Ferrer Ortiz" <jmfo1982(a)yahoo.es> > > > Do you plan to translate other programs and dlls > > that still they lack? > > Probably, if I have enough spare time (I'll have two > exams in September). I think about evaluating the use of all the necessary translations. When I will have this soon, I will inform you, so that you can collaborate more a little. ;) > > What is the best wine mailing list to request the > addition of the Spain's Spanish sublanguage? > wine-patches to send your patches and additions (If I understood your question).

1 0

Re: calls to int 3d corrupt the stack
by Jukka Heinonen 19 Aug '03

19 Aug '03

FPU handling got broken over half a year ago when I removed separate interrupt DLL and added support for DPMI32. Interrupt DLL made sure that builtin protected mode interrupt handlers saw regular IRET return record on stack. Current protected mode interrupt code does not provide an IRET record and real mode interrupt code never did provide it. I'm currently working on a two part fix for FPU code: 1. Make sure that DOSRELAY called via RELAY_BuildCallFrame sees original stack and code pointers and can modify them. 2. Make FPU emulation use CS/IP instead of IRET record. Both of these patches are about 10 lines of code so I guess I shall have it fixed within a week, assuming testing patches don't take up too much time. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

Fw: Fix treeview with checkboxes creation
by Marcelo Duarte 19 Aug '03

19 Aug '03

I think that a comment in the code would have been very good. ;) > ----- Original Message ----- > From: "Dmitry Timoshkov" <dmitry(a)baikal.ru> > To: "Maxime Bellengé" <maxime.bellenge(a)laposte.net> > Cc: <wine-devel(a)winehq.com> > Sent: Monday, August 18, 2003 11:42 PM > Subject: Re: Fix treeview with checkboxes creation > > > > "Maxime Bellengé" <maxime.bellenge(a)laposte.net> wrote: > > > > > - hdc = CreateCompatibleDC(0); > > > - hbm = CreateCompatibleBitmap(hdc, 48, 16); > > > > > > hbm is a 1 bit per pixel bitmap > > > > > > + hdcScreen = CreateDCA("DISPLAY", NULL, NULL, NULL); > > > + > > > + hdc = CreateCompatibleDC(hdcScreen); > > > + hbm = CreateCompatibleBitmap(hdcScreen, 48, 16); > > > > > > hbm has now a screen compliant depth > > > > You are right. Probably it's better to just replace > CreateCompatibleBitmap() > > by CreateBitmap() with the desired number of bits per pixel. In any case > > send what you see more appropriate. > > > > -- > > Dmitry. > > > > > > >

1 0

How Thread Local Storage works in WIN32 and in Visual C++
by Jonathan Wilson 19 Aug '03

19 Aug '03

This is information I have figured out and found out about how Thread Local Storage (that is, variables declared with __declspec(thread)) works in Win32 from the perspective of the exe file (as opposed to the perspective of the kernel). I am posting this to the ReactOS list since it needs support for this in its kernel code. I am posting this to the WINE list since it also should support this from a kernel point of view. Plus it should (ideally) support __declspec(thread) in WineGCC at some point if that is possible I am posting this to the MingW list since MingW needs __declspec(thread) support. First, TLS in visual C++ relies on: 1.the __declspec(thread) keyword & some special stuff the compiler does when accessing TLS variables 2.the .tls segment in the PE file 3.the IMAGE_TLS_DIRECTORY32 structure (pointed at by a field in the PE header and stored in the read only data segment) and the things it points at (specificly the TlsStart, TlsEnd and TlsIndex variables) TlsIndex is stored in the read/write data segment Tls 4.the tlssup.obj file (which is inside the Visual C++ runtime library .lib files like libc.lib and msvcrt.lib) and 5.a linker feature that will combine segments in a special way if they are named right (for example, .tls will be written first, then anything labeled .tls$ then .tls$zzz. All of them will be combined into one segment labeled .tls) Firstly, when you declare a variable as __declspec(thread), the compiler accesses it a special way. It takes the current value in the TlsIndex variable. Then it takes the value stored at offset 2C in the TEB (which contains the pointer to the TLS data area for that thread) it then does TlsPointer + TlsIndex * 4. This is what it uses when it reads and writes from Thread Local Storage variables. The first variable seems to be stored at (this address) + 4 then + 8 and so on. at (this address) is the _tls_start variable as explained below) Also, when you declare a __declspec(thread) variable, its put into the obj file inside the .tls$ segment. Most of the magic happens inside the linker. First, lets explain tlssup.obj This contains an item called __tls_used that resides in the read only data segment which then becomes the TLS directory pointed at by the PE header. This points at __tls_start which is in the .tls segment, __tls_end which is in the .tls$zzz segment and __tls_index which is in the read write data segment There is also ___xl_a and ___xl_z, ___xl_a is pointed to by the thread callbacks pointer. So, what we have in the resulting exe file is: the __tls_used variable in the read only data segment the __tls_index variable in the read write data segment and the .tls segment containing: __tls_start //all the user declared __declspec(thread) variables __tls_end And we also have ___xl_a followed by calls to the thread callback functions folowed by ___xl_z So, basicly, to implement TLS in compilers, we need to: 1.make __declspec(thread) point at the thread local storage and get the compiler to access these variables correctly. 2.make the variables all end up in the correct place in the exe file with the TLS directory pointing at the start and end of the list 3.write the needed support code for the RTL (as needed) 4.make the callbacks (if needed) get generated & output to the exe file properly and 5.make sure that the PE header points to the TLS directory. If anyone has anything to add or wants more details, do reply As for kernel-mode support in ReactOS or whatever, that seems easy enough to implement, anyone wanna have a go?

1 0

How Thread Local Storage works in WIN32 and in Visual C++
by Jonathan Wilson 19 Aug '03

19 Aug '03

This is information I have figured out and found out about how Thread Local Storage (that is, variables declared with __declspec(thread)) works in Win32 from the perspective of the exe file (as opposed to the perspective of the kernel). I am posting this to the ReactOS list since it needs support for this in its kernel code. I am posting this to the WINE list since it also should support this from a kernel point of view. Plus it should (ideally) support __declspec(thread) in WineGCC at some point if that is possible I am posting this to the MingW list since MingW needs __declspec(thread) support. First, TLS in visual C++ relies on: 1.the __declspec(thread) keyword & some special stuff the compiler does when accessing TLS variables 2.the .tls segment in the PE file 3.the IMAGE_TLS_DIRECTORY32 structure (pointed at by a field in the PE header and stored in the read only data segment) and the things it points at (specificly the TlsStart, TlsEnd and TlsIndex variables) TlsIndex is stored in the read/write data segment Tls 4.the tlssup.obj file (which is inside the Visual C++ runtime library .lib files like libc.lib and msvcrt.lib) and 5.a linker feature that will combine segments in a special way if they are named right (for example, .tls will be written first, then anything labeled .tls$ then .tls$zzz. All of them will be combined into one segment labeled .tls) Firstly, when you declare a variable as __declspec(thread), the compiler accesses it a special way. It takes the current value in the TlsIndex variable. Then it takes the value stored at offset 2C in the TEB (which contains the pointer to the TLS data area for that thread) it then does TlsPointer + TlsIndex * 4. This is what it uses when it reads and writes from Thread Local Storage variables. The first variable seems to be stored at (this address) + 4 then + 8 and so on. at (this address) is the _tls_start variable as explained below) Also, when you declare a __declspec(thread) variable, its put into the obj file inside the .tls$ segment. Most of the magic happens inside the linker. First, lets explain tlssup.obj This contains an item called __tls_used that resides in the read only data segment which then becomes the TLS directory pointed at by the PE header. This points at __tls_start which is in the .tls segment, __tls_end which is in the .tls$zzz segment and __tls_index which is in the read write data segment There is also ___xl_a and ___xl_z, ___xl_a is pointed to by the thread callbacks pointer. So, what we have in the resulting exe file is: the __tls_used variable in the read only data segment the __tls_index variable in the read write data segment and the .tls segment containing: __tls_start //all the user declared __declspec(thread) variables __tls_end And we also have ___xl_a followed by calls to the thread callback functions folowed by ___xl_z So, basicly, to implement TLS in compilers, we need to: 1.make __declspec(thread) point at the thread local storage and get the compiler to access these variables correctly. 2.make the variables all end up in the correct place in the exe file with the TLS directory pointing at the start and end of the list 3.write the needed support code for the RTL (as needed) 4.make the callbacks (if needed) get generated & output to the exe file properly and 5.make sure that the PE header points to the TLS directory. If anyone has anything to add or wants more details, do reply :) As for kernel-mode support in ReactOS or whatever, that seems easy enough to implement, anyone wanna have a go?

1 1

Anyone having problems with Alsa ?
by Sylvain Petreolle 19 Aug '03

19 Aug '03

After upgrading my alsa drivers from 0.9.4 to 0.9.6, the wine alsa driver isnt working anymore on my system. Sound is working when I use the OSS emulation with wineoss.drv. But if i use winealsa.drv, many winmm tests fail. (I attached the log) ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: Int21 : Dont reset systematically CFLAG
by Jukka Heinonen 19 Aug '03

19 Aug '03

Sylvain Petreolle wrote: > Dont reset systematically CFLAG when calling the int 21 handler. > Some functions dont change it. This patch must not be applied because it is highly likely that it will break almost all DOS programs. Fix itself is correct but before this patch can be applied it must be made sure that all functions that are supposed to reset CFLAG really reset it. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

Re: Implement registry key unloading
by Steven Edwards 18 Aug '03

18 Aug '03

> ChangeLog: > * Implement registry key unloading Speaking of the registry if you guys are interested in implementing a faster binary format for the registry take a look at what we have done in ReactOS. Eric Kohl has offered to license his work as LGPL if you guys want to try to move to the same format we use. It should be much faster then the existing system currently in WINE. Now that we have a GUI regedit for WINE and ReactOS once write support is implemented then it might be a good idea to implement this. Thanks Steven

1 0

Re: some questions (required for my dmusic work)
by John K. Hohm 18 Aug '03

18 Aug '03

> 2. I still can't figure how to implement interface that consist of two > interfaces (I have IDirectMusicLoaderStream which should consist of > IStream and IDirectMusicGetLoader). Can someone send me detailed > instructions how to do it? (I can't find any examples) I think what you want to do is implement two interfaces in one object, which is a bit different than putting two interfaces in one interface (every interface has IUnknown in it). For an example, see the implementation of the StdComponentCategoriesMgr in dlls/comcat, which might be slightly unusual because there is just one static instance rather than potentially many dynamically created instances. The implementation is broken down like this: comcat_private.h declaration of ComCatMgrImpl struct with three Vtbl pointers manager.c implementation of IUnknown, used by other interface impls too, and static ComCatMgrImpl instance, would normally be alloc'd and init'd information.c implementation of ICatInformation, partially forwards to IUnknown register.c implementation of ICatRegister, partially forwards to IUnknown There are probably other examples, but that is one I'm familiar with.

1 0

Re: Re: winevdm: can't exec
by Christian Costa 18 Aug '03

18 Aug '03

Hi, What about adding the comment in the code? :-) Bye, Christian Message du 18/08/03 12:05 De : Dmitry Timoshkov A : Dominik Strasser Copie à : wine-patches(a)winehq.com Objet : Re: winevdm: can't exec Hello, Changelog: Windows ignores values of e_cparhdr and e_crlc of the MZ header. --- cvs/hq/wine/loader/module.c Tue Jul 22 01:13:12 2003 +++ wine/loader/module.c Mon Aug 18 09:54:32 2003 @@ -200,10 +200,6 @@ * structure encompasses the "Offset to extended header" * field. */ - if ((header.mz.e_cparhdr << 4) < sizeof(IMAGE_DOS_HEADER)) - return BINARY_DOS; - if (header.mz.e_crlc && (header.mz.e_lfarlc < sizeof(IMAGE_DOS_HEADER))) - return BINARY_DOS; if (header.mz.e_lfanew < sizeof(IMAGE_DOS_HEADER)) return BINARY_DOS; if (SetFilePointer( hfile, header.mz.e_lfanew, NULL, SEEK_SET ) == -1)

1 0

exceptions
by flyker 18 Aug '03

18 Aug '03

I use __TRY __EXCEPT defined in <wine/exception.h> but i get error: undefined reference to `__wine_exception_handler(__EXCEPTION_RECORD*, __EXCEPTION_FRAME*, _CONTEXT86*, void*)' what library support this ?

2 1

Compiling winboard (GNU Chess)
by root 18 Aug '03

18 Aug '03

Hi everybody, I'm busy with compiling winboard (the win32 version of xboard -- ftp://ftp.gnu.org/pub/gnu/winboard-4_2_6-src.tar.gz ). I made this makefile based on cygwin.mak (included in the source tarball) and I ran into problem. (I changed none of the source files.) The problem is probably one of the wine header files because the compiler gives this output: winegcc -I. -mwindows -mno-cygwin -g -c -o winboard.o winboard.c In file included from /usr/local/include/wine/windows/windows.h:55, from winboard.c:54: /usr/local/include/wine/windows/mmsystem.h:69: parse-fout voor stringconstante Error: gcc failed. make: [winboard.o] Fout 2 (genegeerd) winegcc -I. -mwindows -mno-cygwin -g -c -o backend.o backend.c flex -L parser.l cp lex.yy.c parser.c winegcc -I. -mwindows -mno-cygwin -g -c -o parser.o parser.c winegcc -I. -mwindows -mno-cygwin -g -c -o moves.o moves.c winegcc -I. -mwindows -mno-cygwin -g -c -o lists.o lists.c winegcc -I. -mwindows -mno-cygwin -g -c -o gamelist.o gamelist.c winegcc -I. -mwindows -mno-cygwin -g -c -o pgntags.o pgntags.c winegcc -I. -mwindows -mno-cygwin -g -c -o wedittags.o wedittags.c In file included from /usr/local/include/wine/windows/windows.h:55, from wedittags.c:26: /usr/local/include/wine/windows/mmsystem.h:69: parse-fout voor stringconstante Error: gcc failed. make: [wedittags.o] Fout 2 (genegeerd) winegcc -I. -mwindows -mno-cygwin -g -c -o wgamelist.o wgamelist.c In file included from /usr/local/include/wine/windows/windows.h:55, from wgamelist.c:26: /usr/local/include/wine/windows/mmsystem.h:69: parse-fout voor stringconstante Error: gcc failed. make: [wgamelist.o] Fout 2 (genegeerd) winegcc -I. -mwindows -mno-cygwin -g -c -o zippy.o zippy.c winegcc -I. -mwindows -mno-cygwin -g -c -o wsockerr.o wsockerr.c res --use-temp-file winboard.rc -O coff -o wbres.o make: res: Commando niet gevonden make: [wbres.o] Fout 127 (genegeerd) winegcc -I. -mwindows -mno-cygwin -g -c -o wclipbrd.o wclipbrd.c In file included from /usr/local/include/wine/windows/windows.h:55, from wclipbrd.c:26: /usr/local/include/wine/windows/mmsystem.h:69: parse-fout voor stringconstante Error: gcc failed. make: [wclipbrd.o] Fout 2 (genegeerd) winegcc -I. -mwindows -mno-cygwin -g -c -o woptions.o woptions.c In file included from /usr/local/include/wine/windows/windows.h:55, from woptions.c:26: /usr/local/include/wine/windows/mmsystem.h:69: parse-fout voor stringconstante Error: gcc failed. make: [woptions.o] Fout 2 (genegeerd) winegcc -I. -mwindows -mno-cygwin -mwindows -Xlinker "-e" -Xlinker "_mainCRTStartup" -g -mno-cygwin winboard.o backend.o parser.o moves.o lists.o gamelist.o pgntags.o wedittags.o wgamelist.o zippy.o wsockerr.o wbres.o wclipbrd.o woptions.o \ -lwsock32 -lcomctl32 -lwinmm -lkernel32 \ -ladvapi32 -luser32 -lgdi32 -lcomdlg32 -lwinspool \ -o winboard.exe gcc: -e: linker input file unused because linking not done gcc: _mainCRTStartup: linker input file unused because linking not done Error: Can n��lllllll Error: /usr/local/bin/winewrap failed. make: [winboard.exe] Fout 2 (genegeerd) [root@erwin winboard]# ock32 -lcomctl32 -lwinmm -lkernel32 \ > -ladvapi32 -luser32 -lgdi32 -lcomdlg32 -lwinspool \ > -o winboard.exe bash: ock32: command not found [root@erwin winboard]# gcc: -e: linker input file unused because linking not done bash: gcc:: command not found [root@erwin winboard]# gcc: _mainCRTStartup: linker input file unused because linking not done bash: gcc:: command not found [root@erwin winboard]# Error: Can n��lllllll bash: Error:: command not found [root@erwin winboard]# Error: /usr/local/bin/winewrap failed. bash: Error:: command not found [root@erwin winboard]# make: [winboard.exe] Fout 2 (genegeerd) As you can clearly see, some of the files compile correctly but 5 files have a problem with a header file called mmsystem.h. If anyone can fix this we have another program for the Fun Projects page :). -- E.C.F. Wolff

1 0

Quick license question
by Jason Edmeades 18 Aug '03

18 Aug '03

I know this has been asked in the past, but whats the deal in using GPL code in wine (which is LGPL)? Can it be used or is it something to completely avoid? Jason

2 1

Int21 : Dont reset systematically CFLAG
by Sylvain Petreolle 17 Aug '03

17 Aug '03

Dont reset systematically CFLAG when calling the int 21 handler. Some functions dont change it. ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: wine/ scheduler/pthread.c dlls/ntdll/sysdeps.c
by Rein Klazes 17 Aug '03

17 Aug '03

On Tue, 12 Aug 2003 13:59:13 -0500, you wrote: > ChangeSet ID: 8958 > CVSROOT: /home/winehq/opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2003/08/12 13:59:13 > > Modified files: > scheduler : pthread.c > dlls/ntdll : sysdeps.c > > Log message: > Fixed the pthread wrappers to work with the new glibc/linuxthreads > interface in glibc 2.3.2. > This causes thread related failures on my Debian unstable system using glibc 2.3.2 (nptl not enabled). For example his is Agent after calling WSAAsyncGetHostByName: | Unhandled exception: page fault on read access to 0xdbdbdbe3 in 32-bit code (0x402ddfaa). | In 32-bit mode. | 0x402ddfaa (NTDLL.DLL.memcpy+0x65fe6 in libc.so.6): testb $0x1,0x8(%eax) | Wine-dbg>bt | Backtrace: | =>0 0x402ddfaa (NTDLL.DLL.memcpy+0x65fe6 in libc.so.6) (ebp=42302e38) | 1 0x402e0195 (NTDLL.DLL.memcpy+0x681d1 in libc.so.6) (ebp=42302e98) | 2 0x4175b8d7 (_async_queryfun+0x1d3(arg=0x4041e480) [async.c:401] in ws2_32.dll.so) (ebp=42302f14) | 3 0x400a0e93 (THREAD_Start+0xd3 [thread.c:1622] in libntdll.dll.so) (ebp=42302fe0) | 4 0x400ba9e3 (SYSDEPS_StartThread+0x27(teb=0x42303000) [sysdeps.c:154] in libntdll.dll.so) (ebp=42302ff4) | 5 0x402cf217 (NTDLL.DLL.memcpy+0x57253 in libc.so.6) (ebp=00000000) (it crashes inside gethostbyname(), without obvious reason). Debugging hints are most welcome. Rein. -- Rein Klazes rklazes(a)xs4all.nl

2 2

Re: calls to int 3d corrupt the stack
by Sylvain Petreolle 17 Aug '03

17 Aug '03

> interrupt handling, as perhaps they affected the EIP that the interrupt > handlers get, making it point before the int instruction instead of > after. Robert Coeyman's code assumes the latter (after the int, > requiring the subtraction), and that's what's happen in real DOS/Win16 > to my knowledge, so I'd say the interrupt handling is what needs to > be fixed, not this code. Do you think that we get a wrong return point ? > Real mode, being 16-bit, uses word stack, not dword. Thanks for this correction. ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

calls to int 3d corrupt the stack
by Sylvain Petreolle 17 Aug '03

17 Aug '03

Actual implementation of the int 3d call (Standalone FWAIT) is to patch the code to an fwait(9b) and a noop(90). It seems that it corrupts the stack in FPU_ModifyCode and prevents vb3 programs to start. (tests made with current CVS) Since we do nothing apart an emulated fwait, I commented the call to FPU_ModifyCode. The call to int3d is equal to nothing and makes vb3 programs start : dlls/winedos/fpu.c : 188 TRACE("Int 0x3d called-- Standalone FWAIT"); /* FPU_ModifyCode(context, 0x90); */ Does it seems to you its the correct way to proceed and will it be valid in all cases ? ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 4

Nothing reported for missing fonts
by Christian Costa 17 Aug '03

17 Aug '03

Hi, I recently configured Wine to use new fake Windows directories and I forgot to copy the font files from Windows. Nothing was reported and some apps displayed unreadable characters. Is there a way to report an error when an app tries to used missing fonts ? That would help users I think. :-) Just a though... :-) Bye, Christian

1 0

Re: winevdm: can't exec
by Dominik.Strasser＠t-online.de 17 Aug '03

17 Aug '03

The attached patch hacks^H^H^H^H^Hfixes this problem. Obviously, this binary doesn't contain a valid PE header. OTOH it seems to be a valid Windows binary (I haven't checked it myself). Maybe somebody with a more deep insight into this can come up with a better fix. Regards Dominik ChangeLog: Dominik Strasser: return Win32 binary istead of DOS binary if no valid header found Index: loader/module.c =================================================================== RCS file: /home/wine/wine/loader/module.c,v retrieving revision 1.186 diff -u -3 -p -u -r1.186 module.c --- loader/module.c 21 Jul 2003 20:02:50 -0000 1.186 +++ loader/module.c 16 Aug 2003 08:30:07 -0000 @@ -201,7 +201,7 @@ enum binary_type MODULE_GetBinaryType( H * field. */ if ((header.mz.e_cparhdr << 4) < sizeof(IMAGE_DOS_HEADER)) - return BINARY_DOS; + return BINARY_PE_EXE; if (header.mz.e_crlc && (header.mz.e_lfarlc < sizeof(IMAGE_DOS_HEADER))) return BINARY_DOS; if (header.mz.e_lfanew < sizeof(IMAGE_DOS_HEADER))

2 4

Re: wrong keyboard layout
by Dmitry Timoshkov 17 Aug '03

17 Aug '03

"Raul" <zombi82(a)hot.ee> wrote: > in xev knows perfectly all my keyboard layout > > but still wine dont know any of my AltGR chars > when i remove all the AltGr chars then it works perfectly > then disapears the fixme and > all my ¨¸ get work > > is there something wrong when i submit the layout whitout the Alt Gr chars? If that really makes a difference for you, yes. -- Dmitry.

1 0

Re: cab_G_00-pre1 (RFC)
by Alexandre Julliard 17 Aug '03

17 Aug '03

"Gregory M. Turner" <gmturner007(a)ameritech.net> writes: > Would love to hear if I have not done things in a properly > "SETUPAPI" way, i.e., am I supposed to be performing certain > logging or memory allocation rituals, anything like that? One ritual is that you should not use msvcrt from other dlls, this will cause trouble with apps that use the Unix libc. -- Alexandre Julliard julliard(a)winehq.com

4 9

Re: Spanish translation of winemine
by Marcelo Duarte 17 Aug '03

17 Aug '03

Please, see http://www.winehq.com/site/sending_patches especially: "cvs diff will always ignore newly added files, so you'll need to do something like: diff -u /dev/null newfile.c >> patch.diff to make a patch for newly added files. " Do you plan to translate other programs and dlls that still they lack? ----- Original Message ----- From: "José Manuel Ferrer Ortiz" <jmfo1982(a)yahoo.es> To: <wine-patches(a)winehq.com> Sent: Friday, August 15, 2003 3:40 PM Subject: Spanish translation of winemine > Hi, I've translated the winemine program into Spanish, > since it was only translated into English and > Portuguese. > > You can find the translation in the file Es.rc and you > should apply too the patch in the other file in order > to include that translation (and maybe something in > the Makefile.in to inform about the new file in the > tree). > > Regards, > José Manuel > > ___________________________________________________ > Yahoo! Messenger - Nueva versión GRATIS > Super Webcam, voz, caritas animadas, y más... > http://messenger.yahoo.es ---------------------------------------------------------------------------- ---- > Only in .: Es.rc > Only in .: Makefile > diff -u /home/jose/wine-20030813/programs/winemine/rsrc.rc ./rsrc.rc > --- /home/jose/wine-20030813/programs/winemine/rsrc.rc Mon Jun 23 20:15:15 2003 > +++ ./rsrc.rc Fri Aug 15 18:32:40 2003 > @@ -23,6 +23,7 @@ > #include "resource.h" > > #include "En.rc" > +#include "Es.rc" > #include "Pt.rc" > > LANGUAGE LANG_NEUTRAL,SUBLANG_NEUTRAL > ---------------------------------------------------------------------------- ---- > /* > * WineMine > * Spanish Language Support > * > * Copyright 2003 José Manuel Ferrer Ortiz <jmfo1982(a)yahoo.es> > * > * This library is free software; you can redistribute it and/or > * modify it under the terms of the GNU Lesser General Public > * License as published by the Free Software Foundation; either > * version 2.1 of the License, or (at your option) any later version. > * > * This library is distributed in the hope that it will be useful, > * but WITHOUT ANY WARRANTY; without even the implied warranty of > * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > * Lesser General Public License for more details. > * > * You should have received a copy of the GNU Lesser General Public > * License along with this library; if not, write to the Free Software > * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA > */ > > LANGUAGE LANG_SPANISH, SUBLANG_DEFAULT > > STRINGTABLE { > IDS_APPNAME, "WineMine" > > } > > MENU_WINEMINE MENU DISCARDABLE > { > POPUP "&Opciones" { > MENUITEM "&Nuevo", IDM_NEW > MENUITEM SEPARATOR > MENUITEM "&Interrogación", IDM_MARKQ > MENUITEM SEPARATOR > MENUITEM "&Principiante", IDM_BEGINNER > MENUITEM "&Avanzado", IDM_ADVANCED > MENUITEM "&Experto", IDM_EXPERT > MENUITEM "P&ersonalizado", IDM_CUSTOM > MENUITEM SEPARATOR > MENUITEM "&Salir", IDM_EXIT > } > POPUP "&Ayuda" { > MENUITEM "&Mejores tiempos", IDM_TIMES > MENUITEM "&Acerca de", IDM_ABOUT > } > } > > DLG_TIMES DIALOG DISCARDABLE 0, 0, 160, 80 > STYLE DS_MODALFRAME | DS_3DLOOK | > WS_VISIBLE | WS_CAPTION | WS_SYSMENU | WS_POPUP > CAPTION "Mejores tiempos" > { > GROUPBOX "Mejores tiempos", IDIGNORE, 10, 10, 140, 45 > LTEXT "Principiante", IDIGNORE, 20, 20, 40, 8 > LTEXT "Avanzado", IDIGNORE, 20, 30, 40, 8 > LTEXT "Experto", IDIGNORE, 20, 40, 40, 8 > LTEXT "999", IDC_TIME1, 70, 20, 15, 8 > LTEXT "999", IDC_TIME2, 70, 30, 15, 8 > LTEXT "999", IDC_TIME3, 70, 40, 15, 8 > LTEXT "", IDC_NAME1, 90, 20, 55, 8 > LTEXT "", IDC_NAME2, 90, 30, 55, 8 > LTEXT "", IDC_NAME3, 90, 40, 55, 8 > DEFPUSHBUTTON "Aceptar", IDOK, 55, 60, 50, 15 > } > > DLG_CONGRATS DIALOG DISCARDABLE 0, 0, 160, 60 > STYLE DS_MODALFRAME | DS_3DLOOK | > WS_VISIBLE | WS_CAPTION | WS_SYSMENU | WS_POPUP > CAPTION "¡Enhorabuena!" > { > LTEXT "Por favor, introduzca su nombre", IDIGNORE, 10, 10, 150, 10 > EDITTEXT IDC_EDITNAME, 25, 20, 110, 12 > DEFPUSHBUTTON "Aceptar", IDOK, 60, 40, 40, 15 > } > > DLG_CUSTOM DIALOG DISCARDABLE 0, 0, 100, 100 > STYLE DS_MODALFRAME | DS_3DLOOK | > WS_VISIBLE | WS_CAPTION | WS_SYSMENU | WS_POPUP > CAPTION "Juego personalizado" > { > LTEXT "Filas", IDIGNORE, 5, 5, 30, 10 > LTEXT "Columnas", IDIGNORE, 5, 35, 30, 10 > LTEXT "Minas", IDIGNORE, 5, 65, 30, 10 > EDITTEXT IDC_EDITROWS, 5, 15, 20, 12, ES_NUMBER > EDITTEXT IDC_EDITCOLS, 5, 45, 20, 12, ES_NUMBER > EDITTEXT IDC_EDITMINES, 5, 75, 20, 12, ES_NUMBER > DEFPUSHBUTTON "Aceptar", IDOK, 40, 30, 50, 15 > PUSHBUTTON "Cancelar", IDCANCEL, 40, 50, 50, 15 > } > > DLG_ABOUT DIALOG DISCARDABLE 0, 0, 145, 80 > STYLE DS_MODALFRAME | DS_3DLOOK | > WS_VISIBLE | WS_CAPTION | WS_SYSMENU | WS_POPUP > CAPTION "Acerca de" > { > LTEXT "Winemine", IDIGNORE, 10, 10, 35, 10 > LTEXT "Copyright 2000, Joshua Thielen", IDIGNORE, 35, 25, 100, 10 > LTEXT "bajo la licencia de Wine", IDIGNORE, 35, 35, 100, 10 > ICON "WINEMINE", IDIGNORE, 10, 25, 20, 20 > DEFPUSHBUTTON "Aceptar", IDOK, 50, 60, 55, 15 > } >

1 0

make crosstest broken?
by Jakob Eriksson 17 Aug '03

17 Aug '03

"make crosstest" seems broken on Debian 3.0 Or is it me? Please give some feedback if you have any. There is a bug filed on http://bugs.winehq.com/show_bug.cgi?id=1602 Tried it on wine-20030813. regards, Jakob ----------------------------------------------- i586-mingw32msvc-dlltool -k -l libwintrust.a -d wintrust/wintrust.spec.def i586-mingw32msvc-dlltool -k -l libwnaspi32.a -d winaspi/wnaspi32.spec.def i586-mingw32msvc-dlltool -k -l libwow32.a -d wow32/wow32.spec.def i586-mingw32msvc-dlltool -k -l libws2_32.a -d winsock/ws2_32.spec.def i586-mingw32msvc-dlltool -k -l libwsock32.a -d wsock32/wsock32.spec.def i586-mingw32msvc-dlltool -k -l libx11drv.a -d x11drv/x11drv.spec.def make[2]: Entering directory `/home/jakov/src/Wine/wine-20030813/dlls/advapi32' make[3]: Entering directory `/home/jakov/src/Wine/wine-20030813/dlls/advapi32/tests' i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o registry.cross.o registry.c cc1: warning: -fPIC ignored for target (all code is position independent) i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o testlist.cross.o testlist.c cc1: warning: -fPIC ignored for target (all code is position independent) i586-mingw32msvc-gcc registry.cross.o testlist.cross.o -o advapi32_crosstest.exe -ladvapi32 -lkernel32 -lntdll -lm /usr/lib/gcc-lib/i586-mingw32msvc/2.95.3-7/../../../../i586-mingw32msvc/bin/ld: cannot find -lntdll make[3]: *** [advapi32_crosstest.exe] Error 1 make[3]: Leaving directory `/home/jakov/src/Wine/wine-20030813/dlls/advapi32/tests' make[2]: *** [tests/__crosstest__] Error 2 make[2]: Leaving directory `/home/jakov/src/Wine/wine-20030813/dlls/advapi32' make[1]: *** [advapi32/__crosstest__] Error 2 make[1]: Leaving directory `/home/jakov/src/Wine/wine-20030813/dlls' make: *** [dlls/__crosstest__] Error 2 jakov@vmlinux:~/src/Wine/wine-20030813

1 0

Re: dlopen libncurses.so in wineconsole (take 3)
by Dimitrie O. Paun 16 Aug '03

16 Aug '03

On August 14, 2003 10:00 pm, Mike McCormack wrote: > +#ifdef HAVE_NCURSES_H > + char *ncname = SONAME_LIBNCURSES; > +#else > + char *ncname = SONAME_LIBCURSES; > +#endif Since we're doing this dynamically, shouldn't we also determine at runtime if we should use ncurses or curses? It would make a lot more sense, as we typically compile on one box, and run on another... -- Dimi.

2 1

API DB - import / export tables by dll
by Dave Miller 16 Aug '03

16 Aug '03

I am making tables which show all APIs exported / imported by a given dll in each version of windows. They are on the same page as the form which does the queries. http://24.229.94.2 Is there anything in the wine spec or source files I can parse to find out what APIs a wine dll imports? Right now in my tables wine dlls don't import anything. :(

1 0

some questions (required for my dmusic work)
by Rok Mandeljc 16 Aug '03

16 Aug '03

I think I've finally figured how dmusic work (especially loading, object and track interfaces). I'll send all my work next week or one after it, but there are still some big flaws I'd like to fix before. 1. I've splitted dmusic debug channel into dmusic, dmusic32, dmband, dmstyle, dmime, etc. and now I'd like to have debug channel dmusicall which will turn all dm* debug channel on (something like debugchannel "all"). Can someone tell me how "all" is defined? 2. I still can't figure how to implement interface that consist of two interfaces (I have IDirectMusicLoaderStream which should consist of IStream and IDirectMusicGetLoader). Can someone send me detailed instructions how to do it? (I can't find any examples) -- Rok Mandeljc <rok.mandeljc(a)gimb.org> "Hold your position! Leave doubt for the dying!" -- Tahngarth of the Weatherlight

1 0

Re: Another problem wih Charlie's Angels
by Dominik.Strasser＠t-online.de 16 Aug '03

16 Aug '03

Hi, attached you find a patch which imporves the compiled-in loadorder detection a little bit. It adds a "win16" flag which states whether the module under scrutiny is a reserved name under Win16, only. Surely some more of the names in the default_loadorder should be marked alike. I am not sure which ones should be changed here. Who can help ? Dominik ChangeLog: Dominik Strasser: add a flag to distinguish reserved names between Win16 and Win32 in default loadorder Index: loader/loadorder.c =================================================================== RCS file: /home/wine/wine/loader/loadorder.c,v retrieving revision 1.63 diff -u -3 -p -u -r1.63 loadorder.c --- loader/loadorder.c 27 Apr 2003 00:40:23 -0000 1.63 +++ loader/loadorder.c 16 Aug 2003 08:38:04 -0000 @@ -41,6 +41,7 @@ WINE_DEFAULT_DEBUG_CHANNEL(module); typedef struct module_loadorder { const char *modulename; + int win16_flag; enum loadorder_type loadorder[LOADORDER_NTYPES]; } module_loadorder_t; @@ -55,36 +56,36 @@ struct loadorder_list /* the list must remain sorted by dll name */ static module_loadorder_t default_order_list[] = { - { "display", { LOADORDER_BI, 0, 0 } }, - { "gdi.exe", { LOADORDER_BI, 0, 0 } }, - { "gdi32", { LOADORDER_BI, 0, 0 } }, - { "icmp", { LOADORDER_BI, 0, 0 } }, - { "kernel", { LOADORDER_BI, 0, 0 } }, - { "kernel32", { LOADORDER_BI, 0, 0 } }, - { "keyboard", { LOADORDER_BI, 0, 0 } }, - { "krnl386.exe", { LOADORDER_BI, 0, 0 } }, - { "mmsystem", { LOADORDER_BI, 0, 0 } }, - { "mouse", { LOADORDER_BI, 0, 0 } }, - { "ntdll", { LOADORDER_BI, 0, 0 } }, - { "odbc32", { LOADORDER_BI, 0, 0 } }, - { "system", { LOADORDER_BI, 0, 0 } }, - { "toolhelp", { LOADORDER_BI, 0, 0 } }, - { "ttydrv", { LOADORDER_BI, 0, 0 } }, - { "user.exe", { LOADORDER_BI, 0, 0 } }, - { "user32", { LOADORDER_BI, 0, 0 } }, - { "w32skrnl", { LOADORDER_BI, 0, 0 } }, - { "winaspi", { LOADORDER_BI, 0, 0 } }, - { "winedos", { LOADORDER_BI, 0, 0 } }, - { "wineps", { LOADORDER_BI, 0, 0 } }, - { "wing", { LOADORDER_BI, 0, 0 } }, - { "winmm", { LOADORDER_BI, 0, 0 } }, - { "winsock", { LOADORDER_BI, 0, 0 } }, - { "wnaspi32", { LOADORDER_BI, 0, 0 } }, - { "wow32", { LOADORDER_BI, 0, 0 } }, - { "wprocs", { LOADORDER_BI, 0, 0 } }, - { "ws2_32", { LOADORDER_BI, 0, 0 } }, - { "wsock32", { LOADORDER_BI, 0, 0 } }, - { "x11drv", { LOADORDER_BI, 0, 0 } } + { "display", 0, { LOADORDER_BI, 0, 0 } }, + { "gdi.exe", 0, { LOADORDER_BI, 0, 0 } }, + { "gdi32", 0, { LOADORDER_BI, 0, 0 } }, + { "icmp", 0, { LOADORDER_BI, 0, 0 } }, + { "kernel", 0, { LOADORDER_BI, 0, 0 } }, + { "kernel32", 0, { LOADORDER_BI, 0, 0 } }, + { "keyboard", 0, { LOADORDER_BI, 0, 0 } }, + { "krnl386.exe", 0, { LOADORDER_BI, 0, 0 } }, + { "mmsystem", 0, { LOADORDER_BI, 0, 0 } }, + { "mouse", 0, { LOADORDER_BI, 0, 0 } }, + { "ntdll", 0, { LOADORDER_BI, 0, 0 } }, + { "odbc32", 0, { LOADORDER_BI, 0, 0 } }, + { "system", 1, { LOADORDER_BI, 0, 0 } }, + { "toolhelp", 0, { LOADORDER_BI, 0, 0 } }, + { "ttydrv", 0, { LOADORDER_BI, 0, 0 } }, + { "user.exe", 0, { LOADORDER_BI, 0, 0 } }, + { "user32", 0, { LOADORDER_BI, 0, 0 } }, + { "w32skrnl", 0, { LOADORDER_BI, 0, 0 } }, + { "winaspi", 0, { LOADORDER_BI, 0, 0 } }, + { "winedos", 0, { LOADORDER_BI, 0, 0 } }, + { "wineps", 0, { LOADORDER_BI, 0, 0 } }, + { "wing", 0, { LOADORDER_BI, 0, 0 } }, + { "winmm", 0, { LOADORDER_BI, 0, 0 } }, + { "winsock", 0, { LOADORDER_BI, 0, 0 } }, + { "wnaspi32", 0, { LOADORDER_BI, 0, 0 } }, + { "wow32", 0, { LOADORDER_BI, 0, 0 } }, + { "wprocs", 0, { LOADORDER_BI, 0, 0 } }, + { "ws2_32", 0, { LOADORDER_BI, 0, 0 } }, + { "wsock32", 0, { LOADORDER_BI, 0, 0 } }, + { "x11drv", 0, { LOADORDER_BI, 0, 0 } } }; static const struct loadorder_list default_list = @@ -300,7 +301,7 @@ static BOOL AddLoadOrder(module_loadorde */ static BOOL AddLoadOrderSet(char *key, char *order) { - module_loadorder_t ldo; + module_loadorder_t ldo = { 0 }; char *cptr; /* Parse the loadorder before the rest because strtok is not reentrant */ @@ -362,7 +363,7 @@ void MODULE_AddLoadOrderOption( const ch * default lists. */ static BOOL get_list_load_order( const char *module, const struct loadorder_list *list, - enum loadorder_type lo[] ) + enum loadorder_type lo[], int win32_flag ) { module_loadorder_t tmp, *res = NULL; @@ -370,7 +371,7 @@ static BOOL get_list_load_order( const c /* some bsearch implementations (Solaris) are buggy when the number of items is 0 */ if (list->count && (res = bsearch(&tmp, list->order, list->count, sizeof(list->order[0]), cmp_sort_func))) memcpy( lo, res->loadorder, sizeof(res->loadorder) ); - return (res != NULL); + return (res != NULL) && !(win32_flag && res->win16_flag); } @@ -591,7 +592,7 @@ void MODULE_GetLoadOrder( enum loadorder } /* check command-line first */ - if (get_list_load_order( module+1, &cmdline_list, loadorder )) + if (get_list_load_order( module+1, &cmdline_list, loadorder, 0 )) { TRACE( "got cmdline %s for %s\n", debugstr_loadorder(loadorder), debugstr_a(path) ); @@ -650,7 +651,7 @@ void MODULE_GetLoadOrder( enum loadorder } /* then base name matching compiled-in defaults */ - if (get_list_load_order( basename, &default_list, loadorder )) + if (get_list_load_order( basename, &default_list, loadorder, win32 )) { TRACE( "got compiled-in default %s for %s\n", debugstr_loadorder(loadorder), debugstr_a(path) );

1 0

Re: Sync(1): include/winerror.h
by Alexandre Julliard 16 Aug '03

16 Aug '03

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > This patch casts hresult errors into HRESULTs as per the native > headers. The native headers don't have a _HR_() macro, so we shouldn't have one either. Please do normal casts instead. -- Alexandre Julliard julliard(a)winehq.com

2 1

Translating wine programs
by puoti＠inwind.it 16 Aug '03

16 Aug '03

I've started with an easy thing, the wine clock, please let me know if I've done this properly.

2 1

Translating wine programs
by puoti＠inwind.it 15 Aug '03

15 Aug '03

I would like to add an italian translation to the wine programs that lack it, can I write it.rc and add # include it.rc to the rc file that contains the language includes? Let me know if this is the correct thing to do, and if yes I'll send in a few diffs.

1 0

Re: Profiler (take 4)
by Dimitrie O. Paun 15 Aug '03

15 Aug '03

On August 15, 2003 01:37 am, Mike McCormack wrote: > Profiles are generated in /tmp/wmon.out.<pid>, and can be examined with > the wprof tool from wine/libs/wprof/wprof. Nice, but should this tool reside in wine/tools/... instead? Also, for consistency with all the other stuff we're doing, shouldn't it be called wineprof? -- Dimi.

1 0

[D3D] New errors on gta3
by root 15 Aug '03

15 Aug '03

Hi everyone, The latest CVS shows this error on GTA3. Although it is an improvement since it doesn't crash into the debugger, but instead it just stops. It generated (after a long list of IDirect3D8Impl_CheckDeviceFormat fixme's) this output: fixme:d3d:IDirect3D8Impl_CheckDeviceFormat (0x405b21a0)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), AdptFmt:(23,D3DFMT_R5G6B5), Use:(0,none), ResTyp:(3,D3DRTYPE_TEXTURE), CheckFmt:(41,D3DFMT_P8)) fixme:d3d:IDirect3D8Impl_CheckDeviceFormat (0x405b21a0)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), AdptFmt:(23,D3DFMT_R5G6B5), Use:(0,none), ResTyp:(3,D3DRTYPE_TEXTURE), CheckFmt:(41,D3DFMT_P8)) fixme:d3d:IDirect3DDevice8Impl_SetPaletteEntries (0x40660b10) : setting p[40] <= RGBA(f8,b1,00,ff) fixme:system:SystemParametersInfoA Unimplemented action: 86 (SPI_SETPOWEROFFACTIVE) fixme:system:SystemParametersInfoA Unimplemented action: 85 (SPI_SETLOWPOWERACTIVE) fixme:system:SystemParametersInfoA Unimplemented action: 59 (SPI_SETSTICKYKEYS) I'm now looking for a game that shows the same output but has a demo for download. -- E. C. F. Wolff

1 0

Re: 5 Wine-Tests fail on FreeBSD 5.1
by Eric Pouech 15 Aug '03

15 Aug '03

>>I think more that's a discrepency in OSS handling between linux & *BSD >>(or a more subtle bug somewhere) >>could you rerun with WINEOPTIONS="-debugmsg +wave,+dsound,+wavemap" back from vacation... the trace only shows a decent startup and a wait for incoming audio packets, which never show up. > Let's take this further. I wrote to you/this list, about winedbg > crashing on startup _every_time_. And I suspect it's this TEB thingy (I > have no clue what a TEB is, but I really think something is broken > there). a TEB is a thread environment block: a user land structure describing a thread status. TEB is usually stored in a page, which is pointer by the fs register. there's a field in the TEB which holds its linear address. Hence, getting the linear address of a TEB is written fs:0x18. Thread commutation (from a scheduler point of view) is (almost as simple as) changing the value of fs (there's also stack switching, context switching...). Anyway, your back trace information don't absolutely show that the TEB get screwed up. Since getting the TEB linear address is inlined, gdb sure has a hard time getting the value from the stack (as it may get overwritten by upper calls). It doesn't mean however that TEB doesn't get overwritten. In gdb, you should check: 1/ at thread startup, where TEB is located, and which is the value of fs. 2/ on each lookup, check if fs value changed, and if TEB struct at address gotten from 1/ is still ok. You would want also to check that LDT entry for fs is still correct. > Now back to "wine winedbg winemine". it should be run as winedbg winemine > wait4: Interrupted system call > wait4: Interrupted system call <this line gets repeated every 1-4 seconds> does this help ? Index: ptrace.c =================================================================== RCS file: /home/cvs/cvsroot/wine/wine/server/ptrace.c,v retrieving revision 1.26 diff -u -u -r1.26 ptrace.c --- ptrace.c 6 May 2003 00:21:21 -0000 1.26 +++ ptrace.c 15 Aug 2003 12:38:14 -0000 @@ -149,6 +149,7 @@ thread->unix_tid = -1; thread->attached = 0; } + else if (errno == EINTR) continue; else perror( "wait4" ); return 0; } A+ -- Eric Pouech

1 0

Re: Fix for treeview
by Martin Fuchs 15 Aug '03

15 Aug '03

On Wed 13. August 2003 14:58, Maxime Bellengé wrote: > In TREEVIEW_UpdateDispInfo, a test is made to determine if the property > we want to change is handled by a callback. If so, the change is > dropped. > But that test was done incorrectly. > > Now the treeview in the statistical page of eMule displays correctly. > > Changelog: > * Fix for TREEVIEW_UpdateDispInfo to test with the correct > callbackMask This patch, which is now commited leads to problems for me. Now the labels in the tree fiew of some explorer test programs remain empty. May be this callback mask has to adjusted at some more points in the code. But I don't know, what it's used exactly for. Anyone any ideas? -- Martin Fuchs martin-fuchs(a)gmx.net

2 3

Problem with wcmd in wineconsole ?
by Sylvain Petreolle 15 Aug '03

15 Aug '03

Using dos32a (free replacement of dos4gw) with wineconsole, I dont get any text output from it under wcmd. With wine in an xterm , i get a normal output: [syl@snoop c]$ wine --debugmsg err-all,fixme-all dos32a Warning: unprotecting the first 64KB of memory to allow real-mode calls. NULL pointer accesses will no longer be caught. DOS/32A -- Protected Mode Run-time Version 7.2 Copyright (C) Supernar Systems, Ltd. 1996-2002 DOS/32A fatal (8001): syntax is DOS32A <execname.xxx> Running 'wineconsole dos32a' is ok too, but it doesnt give the ability to read/copy the messages from the program you run. Failing part : [syl@snoop c]$ wineconsole -- --backend=user wcmd loads ok, internal commands are giving output. But when I try to run dos32a, I have no output : WCMD Version 0.17 C:\>echo internal command test internal command test C:\>dos32a C:\> I made the test with --debugmsg +int, and it should output text : ... trace:int:DOSVM_PutChar char: 0x44(D) trace:int:DOSVM_PutChar char: 0x4f(O) trace:int:DOSVM_PutChar char: 0x53(S) trace:int:DOSVM_PutChar char: 0x2f(/) ... The full log is attached (wineconsole --debugmsg +int -- --backend=user wcmd) Comments ? ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 1

"Cybersquat" ?
by PETREOLLE Sylvain 15 Aug '03

15 Aug '03

I noticed a curious thing when trying to access the AppDB today. Using IE (didnt make test with other browser), entering "appdb.winehq.org" without the htpp:// takes me to a site called "http://appdb.winehq.org.com". Has someone of the wine team done anything to own this URL ?

5 4

Re: wine/ windows/winproc.c windows/win.c windows/ ...
by Dimitrie O. Paun 15 Aug '03

15 Aug '03

On August 12, 2003 07:50 pm, Alexandre Julliard wrote: > Allocate DebugInfo field for all critical sections (based on a > patch by Alex Pasadyn). > Get rid of the Wine-specific CRITICAL_SECTION_INIT macro. +static CRITICAL_SECTION_DEBUG critsect_debug = +{ + 0, 0, &winproc_cs, + { &critsect_debug.ProcessLocksList, &critsect_debug.ProcessLocksList }, + 0, 0, { 0, (DWORD)(__FILE__ ": winproc_cs") } +}; Can we use the C99 initializers, like they do in the Linux kernel? I think they'll do a better job in this case. This one looks a bit too cryptic for me. -- Dimi.

2 1

RPM for Red Hat 7.3
by William M. Quarles 15 Aug '03

15 Aug '03

Is it possible that you could continue building and distributing packages for Red Hat 7.3? A lot of people are still using it, and I was able to build your "RH8" source rpm just fine on an RH 7.3 system -- William M. Quarles quarlewm(a)jmu.edu wquarles(a)bucknell.edu walrus(a)bellsouth.net

3 4

Re: GTA3 crash :( -- RedHat 9
by Ann and Jason Edmeades 14 Aug '03

14 Aug '03

I dont think GTA3 has ever worked yet as it uses palettes and I dont recall us ever finishing it (Raphael is the one to ask). However, try commenting out the line in directx.c : object->visInfo = glXChooseVisual(object->display, DefaultScreen(object->display), dblBuf); This has caused problems on some manufacturers device drivers. Its something we need to fix, but there's also numerous other things... There's no demo for gta3 last time I looked :-( Jason

4 4

Re: wine/programs/regedit regproc.h regproc.c rege ...
by Vincent Béron 14 Aug '03

14 Aug '03

Le jeu 14/08/2003 à 15:36, Dustin Navea a écrit : > --- Vincent Béron <vberon(a)mecano.gme.usherb.ca> wrote: > > @@ -153,6 +153,9 @@ > > } > > } > > > > + if (*s && action == ACTION_UNDEF) > > + action = ACTION_ADD; > > + > > if (action == ACTION_UNDEF) > > return FALSE; > > > > > > <IMHO> I think this would be a little cleaner (or at least easier to read): > > if (*s && action == ACTION_UNDEF) > action = ACTION_ADD; > else if (action == ACTION_UNDEF) > return FALSE; Sure, I agree with that. I was a bit in a hurry yesterday, when I noticed while building RH8 and RH9 RPMs that I had a regedit window (when the import was supposed to stay windowless) and that the file hadn't be imported. My first goal was to get it to work correctly. > > that or > > if (action == ACTION_UNDEF) > { > if (*s) > action = ACTION_ADD; > return FALSE; > } This won't do the same thing (the return statement will always be executed). Vincent

2 1

Re: wine/programs/regedit regproc.h regproc.c rege ...
by Vincent Béron 14 Aug '03

14 Aug '03

Le mer 06/08/2003 à 23:10, Alexandre Julliard a écrit : > ChangeSet ID: 8934 > CVSROOT: /home/winehq/opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2003/08/06 22:10:13 > > Modified files: > programs/regedit: regproc.h regproc.c regedit.c Makefile.in > .cvsignore > Added files: > programs/regedit: treeview.c rsrc.rc resource.rc resource.h > main.h main.c listview.c framewnd.c childwnd.c > about.c En.rc > > Log message: > Robert Dickenson <robd(a)reactos.org> > Steven Edwards <Steven_Ed4153(a)yahoo.com> > Mike McCormack <mike(a)codeweavers.com> > Implemented GUI for regedit. > > Patch: http://cvs.winehq.com/patch.py?root=/home/winehq/opt/cvs-commit&id=8934 regedit.c: @@ -153,10 +154,13 @@ } if (action == ACTION_UNDEF) - { - action = ACTION_ADD; + return FALSE; + + return PerformRegAction(action, s); } This seems to have broken commandline only regedit, for the ACTION_ADD case (used in wineinstall et al.). The included patch should fix it (building in progress). Vincent

2 2

Small Winecfg win version patch
by root 14 Aug '03

14 Aug '03

This patch adds Windows 2k3 to the winecfg program. -- E. C. F. Wolff Note: Based on Beron's version patch for version.c

2 1

GTA3 crash :( -- RedHat 9
by root 14 Aug '03

14 Aug '03

Hey, After been away too long I'm back again :). Thirst thing what I did was checking that GTA3 still worked. But it didn't :( After it produced a lot of CheckDeviceMultiSampleType fixme's it produced this screen :(: fixme:d3d:IDirect3D8Impl_CheckDeviceMultiSampleType (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), SurfFmt:(17,D3DFMT_R5G6B5), Win?0, MultiSamp:b) fixme:d3d:IDirect3D8Impl_CheckDeviceMultiSampleType (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), SurfFmt:(17,D3DFMT_R5G6B5), Win?0, MultiSamp:c) fixme:d3d:IDirect3D8Impl_CheckDeviceMultiSampleType (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), SurfFmt:(17,D3DFMT_R5G6B5), Win?0, MultiSamp:d) fixme:d3d:IDirect3D8Impl_CheckDeviceMultiSampleType (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), SurfFmt:(17,D3DFMT_R5G6B5), Win?0, MultiSamp:e) fixme:d3d:IDirect3D8Impl_CheckDeviceMultiSampleType (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), SurfFmt:(17,D3DFMT_R5G6B5), Win?0, MultiSamp:f) fixme:d3d:IDirect3D8Impl_CheckDeviceMultiSampleType (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), SurfFmt:(17,D3DFMT_R5G6B5), Win?0, MultiSamp:10) fixme:d3d:IDirect3D8Impl_CheckDeviceFormat (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), AdptFmt:(23,D3DFMT_R5G6B5), Use:(2,D3DUSAGE_DEPTHSTENCIL), ResTyp:(1,D3DRTYPE_SURFACE), CheckFmt:(73,D3DFMT_D15S1)) fixme:d3d:IDirect3D8Impl_CheckDepthStencilMatch (0x4a7d0460)->(Adptr:0, DevType:(1,D3DDEVTYPE_HAL), AdptFmt:(17,D3DFMT_R5G6B5), RendrTgtFmt:(17,D3DFMT_R5G6B5), DepthStencilFmt:(49,D3DFMT_D15S1)) fixme:d3d:IDirect3D8Impl_CreateDevice Requested full screen support not implemented, expect windowed operation X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 145 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 488 Current serial number in output stream: 488 I think the last functions (RendrTgtFmt and ImplCreateDevice) are responsible for the crash or could it be my openGL setup (I think not, because it worked before) -- E. C. F. Wolff

1 0

Another problem wih Charlie's Angels
by Dominik.Strasser＠t-online.de 14 Aug '03

14 Aug '03

ReHi, after hacking Wine for the problem in my previous mail I got further, but no success yet. The problem is: Charlie's Angels unpacks a "System.dll" into a temporary directory and tries to load it. But as there is a compiled-in loadorder default which says "builtin", the builtin 16bit system.dll is loaded which results in a failure. Only commenting the loadorder helped. Neither --dll nor DllOverrides worked. Perhaps we need a more sophisticated loadorder detection. Regards Dominik PS: Now as the game is installed, it doesn't work. It crashes right at the begining even before the game is loaded. I'll dig deeper into this.

1 0

Re: [winegcc03] winewrap can handle the default output name
by Dimitrie O. Paun 14 Aug '03

14 Aug '03

On August 13, 2003 09:55 pm, Richard Cohen wrote: > Default name that mingw uses is a.exe > This also stops winewrap from segfaulting when passed no arguments. > > Changelog > Handle default linker output name (a.exe) in winewrap The reason I've handled it in winegcc rather than winewrap is that this seems to be a (historical) feature that's specific to gcc, and there doesn't seem to be any reason to have such a feature perpetuated in winewrap. -- Dimi.

2 2

Fwd: Re: status of Kazaalite crash patch ?
by Dimitrie O. Paun 14 Aug '03

14 Aug '03

-- Dimi.

1 0

Re: [X11DRV] Re-add support for the 'UseXShm' config key.
by Alexandre Julliard 14 Aug '03

14 Aug '03

Lionel Ulmer <lionel.ulmer(a)free.fr> writes: > Changelog: > - the UseXShm key was still present but not used anymore Do you actually need it? Otherwise I think we might as well remove it completely, clearly nobody depends on it since it has been broken for a long time. -- Alexandre Julliard julliard(a)winehq.com

2 3

winevdm: can't exec
by Dominik.Strasser＠t-online.de 14 Aug '03

14 Aug '03

Hi, trying to run the game demo of "Charlie's Angels" which can be found here: http://www.gamesdomain.com/demos/demo/1861.html I am running into a strange problem. The demo is a NE binary, so winevdm is called. But is has the "32-bit-flag" set, so MODULE_LoadModule16 returns handle 21 (Win32 binary). Consequently winevdm emits "can't exec". By hacking __wine_process_init to start WIN16 binaries as WIN32, I am proceeding much further. Should I modify MODULE_GetBinaryType to look for the above mentioned 32-bit-flag and to return a new binary type which is treated like PE ? Regards Dominik

1 0

Re: [winegcc01] Don't use BINDIR to spawn subprograms
by Dimitrie O. Paun 14 Aug '03

14 Aug '03

On August 13, 2003 09:49 pm, Richard Cohen wrote: > Just using $PATH to find stuff makes it much easier to spawn off tools > when running within the tree. > > Changelog: > Remove hardcoded BINDIR paths Yes, this is a problem -- eventually we want to use these things from within the tree. I guess we can prepend $WINE_HOME/tools to the PATH within the Makefile. Another way do to it is to look at argv[0], and if we're running from within the tree, we automatically select the in-tree tools, rather than the ones from BINDIR. What do people think, any other suggestions? -- Dimi.

2 1

Re: Implementations of WCSToMBEx and MBToWCSEx and PolyPatBlt
by Dimitrie O. Paun 14 Aug '03

14 Aug '03

On August 13, 2003 10:10 pm, Jonathan Wilson wrote: > Here are the implementations of those functions I did for ReactOS. (and no, > I didnt use disassembler on them this time :) > I am licencing them under whatever licence I need to in order for them to > go into WINE (if the WINE team wants them that is) > They compile on ReactOS just fine. Not sure if they work or not, tests > would be usefull :) Please submit them as a patch, so that Alexandre can apply them to the tree like all the other patches. > BTW, I can also share some of the info I have on other user32 functions I > was able to figure out/find info on if there is a need for it. Sure, more info can't hurt (if you got it through legal means :)). -- Dimi.

2 2

status of Kazaalite crash patch ?
by wim delvaux 14 Aug '03

14 Aug '03

Hi, Read on the devel archive (using search) about crashing Kazaalite .. I can confirm. I have the same problem since 200306 version. Just upgraded to 200307 but still crashes. What's the status of this problem ? W

2 1

Re: [resend 3rd time ] SetMenu patch
by Alexandre Julliard 13 Aug '03

13 Aug '03

Oleg Prokhorov <xolegpro(a)rbcmail.ru> writes: > Cause: > SetMenu was limited to update client/non-client only if window is > visible, while MS Windows SetMenu updates it anyway. > > Changelog: > SetMenu always updates client/non-client. This causes a SetWindowPos to happen during window creation, before the window is properly initialized, with bad results. This will need more work I'm afraid. -- Alexandre Julliard julliard(a)winehq.com

1 0

finaly vacations
by Raphaël Junqueira 13 Aug '03

13 Aug '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I'll be on vacation (and most of the time off line) for 2 weeks. Finaly after a lot of hard work at office (and few time for wine), some holydays. The return will be "hot" ;=) Best Regards, Raphael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/OmjDp7NA3AmQTU4RAstGAJ0TUuXqNHciWD6MUodk540dJ/NFHACeOM15 QW0K5IHbtqblTS6KJFtOPC4= =c05x -----END PGP SIGNATURE-----

1 0

winver
by puoti＠inwind.it 13 Aug '03

13 Aug '03

I've noticed that wine doesn't yet seem to have a winver option for windows server 2003, I suppose it a trivial thing to implement, at least by seeing how quickly this was done for windows xp.

3 6

Re: Other winefile fixes
by Dimitrie O. Paun 13 Aug '03

13 Aug '03

On August 13, 2003 09:25 am, Richard Cohen wrote: > Use __WINE instead of _WINE_, _WIN32 Why do we need to know that we're running under Wine in so many places? I think we have fewer tests for __WINE__ in a huge lib like wxWindows than we have in winefile! -- Dimi.

2 1

Re: wrong keyboard layout
by Dmitry Timoshkov 13 Aug '03

13 Aug '03

"Phil Krylov" <phil(a)newstar.rinet.ru> wrote: > XFree86 -version reports: > > XFree86 Version 4.3.0 > Release Date: 27 February 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.4.22_pre2-gss i686 [ELF] > Build Date: 23 July 2003 > > The log you asked for is attached. It's rather big, so I truncated it > after ToUnicode entries. Here is your problem: trace:x11drv:x11drv_init_thread_data Using C locale of Input Method XFree86 uses C locale, not UTF-8 one. As I wrote previously, test with 'xev' first. As soon as it starts to work, Wine should work as well. -- Dmitry.

2 2

Re: Other winefile fixes
by Dimitrie O. Paun 13 Aug '03

13 Aug '03

On August 13, 2003 09:25 am, Richard Cohen wrote: > Dimi, I have some patches for winegcc/winewrap. Are you working on it > at the moment, or should I just send them to wine-patches? Don't worry about me, send whatever you have to wine-patches. -- Dimi.

1 0

__stdcall__ pointer to member function
by Boaz Harrosh 13 Aug '03

13 Aug '03

the GCC (3.2.2) compiler will not let me declare an __stdcall__ pointer to function member and code will than SEGFAULT on invocation of the member pointer. This is not the case for Regular pointers to functions. ( The compiler will also issue a warning on mismatch.) Listing of the Error: (BAD) class AFoo { public: __attribute__((__stdcall__)) void foo(int i ,int ii ,int iii) ; } ; __attribute__((__stdcall__)) void AFoo::foo(int i ,int ii ,int iii) { return ; } int main() { AFoo afoo ; void ( AFoo::*func)(int,int,int) ; func = &AFoo::foo ; for(int i=0 ; i < 0x8000000 ;i++) (afoo.*func)(1,2,3) ; // SEGFAULT or SEGIL when stack is Exhausted return 0 ; } any attempt to place the __atribute__((stdcall)) in the pointer declaration causes a compilation error. With out it the code will SEGFAULT. If declaring a regular pointer to function than no compilation error is issued and all is well. Listing of Regular function pointer: (GOOD) void __attribute__((stdcall)) foo(int i ,int ii ,int iii) { } int main() { void ( __attribute__((stdcall)) *func)(int,int,int) = &foo ; for(int i=0 ; i < 0x8000000 ;i++) (func)(1,2,3) ; return 0 ; } removing the __attribute__((stdcall)) from the *func declaration will rightfully issue a warning ( should be an error if you ask me, type mismatch). But Not so on our first example. !!!!!!!!!!!!!!!!!! Please if any body can help me? This totaly breaks COM. Is there a GCC switch to have all members (and pointers)__stdcall, to by pass this problem? Free Life Boaz

1 1

Re[2]: wrong keyboard layout
by Phil Krylov 13 Aug '03

13 Aug '03

Hello Shachar, Tuesday, August 12, 2003, 12:15:51 AM, you wrote: SS> Dmitry Timoshkov wrote: >>BTW, what wrong happens if your keyboard was misdetected? In the current >>CVS all national characters should work fine regardless what keyboard >>layout was detected. Is that only a warning message which makes you worry? >> >> SS> Does this also apply to UTF-8? I, for one, still can't get any SS> characters recognized when the locale is UTF-8. With the current CVS, I can't get any Cyrillic input with any setting of LANG: ru_RU.KOI8-R, ru_RU.UTF-8, ru_RU.CP1251, and en_US.UTF-8. Only ? characters are input. -- Best regards, Phil mailto:phil@newstar.rinet.ru

2 7

Better GNOME integration
by Christian Neumair 13 Aug '03

13 Aug '03

When trying to use the latest Debian package I noted that there are no MIME bindings available for GNOME and that applications installed with wine are not visible in the application menu. In my opinion the first issue is really easily solvable, just three more files need to be included in the package and copied into /usr/share/mime-info and /usr/share/application-registry - is the official source the right place or should package maintainers include this? The second is a bit more tricky. I propose that as a 1.0 target wine should implement the freedesktop.org menu spec [1], which is definitly the future. We should contact the freedesktop guys and tell them that we want a registered category "WINE" :). regs, Chris [1] http://www.freedesktop.org/standards/menu-spec/0.5-onehtml/

1 0

WCSToMBEx and MBToWCSEx
by Jonathan Wilson 13 Aug '03

13 Aug '03

I have come up with some info on these 2 (previously undocumented) calls: DWORD STDCALL WCSToMBEx(WORD CodePage,LPWSTR UnicodeString,DWORD UnicodeSize,LPSTR *MBString,DWORD MBSize,BOOL Allocate); DWORD STDCALL MBToWCSEx(WORD CodePage,LPSTR MBString,DWORD MBSize,LPWSTR *UnicodeString,DWORD MBSize,BOOL Allocate); Return value for both is the count of characters copies (or mabie count of bytes, not sure) for WCSToMBEx, the parameters are: CodePage: specifies which code page to use (its the same code page as passed to WideCharToMultiByte) UnicodeString: the input unicode string UnicodeSize: the size of the unicode string (not sure if its bytes or characters). Pass -1 to ask the function to calculate it for you. MBString: the output ascii string MBSize: the size of the ascii string (not sure if its bytes or characters). Pass -1 to ask the function to calculate it for you. Allocate: Set to true to ask the function to allocate the destination memory. Set to false and it assumes that the memory is preallocated by the caller. For MBToWCSEx, the parameters are: CodePage: specifies which code page to use (its the same code page as passed to MultiByteToWideChar) MBString: the input ascii string MBSize: the size of the ascii string (not sure if its bytes or characters). Pass -1 to ask the function to calculate it for you. MBString: the output unicode string MBSize: the size of the unicode string (not sure if its bytes or characters). Pass -1 to ask the function to calculate it for you. Allocate: Set to true to ask the function to allocate the destination memory. Set to false and it assumes that the memory is preallocated by the caller. I am going to implement these functions and contribute the code to ReactOS & WINE but I want someone else to play whith them and confirm all my findings as to what these functions do and how they work first.

3 2

Question about dlls/dinput/mouse/main.c
by Michael Schlüter 12 Aug '03

12 Aug '03

Hi, I've a small problem with the game "Star Trek Elite Force II Single Player Demo". The mouse button event seems not to be send back to the game. After changing the return value of dinput_mouse_hook in dlls/dinput/mouse/main.c to return always "CallNextHookEx( This->hook, code, wparam, lparam );" it works. Does anybody has a solution for that issue? Bye, Michael

1 0

Re: Implement a typelib loader cache
by Alexandre Julliard 12 Aug '03

12 Aug '03

Mike Hearn <mike(a)theoretic.com> writes: > ChangeLog: > Implement a typelib loader cache You'll need to protect the list with a critical section. Also it's probably better to store the list directly in the typelib structure instead of allocating a separate object. -- Alexandre Julliard julliard(a)winehq.com

1 0

DRIVE_GetUnixCwd and drives other than the current one
by Troy Rollo 12 Aug '03

12 Aug '03

It appears that Wine is storing and using a "current directory" for each DOS drive. According to some testing we have just done on Windows 2000 and Windows 98, Windows only stores a current directory for the current drive. "But CMD.EXE seems to remember drives, and their children too", comes the reply. Well, sort of. The documentation for CreateProcess talks about environment variables used to hold the current directory for each drive, with an environment variable with a name of the form "=C:" having the value, say "C:\WINDOWS". That documentation suggests you must make sure all these environment variables are set if you construct a new environment block, and that you need to get the values of them using "GetFullPathName". Shock, horror, the Windows documentation is wrong. What actually happens is that CMD.EXE and COMMAND.COM independently set those environment variables when you change directories in those shells. SetCurrentDirectory has no effect on those environment variables - either in the current process or in child processes. It is the responsibility of the application to set them if it wants the children to have access to its current directory on drives other than its current drive. However, SetCurrentDirectory("D:") (assuming a starting point of drive "C") will read those environment variables to determine which directory of drive "D" to go to. You can even 'SetEnvironmentVariable("=D:", "\\foo")' to make the next 'SetCurrentDirectory("D:")' end up in "D:\foo". GetFullPathName also picks up the environment variable if the path requested is not on the current drive (although it also checks that the path is valid, so 'GetFullPathName("A:\\", ...)' will rattle drive A if drive A is empty). If there's no environment variable, both GetFullPathName and SetCurrentDirectory assume "x:\". If the drive in question is the current drive, SetCurrentDirectory and GetFullPathName both ignore the environment variables and use the value from GetCurrentDirectory. So, for example: // Start with no "=D:" variable in environment SetCurrentDirectory("d:\\bar"); SetCurrentDirectory("c:"); SetCurrentDirectory("d:"); // Current directory now d:\ SetCurrentDirectory("d:\\bar"); SetCurrentDirectory("c:"); SetEnvironmentVariable("=D:", "\\foo"); SetCurrentDirectory("d:"); // Current directory now "d:\\foo"; SetEnvironmentVariable("=D:", "\\bar"); SetCurrentDirectory("d:"); // Current directory still d:\\foo The Borland C++ run-time libraries have code in their chdir functions that sets these variables, but it's inside a "#if 0" section, presumably reflecting an attempt to be compatible with MSC. I'm not aware of anything that relies on this perverse behaviour, so whether Wine needs to be adjusted to mimic it may be an open question. It is probably of more interest to people who want to pass an environment block to CreateProcess. If you're doing that, ignore what the documentation says about including "=C:" & etc environment variables in the environment block - simply start with the environment block returned by GetEnvironmentBlock and make the desired changes, ensuring the block is sorted according to instructions I gave previously on one of the Cygwin mailing lists.

2 1

can't redirect stdout?!
by Dan Kegel 12 Aug '03

12 Aug '03

OK, so with the normal X11 driver, you can no longer redirect stdout from commandline apps under Wine; the output just vanishes if you try to send it to a file. That's rather unacceptable dain bramage, if you ask me. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

4 5

Re: dlopen libncurses.so in wineconsole
by Eric Pouech 12 Aug '03

12 Aug '03

Mike McCormack wrote: > > This patch doesn't include changes to configure. Run autoconf to > regenerate it... several comments to this needed patch: 1/ in configure.ac why not checking also for curses if ncurses isn't present ? BTW, you can also remove the ncurses library lookup in configure.ac, we no longer need it. 2/ in curses.c some of the functions we use in curses.c can in fact be macros in some curses' implementations. According to my doc, this includes initscr, intrflush, nodelay, noecho. So, you could pass LOAD_FUNCPTR a boolean not to fail if the symbol is not found (for those functions), and not #define initscr to p_initscr if initscr is already #define:d > + if( !WCCURSES_bind_libcurses() ) > + return FALSE; you'd better return init_failed from the enum instead of a boolean here A+ -- Eric Pouech

1 0

Is wine a debugger?
by Dan Timis 12 Aug '03

12 Aug '03

I am trying to load a security Windows dll that does not run under a debugger. When I load the dll I get a SIGTRAP, and then wine breaks in its debugger. My understanding is that if I run wine as opposed to winedbg I am not running under a debugger. But, if there is a crash or some other exception wine will start a debugger. I sent some memory dumps to the developer of the security dll, and he said that it behaves like it was running under a debugger. He's question was something like does wine have an always "on" debugger? I would appreciate any help. Thanks, Dan Timis Muse Research, Inc.

3 2

Re: Some advapi32 stubs
by Stefan Leichter 12 Aug '03

12 Aug '03

On Tuesday 12 August 2003 07:06, Mike McCormack wrote: > ChangeLog: > * stubs for advapi32 functions InitiateSystemShutdownEx, SetEntriesInAcl > and SetNamedSecurityInfo +@ stdcall InitiateSystemShutdownExA(wstr wstr long long long long) This looks wrong to me (wstr as parameter of A function) Bye Stefan

1 0

bidi support test program
by Shachar Shemesh 12 Aug '03

12 Aug '03

Hi all, Attached is a simple program to test whether the Win32 API supports BiDi reordering. Some packagers asked me for such a utility in the past, so they can make sure that their inclusion of ICU worked, and without forcing them to actually understand languages that are all Hebrew to them. I'm not sure whether it would be necessary to include this utility inside the Wine soure, or how to do so. This is not exactly a test, as a failure is totally justified under some circumstances. Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

1 0

Threading experts?
by Jason Edmeades 11 Aug '03

11 Aug '03

Hi, I seem to have found a recreatable threading problem and I am not convinced it it wines fault either. Are there any experts here who want to offer any advice on where to go to persue this please? Problem: 'wine appname' hangs when it creates one of its threads. The hang is inside pthread_create and control is never returned to the caller Environment uname -a returns kernel 2.4.21-0.13mdk, and its basically Mandrake Linux 9.1 with no updates. Wine is cvs as of today, configured with --with-nptl More info: Looking through an strace, I can see a difference between a working and failing case, and it would appear there is a timing issue inside the pthread routines. However, I would normally expect it far more likely that it is a wine bug than a kernel / threading bug, so I dont really know how to proceed. I can recreate this about 95% of the time with one app and one app only, so I really suspect it to be a wine problem, but I just cant see why. Here's a working case =============== (Note SY3 and SY4 are fixmes I added each side of the pthread_create) 394 issues a create thread. [pid 394] write(2, "fixme:thread:SYSDEPS_SpawnThread"..., 38fixme:thread:SYSDEPS_SpawnThread SY 3) = 38 [pid 394] rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], 8) = 0 [pid 394] write(12, "\240@4@\0\0\0\0\230,s@\240\177\v@\0000\20J\0\0\0\200\0"..., 148 <unfinished ...> : 398 is the pthread thread manager thread [pid 398] getppid() = 394 [pid 398] read(10, "\240@4@\0\0\0\0\230,s@\240\177\v@\0000\20J\0\0\0\200\0"..., 148) = 148 [pid 398] clone(child_stack=0x4a102bd0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|0x21) = 400 : It wakes up 394 to indicate it can continue [pid 398] kill(394, SIGRTMIN) = 0 : [pid 394] <... write resumed> ) = 148 [pid 394] rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], 8) = 0 [pid 394] rt_sigsuspend([] <unfinished ...> *** sigsuspend gets back a SIGRTMIN to wake it up. [pid 394] --- SIGRTMIN (Unknown signal 32) @ 0 (0) --- [pid 394] <... rt_sigsuspend resumed> ) = -1 EINTR (Interrupted system call) [pid 394] sigreturn() = ? (mask now [RTMIN]) [pid 394] write(2, "fixme:thread:SYSDEPS_SpawnThread"..., 38fixme:thread:SYSDEPS_SpawnThread SY 4 Failing case ======== 394 issues a create thread. [pid 394] write(2, "fixme:thread:SYSDEPS_SpawnThread"..., 38fixme:thread:SYSDEPS_SpawnThread SY 3) = 38 [pid 394] rt_sigprocmask(SIG_SETMASK, NULL, [], 8) = 0 [pid 394] write(12, "\240@4@\0\0\0\0$&s@\240\177\v@\0000xJ\0\0\0\0\0\0\0\0`"..., 148 <unfinished ...> : 398 is the pthread thread manager thread [pid 398] <... poll resumed> [{fd=10, events=POLLIN, revents=POLLIN}], 1, 2000) = 1 [pid 398] getppid() = 394 [pid 398] read(10, "\240@4@\0\0\0\0$&s@\240\177\v@\0000xJ\0\0\0\0\0\0\0\0`"..., 148) = 148 [pid 398] clone(child_stack=0x4a782bd0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|0x21) = 401 : It wakes up 394 to indicate it can continue [pid 398] kill(394, SIGRTMIN) = 0 : (Now for the difference...) [pid 394] <... write resumed> ) = 148 : vvv What is this, and why is it getting the signal [pid 394] --- SIGRTMIN (Unknown signal 32) @ 0 (0) --- [pid 394] sigreturn() = ? (mask now []) : vvv Since the signal is absorbed already, suspend just hangs forever. [pid 394] rt_sigprocmask(SIG_SETMASK, NULL, [], 8) = 0 [pid 394] rt_sigsuspend([] <unfinished ...> Any help? Its really annoying Jason

5 5

question about mouse_event
by dd jj 11 Aug '03

11 Aug '03

Hello, I have ported a windows code to linux using winemaker: it works fine on windows, but doesn't work on linux, Could anyone give some comments on this problem? THanks. Here's the code. #include <windows.h> int APIENTRY WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) { // TODO: Place code here. mouse_event(MOUSEEVENTF_LEFTDOWN,0,0,0,0); mouse_event(MOUSEEVENTF_LEFTUP,0,0,0,0); return 0; } --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

3 3

Does anyone have prototypes for the following user32.dll functions?
by Jonathan Wilson 11 Aug '03

11 Aug '03

ok, here are the ones I still need: TranslateMessageEx UnlockWindowStation UpdatePerUserSystemParameters UserRegisterWowHandlers WCSToMBEx TileChildWindows ShowStartGlass SetConsoleReserveKeys SetCursorContents PrivateKDBreakPoint QuerySendMessage MBToWCSEx MB_GetString LockWindowStation LoadKeyboardLayoutEx GetInputDesktop GetAccCursorInfo FullScreenControl DrawFrame DdeGetQualityOfService ClientThreadSetup CascadeChildWindows

2 1

Re: Threading experts?
by puoti＠inwind.it 11 Aug '03

11 Aug '03

I had to use with-nptl to build winex pn Mandrake 9.1, the binarys did't work without that option. This wasn't necessarry on wine, but winex won't run without it. Dmitry wrote: I may be wrong, but according to the information posted to one of our support forums, support for NPTL was backported from 2.5 kernels by RedHat, and nobody else has support for NPTL in 2.4 kernel series. So, you shouldn't compile --with-nptl on Mandrake. -- Dmitry.

3 2

wrong keyboard layout
by Raul 11 Aug '03

11 Aug '03

couple years ago, when i sent the estonian layout patch, worked fine put now im using redhat 9 and detects wrong layout (Latin American keyboard layout) is there some changes that breaks the layout or im making something wrong? Raul

3 7

Does anyone have prototypes for the following user32.dll functions?
by Jonathan Wilson 11 Aug '03

11 Aug '03

All of them are exported by user32.dll from NT4SP6a CascadeChildWindows ClientThreadSetup DdeGetQualityOfService DrawCaptionTempA DrawCaptionTempW DrawFrame DrawMenuBarTemp EditWndProc FullScreenControl GetAccCursorInfo GetAppCompatFlags GetInputDesktop GetInternalWindowPos GetProgmanWindow GetTaskmanWindow KillSystemTimer LoadKeyboardLayoutEx LoadLocalFonts LoadRemoteFonts LockWindowStation MBToWCSEx MB_GetString MenuWindowProcA MenuWindowProcW PrivateExtractIconExA PrivateExtractIconExW PrivateKDBreakPoint QuerySendMessage RegisterLogonProcess RegisterSystemThread RegisterTasklist ScrollChildren SetConsoleReserveKeys SetCursorContents SetDeskWallpaper SetInternalWindowPos SetLogonNotifyWindow SetProgmanWindow SetSysColorsTemp SetSystemMenu SetSystemTimer SetTaskmanWindow SetWindowStationUser ShowStartGlass TileChildWindows TranslateAccelerator TranslateMessageEx UnlockWindowStation UpdatePerUserSystemParameters UserClientDllInitialize UserRealizePalette UserRegisterWowHandlers WCSToMBEx

2 1

Unable to print from wine
by Peter Stokes 11 Aug '03

11 Aug '03

Hi I downloaded the Mandrake wine-20030709-mdk9.1.i586.rpm and my main issue is still printing from an old 16 bit app. The previous MDK version 20030618 allowed me to pick a printer and select a print format. It then proceeded to print to my CUPS default printer with some of the information it was supposd to print, but not in the correct page size (lost the header and footer info off of the top/bottom of the page). This time when I try to pick a print format I get the following wine: Unhandled exception (thread 000a), starting debugger... err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 8 112") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger The app then completely hangs. So how do I use the debugger to get some useful info for you to look at? Thanks Peter

1 0

Stubs for BuildTrusteeWithSid(A/W)
by Mike McCormack 11 Aug '03

11 Aug '03

ChangeLog: * Stubs for BuildTrusteeWithSid(A/W) Index: dlls/advapi32/advapi32.spec =================================================================== RCS file: /home/wine/wine/dlls/advapi32/advapi32.spec,v retrieving revision 1.38 diff -u -r1.38 advapi32.spec --- dlls/advapi32/advapi32.spec 24 Jul 2003 00:01:16 -0000 1.38 +++ dlls/advapi32/advapi32.spec 11 Aug 2003 09:03:40 -0000 @@ -338,3 +338,6 @@ @ stub WmiSetSingleInstanceW @ stub WmiOpenBlock @ stub WmiCloseBlock +@ stdcall BuildTrusteeWithSidA(ptr ptr) +@ stdcall BuildTrusteeWithSidW(ptr ptr) + Index: dlls/advapi32/security.c =================================================================== RCS file: /home/wine/wine/dlls/advapi32/security.c,v retrieving revision 1.56 diff -u -r1.56 security.c --- dlls/advapi32/security.c 24 Jul 2003 00:01:16 -0000 1.56 +++ dlls/advapi32/security.c 11 Aug 2003 09:03:40 -0000 @@ -1334,3 +1334,20 @@ FIXME("stub!\n"); return ERROR_BAD_PROVIDER; } + +/****************************************************************************** + * BuildTrusteeWithSidA [ADVAPI32.@] + */ +VOID WINAPI BuildTrusteeWithSidA(PTRUSTEEA pTrustee, PSID pSid) +{ + FIXME("%p %p\n", pTrustee, pSid); +} + +/****************************************************************************** + * BuildTrusteeWithSidW [ADVAPI32.@] + */ +VOID WINAPI BuildTrusteeWithSidW(PTRUSTEEW pTrustee, PSID pSid) +{ + FIXME("%p %p\n", pTrustee, pSid); +} +

1 0

Wine CVS Build Error
by Casey McGinty 11 Aug '03

11 Aug '03

I'm trying to get Wine and/or Winex to build on my system with no luck. I get the same error in both releases, I was hoping someone would know how to fix this, or what I am doing wrong. I'm using GCC 3.2.3 and kerenl 2.4.21 on a Linux From Scratch distribution. The error output I get in Wine: gcc -s -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -D__WINESRC__ -DDLLDIR="\"/usr/local/lib/wine\"" -Wall -mpreferred-stack-boundary=2 -gstabs+ -Wpointer-arith -O3 -march=athlon-xp -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4 -o ldt.o ldt.c ldt.c: In function `modify_ldt': ldt.c:78: `SYS_modify_ldt' undeclared (first use in this function) ldt.c:78: (Each undeclared identifier is reported only once ldt.c:78: for each function it appears in.) make[2]: *** [ldt.o] Error 1 make[2]: Leaving directory `/tmp/wine-20030709/libs/wine' make[1]: *** [wine] Error 2 make[1]: Leaving directory `/tmp/wine-20030709/libs' make: *** [libs] Error 2 The error is basically the same in Winex, undefined SYS_modify_ldt. I tried searching for SYS_modify_ldt definition in my kernel sources and the Wine source and I failed to find anything. What gives ? I hope someone can help me with this. Thanks - Casey

2 1

Re: Add support for CS_NOCLOSE
by Alexandre Julliard 10 Aug '03

10 Aug '03

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Hello, > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Add support for CS_NOCLOSE. This is implemented already in MENU_InitSysMenuPopup; if it doesn't work right it should be fixed there. -- Alexandre Julliard julliard(a)winehq.com

2 7

Re: Implement a typelib loader cache
by Dmitry Timoshkov 10 Aug '03

10 Aug '03

"Mike Hearn" <mike(a)theoretic.com> wrote: > Implement a typelib loader cache, minor debug message improvements + for (entry = tlb_cache_tail; entry != NULL; entry = entry->next) + if (!strcmpW(entry->path, szPath)) { + TRACE("cache hit\n"); Shouldn't this be a case insensitive comparison? -- Dmitry.

2 2

Re: Status Update#2 Again
by Dmitry Timoshkov 10 Aug '03

10 Aug '03

"Tom" <twickline(a)skybest.com> wrote: + <li>ADD - RCPT4 ToDo and entries</li> Sorry, didn't notice it first time: it seems that RCPT4 should actually be RPCRT4. -- Dmitry.

1 0

missing #define in winuser.h
by Alfredo K. Kojima 09 Aug '03

09 Aug '03

The owner draw states in winuser.h do not include ODS_DEFAULT (among others), which is described in the documentation in MSDN: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pl… -- Alfredo

1 0

Re: Status Update - Lostwages
by Dmitry Timoshkov 09 Aug '03

09 Aug '03

"Tom" <twickline(a)skybest.com> wrote: > Here is a small update to the status pages. + <li>Remove - Some of the bullets from DierctX section</li> an apparent typo above -- Dmitry.

3 3

wine seti team
by puoti＠inwind.it 08 Aug '03

08 Aug '03

Is m$ does it, we must do it too. The Wine seti@home team can be found here. http://setiathome.ssl.berkeley.edu/stats/team/team_172471.html Microsoft also has a team, we are ...a bit behind, there stats are here http://setiathome.ssl.berkeley.edu/stats/team/team_28.html Will we catch up?

1 0

Seti@home
by puoti＠inwind.it 08 Aug '03

08 Aug '03

What about having a wine seti team?

1 0

Re: Small cleanup
by Alexandre Julliard 08 Aug '03

08 Aug '03

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > ChangeLog > Remove unused defines. The idea is to have the same defines as Windows; even though we don't actually need them at this point we might want to someday. -- Alexandre Julliard julliard(a)winehq.com

3 3

Re: partial implementation of msi.dll
by Mike McCormack 08 Aug '03

08 Aug '03

Gregory M. Turner wrote: > Hmm, that pure parser business... is that for reentrancy? Or is that a > side-effect of some larger "pureness"? > > If they aren't portably generated, just do it ahead of time -- betcha AJ will > have no problem checking in some pre-generated stuff so long as the sources > to regenerate them are available to those who have the right tools. The pureness is about reentrancy, though it maybe necessary so that two parsers don't have conflicting global variable names. I also thought about pre-generated parser code... that's probably a good idea if Alexandre agrees. >>2) make the database read/write - not immediately important, but >>necessary later > > > does MSI do that? I thought that was done by some funky tool... or does it > use msi.dll to do the work? There's some tools you can download from MSDN, however MSI.DLL does all the work of reading and writing the database. >>I don't have lots of time to work on this at the moment, so if somebody >>wants to have a go, I'm happy to help them out. > > > well considering I'm the only recipient of this, would I be the "somebody" you > have in mind? ;) (just kidding of course ... as for me, my plate is pretty > full right now, but I will of course take a look at it when I get the chance > and see if there's anything I can do to help. Since I need to brush up on my > parsing skills if I ever want to help Ove with widl, maybe I can find > something to do in that arena.) It's probably better that somebody who's looking for stuff to do does it, seeing you've got other stuff to do. I might do some work on it periodically, but it seems like it might be a fun project for somebody to take up. Mike

2 2

age of empires 1 trial uninstall script
by puoti＠inwind.it 07 Aug '03

07 Aug '03

The age of empires trial uninstaller writes a batch script to the c drive, then exits, the script :Repeat del "C:\Program Files\Microsoft Games\Age of Empires Trial\UNINSTAL.EXE" del "C:\Program Files\Microsoft Games\Age of Empires Trial\SETUPENU.DLL" if exist "C:\Program Files\Microsoft Games\Age of Empires Trial\UNINSTAL.EXE" goto Repeat if exist "C:\Program Files\Microsoft Games\Age of Empires Trial\SETUPENU.DLL" goto Repeat rmdir "C:\Program Files\Microsoft Games\Age of Empires Trial" rmdir "C:\Program Files\Microsoft Games" rmdir "C:\Program Files" rmdir "C:" del "\DelUS.bat" is meant to delete itself, but ti dosen'tas after the uninstall has finished, I find it in the fake c: directory. Running it under wcmd outputs this C:\>delus C:\>del "C:\Program Files\Microsoft Games\Age of Empires Trial\UNINSTAL.EXE" C:\Program Files\Microsoft Games\Age of Empires Trial\UNINSTAL.EXE :File Not Found C:\>del "C:\Program Files\Microsoft Games\Age of Empires Trial\SETUPENU.DLL" C:\Program Files\Microsoft Games\Age of Empires Trial\SETUPENU.DLL :File Not Found C:\>if exist "C:\Program Files\Microsoft Games\Age of Empires Trial\UNINSTAL.EXE" goto Repeat C:\>if exist "C:\Program Files\Microsoft Games\Age of Empires Trial\SETUPENU.DLL" goto Repeat C:\>rmdir "C:\Program Files\Microsoft Games\Age of Empires Trial" File not found C:\>rmdir "C:\Program Files\Microsoft Games" Directory is not empty C:\>rmdir "C:\Program Files" Directory is not empty C:\>rmdir "C:" Directory is not empty C:\>del "\DelUS.bat" Sharing violation C:\> The rmdir errors are normal, they aren't meant to do anything if they try to delete not-empty folders, but the del "DelUS.bat" instructions, (The self destruction mechanism of the script) gives a sharing violation error. This is a very trivial problem, the rest of the uninstall works, and (If it's there) the game directory is deleted successfully, so one only has to delete the script by hand, but it would at least look good if this was fixed before 1.0

1 0

propset.c: In function `DSPROPERTY_EnumerateW
by Peter Birch 07 Aug '03

07 Aug '03

The latest cvs code (08/06/2003 20:45:00 pst) will not compile - I get the following error: gcc -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -D__WINESRC__ -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o propset.o propset.c propset.c: In function `DSPROPERTY_EnumerateW': propset.c:522: parse error before `*' propset.c:526: `wDescription' undeclared (first use in this function) propset.c:526: (Each undeclared identifier is reported only once propset.c:526: for each function it appears in.) propset.c:527: `wModule' undeclared (first use in this function) propset.c:528: `wInterface' undeclared (first use in this function) propset.c:550: parse error before `*' This is on Linux kernel 2.4.20 (i586), GCC 2.95.4 with the configure line: ./configure --prefix=/usr --sysconfdir=/etc --with-opengl --with-x This used to work, and the error amazes me because the exact same code appears in the source file several times before the error. Any ideas? Thanks.

2 3

Re: [antony@antgel.co.uk: .msi files]
by Robert Shearman 07 Aug '03

07 Aug '03

> Date: Fri, 1 Aug 2003 16:03:01 +0100 > From: Antony Gelberg <antony(a)antgel.co.uk> > To: wine-devel(a)winehq.com > Subject: [antony(a)antgel.co.uk: .msi files] > > Does Windows Installer work? Yes, I have installed MSN Messenger using it. > I've tried installing bout the 98 and 2K versions under wine, but only > get: > > cdrom $ /usr/local/bin/wine ./instmsiw.exe > fixme:win32:PE_CreateModule Security directory ignored > fixme:process:CreateProcessA (X:\IXP000.TMP\msiinst.exe,...): > NORMAL_PRIORITY_CLASS ignored This is your problem. Only the Win9x version of MSI works at the moment and only if your version is set to Win9x in your config file. I submitted a few patches a while ago to get the WinNT version a bit further but it needs a load of security functions which aren't implemented (properly) yet. There was talk a while ago about reimplementing MSI in Wine, but we rejected the idea on the grounds that it was undocumented, very complicated and not needed yet. > On another note, I'm really surprised that the wine-users list is so > quiet as it's such an important bit of software. I apologise for this. We do have a few developers that regularly post there (including me on occasions), it just seems you caught us at a busy moment. Rob

5 15

Re: Some suggestions on API database
by Dave Miller 07 Aug '03

07 Aug '03

A few updates to this project. First, I have completed work on a script which makes an export table. That is, it's completed if noone discovers a problem or feature that should be added. This table will have all windows versions in a row across the top, and dlls in a column down the left side. Each dll has an X for versions of windows - including wine which export that dll. The X is a link to one of the CGIs which queries for all APIs exported by that dll in that particular windows version. The script is currently generating the table and it seems it will take a good 8 hours or so to finish!! There is a HUGE number of dlls. I think some .ref files might not be from clean installs. If anyone can identify for certain dlls which are not part of windows please let me know so I can clean up the database and the table. You can check it's progress at http://24.229.94.2/export_table.html. I think when finished it could use some color, maybe a style sheet. Any other comments? The compare.cgi script now has a checkbox which toggles all output vs only differences as Dimi suggested. In case anyone noticed winnt40-sp6a queries did not return any results. The version field was truncated. I fixed it by dropping the 0. :) A windows NT 3.51 version has been added to the database. Juan Lang wrote: >Hi David--thanks for posting those! Here's my input: >Your list of APIs (from WINE, Windows versions) is not >likely to change terribly frequently. As such, I'd >suggest using your Perl script to pregenerate static >web pages that have some sought-after info. This >should cut down load on your box quite a bit. > >Perhaps there'll be debate on the most useful pages, >but personally I'd like to see: >- which DLLs exist under which versions of >Windows/WINE. I'm thinking a table which lists each >DLL (the union of all of them) in a row, and column >for each Windows version indicating whether it exists. >- for each DLL, which functions it exports under which >versions of Windows/WINE. > >Cheers, >--Juan > >__________________________________ >Do you Yahoo!? >Yahoo! SiteBuilder - Free, easy-to-use web site design software >http://sitebuilder.yahoo.com > > > >

1 0

bug in dlls/dplayx/version.rc drectx gurus please read.
by puoti＠inwind.it 07 Aug '03

07 Aug '03

I (Think) I've found a bug in dlls/dplayx/version.rc. As you can see from this bug report I submitted http://bugs.winehq.com/show_bug.cgi?id=1299 a few moths ago I discovered that m$ age of empires trial didn't run any more. Someone did some testing, and the result was that version 1.2 of version.rc worked, and version 1.3 didn't I did some testing and I discovered that the problem is in these two lines of code #define WINE_FILEVERSION 4,7,0,0 #define WINE_FILEVERSION_STR "4.7.0.0" Compiling wine with one of these two, or without both of them works perfectly, the game is quite playable, but if you compile with both (As in current CVS) when starting the game you get an error message saying that the game needs directx 6.1a I did send an email to the developer that sent the patch that adds these lines, but about 3 weeks have gone and I never got an answer. I don't think it's anything complex, the easy way is to just remove the 2 lines (Or one of them), but I suppose Lionel or some other directx developer could work out a better solution than that.

1 0

Re: Accept SIZE_MAXIMIZED as one of statuses of MDI windows
by Alexandre Julliard 07 Aug '03

07 Aug '03

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > @@ -1070,9 +1072,10 @@ STATUSBAR_WMSize (STATUSWINDOWINFO *info > width = parent_rect.right - parent_rect.left; > x = parent_rect.left; > y = parent_rect.bottom - infoPtr->height; > - MoveWindow (infoPtr->Self, parent_rect.left, > - parent_rect.bottom - infoPtr->height, > - width, infoPtr->height, TRUE); > + SetWindowPos(infoPtr->Self, HWND_TOP, > + parent_rect.left, parent_rect.bottom - infoPtr->height, > + width, infoPtr->height, SWP_NOZORDER); > + What is this change for? -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: partial implementation of msi.dll
by Gregory M. Turner 07 Aug '03

07 Aug '03

On Wednesday 06 August 2003 09:48 am, Mike McCormack wrote: > Hi, > > This is a partial implementation of the Microsoft Installer (msi.dll). > At the moment, it is capable of querying an MSI database with read only > SQL queries, but can't use it to install anything. > > Mike Cool! But "Micorosft Installer" might not be the most appropriate name for this implementation, eh? :P How about "Mike's Sexy Installer" ;) Having clearly delved into this deeper than most of us, how complete would you say the documentation for MSI is? What do you think is the future outlook of this work? -- gmt "Jesse Ventura took American politics and raised it to the level of professional wrestling." -- Argus Hamilton

2 1

Using Wine for Production Build Processes
by Bob Dixon 06 Aug '03

06 Aug '03

We currently support production build processes using both FreeBSD and Windows 2000 and we're interested in consolidating our builds on FreeBSD systems as much as possible. Our Windows builds currently run Visual Studio 6.0, 7.0, and 7.1 on Windows 2000 compute servers. There's an ongoing discussion about whether Wine is appropriate for trying to run these Windows builds. Rather than guessing or hacking around with this, I'd like to ask the experts. We're currently using some in-house tools that drive Visual Studio using a COM interface, vs using command-line compilers and nmake. Does it make sense to try to run these builds using Wine? Thanks! Bob Dixon

1 0

Re: PATCH - msvcrt.spec exports
by Alexandre Julliard 06 Aug '03

06 Aug '03

Steven Edwards <steven_ed4153(a)yahoo.com> writes: > This is untested on *nix build. With this we can build and link regression tests on Mingw again. > > Changelog: > Casper Hornstrup <chorns_at_users.sourceforge.net> > Fix export definition _onexit and atexit. This is wrong, _onexit and atexit are functions, not variables. The bug is in Mingw. -- Alexandre Julliard julliard(a)winehq.com

1 0

dlls/d3d8/device.c
by Gerald Pfeifer 06 Aug '03

06 Aug '03

I may be wrong, and I'm sorry if that's the case, but are you sure the following new code in dlls/d3d8/device.c does what you believe it does? if ((This->StateBlock->texture_state[Stage][D3DTSS_ALPHAARG1] == D3DTA_TEXTURE) && ((oldTxt == NULL) && (pTexture != NULL)) || ((pTexture == NULL) && (oldTxt != NULL))) { reapplyFlags |= REAPPLY_ALPHAOP; } && binds stronger than ||, so in fact the above boils down to (first line && second line) || third line while it occurs to me that you ment to achieve the following if ( This->StateBlock->texture_state[Stage][D3DTSS_ALPHAARG1] == D3DTA_TEXTURE) && ( ( oldTxt == NULL && pTexture != NULL ) || ( pTexture == NULL && oldTxt != NULL ) ) ) (Personally, I think it's also nicer to omit the parentheses around == and !=, but that's a different one.) Gerald -- Gerald Pfeifer (Jerry) gerald(a)pfeifer.com http://www.pfeifer.com/gerald/

2 1

Re: Web: Press section update
by biggun from the sun 06 Aug '03

06 Aug '03

Hi, The following links from LinuxWorld may be broken, above of each there is their new location: ** The latest and greatest ways to run Windows desktop apps http://www.linuxworld.com/story/32684.htm ** How to Install Neverwinter Nights on Linux http://www.linuxworld.com/story/32654.htm ** Codeweaver's CrossOver Office is the best way to do the wrong thing http://www.linuxworld.com/story/32751.htm *** IMO, definitively broken WINE and the WINEmakers http://www.linuxworld.com/linuxworld/lw-1998-12/lw-12-corel.html Corel's CEO shares Linux vision http://www.linuxworld.com/linuxworld/expo/lw-wine.html Stephan _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

1 0

re: __declspec(selectany)
by Dan Kegel 06 Aug '03

06 Aug '03

Boaz Harrosh (boaz(a)hishome.net) wrote: > background: > I have managed to compile ATL/WTL from MSVC6. > I will have available a public patch-file for patching ATL/WTL to > compile under wine, Once I have every thing running > > Question: > All symbols and functions declared __declspec(selectany) show up as > "duplicate symbols" errors on the linker. Eliminating it has the same > results. > > I have searched in google and the few lines I found is that GCC will > accept __declspec(selectany) if "-fms-extensions" is used. Well it will > accept it but will only ignore it all together. > > Does any body know how to properly merge duplicate definitions of > symbols in GCC? Yes, I think it's attribute((weak)). > (before I go and change the code) maybe a command line switch to the > compiler or linker can do the trick ? Part of the solution might be to apply the following patch to the gcc-3.3 source tree: Index: linux.h =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/config/i386/linux.h,v retrieving revision 1.42 diff -u -d -u -r1.42 linux.h --- linux.h 15 Nov 2002 14:57:12 -0000 1.42 +++ linux.h 5 Aug 2003 21:33:39 -0000 @@ -82,6 +82,14 @@ builtin_define ("__ELF__"); \ builtin_define ("__gnu_linux__"); \ builtin_assert ("system=posix"); \ + builtin_define ("__stdcall=__attribute__((__stdcall__))"); \ + builtin_define ("__cdecl=__attribute__((__cdecl__))"); \ + builtin_define ("__declspec(x)=__attribute__((x))"); \ + if (!flag_iso) \ + { \ + builtin_define ("_stdcall=__attribute__((__stdcall__))"); \ + builtin_define ("_cdecl=__attribute__((__cdecl__))"); \ + } \ if (flag_pic) \ { \ builtin_define ("__PIC__"); \ but I'm sure more is needed; I haven't tested this at all. (gcc/doc/extend.texi would need updating, too, at least, and maybe whatever code implements -fms-extensions.) I suspect the folks who did the original ms-extensions for gcc never figured we'd be compiling Windows source code on Linux, but here we are... - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

7 9

wine in the press :)
by Tom 06 Aug '03

06 Aug '03

Hi, I just seen this on /. I though I would post the link here. http://www.eweek.com/article2/0,3959,1210083,00.asp Tom

7 8

Re: WaitForMultipleObjects loops forever if passed an array of size zero
by Alexandre Julliard 05 Aug '03

05 Aug '03

Troy Rollo <wine(a)troy.rollo.name> writes: > @@ -412,7 +412,7 @@ > { > int ret, cookie; > > - if (count > MAXIMUM_WAIT_OBJECTS) return STATUS_INVALID_PARAMETER_1; > + if (count > MAXIMUM_WAIT_OBJECTS || count <= 0) return > STATUS_INVALID_PARAMETER_1; This is wrong, 0 is a valid count, and shouldn't cause an infinite loop. You'll need to debug this some more. -- Alexandre Julliard julliard(a)winehq.com

6 12

HELP with IID_XXX
by Boaz Harrosh 05 Aug '03

05 Aug '03

There are tons of: EXTERN_C const IID_XXX all over the COM place. My Wine App compiles and links fine but when I try to run it. I get the error: /home/wine/bin/wine: cannot open builtin library for 'C:\WINDOWS\SYSTEM\wtlmdi.exe': ./wtlmdi.exe.so: undefined symbol: CLSID_HTMLDocument How can I know of all the undefined symbols in my wine-app before I try to run it. can one force the linker to list all undefined simbols? and on more question is there a ready made program to take a defenition of type: MIDL_INTERFACE(" FC4801A3-2BA9-11CF-A229-00AA003D7352" ) to: DEFINE_GUID( IID_IObjectWithSite, 0xFC4801A3,0x2BA9,0x11CF,0xA2,0x29,0x00,0xAA,0x00,0x3D,0x73,0x52) ; Free Life Boaz

1 0

Stuck with winelib + DLL import
by Martin Wilck 05 Aug '03

05 Aug '03

Hi, after a good while I had some time to look at my winelib project again. Last time I worked on it was last December, before the "import library" concept was introduced. I had to realize that winelib had changed so much that I couldn't make my code compile anymore. I tried all day to figure it out for myself, but it seems I'll need some guidance. This is what I have (strongly simplified): a DLL written in C++ and an App (also C++) importing that DLL. I want to compile both under winelib, and link everything together to get a working app. I fail miserably in setting this up with winemaker like I did it in the past. This is what I understood so far: - DLLs now need an associated ".def" file to be imported, - winebuild generates ".def" from ".spec", - winewrap/winegcc are the future way to go, but they don't support building DLLs yet. My problem is that I don't have a "spec" file for my DLL except the winemaker-generated one (which is just a zero-length dummy). I also have no "def" file, and because the DLL is C++, I have no clue how to write a spec or def file manually (name mangling). Actually, I'd rather avoid writing that stuff by hand. It would be fine to use static linking instead of a DLL (ie the equivalent of linking statically with a .lib file), but I have no clue how to do that either except to brutally link all object files together into a single executable. As long as no wrapper code is involved, it seems that I can avoid the problem by simply linking with unix ld.so. But I recall that this is utterly wrong. In short, I am clueless. Any hints appreciated. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

1 0

Windows API db / find APIs missing for a given app
by David Miller 05 Aug '03

05 Aug '03

Recently I spent some time on this again and would like anyone interested in the database to take a look and email me comments. (What's good, how it can be better, and what features could be there, but aren't) Currently the web interface consists of a few forms which do the following: 1. Compare imports or exports between two windows versions. This will output all APIs imported or exported by a dll you specify along with which version exports that API. Example: you specify wine and windows95 as windows versions. Each API will say it is exported by wine only, win95 only, or both. It is color coded in the hope of making it slightly more readable. 2. Perform general queries. This just does SQL queries based on the criteria you specify. You can query by any or all fields. 3. Find unimplemented APIs for a given program. This locates all APIs imported by a specified application and outputs the ones which are unimplemented or stubs in wine. This is broken down by dll which the app tries to import from. Red APIs are not in wine spec files while blue APIs are listed as stubs in the spec files. There are only a couple of apps listed right now. Leave the application field empty for a complete list. I intend to make the output hyperlinks which will query for all apps importing that specific API. Maybe that will help find test cases when tracking down a bug. The forms are currently at http://24.229.94.2 Unfortunately I can't keep this as a permanent location. The PC is just too slow and the scripts really hog CPU. They do lots of SQL queries. :)

7 9

Crash in EnumMRUListA
by Duane Clark 05 Aug '03

05 Aug '03

Running MS Excel viewer, I seem to be able to crash it fairly easily when opening files. The is occurring in the apparently undocumented function EnumMRUListA, so I am not really sure what to expect here. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x40a231f0). In 32-bit mode. 0x40a231f0 (EnumMRUListA+0x88 [comctl32undoc.c:1056] in comctl32.dll.so): movl 0x0(%edi),%eax 1056 datasize = min( witem->size, nBufferSize ); Wine-dbg>bt Backtrace: =>0 0x40a231f0 (EnumMRUListA+0x88(hList=0x416c00b8, nItemPos=0x3, lpBuffer=0x405816a8, nBufferSize=0x800) [comctl32undoc.c:1056] in comctl32.dll.so) (ebp=40581230) 1 0x4097b3d9 (SHAddToRecentDocs+0x3c9(uFlags=0x2, pv=0x4058242c) [shellord.c:788] in shell32.dll.so) (ebp=40582414) 2 0x300c4151 (XLVIEW.EXE.EntryPoint+0xabc81 in XLVIEW.EXE) (ebp=40582530) 3 0x301851a2 (XLVIEW.EXE.EntryPoint+0x16ccd2 in XLVIEW.EXE) (ebp=40582950) 4 0x30047dae (XLVIEW.EXE.EntryPoint+0x2f8de in XLVIEW.EXE) (ebp=40582b94) 5 0x30046b30 (XLVIEW.EXE.EntryPoint+0x2e660 in XLVIEW.EXE) (ebp=40582c10) 6 0x300476cb (XLVIEW.EXE.EntryPoint+0x2f1fb in XLVIEW.EXE) (ebp=40582c44) 7 0x30047790 (XLVIEW.EXE.EntryPoint+0x2f2c0 in XLVIEW.EXE) (ebp=40582c68) 8 0x407de4f7 (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=40582c8c) 9 0x407de582 (WINPROC_CallWndProc+0x82(proc=0x300476d2, hwnd=0x10021, msg=0x111, wParam=0x2001, lParam=0x0) [winproc.c:219] in user32.dll.so) (ebp=40582cbc) 10 0x407e492f (CallWindowProcW+0xcf(func=0x4086e3f4, hwnd=0x10021, msg=0x111, wParam=0x2001, lParam=0x0) [winproc.c:2928] in user32.dll.so) (ebp=40582cf0) 11 0x407c7bd2 (DispatchMessageW+0x11e(msg=0x40582dc0) [message.c:886] in user32.dll.so) (ebp=40582d34) 12 0x30043eae (XLVIEW.EXE.EntryPoint+0x2b9de in XLVIEW.EXE) (ebp=00000000)

2 1

__declspec(selectany)
by Boaz Harrosh 05 Aug '03

05 Aug '03

background: I have managed to compile ATL/WTL from MSVC6. I will have available a public patch-file for patching ATL/WTL to compile under wine, Once I have every thing running Question: All symbols and functions declared __declspec(selectany) show up as "duplicate symbols" errors on the linker. Eliminating it has the same results. I have searched in google and the few lines I found is that GCC will accept __declspec(selectany) if "-fms-extensions" is used. Well it will accept it but will only ignore it all together. Does any body know how to properly merge duplicate definitions of symbols in GCC? (before I go and change the code) maybe a command line switch to the compiler or linker can do the trick ? Free Life Boaz Harrosh

1 0

Thai Keyboard map Patch
by Supphachoke Suntiwichaya 05 Aug '03

05 Aug '03

Hi, This is a patch for Thai keyboard map. MrChoke -- Name : Supphachoke Suntiwichaya Email : MrChoke(a)opentle.org URL : http://www.opentle.org/~mrchoke/ Distribution : Linux TLE 5.0 (Andaman) OS : Linux 2.4.22-pre6-ac1 #1 พฤ. ก.ค. 24 16:45:01 ICT 2003 i686 GNU/Linux Uptime : 11:15am up 1 day, 2:40, 1 user, load average: 0.08, 0.18, 0.29 --- wine-20030709/dlls/x11drv/keyboard.c 2003-07-09 11:22:57.000000000 +0700 +++ wine-20030709/dlls/x11drv/keyboard.c-th 2003-08-05 09:29:24.000000000 +0700 @@ -646,6 +646,15 @@ "<>" }; +/*** Thai (Kedmanee) keyboard layout by Supphachoke Suntiwichaya <mrchoke(a)opentle.org> */ +static const char main_key_th[MAIN_LEN][4] = +{ + "`~_%","1!å+","2@/ñ","3#-ò","4$Àó","5%¶ô","6^ØÙ","7&Öß","8*€õ","9(µö","0)š÷","-_¢ø","=+ªù", + "qQæð","wWä\"","eEÓ®","rRŸ±","tTÐž","yYÑí","uUÕê","iIÃ³","oO¹Ï","pPÂ","[{º°","]}Å,", + "aA¿Ä","sSËŠ","dD¡¯","fFŽâ","gGà¬","hHéç","jJèë","kKÒÉ","lLÊÈ",";:Ç«","\'\"§.","\\|£¥", + "zZŒ(","xX»)","cCá©","vVÍÎ","bBÚ","nN×ì","mM·?",",<Á²",".>ãÌ","/?œÆ" +}; + /*** VNC keyboard layout */ static const WORD main_key_scan_vnc[MAIN_LEN] = { @@ -724,7 +733,7 @@ {"Israeli keyboard layout", &main_key_IL, &main_key_scan_qwerty, &main_key_vkey_qwerty}, {"VNC keyboard layout", &main_key_vnc, &main_key_scan_vnc, &main_key_vkey_vnc}, {"Greek keyboard layout", &main_key_EL, &main_key_scan_qwerty, &main_key_vkey_qwerty}, - + {"Thai (Kedmanee) keyboard layout", &main_key_th, &main_key_scan_qwerty, &main_key_vkey_qwerty}, {NULL, NULL, NULL, NULL} /* sentinel */ }; static unsigned kbd_layout=0; /* index into above table of layouts */

1 0

Re: Trackbar select range tweaks
by Dustin Navea 04 Aug '03

04 Aug '03

--- Duane Clark <dclark(a)akamail.com> wrote: > Dustin Navea wrote: > > ok thx, running on win2k sp2, the attached executable showed > > > > GetSystemMetrics(SM_CYCAPTION) = 19 > > > > Hmm, that's interesting. I'm running Win2K "Professional" SP3. Anyway, I > played around a bit and found out that if I login as administrator, then > GetSystemMetrics(SM_CYCAPTION) = 19, but if I login as dclark then > GetSystemMetrics(SM_CYCAPTION) = 20. Very strange ;) There is no visible > difference between the two accounts that I can see. In both cases, the > thumb is 21. > > I can get a different metric if I set Windows to use large fonts, and > that does increase the size of the trackbar thumb. That is odd.. Because when I ran that, I was running it on a user account on a computer that I did not have administrative access to.. here is the output on my home comp (w2k sp3) from my user acct: GetSystemMetrics(SM_CYCAPTION) = 19 admin acct in a min.. ===== -- Dustin Navea Minor Contributor, http://www.winehq.com Bugzilla Janitor, http://bugs.winehq.com Network Admin, irc://irc.blynk.net (down) __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Re: [dx73b] Try3: Performance of texture states
by Gregory M. Turner 04 Aug '03

04 Aug '03

On Sunday 03 August 2003 05:02 am, Ann and Jason Edmeades wrote: > (Try#3 - Also fixes Operation Flashpoint problem which was introduced > AND includes the patch... oops!) My goodness... Flashpoint works? How long has that been? Good $*^!$#^@ work!! But: you should /not/ have told me this as I will be much less productive now. -- gmt "Microsoft is committed to making cabinet files an open technology" http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncabsdk/h…

2 1

Profiling wine
by Mike Hearn 04 Aug '03

04 Aug '03

Hi, Is there any way to get measurements of where Wine is spending most of its time? I have a problem where typing text into the WebBrowser control is incredibly slow, but don't really have a clue where to start looking. A profiling tool would be handy about now...... thanks -mike

6 6

RE: Linking to _wtol function
by thomas.mertes＠gmx.at 04 Aug '03

04 Aug '03

"Robert Shearman" <R.J.Shearman_at_warwick.ac.uk> wrote: > I'd like to get people's opinions on how I should link to the _wtol function > from a Wine DLL. Should I: > > a) Link to NTDLL and use the function there > b) Link to MSVCRT and use the function there > c) Create a new function in unicode.h > d) Copy the function into my DLL a) and b) are equivalent. In dlls/msvcrt/msvcrt.spec _wtol is just a link to ntdll._wtol. I suggest you use a) since NTDLL is always present (in NT systems). If your program/dll should also run in DOS based systems you should use b). Btw. The wine implementation of the _wtol function is okay, so c) is not necessary. And code duplication d) is also not a good idea. > In that case should I reimplement _wtol in NTDLL function using strtolW? The > rest of the functions in wcstring.c call their libunicode versions, but this > one doesn't. This is wrong the only function in wcstring.c calling strtolW is _wcstol. As you can see in the changelog several months ago I implemented the functions _ultoa, _ltoa, _itoa, _ui64toa, _i64toa, _atoi64, _ultow, _ltow, _itow, _ui64tow, _i64tow, _wtol, _wtoi, _wtoi64. There are also test functions for this functions in the dlls/ntdll/tests directory. All this functions work correct and are documented. There is no reason to rewrite them for fun unless you find a bug. If you want to write little library functions, It is not necessary to rewrite something already working. Search for library functions in msvcrt. There are tons of unimplemented functions. Greetings Thomas Mertes -- COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -------------------------------------------------- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post

1 0

Strange code in misc/registry.c
by Lionel Ulmer 04 Aug '03

04 Aug '03

Hi all, Having lately some strange crashes when I start Wine with any --debugmsg command, I started to look at where the problem occured. >From my investigations, it came in the file misc/registry.c while loading 'system.1st' (yeah, I know, I should run in a no-Windows install, but well, my Wine installation is 6 years old and still working, so I won't change now :-) ). Anyway, the faulty function is '_strdupnA'. I added some traces and I have this : 0009:trace:reg:_strdupnA System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick (0x3c003f40) 79 0009:trace:reg:_strdupnA 0x3c003f90 This means that the string given as a parameter has the pointer '0x3c003f40', the length parameter is '79' and it returns '0x3c003f90'. It crashes later on at : 0009:trace:reg:_strdupnA System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM (0x3c003f90) 114 0009:trace:reg:_strdupnA 0x3c003418 So we give the '0x3c003f90' pointer (which is of length 79 as seen in the previous debug output) but (if you look at the code), will read 114 bytes from it (as the function uses 'memcpy' and not 'strncpy'). The attached patch fixes all crashes on my box, but well, as I am not very familiar with this code, sent it to wine-devel and not wine-patches for review by Registry gurus :-) Lionel -- Lionel Ulmer - http://www.bbrox.org/

2 6

Linking to _wtol function
by Robert Shearman 04 Aug '03

04 Aug '03

Hi, I'd like to get people's opinions on how I should link to the _wtol function from a Wine DLL. Should I: a) Link to NTDLL and use the function there b) Link to MSVCRT and use the function there c) Create a new function in unicode.h d) Copy the function into my DLL Rob

2 3

Re: Small FAQ fixes
by Tom 04 Aug '03

04 Aug '03

Francois Gouget wrote: >Changelog: > > * documentation/faq.sgml > > Small spelling/punctuation fixes. > Small rephrasings. > > > > Hi, Small question.. If I take Mikes updates and these updates and apply them againt the faq.template in /lostwages can we just update the faq there ? And whenever a large amount of changes have been made just build a .sgml of it. Or just make sure we update both at the same time ? Because the way were going I have sent patches to update the .template and you guy's have sent patches againt this one and before long there going to be two very different faq's. Comments ? Tom

2 2

Re: Trackbar select range tweaks
by puoti＠inwind.it 03 Aug '03

03 Aug '03

If it can help, I can run this on windows server 2003 (Evaluation copy, I would never buy anything from m$). Dustin Navea wrote: > could someone send me the testcase and i will run it on a win2k machine, a > win98 machine and a winxp machine? > Hmm, an executable for determining the SM_CYCAPTION metric is small, so I'll attach that. It comes from this code. #include "windows.h" #include "stdio.h" main() { printf("GetSystemMetrics(SM_CYCAPTION) = %d\n", GetSystemMetrics(SM_CYCAPTION)); } For determing thumb size, I use MS ControlSpy, available here: http://www.microsoft.com/msj/0798/controlspy.aspx That includes binaries. Just run the Trackbar binary, click on "TBM_GETTHUMBLENGTH" in the window on the lower left, and then click the "Send" button. In the window below that button, it should say something like: lResult: 21 (0x15) which means the thumb size is 21.

1 0

Re: CVS Update: reactos
by Steven Edwards 03 Aug '03

03 Aug '03

There have been some minor additons to ReactOS's pe.h to help identify X-box applications. It is my understanding that X-box applications use a form of directx and a NT like kernel so maybe the WINE project can make use of some of the initial work we are doing to add support these applications. Thanks Steven --- ea(a)mok.lvcm.com wrote: > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/include/ > Changes by: ea(a)mok.lvcm.com 03/08/03 08:34:52 > > Modified files: > reactos/include/: pe.h > > Log message: > IMAGE_SUBSYSTEM_EFI_xxx added (KJK::Hyperion) > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

(no subject)
by puoti＠inwind.it 03 Aug '03

03 Aug '03

I've decided I'll include the wine faq and wine user guide into my next wine rpm, but I've noticed that the docs need some updates. For a start, they need a version for rpm packages, it seems a bit crazy to install a binary rpm of wine, open the user manual, and find a guide on where you can download wine and howto compile the source, one would usually expect something like 'thank you for installing wine, we hope you enjoy out product'. Also, as the wine packaging guide says that rpms should get the user up and running in minutes, using a script or something like winesetuptk, so I don't think that a guide for end users that what to install office/there new windows 3D game/whatever should have a long description of the wine config file (I don't remember seeing documentation about the windows registry anyware after installing windows 98). The current manual presumes that one doesn't have wine installed, so all the where to get/how to install part should go, at least from the version we want i packages after 1.0, and something like 'you can download the most recent version of wine from <link to the wine sourceforge download page>' should go in it's place. Once wine reaches 0.9, I would be happy to help updating the docs, so we have something very user friendly before 1.0, and I could also translate the docs to italian.

2 1

Re: Trackbar select range tweaks
by BiGgUn 03 Aug '03

03 Aug '03

> Changelog: > Oops, initial thumb length doesn't appear to depend on > SM_CYCAPTION after all. Thumb length DOES depend on GetSystemMetrics( SM_CYCAPTION) on a native platform. ( thumb_length = GetSystemMetrics( SM_CYCAPTION) + 2 [with no select range]) If wine uses standard values from windows there's no matter. But if a user decides to change these values in its registry, trackbars won't reflect those changes in their sizes. So i think that thumb length still need to depend on this metrics value. Stephan > /* initial thumb length */ > clientMetric = GetSystemMetrics(SM_CYCAPTION); > ....

3 3

Re: [dx73b] Try2: Performance of texture states
by Marcelo Duarte 03 Aug '03

03 Aug '03

You forget the patch ;) ----- Original Message ----- From: "Ann and Jason Edmeades" <us(a)the-edmeades.demon.co.uk> To: "wine patches" <wine-patches(a)winehq.com>; "Raphael Junqueira" <fenix(a)club-internet.fr> Sent: Saturday, August 02, 2003 8:19 PM Subject: [dx73b] Try2: Performance of texture states > (Try#2 - Also fixes Operation Flashpoint problem which was introduced) > > This is the first patch which looks at the performance of changing the > textures on a texture unit. As was pointed out to me by Lucho, certain > information is per texture unit and hence not affected when a different > texture object is bound. This patch on my machine changes the displayed > fps by the Billboard sample from 30.6 to about 42.6. [Actually it was > 43.0 > with patch b, but I dont see why!] > > There is still more optimization which can be done here, but this is a > start. > > Let me know if anyone notices any regressions with this one. > > Changelog > Only reapply the texture states necessary when a different texture gets > bound to the same texture unit. > Jason >

1 0

Re:how to use wine on linux??
by puoti＠inwind.it 03 Aug '03

03 Aug '03

This site may help you http://digilander.libero.it/winehqitalia

1 0

how to use wine on linux??
by csy annie 02 Aug '03

02 Aug '03

hi, i'm new to WINE. I've install it on linux in order to run my developed chat application (which need to run with a file called 'client.dll). Inorder to run windows application on linux i've choose to install WINE. However, i don't know how to use it after installing & configuring it on my linux(mandrake). For example, if i want to run my java file 'Client.java'. Do i type java Client.java to run as normal java program?? If so, will WINE automatically detect it's a windows file & execute it?? If not, what should i do?? Thanks in advance. _________________________________________________________________ Download ringtones, logos and picture messages from MSN Malaysia http://www.msn.com.my/mobile/ringtones/default.asp

1 0

[antony@antgel.co.uk: .msi files]
by Antony Gelberg 01 Aug '03

01 Aug '03

Hi Wine developers, I posted this to the wine-users list but no joy. I was wondering if anyone could give me some advice? Does Windows Installer work? Sorry for posting here, but I have searched and searched and just can't find anything helpful on the subject. FYI - I'm using ~/.wine/fake_windows, as I want to eventually get rid of my Windows partition altogether. But if anything needs copying across, I can do that. On another note, I'm really surprised that the wine-users list is so quiet as it's such an important bit of software. Antony ----- Forwarded message from Antony Gelberg <antony(a)antgel.co.uk> ----- From: Antony Gelberg <antony(a)antgel.co.uk> To: wine-users(a)winehq.com Subject: .msi files Hi all, I've done some searching, but no joy. Anyone have any idea on how to install software that needs Windows Installer to install? I've tried installing bout the 98 and 2K versions under wine, but only get: cdrom $ /usr/local/bin/wine ./instmsiw.exe fixme:win32:PE_CreateModule Security directory ignored fixme:process:CreateProcessA (X:\IXP000.TMP\msiinst.exe,...): NORMAL_PRIORITY_CLASS ignored cdrom $ /usr/local/bin/wine --version Wine 20030709 cdrom $ Any ideas? Antony ----- End forwarded message -----

2 1

Re: Trackbar size fixes
by Duane Clark 01 Aug '03

01 Aug '03

Mike Hearn wrote: > On Tue, 2003-07-29 at 05:19, Duane Clark wrote: > >>I have done quite a bit of comparison testing with ControlSpy on Wine >>and Win2K, so these changes should be accurate. Mainly done to fix >>earthquake (which was completely broken). >> >>Changelog: >> Fix the size/position of the thumb/channel/tics to match Win. > > > There's clearly something strange going on here we don't fully > understand - this patch breaks Internet Explorer again. See attached > screenshot. Builtin after this patch is on the left, native (98) is in > the middle, CVS wine is on the right. Hmm, attached is what that looks like for me. So I don't know why it looks bad to you. > Horizontal trackbars are still OK, though with this patch the thumb is > bigger than native 98. I didn't bother with a screenshot of that since > it still looks OK. One part of the code I did not test is the function TRACKBAR_InitializeThumb(), which sets the initial thumb length. My confidence in that part is not very good, since it doesn't make sense to have different calculations for the horizontal and vertical bars. So if someone were to do some simple testing to verify/correct that function, it would be a good thing. All of the rest of the patch sets the rest of the dimensions of the control based on the length of the thumb and the size of the window, which is how Windows does it. That part I tested extensively, and am very confident is correct.

4 8

thanks for all the help :)
by Mike Hearn 01 Aug '03

01 Aug '03

Well, I made it. Our app no longer crashes, hangs, or blows its resource limits :) A slightly close shave with only 2 hours to go before I leave the company, but never mind. A big thanks to all the people who helped me, especially Ove, Mike, Robert, Greg, all the others and of course Alexandre. I've got quite a few bugfixes in my tree, which I'll try and get submitted sometime next week before I go off to bum around Europe for a month. I'll also try and do a patch dump of the DCOM stuff, which is just oves work (badly) merged with some bugfixes, a few new features and lots of no-op changes and useless trace statements. I never did bother figuring out or eliminating the duplication between Oves and Marcus' code, so it's not really in a mergable state. If nobody else attempts to do a proper merge then hopefully I'll get time to do it, this code is really useful. It'd be quicker/easier for a COM guru however. thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

1 0

Website Question
by dd jj 31 Jul '03

31 Jul '03

Hello Everyone, Does anyone know a website listing all the Win32 API calls and their X window API equivalents or Unix command equivalents? Thank you --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

1 0

Licensing Question
by Anthony Tuininga 31 Jul '03

31 Jul '03

The MingW32 project is developing its own set of Windows headers under a different license than Wine (which uses LGPL, right?) and I have noticed (using both projects) that the Wine headers are more complete in a number of areas. I was wondering if it would be acceptable to use the Wine headers as a source for filling in gaps in the MinGW32 headers? In essence, would the Wine group be willing to allow this cross pollination since (clearly) it would be a violation of the licenses as they stand today. Any thoughts on this? Or am I treading into a minefield?? :-) -- Anthony Tuininga anthony(a)computronix.com Computronix Distinctive Software. Real People. Suite 200, 10216 - 124 Street NW Edmonton, AB, Canada T5N 4A3 Phone: (780) 454-3700 Fax: (780) 454-3838 http://www.computronix.com

5 4

Expect deadlock!
by Marcelo Duarte 31 Jul '03

31 Jul '03

Hi all, Somebody could help saying me what it means the messages below and where I must look for to finish with them? Thank you! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! err:win32:_EnterSysLevel (0x4087eda8, level 2): Holding 0x4092f8e0, level 3. Expect deadlock! -- Marcelo Duarte

4 4

Unhandled exception (wine-20030709)
by Magnus Solvang 30 Jul '03

30 Jul '03

(I posted this to the wine-users-list a week ago, but didn't get any respons) I just tried to install wine for my first time. Redhat 9.0, kernel 2.5.73. Downloaded the rpm-binary, but when trying to start notepad.exe, it looped with a message like: wine: Unhandled exception (thread 01f9), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: While looping it started nearly 255 processes (max PTYs?), before the machine halted. I did this before modifying my config-file (using the default one). After adjusting the config-file, I no longer got any error-messages, but the same thing happened. [...] wine: Unhandled exception (thread 01f1), starting debugger... wine: Unhandled exception (thread 01f3), starting debugger... wine: Unhandled exception (thread 01f5), starting debugger... wine: Unhandled exception (thread 01f7), starting debugger... wine: Unhandled exception (thread 01f9), starting debugger... wine: Unhandled exception (thread 01fb), starting debugger... Fine! I then tried to compile wine from source, but at the end of the installation (su root/make install - wine only), the same thing happened: [...] wine: Unhandled exception (thread 01f5), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01f7), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01f9), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01fb), starting debugger... Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Could not stat /cdrom (No such file or directory), ignoring drive D: wine: Unhandled exception (thread 01fd), starting debugger... ./tools/wineinstall: line 645: 26966 Killed $REGEDIT $DEFREG >/dev/null Registry install failed. I managed to open a terminal and do a "killall -9 wine". This happened during "make install", so I didn't get to edit the config-file before this happened. I have tried booting with both 2.4 and 2.5-kernels, with the same result. - M

2 2

fontview.exe...
by Jonathan Wilson 30 Jul '03

30 Jul '03

Its used by windows to display fonts before and after installation. And I know of at least one setup program (might have been a Corel app, I forget) that displays a long list of fonts which you can select from to install and then uses fontview.exe (I think its fontview.exe, it loks very similar anyhow) for previewing the fonts (so you can see what they look like before they are installed). Anyone want to comment on this: 1.does anyone else remeber the app and/or the dialog? 2.does anyone know if it really is fontview.exe? 3.does wine need a fontview.exe? and 4.if I was to code a fontview.exe, would it be of use to anyone (wine, reactos etc)?

2 1

Strange behavior on build
by David D. Hagood 29 Jul '03

29 Jul '03

I'm having a strange behavior trying to build Wine on my machine at work (which is a modified RH7.3 machine): First of all, if I attempt to do a standard CVS checkout followed by a make depend, the make depend failes with a "dlls - no such directory" error, even though it exists. Changing SHELL=/bin/sh to SHELL=/bin/bash in Make.rules and re-running configure fixes this, but then I get stuck in a loop building - it looks like the makefile starts building the dependancy "wine", then builds "libs", then decides it needs to build "wine" to build "libs" and starts that, then builds "libs".... I'm at a bit of a loss to explain the behavior, so does anybody have any good suggestions? Versions: GNU bash, version 2.05b.0(1)-release (i586-redhat-linux-gnu) Copyright (C) 2002 Free Software Foundation, Inc. GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i386-redhat-linux-gnu Linux version 2.4.20-openmosix1 (root@(none)) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)) #1 Sun Jan 12 04:18:51 CST 2003 (if you would be so kind, please copy my work address of David decimalpoint Hagood ('A'-1) aeroflex decimalpoint com since I am only subscribed to the list on my personal email).

1 0

API tracking and documentation
by Steven Edwards 29 Jul '03

29 Jul '03

Hello, The ReactOS project is interested in making a change to WINE the function commented that would make API tracking a little nicer. We have implemented a web page like the mono project has that shows the implemented and unimplemented functions in the API. Will the WINE project accept patches to the comments to support this type of tracking system? It would be nice because you guys could implement the same thing on your website. If the answer is no it is REALLY going to be a PITA for us to diff our sources to yours for every function. Please take a momenet to look at the site and how it works. http://reactos.wox.org/index.php?page=apistatus Here is the documentation for how we do it. Abstract Explains what tags are and how to use them. TABLE OF CONTENTS * 1 Overview * 2 MS API compatibility 1 Overview We define tagging a function as the process of associating metadata with a function. We define a tag to be a piece of information that has a well-defined meaning. A tag has one attribute - a name. The name of a tag always begin with the at sign (@) and it can include only the letters a-z and digits 0-9 and the underscore (_). Tagnames are case-insensitive. In the future a tag could have one more attribute - a value, but this is currently not needed. In ReactOS, tags are currently only used to track compatibility with Microsoft APIs, but it could be used for so much more. Tags are applied to functions by including them in a comment just before the function. Eg. if you have a function called MyFunction, then you can tag it with the tag @mytag like this: /* * @mytag */ VOID MyFunction() { } 2 Microsoft API compatibility Two tags are defined to track compatibility with Microsoft APIs. @implemented and @unimplemented. Apply @implemented to functions which match and behaves like a Microsoft API. Use @unimplemented to functions which match, but does not behave like a Microsoft API. The regenstat tool (located in reactos/tools/rgenstat) will parse the source code for these tags and generate an xml file containing functions that have these tags. The xml file can be processed by the rapistatus.xsl xml stylesheet (located in reactos/tools/rgenstat/web) to create an html file suitable for display using a browser. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

3 3

Re: Trackbar size fixes
by Mike Hearn 29 Jul '03

29 Jul '03

Odd, I remember doing some work on the trackbar a few months ago (it was pretty broken). Testing against the native comctl32 from Windows 98 showed that I got it pretty close - do you have before/after screenshots for this patch? Perhaps the trackbar looks different in 98 vs 2K. -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 2

WineHQ website (lostwages) url changes
by Jeremy Newman 29 Jul '03

29 Jul '03

I spent some time today working on the lostwages codebase. I finally discovered how to get PHP to see the PATH_INFO without getting a 404. Seems you need to put "AllowPathInfo On" in the .htaccess. In doing so, I can get rid of the ugly ?page=about urls and instead use /site/about. I updated .htaccess to catch the old urls and put them to the new style. NOTE to template authors, if you want to put a relative link in the site from now on, use {$root} to have the site put the correct path in for you. For example, <a href="{$root}/site/about">About Wine</a>. This also works for images: <img src="{$root}/images/foo.jpg"> -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

2 2

Re: Trackbar size fixes
by maxime.bellenge＠laposte.net 29 Jul '03

29 Jul '03

A recent patch ( 2 or 3 monthes I think) for trackbars broke them totally in emule. So there was a problem for sure. I have not tested the patch yet to know if it is fixed now. >Odd, I remember doing some work on the trackbar a few months ago (it was >pretty broken). Testing against the native comctl32 from Windows 98 >showed that I got it pretty close - do you have before/after screenshots >for this patch? Perhaps the trackbar looks different in 98 vs 2K. > > >-- >Mike Hearn <m.hearn(a)signal.qinetiq.com> >QinetiQ - Malvern Technology Center Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

2 1

dmusic loader question
by Rok Mandeljc 29 Jul '03

29 Jul '03

I was planning to (properly) implement DirectMusic Loader, based on example I've found in MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmusic/ht…). But as I don't have enough experience with COM interfaces, I got stuck with implementing IStream interface; how does one declare interface, which consists of two other interfaces (CMyIStream class in example code is actually IDirectMusicGetLoader and IStream at the same time)? BTW, is it illegal to use MSDN examples to implement stuff in wine (EULA...)? -- Rok Mandeljc <rok.mandeljc(a)gimb.org> "All that is gold does not glitter, Not all those who wander are lost; The old that is strong does not wither, Deep roots are not reached by the frost. From the ashes a fire shall be woken, A light from the shadows shall spring; Renewed shall be blade that was broken, The crownless again shall be king." -- J.R.R. Tolkien

3 3

how cards.dll works
by Jonathan Wilson 29 Jul '03

29 Jul '03

After finding out that certain things I did when coding cards.dll (such as studying the complete code in a disassembler) mean that any code I write for it a potential "derivitave work", I have come up with a descrition that is (hopefully) detailed enough to enable someone else with windows GDI programming experience to write cards.dll for wine but (hopefully) not detailed enough to be considered a "derivitive work" The folowing files can be made available to whoever ends up working on cards.dll: 1.cards.spec, a ready made spec file for the dll 2.cards.rc, a RC file containing the card bitmaps (which are licenced under a licence that gave permission to use them) and also the card back bitmaps that were sent to me before (to whoever ends up working on this, feel free to modify the images if you dont like them :) 3.makefile.in ready made for the dll and 4.cards.h which contains the publicly documented interface to cards.dll (which I pulled from various info documents found on the net) IANAL but I dont think that any of these could be claimed to be covered by that "derivitave work" thing, if they are, please do tell me. This document explains the workings of cards.dll (version 5.00.2134.1 from windows XP SP1) Cards.dll exports 7 different functions. These are: cdtInit cdtTerm cdtAnimate cdtDraw cdtDrawExt DllMain and WEP cdtInit takes 2 int * variables. It should return TRUE if the initalization was sucessfull and FALSE if it was not. It is a place to do any initalization you require (depending on for example if you want to preload the resource bitmaps or whatever). It should return the x and y size of the card bitmaps in the 2 variables. For the cards I am using, the x size is 71 and the y size is 96 (which just happened to match up with the size of microsofts cards which is good) the main purpose of DllMain is to store the HINSTANCE of the cards.dll to use later when the bitmaps are loaded WEP is a holdover from when cards.dll was a 16 bit dll and doesnt actually need to be implemented (since its never called by 32 bit windows) cdtTerm is where you undo anything you did in cdtInit (such as unloading any preloaded resources) It takes no parameters and returns nothing. cdtAnimate is supposed to handle animations for the card backs but since the backs we are using dont animate, it can just return TRUE (hence why the resource file I wrote returns the windows XP version number since XP doesnt have animated backs either) As for parameters, it takes a HDC, an x and y position and a frame number (each individual microsoft back has a specific number of frames and applictions tend to hard-code these values) cdtDraw basicly calls cdtDrawExt passing the default size of the card bitmaps as the x and y size parameters The real work is done in cdtDrawExt This function takes: a HDC (for the screen window to draw the card on) an X positon and a Y position to draw the card at a card number (cards.h lists the different values) a mode number (again cards.h lists the different values) and a RGB background color What the function does depends on the value of the mode. If the upper bit of md (which is an int) is set, then it shouldnt save and resore the corner pixels (as explained below) modes greater than 7 should (as far as I can tell) do nothing. mode 0 is "draw face card" mode 1 is "draw back" mode 2 is "draw highlighted face card" mode 3 is "draw empty card spot" mode 4 is "erase card" mode 5 is "draw empty card spot but doesnt paint background" mode 6 is "draw red X card" and mode 7 is "draw green O card" all modes use the same "drawing logic" except for mode 4 which doesnt draw any bitmap. You need a resource ID and a raster OP to do the drawing For modes 0 and 2, the resource ID uses this formula resource id equals ((((card number shl 2) mod 0dh) plus ((card number and 3) times 0dh)) plus 1) For mode 1, the resource ID is just the card number For modes 3 and 5, the resource ID is 53 (the resource ID of the empty card spot graphic, also the contant hb in cards.h) For mode 1, the resource ID is just the card number For mode 6, the resource ID is 67 (the resource ID of the card with the red X on a green background graphic, also the contant xb in cards.h) For mode 7, the resource ID is 68 (the resource ID of the card with the green O on a green background graphic, also the contant ob in cards.h) and mode 4 doesnt use any ID since it doesnt draw anything. For the raster OP, all modes use SRCCOPY except for: mode 2 which uses NOTSRCCOPY and modes 3 and 5 which use SRCAND Also, if the mode is 0, the background color is set to white (0xFFFFFF) before drawing. And after drawing, if the card is a red card (resource IDs 0x0E to ox17 and 0x1B to 0x24), it paints over the boarders of the card using PatBlt and the BLACKNESS rasterop. If the mode is 3 or 4, it creates a solid brush using the background color, uses SetBrushOrgEx to set the brush origin to the screen DC origin and then uses PatBlt to paint over the area of the card using PATCOPY. If the mode has the top bit clear (as explained above) and the size matches with the default card size, before drawing, it saves the corner pixels of the cards (the card bitmaps I am using have one pixel in each corner) and then restore them after drawing. To do the actual drawing, you need to load the bitmap resource into memory and load the resulting HBITMAP into a memory DC. You also need to set the background color of the screen DC to whatever was passed in (unless its mode 0, in which case its 0xFFFFFF as explained above). And then, you need to copy the data from the memory DC to the screen DC using either BitBlt or StretchBlt as appropriate. Remeber to free all the GDI resources (bitmaps, memory DCs etc) that you used. And also to restore the background color to whatever it was before you changed it. If the function is a sucess, you return TRUE. If the function is a failure (e.g. a GDI function call fails), you return FALSE. Hoepfully someone can use this information to implement cards.dll in a way that is legally safe.

2 1

mailing lists down 9am - 7pm CST
by Jeremy Newman 28 Jul '03

28 Jul '03

The WineHQ mailing lists were down today. There was a message in the queue that caused mailman to bomb. I found and removed the message (it was a spam). I also stayed in late and upgraded our Mailman to ver 2.0.13 from ver 2.0.0. Let me notice if you notice anything unusual happening in the next few days. Also, I am considering putting a SpamAssassin filter into our Mailman using info from this page: http://www.daa.com.au/~james/articles/mailman-spamassassin/ Anyone against this idea? -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

1 0

Re: Is wine a debugger?
by Dan Timis 28 Jul '03

28 Jul '03

Dan Timis wrote: > I am trying to load a security Windows dll that does not run under a > debugger. When I load the dll I get a SIGTRAP, and then wine breaks > in its debugger. > My understanding is that if I run wine as opposed to winedbg I am not > running under a debugger. But, if there is a crash or some other > exception wine will start a debugger. > I sent some memory dumps to the developer of the security dll, and he > said that it behaves like it was running under a debugger. He's > question was something like does wine have an always "on" debugger? Just in case someone else runs into this problem, the fix is to run wine as nt not as win98. Thanks to Alex Pasadyn for the help. Dan Timis Muse Research, Inc.

1 0

Re: first go at some notepad changes
by Dmitry Timoshkov 28 Jul '03

28 Jul '03

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > > A possibility that status bar will change its size behind your back > > justifies the use of GetWindowRect. > ok, good point. > I intend to change it to use GetWindowRect. > But I am going to keep the WM_SIZE stuff in there unless someone can show a > reason why its a bad idea. WM_SIZE is usually sent due to a change in the window size in order to notify window and allow it to do some necessary job. Sending a bogus WM_SIZE might easily mess the thing up since the size you are sending might be not a real window size. -- Dmitry.

1 0

Re: first go at some notepad changes
by Dmitry Timoshkov 28 Jul '03

28 Jul '03

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > +VOID DIALOG_ShowStatusBar(VOID) > +{ > + RECT rcs; > + RECT rc; > + GetClientRect(Globals.hMainWnd, &rc); > + Globals.bStatusBarEnabled = !Globals.bStatusBarEnabled; > + if (Globals.bStatusBarEnabled == TRUE) > + { > + ShowWindow(Globals.hStatusBar,SW_SHOW); > + GetClientRect(Globals.hStatusBar,&rcs); > + Globals.iStatusBarHeight = rcs.bottom - rcs.top; > + SendMessage(Globals.hStatusBar, WM_SIZE, 0, 0); > case WM_SIZE: > - SetWindowPos(Globals.hEdit, NULL, 0, 0, LOWORD(lParam), HIWORD(lParam), > + SetWindowPos(Globals.hEdit, NULL, 0, 0, LOWORD(lParam), (HIWORD(lParam)-Globals.iStatusBarHeight), > SWP_NOOWNERZORDER | SWP_NOZORDER); > + if (Globals.bStatusBarEnabled == TRUE) > + { > + SendMessage(Globals.hStatusBar, WM_SIZE, 0, 0); > + } Do not send bogus WM_SIZE messages, use SetWindowPos instead. Remove iStatusBarHeight from globals and use IsWindowVisible and GetWindowRect when you need to take into account status bar size. -- Dmitry

4 5

Re: [Mono-winforms-list] SWF Examples/Tests
by Mike Hearn 28 Jul '03

28 Jul '03

This will be really great for Wine also, I'm forwarding this on to the Wine list. We really need tests like this, but AFAIK nobody has ever done them. As you can see the Wine widget toolkit does not implement all the features of the MS Windows one (primarily because very few apps actually use them). Nonetheless, adding them should be easy, and it's good to have a refererence like this. thanks -mike On Mon, 2003-07-28 at 11:47, Timothy Parez wrote: > Hi, > > Some time ago I started writing simple tests for SWF control rendering. > At that time I had no way to manage them, but now Duncan has created a > new page on the Mono Wiki where I will add the samples. > > Each sample contains the sourcecode, makefile and screenshots. > I will try to create these samples for each of the controls in SWF > > I will however make seperate projects for controls which use images, > because these don't seem to run on SWF yet. (For example a button with a > background image) > > You can find the wiki page here: > http://www.nullenvoid.com/mono/wiki/index.php/WineSamples > > I hope this helps > Timothy. > > > _______________________________________________ > Mono-winforms-list maillist - Mono-winforms-list(a)lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-winforms-list -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

1 0

Fw: Child's OninitDialog and Parent's OnKillFocus
by Omer Sahin (Link Bilgisayar) 28 Jul '03

28 Jul '03

In a CFormView , I create and display a CToolbarDialog. I use DoModal to display the dialog. A control (in Parent Windows) 's OnKillFocus event is called AFTER the child dialog's OninitDialog. This seems meaningfull to me, but in my Windows 2000 professional machine, child's OninitDialog is called BEFORE parent control's OnKillFocus. What should be done to correct this problem?

2 2

RE: Direct access to LPT1
by E Lea 28 Jul '03

28 Jul '03

> > The plotter doesn't need a specific driver - it doesn't even have one. In > > Windows it uses any old printer driver just to open the printer port, then > > sends commands to the plotter through the printer driver. > > > > Should it not be possible to do this with Wine? Possibly not with CUPS > > though... > Well that should work with cups too, you need to configure a printer > with model "RAW". It doen't - I get a an error saying "Call to StartDocPrinter failed"

1 0

Re: cab_F_00: codename: "whee"
by Dimitrie O. Paun 28 Jul '03

28 Jul '03

On July 27, 2003 04:46 pm, Gregory M. Turner wrote: > - WARN("FDIIsCabinet failed.\n"); > + ERR("FDIIsCabinet failed.\n"); Why these changes, they don't seem to make sense. The function handles the problem just fine, no need to spam the user with such messages, we already have too many IMO. -- Dimi.

2 2

Re: first go at some notepad changes
by Dimitrie O. Paun 28 Jul '03

28 Jul '03

On July 27, 2003 08:16 am, Jonathan Wilson wrote: > 25.modify WM_SIZE to correctly size the edit controll if the status bar > is visble and to tell the status bar to resize itself if needed Shouldn't the status bar do this automatically when CCS_BOTTOM is specified? If our status bar needs some work to have this style properly implemented, we better fix it there. -- Dimi.

1 0

Work for hire^H^H^H^Hgrade
by Shachar Shemesh 28 Jul '03

28 Jul '03

Hi all, A prof. in a locale university is doing a summer course about open source development. I gave them a short power point lecture (on Linux :-), and showed them IE running, and managed to hook one vulenteer to do his assignment in Wine. I have managed to interest him in some of open issues that are close to my heart (i.e. - BiDi related issues). However, this is far from final. I'm sure he would love to hear about other interesting areas, but some criteria must be kept. It must be a task that is moreorless self contained (he is supposed to be graded for it at the end), and it must be something known to be possible in a reasonable amount of hours (i.e - it can't be "implementing MSI"). Then again, it can't be something too trivial (i.e. - not "localize notepad"). Currently at hand are adding encoding selection to the font dlg (and making it ANSI call Unicode in the process), and adding BiDi to the edit control. If you feel you have something else that may be of interest to him, feel free to try and grab him away :-) Shachar P.S. No, I have not dropped of the face of the planet, and I still read this list. Just too busy to be doing anything useful (except hiring other working hands, which may count for something, I guess). I'll be back, though. -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

5 7

MACRO and other problems on porting to w32api headers
by Steven Edwards 28 Jul '03

28 Jul '03

Hello, I am trying to get some of the WINE dlls to build with the w32api package and am running in to problems with typedefs. When I try to build some of the dlls lets take mapi32 as a example I am getting a parse error because of this: typedef unsigned long FAR *LPLHANDLE, FAR *LPULONG; Also some of the functions and structures are declaired as STDCALL in MS_VC and w32api but in wine it is listed as CALLBACK and this causes problems. Is there any documentation anywhere on how I should deal with the macro FAR and CALLBACK type in the headers? Thanks Steven

1 0

[libmspack] A library for Microsoft compression formats
by Michael B Allen 27 Jul '03

27 Jul '03

I haven't tried this lib but it looks well organized and clean which is rare so check it out or fwd this link to interested parties... http://www.kyz.uklinux.net/libmspack/ Mike

2 1

Mouse not working in old DOS game ("MadTV")
by Christian Neumair 26 Jul '03

26 Jul '03

Today I tried to play a game, which is cult in Europe and nearly unknown in the USA: MadTV. When trying to start it, I encountered a problem: The mouse cursor of the game wasn't moved together with the wine mouse cursor and wine spit out a lot of int irq fixme messages: "fixme:int:DOSVM_Int33Handler Position mouse cursor" So I created a log with --debugmsg +int appended. Since the first ~300.000 lines contained a lot of repititions I decided to completely trash them. The attached backtrace contains a few thousands of lines output. Maybe sb, of you already experienced this problem, too - or even works on a solution. regs, Chris

1 1

Re: cards.dll, first patch
by Alexandre Julliard 26 Jul '03

26 Jul '03

Jonathan Wilson <jonwil(a)tpgi.com.au> writes: > No code or images have been taken from anything thats (c) microsoft > although studying cards.dll in IDA did help me to figure out how it > all works :) That's not a good idea at all. Your code is obviously a straight transcription of the disassembled code, with lots of magic numbers and meaningless variable names. That is not an acceptable way of implementing something for Wine. -- Alexandre Julliard julliard(a)winehq.com

1 0

Mouse not working in old DOS game ("MadTV")
by Christian Neumair 26 Jul '03

26 Jul '03

Today I tried to play a game, which is cult in Europe and nearly unknown in the USA: MadTV. When trying to start it, I encountered a problem: The mouse cursor of the game wasn't moved together with the wine mouse cursor and wine spit out a lot of int irq fixme messages: "fixme:int:DOSVM_Int33Handler Position mouse cursor" So I created a log with --debugmsg +int appended. Since the first ~300.000 lines contained a lot of repititions I decided to completely trash them. The attached backtrace contains a few thousands of lines output. Maybe sb, of you already experienced this problem, too - or even works on a solution. regs, Chris

1 0

notepad improvements?
by Jonathan Wilson 26 Jul '03

26 Jul '03

Are the notepad improvements from crossover office going to be merged into the main wine tree? What has to happen first?

2 2

How to compiling spec file and source file to generate a wine dll
by dd jj 25 Jul '03

25 Jul '03

Hello Finally I found the HOW-TO winelib which gives me a pretty useful example in it: 2. a Windows executable with WineLib DLL... .... During the compile process, a command like winebuild -fPIC -o winedll.spec.c -spec winedll.spec will be executed to create the file winedll.spec.c from information in the file winedll.spec. The file winedll.spec.c and winedll.c are compiled into object files and used to create the shared library. ...... My question is How to generate winedll.dll.so from winedll.spec.c and winedll.c and other source file like winedll.h if needed.. I am wondering whether someone can give me a detailed implementation command about this: It should something like "gcc -shared -Wl, -Bsymbolic -o ... or use winebuild directly.. Thanks --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

1 0

RE: Direct access to LPT1
by E Lea 25 Jul '03

25 Jul '03

> E> I'm playing around with a program that controls a small "design > E> cutter" - it's basically a plotter that connects via the parallel > E> port. > > E> There is some Windows CAD software that knows about the plotter and > E> sends commands to it, as far as I can tell in one of two ways: > > E> 1) Through a printer driver. It doesn't seem too bothered about the > E> details of the driver though. I'm assuming that one would normally > E> use a generic, text-only Windows driver. This method, apparently, has > E> the advantage of the driver buffering the output > > Wine can't run Ring 0 drivers, like something ending in .sys/ .vxd The plotter doesn't need a specific driver - it doesn't even have one. In Windows it uses any old printer driver just to open the printer port, then sends commands to the plotter through the printer driver. Should it not be possible to do this with Wine? Possibly not with CUPS though...

2 1

Re: having problems with my spec file for cards.dll
by Dmitry Timoshkov 25 Jul '03

25 Jul '03

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > > Only native Win32 compilers do that. gcc under Linux doesn't generate > > that crap. > aah, I was using MingW on windows to test the dll. You can use Wine build system in order to test your dll. For that you just need to make your new dll a part of the Wine dll tree (which you will need to do anyway). Wine makefiles already have all the needed tweaks to strip stdcall @xx suffixes when building under MinGW or Cygwin. > Looks like my .spec file should work when I solve this bitblt problem, > finish testing and move the code over to linux to add it to my WINE tree. ok. -- Dmitry.

3 3

RE: Direct access to LPT1
by E Lea 25 Jul '03

25 Jul '03

> > E> 2) The second method is a direct connection to LPT1. > E> With Wine, in the first case I get a message in a dialog box saying > E> the call to "StartDocPrinter" failed and > E> fixme:winspool:StartDocPrinterA (hPrinter=0x1, Level=0x1, > E> pDocInfo=0x408a28dc): stub > E> to stdout. > E> In the second case I get a dialog saying "LPT1 was not found" and > E> fixme:dosfs:DOSFS_OpenDevice device open L"LPT1" not supported (yet) > E> err:file:CreateFileW Couldn't open device L"LPT1"! > E> to stdout. > E> Is this a config issue? I'm assuming that is should be easier for me > E> to get the second method working. > > No. You hit an area of unimplemented functionality. > > However Win can translate direct port accesses, either as root to inp/outp > or when configured right, via /dev/parport I have ppdev, parport_pc and lp kernel modules installed. And [parallelports] "Lpt1" = "/dev/lp0" [ppdev] "378" = "/dev/parport0" [ports] "read" = "0x779,0x378,0x379,0x280-0x2a0" "write" = "0x779,0x378,0x379,0x280-0x2a0" in my ~/.wine/config Should this be enough to get it working? Or does the fact I get error messages about not being able to open LPT1 mean that the Windows program is behaving in such a way that the port access translation you describe will never work? > Perhaps look around if you don't > find some tool that talks to your device with direct hardware access. Win31 > programms might do so. I unfortunately don't have any choice in the tool I use - I'm tied to a specific app.

2 1

having problems with my spec file for cards.dll
by Jonathan Wilson 25 Jul '03

25 Jul '03

the MS Cards.dll is complled with "the dll does the cleanup" set to on (i.e. its using retn xx instructions). When I compile it, i get the @nn on the end of the names. This is a problem since cards.dll exports the names without the @nn How do I set things up in my .spec file?

2 1

Re: [patch] documentation patches
by Vincent Béron 25 Jul '03

25 Jul '03

Le mar 22/07/2003 à 12:43, Peter Hanecak a écrit : > Hello, > > while building Wine on "RedHat 8"-like system I encountered two typos in > Wine documentation which prevented me from "compiling" documentation with > jade (openjade-1.3.1-9). I'm interested in how exactly it prevented you to compile them, as I didn't have any problem to do so (although some other errors have caused the compilation to fail in the past). Special more strict switch? Docbook validator? Vincent

2 2

Focus Bug
by Dimitrie O. Paun 25 Jul '03

25 Jul '03

Summary: Clicking on the caption of a manage window does not move the focus as it should. This results in ugly artifacts. Steps to reproduce: 1. Fire up Notepad 2. Open the "Open" dialog (File | Open) 3. Expand the "Look in" dropdown (the one at the top, with the drives) 4. Click on the dialog caption, and drag it away Result: The dropdown does not close, and remains on the spot. Any way to know that the WM has now the focus, so we can release it? -- Dimi.

1 0

Still problmes about building winelib dll using winemaker and winedump
by dd jj 25 Jul '03

25 Jul '03

Hello everyone, Sorry to bother if there are lots of repeated comments with my original posts... So far, I failed to use winelib dll generated by wine tools: 1)winemaker: I copied all windows source codes (.h .c .dll .dsp files which are used to build natives dll under visual studio) into one directory, then execute: %winemaker --lower-uppercase -nomfc . %./configure --with-wine-includes=/usr/local/inlcude/wine/windows %make When I run wine ./ping.exe it shows the error then terminate: err:module:import_dll Loading module (file) pingdll.dll (which is needed by C:\ping\ping.exe) failed (error -1073741595) (Sorry, I forgot to mention this last time) 2)winedump: I generated a stub dll which fowarded all the requst to native dll, but I can't figure it out where I can put the exported function codes to the stub dll, cause I need reimplement windows dll to be a local shared library. Could anyone give me some comments on what I should solve these? I really got headache on this... Thanks a lot. -Lechun --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

1 0

Re: Status_Wine #2 -- lostwages
by Brian Vincent (C) 25 Jul '03

25 Jul '03

>> So, may I ask if either of you plan to volunteer to write a *official* >> History/Time line page ? > >Im no writer, really, so no, I don't plan on working on this. >Hopefully a better word craftsman will volunteer soon... Pencil me in on this. I already have the makings of it. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

2 1

Re: Make aclocal.m4:WINE_GET_SONAME more flexible
by Alexandre Julliard 24 Jul '03

24 Jul '03

Todd Vierling <tv(a)pobox.com> writes: > The following patch to aclocal.m4 (will require a run of "autoconf" after > changing to pick up the change) will make WINE_GET_SONAME work on NetBSD, > and likely the other *BSDs. It is still Linux compatible -- in fact, this > new incarnation returns the fully qualified path to the shared object, > eliminating fears of runtime linking path searches. I don't think that's a good idea. There is no guarantee that the full path is valid on other systems, and we don't want to bypass the user's LD_LIBRARY_PATH settings. -- Alexandre Julliard julliard(a)winehq.com

2 2

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