November 2002 - Wine-Devel - list.winehq.org

RE: Stub implementation of CABINET.DLL
by Jeff Smith Nov. 19, 2002

Nov. 19, 2002

>From: Patrik Stridvall <ps(a)leissner.se> >To: "'Greg Turner'" <gmturner007(a)ameritech.net>, wine-devel(a)winehq.com > > > On Friday 15 November 2002 12:47 pm, Patrik Stridvall wrote: > > > Now that we have the permission to use cabextract > > > under the LGPL it would be useful to have stubs > > > for CABINET.DLL so intrested people can work > > > with implementing it with fewer "infrastructure" > > > problems. >[snip] > > Anyone working on this? If not I'd be glad to take it on, > > seems like it > > should be easy. > >I personally doesn't currently have that much time to work with it. > >However, when I saw that not much happend despite >getting code from cabextrect under LGPL I thought >that perhaps people were having trouble on how >to create a new DLL in Wine and how to extract >the declarations from the Microsoft header without >creating a derived work. I have done it many >times before so thought why not do it... > >So I very happy that somebody is intrested in continuing. > >PS. If anybody have some other DLL that they wish to implement >but don't now how to do it, don't hesitate to ask me to >create a stub DLL with related headers. If it is not too much effort, could you elaborate on the derived work issue. I have been thinking about trying to stub out, then work at implementing, a particular component. Rather than have someone else do the work, I am more interested in learning about doing it myself, and about any issues (legal and technical) involved. I am not asking for a complete howto here, but even a summary of the highlights would be quite valuable (to me at least). -- Thanks -- Jeff S. _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

1 0

Configure question
by Martin Wilck Nov. 19, 2002

Nov. 19, 2002

I am thinking about some netapi32 improvements where I'd need to call the functions of the getpw/getgr family: getpwnam(), getpwent(), getgrent(), etc. Configure checks for the "pwd.h" header and getpwuid(). Must I add more checks for all the functions I use, or is it ok to assume that getpwuid() presence implies getpwnam() presence? Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 2

windres vs. wrc
by Dimitrie O. Paun Nov. 19, 2002

Nov. 19, 2002

Folks, I've just discovered (DUH!) another free resource compiler: http://www.redhat.com/docs/manuals/gnupro/GNUPro-Toolkit-98r2/5_ut/c_Usingb… This one is part of binutils. Now, like any good hacker, I hate such code duplication. Granted, I haven't looked through the code of windres, so I can't say if it's any good. However, here are some points to ponder: -- all Win32 free software projects out there use windres, not wrc -- for this reason, it is like it's more generic / better maintained -- do we want eventually to phase one of them out? -- their command line arguments are incompatible. This causes problems when trying to build portable Makefiles. Should we try to be command line compatible with windres, so we are a drop in replacement (for the .rc/.res -> .o conversion)? Any windres experiences? Comments? -- Dimi.

3 4

