- Wine-Devel - list.winehq.org

Re: Symbol stripping?
by Shachar Shemesh Jan. 8, 2003

Jan. 8, 2003

Eric Pouech wrote: > aren't you, by any chance, compiling with gcc >= 3.1 ? > if so, you need to force emission of stabs as a debugging format while > running configure > something like this should work > CFLAGS=-gstabs+ ./configure Maybe we should patch configure.ac to detect this and add the apropriate compile switch? > > A+

5 5

Re: Possible bug (with fix) in MENU_FindItem()
by Duane Clark Jan. 8, 2003

Jan. 8, 2003

Peter Gerwinski wrote: > Hello, > > while developing an application for WINE (also intended to run under > MSPOW = MicroSoft's Parody Of WINE, spoken "m-spow";-) I encountered > something which I consider a bug in WINE: > > When I invoke EnableMenuItem to enable/disable a menu item holding > a command with the numeric value 200, the first popup menu is > enabled/disabled instead of the menu item. (This behaviour does not > show up under MSPOW, version "ME".) > > IMHO this is due to a wrong order of two "if" conditions in > control/menu.c:MENU_FindItem(). > > I am attaching a patch which fixed the problem for me. Hi. Please submit to wine-patches. It will be unlikely to get into wine if submitted here.

1 0

Stuck in SetMenuItemInfo
by Mike Hearn Jan. 8, 2003

Jan. 8, 2003

Hi, Debugging a crash in IE in the menus, I traced it to this check in SetMenuItemInfoA, apparently trying to stop apps passing in bad data. if ((lpmii->fType & (MF_HILITE|MF_POPUP)) || (lpmii->fState)) { /* QuickTime does pass invalid data into SetMenuItemInfo. * do some of the checks Windows does. */ WARN("Bad masks for type (0x%08x) or state (0x%08x)\n", lpmii->fType,lpmii->fState ); return FALSE; } In particular, it seems to check for a couple of bits set that aren't by IE, this is the function trace in Windows: SetMenuItemInfoW( 0x000B032B 0 TRUE [0x0013E070] -> 44 , MIIM_ID | MIIM_SUBMENU , MFT_BITMAP | MFT_RIGHTORDER , MFS_CHECKED , 3169 , NULL , 0x003C7FC8 , 0x40000064 , 0x003C806C , NULL , 2012758772 , 0x003B0000 ) -> TRUE So as you can see it sets MFT_BITMAP, MFT_RIGHTORDER and MFT_CHECKED, but not HILITE or POPUP. This is where I got stuck. I can't see what this check should actually be, but it's clearly incomplete at the moment, as Windows doesn't return false with this input. Has anybody got any advice? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

1 0

dsound test fails
by Zsolt Rizsanyi Jan. 8, 2003

Jan. 8, 2003

Hi! I tried doing make test, and got the next errors for the dsound test: make[2]: Entering directory `/home/zsolt/src/wine/dlls/dsound' make[3]: Entering directory `/home/zsolt/src/wine/dlls/dsound/tests' ../../../tools/runtest -q -P wine -M dsound.dll -T ../../.. -p dsound_test.exe.so dsound.c && touch dsound.ok fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x4025e290,00010020,2):stub fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x4025e290,00010020,1):stub fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x4025e290,00010020,2):stub fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x4025e290,00010020,1):stub err:ntdll:RtlpWaitForCriticalSection section 0x400d9d44 "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) tid=081b0f88 wine: Unhandled exception, starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x400d9d44 "../../loader/module.c: loader_section" wait timed out, retrying (60 sec) tid=081b0f88 err:seh:EXC_DefaultHandling Unhandled exception code c0000194 flags 0 addr 0x400ab624 make[3]: Leaving directory `/home/zsolt/src/wine/dlls/dsound/tests' make[2]: Leaving directory `/home/zsolt/src/wine/dlls/dsound' What does that mean? I got similar errors when trying to run some games. I have a Creative SB Live card. Using alsa 0.9.0rc1 with oss emulation (using wineoss and not winealsa - tough I have tried with winealsa and nothing changes). I know that the problem is with my system, but dont know where. Thanks Zsolt

1 0

Re: DirectSound and i810 soundcards
by Glen Kaukola Jan. 8, 2003

Jan. 8, 2003

Ok, here's output from dsound_test.exe, I heard all 6 sounds: C:\Documents and Settings\sauron\Desktop>dsound_test.exe dsound dsound.c:373:Testing Primary Sound Driver - dsound.c:387: DirectSound Caps: flags=0x00000b5b secondary min=8000 max=48000 dsound.c:398: Testing the primary buffer dsound.c:240: Caps: flags=0x00000009 size=32768 dsound.c:254: tag=0x0001 22050x8x2 avg.B/s=44100 align=2 dsound.c:270: status=0x0000 dsound.c:307: Playing 440Hz LA at 11025x16x2 dsound.c:413: Testing a secondary buffer at 11025x8x1 dsound.c:240: Caps: flags=0x000100e8 size=4410 dsound.c:254: tag=0x0001 11025x8x1 avg.B/s=11025 align=1 dsound.c:270: status=0x0000 dsound.c:307: Playing 440Hz LA at 11025x 8x1 dsound.c:322: volume=0 dsound.c:428: Testing a secondary buffer at 48000x16x2 dsound.c:240: Caps: flags=0x000100e8 size=76800 dsound.c:254: tag=0x0001 48000x16x2 avg.B/s=192000 align=4 dsound.c:270: status=0x0000 dsound.c:307: Playing 440Hz LA at 48000x16x2 dsound.c:322: volume=0 dsound.c:373:Testing AC'97 Sound Card - ichaud.sys dsound.c:387: DirectSound Caps: flags=0x00000b5b secondary min=8000 max=48000 dsound.c:398: Testing the primary buffer dsound.c:240: Caps: flags=0x00000009 size=32768 dsound.c:254: tag=0x0001 22050x8x2 avg.B/s=44100 align=2 dsound.c:270: status=0x0000 dsound.c:307: Playing 440Hz LA at 11025x16x2 dsound.c:413: Testing a secondary buffer at 11025x8x1 dsound.c:240: Caps: flags=0x000100e8 size=4410 dsound.c:254: tag=0x0001 11025x8x1 avg.B/s=11025 align=1 dsound.c:270: status=0x0000 dsound.c:307: Playing 440Hz LA at 11025x 8x1 dsound.c:322: volume=0 dsound.c:428: Testing a secondary buffer at 48000x16x2 dsound.c:240: Caps: flags=0x000100e8 size=76800 dsound.c:254: tag=0x0001 48000x16x2 avg.B/s=192000 align=4 dsound.c:270: status=0x0000 dsound.c:307: Playing 440Hz LA at 48000x16x2 dsound.c:322: volume=0 dsound: 307 tests executed, 0 marked as todo, 0 failures. Here's the output from winmm_text.exe, I heard all 24 sounds: C:\Documents and Settings\sauron\Desktop>winmm_test.exe wave wave.c:182:found 1 WaveOut devices wave.c:206: 0: "AC'97 Sound Card" 5.0 (1:100): channels=65535 formats=0fff support=002c wave.c:150:Playing 440Hz LA at 11025x 8x1 0000 wave.c:150:Playing 440Hz LA at 11025x 8x1 0008 wave.c:150:Playing 440Hz LA at 11025x 8x2 0000 wave.c:150:Playing 440Hz LA at 11025x 8x2 0008 wave.c:150:Playing 440Hz LA at 11025x16x1 0000 wave.c:150:Playing 440Hz LA at 11025x16x1 0008 wave.c:150:Playing 440Hz LA at 11025x16x2 0000 wave.c:150:Playing 440Hz LA at 11025x16x2 0008 wave.c:150:Playing 440Hz LA at 22050x 8x1 0000 wave.c:150:Playing 440Hz LA at 22050x 8x1 0008 wave.c:150:Playing 440Hz LA at 22050x 8x2 0000 wave.c:150:Playing 440Hz LA at 22050x 8x2 0008 wave.c:150:Playing 440Hz LA at 22050x16x1 0000 wave.c:150:Playing 440Hz LA at 22050x16x1 0008 wave.c:150:Playing 440Hz LA at 22050x16x2 0000 wave.c:150:Playing 440Hz LA at 22050x16x2 0008 wave.c:150:Playing 440Hz LA at 44100x 8x1 0000 wave.c:150:Playing 440Hz LA at 44100x 8x1 0008 wave.c:150:Playing 440Hz LA at 44100x 8x2 0000 wave.c:150:Playing 440Hz LA at 44100x 8x2 0008 wave.c:150:Playing 440Hz LA at 44100x16x1 0000 wave.c:150:Playing 440Hz LA at 44100x16x1 0008 wave.c:150:Playing 440Hz LA at 44100x16x2 0000 wave.c:150:Playing 440Hz LA at 44100x16x2 0008 wave.c:220:Testing invalid 2MHz format wave: 221 tests executed, 0 marked as todo, 0 failures. The sounds all seem to be the same exact note and just at different volumes on the first test. Heh, or I'm completely tone deaf. Francois Gouget wrote: > On Mon, 6 Jan 2003, Glen Kaukola wrote: > > >>Francois Gouget wrote: >> >>>I'm not really sure this is what Windows is doing however. I would be >>>interested if people with Windows NT/2000/XP and an i810 soundcard could >>>run both the dsound and the winmm tests and send me the output. >> >>Hi, I hope I've got the type of sound card you're after. I'm pretty >>sure the i810 module gets loaded when I run Linux. >> >>Anyway, here's the output I get on win2k from dsound_test.exe: > > > Thanks. I forgot to mention to do the following before running the > tests: > set WINETEST_INTERACTIVE=1 > > This will cause them to play test tones and do more tests. I would be > interested to know if you hear all the tones and if you could send me > the corresponding output of each test. >

2 2

Re: Symbol stripping=?iso-8859-1?Q?=3F ?=
by Mike Hearn Jan. 8, 2003

Jan. 8, 2003

I can look into doing this, but is there a reason we can't use -gstabs+ for all compilers? Will some compilers barf with this flag? I can see the benefits of doing it this way, but configure already takes ages :) On Wed, 2003-01-08 at 10:04, Eric POUECH wrote: > IMO the test should be: > - compile a little test program > - test if it contains stabs info (this adds a dependency on binutils, but since the test is meant to compile wine it shouldn't be too much an issue) > - if it doesn't, and if compiler is gcc then rerun the test with the -gstabs+ flag > - it the test passes add the flag to CFLAG, otherwise warn the user (at the end of configuration) as we do for opengl > however, this would be better in wine.ac (or equivalent) so that we can make use of it for other winelib programs for instance > > A+ > >Messsage du 08/01/2003 08:59 > >De : Mike Hearn <m.hearn(a)signal.qinetiq.com> > >A : Shachar Shemesh <wine-devel(a)sun.consumer.org.il> > >Copie à : Eric Pouech <eric.pouech(a)wanadoo.fr>, Mike Hearn <m.hearn(a)signal.dera.gov.uk>, <wine-devel(a)winehq.org> > >Objet : Re: Symbol stripping? > > > > What does gcc prior to 3.1 do with the -gstabs+ flag? If it ignores it, > > or it's implied anyway, we could just have it always on. > > > > If not then I have some bash here that can parse the output of gcc -v > > and determine whether it's >= 3.1, would that be acceptable as a patch > > to configure.ac? > > > > The only other way would be to compile a little test app then run > > objdump on it to figure out if stabs data was included, but testing the > > GCC version would be faster. > > > > On Tue, 2003-01-07 at 09:19, Shachar Shemesh wrote: > > > Eric Pouech wrote: > > > > > > > aren't you, by any chance, compiling with gcc >= 3.1 ? > > > > if so, you need to force emission of stabs as a debugging format while > > > > running configure > > > > something like this should work > > > > CFLAGS=-gstabs+ ./configure > > > > > > Maybe we should patch configure.ac to detect this and add the apropriate > > > compile switch? > > > > > > > > > > > A+ > > > > > > > > -- > > Mike Hearn <m.hearn(a)signal.qinetiq.com> > > QinetiQ - Malvern Technology Center > > > > > > > -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

1 0

Re: Re: bug report.
by yf Jan. 8, 2003

Jan. 8, 2003

>> [yf(a)yf 2002]$ wine ./hexin.exe >> fixme:ole:CoRegisterMessageFilter stub >> fixme:shdocvw:WBPCI2_GetGUID stub: dwGuidKind = 1, pGUID = {00000000-0000-0000-0000-000000000000} >> fixme:shdocvw:WBPCI2_GetGUID Wrongly returning IPropertyNotifySink interface {9bfbbc02-eff1-101a-84ed-00aa00341d07} >> fixme:shdocvw:WBQA_QuickActivate stub: QACONTAINER = 0x40760874, QACONTROL = 0x407608b4 >> fixme:shdocvw:WBPSI_InitNew stub >> fixme:shdocvw:WBCP_Advise stub: IUnknown = 0x4183bfe4, connection cookie = 0 >> fixme:shdocvw:WBOOBJ_SetExtent stub: (0x41f0a940, 1, (0 x 0)) >> fixme:shdocvw:WBOOBJ_DoVerb : stub iVerb = -5 >> fixme:shdocvw:WBOOBJ_DoVerb stub for OLEIVERB_INPLACEACTIVATE >> fixme:shdocvw:WBOC_GetControlInfo stub: LPCONTROLINFO = 0x4183bf84 >> fixme:shdocvw:WBOIPO_GetWindow stub HWND* = 0x40760980 >> fixme:shdocvw:WB_Invoke stub dispIdMember = -518, IID = {00000000-0000-0000-0000-000000000000} >> fixme:shdocvw:WBCP_Unadvise stub: cookie to disconnect = 1099153244 >> fixme:shdocvw:WBCP_Unadvise stub: cookie to disconnect = 1099153168 >> fixme:shdocvw:WBCP_Unadvise stub: cookie to disconnect = 1 >> fixme:shdocvw:WBOIPO_InPlaceDeactivate stub >> fixme:shdocvw:WBOOBJ_SetClientSite stub: (0x41f0a940, (nil)) >> fixme:shdocvw:WBOOBJ_Close stub: () >I get as far, than it fscks up its double byte names. >With what 'LANG' var do you run it? my 'LANG' is zh_CN.GB18030 >> err:clipping:CLIPPING_UpdateGCRegion hVisRgn is zero. Please report this. >This will do an immediate exit(1); so WINE terminates here. It probably should not.

1 0

getting started
by Glen Kaukola Jan. 8, 2003

Jan. 8, 2003

Hi everyone, I forget who's advice it was I took, but I went out and bought a few books on windows programming. And I plan to get started trying to help out with the wine project by trying to get the sample applications from the books to run under wine. If nothing else I guess I can let everyone know what it is I can't get working under wine (hopefully everyone welcomes that sort of input). So what I'm wondering now is what I should be using to compile my applications on windows. One of the books I have says all I need is the win32 sdk and I can compile apps. The closest thing I can find on msdn is the microsoft platform sdk, or perhaps the .net sdk. I've installed the microsoft platform sdk core but it doesn't seem to contain nmake.exe like the book I have talks about. So maybe I just need more pieces of the sdk? Or maybe I've installed the wrong thing entirely? I know of some other things I could use like borland's compiler or the bloodshed ide, that uses mingw I believe, but I was thinking it might be better if I stuck with microsoft development apps so everything happens the microsoft way in my programs. So maybe I just need to take one for the team and go out and buy visual studio? Thanks in advance, Glen

4 9

Re: wineboot : rename wininit.ini
by Shachar Shemesh Jan. 8, 2003

Jan. 8, 2003

Beat you to it, I'm afraid. I also made the parsing unnecessary by means of a simple CD. Thanks though. Shachar P.S. Try to tweak your mime settings so that, next time, attached .diff files are shown inline. Either that or just copy/paste into the message like everyone here except me seem to think is best. Sylvain Petreolle wrote: >Changelog : >Rename wininit.ini instead of deleting it. > >===== >Sylvain Petreolle >spetreolle(a)users.sourceforge.net >Fight against Spam ! http://www.euro.cauce.org/en/index.html >ICQ #170597259 > >"Don't think you are. Know you are." Morpheus in Matrix, chapter 15. > >___________________________________________________________ >Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! >Yahoo! Mail : http://fr.mail.yahoo.com >

1 0

Re: Window menu
by Dmitry Timoshkov Jan. 8, 2003

Jan. 8, 2003

"Duane Clark" <dclark(a)akamail.com> wrote: > Changelog: > A window with a WS_EX_APPWINDOW extended style can also > get a menu. [skipped] > /* Set the window menu */ > > - if ((wndPtr->dwStyle & (WS_CAPTION | WS_CHILD)) == WS_CAPTION ) > + if ((wndPtr->dwStyle & WS_CAPTION || wndPtr->dwExStyle & WS_EX_APPWINDOW) > + && !( wndPtr->dwStyle & WS_CHILD) ) Sorry for the late response, but this doesn't look right to me. First of all check for WS_CAPTION should be if ((dwStyle & WS_CAPTION) == WS_CAPTION) because WS_CAPTION is a two bit style. Next, apparently menu can be assigned only for a window that has a caption and not is a child. If for some reason in your case a window has no WS_CAPTION style set (even after all style corrections) then it's a bug in Wine and it should be found and fixed. I would suggest to write a conformance test for this, which will create windows with various styles, check whether they have a caption (by comparing client and window rectangles), then try to set a menu for a window. -- Dmitry.

2 2