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

RE: Nameless struct problem
by Patrik Stridvall 18 Nov '02

18 Nov '02

> 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 18 Nov '02

18 Nov '02

-----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 17 Nov '02

17 Nov '02

> 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 17 Nov '02

17 Nov '02

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 17 Nov '02

17 Nov '02

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 17 Nov '02

17 Nov '02

"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 17 Nov '02

17 Nov '02

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

Visual-MingW
by Dimitrie O. Paun 17 Nov '02

17 Nov '02

Just a quick heads up. I've been working on compiling Visual-MingW as a Winelib app. Hence the header patches I've sent :) I got it to compile (including resources), but it does not link. Shouldn't be too hard to do, I'll post what changes I had to do later on. -- Dimi.

1 0

RE: Wine with .NET?
by Fredrick P. Lackey 16 Nov '02

16 Nov '02

By the way, I would PREFER to use Wine and NOT VMWare. I guess I should have mentioned that. Thanx, Fred > -----Original Message----- > From: Fredrick P. Lackey > [mailto:fred.lackey(a)marbellasoftware.com] > Sent: Saturday, November 16, 2002 1:43 PM > To: 'wine-devel(a)winehq.com' > Subject: Wine with .NET? > Importance: High > > 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

2 1

CoInitialize
by steve.lustbader＠philips.com 16 Nov '02

16 Nov '02

One of the threads in my app calls CoInitialize, expecting it to return S_OK (in fact, it's followed by an assert statement requiring that it returns S_OK). When I run it in Wine, however, CoInitialize returns S_FALSE, implying that this thread has already initialized the COM library. Other threads call CoInitialize, but this is the first time that this thread calls it. Does Wine initialize COM differently from Windows? Are the other threads' calls to CoInitialize screwing up this thread's call? -Steve

3 2