RE: WineHQ FTP (ftp://ftp.winehq.com/pub/wine/)
by Kye Lewis Nov. 19, 2002

Nov. 19, 2002

Hi, It just seems odd, as this FTP site worked fine with internet explorer before. - no errors at all. Thanks, Kye Lewis kyethespy(a)liquid2k.com -----Original Message----- From: wine-devel-admin(a)winehq.com [mailto:wine-devel-admin(a)winehq.com] On Behalf Of Keith Matthews Sent: Tuesday, November 19, 2002 8:32 PM To: wine devel < Subject: Re: WineHQ FTP (ftp://ftp.winehq.com/pub/wine/) On Tue, 19 Nov 2002 16:29:09 +1100 "Kye Lewis" <kyethespy(a)liquid2k.com> wrote: > Hi, > > While trying to connect to the wineHQ ftp site, I am getting the > following error with IE6: > > 200 Type set to A. > 500 Illegal PORT command. > 500 LPRT not understood > Don't know about the last error, but the illegal PORT is typically seen when trying to use active FTP from behind a firewall that does not support it. Command-line MS FTP clients don't support passive mode and I have heard reports that IE does not also. If that is the problem you'll have to switch to a Linux box or find a windows FTP client that supports passive.

1 0

RE: vxdcall calling convention
by Patrik Stridvall Nov. 18, 2002

Nov. 18, 2002

> Patrik Stridvall <ps(a)leissner.se> writes: > > > In any case I think Vincent and Marcus is right, it should be have a > > WINAPI like in Vincent patch because otherwise the "DWORD service" > > parameter is not popped from the stack AFAICS. > > No, it makes no difference whatsoever, the stack is restored from the > context structure in any case. Ah, OK. Wrong solution. But still, shouldn't the "DWORD service" parameter be popped somewhere? I can't see any place where it is. > The only use of WINAPI would be to make > winapi_check happy, but it would probably be better to teach it to not > do that check for register functions. VxDCall is the only register function that violates stdcall => WINAPI. But sure turning the check off in winapi_check is easy.

3 2

Wine (Debian) problems
by Anant Kabra Nov. 18, 2002

Nov. 18, 2002

Hi, I've been having the following problems with wine for the last couple of days. I'm using the daily cvs snapshot builds from http://people.debian.org/~andreas/debian Here's the output (this happens with every thing that I try with wine). Any suggestions? fixme:win32:PE_CreateModule Security directory ignored err:module:BUILTIN32_dlopen failed to load .so lib for builtin x11drv.dll: /usr/lib/wine/x11drv.dll.so: undefined symbol: X11DRV_OpenGL_Init Could not load graphics driver 'x11drv' err:module:BUILTIN32_dlopen failed to load .so lib for builtin x11drv.dll: /usr/lib/wine/x11drv.dll.so: undefined symbol: X11DRV_OpenGL_Init Could not load graphics driver 'x11drv' fixme:process:CreateProcessA (X:\IXP000.TMP\ie6wzd.exe,...): NORMAL_PRIORITY_CLASS ignored err:module:BUILTIN32_dlopen failed to load .so lib for builtin x11drv.dll: /usr/lib/wine/x11drv.dll.so: undefined symbol: X11DRV_OpenGL_Init Could not load graphics driver 'x11drv' err:heap:HEAP_GetPtr Invalid heap 00000000! Wine exited with a successful status -- Anant Kabra <anant(a)yash.com>

3 2

Patch for Bug 1145 - Compile ntdll with -DSTRICT
by Andrew John Hughes Nov. 18, 2002

Nov. 18, 2002

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Should fix all warnings - -- Andrew :-) Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE92WZWSE/kMce1ABARApuoAJ49FI04qMlgt5dJvaG6ShzRdPthKACeOLmQ UhjYFSZ6RYkpCxyEzPiAG3Q= =Vykj -----END PGP SIGNATURE-----

1 0

Possibly my last question... for a while. ;-)
by Fredrick P. Lackey Nov. 18, 2002

Nov. 18, 2002

Gentlemen, I feel really bad bothering a developers list with such basic questions, but. well. you all ARE the most responsive of everyone I've met so far. And, since you seem to hold the key to getting my @$$ of Micrsoshaft, then. well. I guess I'm sorry but I'm not. ;-) (By the way, if there is every anything I can do to repay you for your assistance and patience, consider it done.) As much as it pains me to ask, has anyone tried installing VMWare v3.x (either the Linux or Windows version) into Red Hat v8.0? If so, did you get it work? And, if so, then how? Again, my goal most definitely is to use Wine and Wine alone, however, I can't even consider moving forward unless I can use my environment for ALL of my current tasks (which includes development for M$, unfortunately). Thanx, either way. And, again, thank you for all of your help. R/S Fred www.fredlackey.com

2 1

RE: vxdcall calling convention
by Patrik Stridvall Nov. 18, 2002

Nov. 18, 2002

> Patrik Stridvall <ps(a)leissner.se> writes: > > > However, I don't think it is enough. It will work for the > > implemented VxDCall that pops the stack itself, however it will not > > work for unimplemented VxDCalls since they will not clean up the > > stack correctly AFAICS. > > The problem is you don't know how many args to pop. In theory the name > of the function tells you that, but in practice apps don't call the > right version, and VxDCall pops the number of args the specific call > requires no matter which version of the function is called. So this is > how we do it too. Ah. Microsoft. :-( In any case I think Vincent and Marcus is right, it should be have a WINAPI like in Vincent patch because otherwise the "DWORD service" parameter is not popped from the stack AFAICS.

2 1

wine commandline options
by Rick Romero Nov. 18, 2002

Nov. 18, 2002

I was playing with Pegasus Mail (silver list) to see what I could get working. It looks like it doesn't detect winsock.dll using it's own 'search algorythm, so the TCP/IP options don't get enabled - hence the (paraphrased) 'wtf?' in the silver list description. So, I tried to force Pegasus Mail to load winsock explicitly using the -Z 128 option: $wine winpm-32 -Z 128 but wine comes back with 'Unknown option -Z'. I'm not quite sure how these are getting parsed, but I see in misc/options.c parse_options() if (*p++ != '-') continue; /* not an option */ Should exit if the 2nd char isn't a - (am I right?) BUT, when parse_options returns to OPTIONS_ParseOptions() The following: /* check if any option remains */ for (i = 1; argv[i]; i++) { if (!strcmp( argv[i], "--" )) { remove_options( argv, i, 1, 0 ); break; } if (argv[i][0] == '-') { MESSAGE( "Unknown option '%s'\n\n", argv[i] ); // OPTIONS_Usage(); } } Still picks up '-' as an invalid option. My first thought would be to stop checking for options after the 1st and 2nd chars are not '-' (ie. after the Win32 program name), but I'm not sure if that's correct. Any thoughts? (FYI, no, the option didn't make Pmail work.) Rick -- -- Rick Romero IT Manager Valeo, Inc. ph: 262.695.4841 Sussex, WI. fax: 262.695.4850 Rick(a)valeoinc.com

5 6

Dual boot solves everything?
by Fredrick P. Lackey Nov. 18, 2002

Nov. 18, 2002

Gentlemen, First of all, thanks to everyone with your input so far. I've now been able to get IE v6.0 up and running as well as a few other less important applications. Which brings me to a few more questions. 1. Since it is possible to use native DLLs with applications, can one assume that on a dual boot machine with Win98 SE2 and Red Hat v8.0 that it would only be necessary to install the desired application under Windows, then add native DLLs to the Wine config file to get [almost] *any* Windows application to function? 2. Each time I launch a program, a black window appears that seems to make up the "shell" (for lack of a better term) for that instance of the application. This window is always somewhere around 800x600 pixels. Is there any way to not show this window and/or get the size to be something else? I am running in 1600x1200 resolution and only using half of the screen is frustrating. 3. Is there an easy way within Linux/Wine to determine what native DLLs the application should/could use? Thanx again, Fred Lackey Orlando, Florida

6 5

Progress report wine faq
by Tony Lambregts Nov. 18, 2002

Nov. 18, 2002

Vincent Berone has provided me with a dsl that works on my system and I am able to build the html so that it looks like it should. link to html built from sgml: http://www.telusplanet.net/public/lambregt/index.html link to original html: http://www.dssd.ca/wine/Wine-FAQ.html Please test this with your browser and let me know of any problems. We have already tested with Mozilla (1.0 and 1.0.1) and IE 5.5 -- Tony Lambregts

3 4

Fun Projects on Slashdot
by Dimitrie O. Paun Nov. 18, 2002

Nov. 18, 2002

Hehe, It's hard to keep these things 'secret' :))) http://developers.slashdot.org/developers/02/11/17/1648220.shtml?tid=125 -- Dimi.

3 3

wine-devel@winehq.com
by Mark Hannessen Nov. 18, 2002

Nov. 18, 2002

> I know I sound like a broken record, but just so it's out there: > Visual Foxpro 5 and 6 IDE's DO run under Wine, BUT, left mouse clicks in > child windows are broken. I've compiled and run VFP apps under wine, > but it's a pain in the butt to go kybd only in a Visual IDE :P are you volontairing ? > Sorry not to answer your main questions, but some ideas on this ... > We use gcc, wxWindows and mingw. Not sure how much you _need_ .NET > but we migrated our (fairly complex) app from Visual C++/MFC to wxWindows > and it was definitely worth it. Also we can use gcc to cross-compile > from Linux for Windows, so basically although our software is currently used > exclusively on Windows, I can develop it all on Linux (obviously some > testing to be done on Windows as well, but basically it works). And it's all > free, open-source software. I'd recommend checking it out. this combined with mono might give you just enough to develop .NET progs under linux. Mark Hannessen

2 1

RE: vxdcall calling convention
by Patrik Stridvall Nov. 18, 2002

Nov. 18, 2002

> On Mon, Nov 18, 2002 at 04:21:37PM +0100, Patrik Stridvall wrote: > > > Le lun 18/11/2002 à 02:51, Patrik Stridvall a écrit : > > > > > Corrects this line in winapi_check: > > > > > win32/device.c:544: kernel32: void > > > VxDCall(DWORD,CONTEXT86 *): calling > > > > > convention mismatch: cdecl != stdcall > > > > > > > > I'm not 100% sure this really is a bug. > > > > Don't trust winapi_check too much it is very ad hoc. :-) > > > > > > > > It might however be a bug but I never got around to test it > > > properly. > > > > > > > > So, have you verified that this really is correct? > > > > > > Well, kernel32.spec references them by "stdcall -register -i386". > > > Another API referenced the same way is CommonUnimpStub, and > > > in thunk.c, > > > it is declared as "void WINAPI". > > > > > > Is it sufficient checking? > > > > I'm not sure, it might be the other API(s) that are wrong > > or that VxDCall is a special case. That why I haven't dared > > changed anything. > > I think it needs to be WINAPI, the __wine_call_from_32_regs > assembler thunk > does not remove arguments from stack. Yes, I'm leaning in that direction as well the more I think about it. However, I don't think it is enough. It will work for the implemented VxDCall that pops the stack itself, however it will not work for unimplemented VxDCalls since they will not clean up the stack correctly AFAICS. Anyway, if so it has been wrong a long time (so long that I don't notice the warning from winapi_check any longer :-), so I wonder why it wasn't noticed by anybody else running an application using VxD calls.

2 1

RE: vxdcall calling convention
by Patrik Stridvall Nov. 18, 2002

Nov. 18, 2002

> Le lun 18/11/2002 à 02:51, Patrik Stridvall a écrit : > > > Corrects this line in winapi_check: > > > win32/device.c:544: kernel32: void > VxDCall(DWORD,CONTEXT86 *): calling > > > convention mismatch: cdecl != stdcall > > > > I'm not 100% sure this really is a bug. > > Don't trust winapi_check too much it is very ad hoc. :-) > > > > It might however be a bug but I never got around to test it > properly. > > > > So, have you verified that this really is correct? > > Well, kernel32.spec references them by "stdcall -register -i386". > Another API referenced the same way is CommonUnimpStub, and > in thunk.c, > it is declared as "void WINAPI". > > Is it sufficient checking? I'm not sure, it might be the other API(s) that are wrong or that VxDCall is a special case. That why I haven't dared changed anything. The problem with VxDCall is that is have multiple entries under different external names. ./dlls/kernel/kernel32.spec: 1 stdcall -register -i386 VxDCall0(long) VxDCall ./dlls/kernel/kernel32.spec: 2 stdcall -register -i386 VxDCall1(long) VxDCall ./dlls/kernel/kernel32.spec: 3 stdcall -register -i386 VxDCall2(long) VxDCall ./dlls/kernel/kernel32.spec: 4 stdcall -register -i386 VxDCall3(long) VxDCall ./dlls/kernel/kernel32.spec: 5 stdcall -register -i386 VxDCall4(long) VxDCall /dlls/kernel/kernel32.spec: 6 stdcall -register -i386 VxDCall5(long) VxDCall ./dlls/kernel/kernel32.spec: 7 stdcall -register -i386 VxDCall6(long) VxDCall ./dlls/kernel/kernel32.spec: 8 stdcall -register -i386 VxDCall7(long) VxDCall ./dlls/kernel/kernel32.spec: 9 stdcall -register -i386 VxDCall8(long) VxDCall Searching on the Internet reveals this page: http://www.mbs.spb.ru/kb/w32mbr.htm According to this page VxDCall[0-8] really should be stdcall. ---8<--- /* Kernel32 W32-caller prototypes */ DWORD WINAPI VxDCall0(DWORD service); DWORD WINAPI VxDCall1(DWORD service, DWORD); DWORD WINAPI VxDCall2(DWORD service, DWORD, DWORD); DWORD WINAPI VxDCall3(DWORD service, DWORD, DWORD, DWORD); DWORD WINAPI VxDCall4(DWORD service, DWORD, DWORD, DWORD, DWORD); DWORD WINAPI VxDCall5(DWORD service, DWORD, DWORD, DWORD, DWORD, DWORD); DWORD WINAPI VxDCall6(DWORD service, DWORD, DWORD, DWORD, DWORD, DWORD, DWORD); DWORD WINAPI VxDCall7(DWORD service, DWORD, DWORD, DWORD, DWORD, DWORD, DWORD, DWORD); DWORD WINAPI VxDCall8(DWORD service, DWORD, DWORD, DWORD, DWORD, DWORD, DWORD, DWORD, DWORD); ---8<--- and this ---8<--- vxdcall.def LIBRARY KERNEL32 EXPORTS VxDCall0(a)0 @1 VxDCall1(a)8 @2 VxDCall2(a)12 @3 VxDCall3(a)16 @4 VxDCall4(a)20 @5 VxDCall5(a)24 @6 VxDCall6(a)28 @7 VxDCall7(a)32 @8 VxDCall8(a)36 @9 ---8<--- However something with VxDCall is wrong nether the less. WINAPI functions (read: __stdcall) functions expects that the callee cleans up the argument stack and the number of arguments is different depending on which function is called. Looking at VxDCall (and what it calls) in win32/device.c I see that the implemented VxDCall pops the stack. However the unimplemented VxDCalls doesn't even though they might have gotten some arguments. This means AFAICS that VxDCall corrupts the stack in such cases... So I'm pretty convinced that something is wrong however I don't think you patch is the solution to the problem. It might possible be part of a solution though... Any suggestions?

2 1

RE: vxdcall calling convention
by Patrik Stridvall Nov. 18, 2002

Nov. 18, 2002

> Corrects this line in winapi_check: > win32/device.c:544: kernel32: void VxDCall(DWORD,CONTEXT86 *): calling > convention mismatch: cdecl != stdcall I'm not 100% sure this really is a bug. Don't trust winapi_check too much it is very ad hoc. :-) It might however be a bug but I never got around to test it properly. So, have you verified that this really is correct?

2 1

Re: Wine with .NET?
by Mark Hannessen Nov. 18, 2002

Nov. 18, 2002

> Ladies and Gentlemen, > > I am a Microsoft developer and currently pushing the capabilities of the > .NET Framework. On that same note, I am considering moving my laptop to > some version of Linux (either Solaris v8.0 or Red Hat). I assumed that > I would need to use VMWare or some equivalent to continue using Visual > Studio .NET. Can anyone give me some advice? > > Many thanx, > Fred Lackey > Orlando, Florida have you already tryd wine to run visual studio .NET ? in theory it is possible but i don't think anyone has ever tryd. ( and it will likely not work yet, feel free to send patches ) if you want to port visual studio .NET to linux using wine you should use winemaker. Mark Hannessen

7 8

RE: Nameless struct problem
by Patrik Stridvall Nov. 18, 2002

Nov. 18, 2002

> Dimitrie O. Paun wrote: > > >I had to use the following hack to allow this > >bit to go through my g++ compiler. > > > >I'm using RedHat 8.0, so this gives me: > > > >[dimi(a)dimi wine.src]$ g++ --version > >g++ (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7) > >Copyright (C) 2002 Free Software Foundation, Inc. > >This is free software; see the source for copying > conditions. There is NO > >warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > > > Glad you included the warranty bit :-) > > > > >Any ideas what's wrong here, and how it can be fixed? > > > > > Not particularly, but I know I've seen other examples of g++ > being more > strict / particular > about structs than gcc. What error do you get? You could try > -E for the > preprocessor > output and search through it for DUMMYSTRUCTNAME ; it could > be being defined > earlier on or somewhere else in a way that confuses it here... DUMMYSTRUCT is defined as nothing if the compiler supports nameless structs. GNU C++ was mistakenly believed by me to support nameless structs. I didn't check however, I have check now and it seem like no version of GNU C++ does. :-( Not that it really needs to support it since you could get the same effect with "dummy" structs/classes and inheritence, but then I really can't see any particular reason not to support it since makes at least as much sense (if not more) in C++ to have unnamed structs as in C... Anyway, there is a patch in wine-patches that fixes the problem and since it as I said is always possible to "fake it" in C++ there is no great need to ask the GNU C++ developers the fix the problem either...

1 0

Patch for bug 1150
by Andrew John Hughes Nov. 18, 2002

Nov. 18, 2002

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This patch should resolve bug 1150, compiling commdlg with -DSTRICT. Hope this is okay - this is my first time hacking on Wine. The patch is also attached to the bug. - -- Andrew :-) Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE92DtTSE/kMce1ABARAgXdAJ0RKUv3appMGjMo1+TgyhyujuMzGwCdHhNc dYlWgrnc+lCHhrdfM2cwYXY= =hum9 -----END PGP SIGNATURE-----

1 0

RE: Nameless struct problem
by Patrik Stridvall Nov. 17, 2002

Nov. 17, 2002

> I had to use the following hack to allow this > bit to go through my g++ compiler. > > I'm using RedHat 8.0, so this gives me: > > [dimi(a)dimi wine.src]$ g++ --version > g++ (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7) > Copyright (C) 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. > There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > > Any ideas what's wrong here, and how it can be fixed? Yes, it seems that GNU C++ 3.2 (unlike GNU C 3.2) doesn't support unnamed structs. Strange. Not that it really matters that much because you could do "magic" with inheritance in C++. See below. > Index: include/winuser.h > =================================================================== > RCS file: /var/cvs/wine/include/winuser.h,v > retrieving revision 1.152 > diff -u -r1.152 winuser.h > --- include/winuser.h 4 Nov 2002 22:47:59 -0000 1.152 > +++ include/winuser.h 17 Nov 2002 01:32:56 -0000 > @@ -2387,13 +2387,13 @@ > > typedef struct tagMONITORINFOEXA > { > - MONITORINFO DUMMYSTRUCTNAME; > + MONITORINFO DUMMYSTRUCTNAMEx; > CHAR szDevice[CCHDEVICENAME]; > } MONITORINFOEXA, *LPMONITORINFOEXA; > > typedef struct tagMONITORINFOEXW > { > - MONITORINFO DUMMYSTRUCTNAME; > + MONITORINFO DUMMYSTRUCTNAMEx; > WCHAR szDevice[CCHDEVICENAME]; > } MONITORINFOEXW, *LPMONITORINFOEXW; This uses inheritance with C++ in the Microsoft SDK. Working on patch. Coming very soon.

1 0

Nameless struct problem
by Dimitrie O. Paun Nov. 17, 2002

Nov. 17, 2002

I had to use the following hack to allow this bit to go through my g++ compiler. I'm using RedHat 8.0, so this gives me: [dimi(a)dimi wine.src]$ g++ --version g++ (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Any ideas what's wrong here, and how it can be fixed? Index: include/winuser.h =================================================================== RCS file: /var/cvs/wine/include/winuser.h,v retrieving revision 1.152 diff -u -r1.152 winuser.h --- include/winuser.h 4 Nov 2002 22:47:59 -0000 1.152 +++ include/winuser.h 17 Nov 2002 01:32:56 -0000 @@ -2387,13 +2387,13 @@ typedef struct tagMONITORINFOEXA { - MONITORINFO DUMMYSTRUCTNAME; + MONITORINFO DUMMYSTRUCTNAMEx; CHAR szDevice[CCHDEVICENAME]; } MONITORINFOEXA, *LPMONITORINFOEXA; typedef struct tagMONITORINFOEXW { - MONITORINFO DUMMYSTRUCTNAME; + MONITORINFO DUMMYSTRUCTNAMEx; WCHAR szDevice[CCHDEVICENAME]; } MONITORINFOEXW, *LPMONITORINFOEXW; -- Dimi.

2 1

Problem running Anstoss2 under Wine
by Adrian Bunk Nov. 17, 2002

Nov. 17, 2002

I'm trying to run Anstoss2 (a five years old German soccer simulation - I'm only interested in the strategic part of the game) under Wine. I tried the Debian package of the 20021031 Release and a self-compiled package of a 20021116 CVS snapshot. The following messages occur during the start of the game: <-- snip --> $ wine anstoss2.exe fixme:file:DEVICE_Open Unknown/unsupported VxD SICE. Try setting Windows version to 'nt40' or 'win31'. fixme:file:DEVICE_Open Unknown/unsupported VxD NTICE. Try setting Windows version to 'nt40' or 'win31'. err:ntdll:RtlpWaitForCriticalSection section 0x400f10bc "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) tid=081b1ce0 fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403a7528)->(00010024,00000008) fixme:ddraw:Main_DirectDrawClipper_Initialize (0x403a7e38)->(0x403a7534,0x00000000),stub! err:msg:DispatchMessageW BeginPaint not called on WM_PAINT for hwnd 10026! err:msg:DispatchMessageA BeginPaint not called on WM_PAINT for hwnd 10026! err:msg:DispatchMessageA BeginPaint not called on WM_PAINT for hwnd 10026! fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403a7428)->(0002002d,00000008) fixme:ddraw:Main_DirectDrawClipper_Initialize (0x403ae128)->(0x403a7434,0x00000000),stub! fixme:ddraw:DIB_DirectDrawSurface_Blt dwFlags DDBLT_WAIT and/or DDBLT_ASYNC: can't handle right now. <-- snip --> The "DEVICE_Open" messages might be related to the copy protection (?). At the beginning I see a small "Cannot open file" window [1] that seems to be non-fatal. The screenshot at [2] shows the main problem I observe: Something with the left-right justification of elements doesn't work. There are three checkbuttons and the one besides "Neues Spiel beginnen" is selected and that's the place where you can select it - but the background black circles that should indicate where you are able to click are 2cm left and a bit ahead of the correct location. The smiling ball at the right bottom is the place to click when you are finished with this page - but it's outside the rest, the thing that is painted in the two light blue colors (e.g. the "ADY" at the left bottom) is the background picture of my window manager. If there's any other information that might help simply ask. TIA Adrian [1] http://www.fs.tum.de/~bunk/TMP/cannot-open-file.png [2] http://www.fs.tum.de/~bunk/TMP/anstoss2-start.png -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed

1 0

Re: some ismbc* functions: third try
by Dmitry Timoshkov Nov. 17, 2002

Nov. 17, 2002

"Greg Turner" <gmturner007(a)ameritech.net> wrote: > totally untested, but it does compile, and seems logical > enough. while i was at it, i added a few more. Probably it would be better to create a common internal function which accepts C1_???? flags, does all remaining common operations with converting character(s) to unicode and returns (ctype & flags) != 0? -- Dmitry.

2 1

Re: FAQ in sgml format
by Dimitrie O. Paun Nov. 17, 2002

Nov. 17, 2002

On November 15, 2002 09:19 pm, Tony Lambregts wrote: > Here is the FAQ in sgml format with some very minor additions from the > html version by Dimitrie O. Paun, Keith Matthews and Thomas Wickline Can you please send me a copy of the file you used to generate the SGML, so I can track changes? TIA. -- Dimi.

2 1