- Wine-Devel - list.winehq.org

Re: [Fwd: WineTools is in need of some major house cleaning!]
by Juan Lang Jan. 25, 2006

Jan. 25, 2006

Hm. Felt I needed to offer a counterpoint to Vitaliy's rather enthusiastic response. I support winetools, though I don't use it myself. Not only as a matter of principle (this is open source we're talking about, and one of the beauties is we don't get to constrain how it's used.) Also because it's in line with the aims of the Wine project: run Windows apps. Wine is nice in that it doesn't require you to have any MS license to run Windows apps, but it can use MS software if you have a licensed copy. So winetools offers folks with MS licenses a relatively easy way to get apps to run. Still, while that's nice for the users, it's not so nice for us Wine developers, because it's hard to get widespread testing of things we're improving if they're not being widely used. So, as Vitaliy suggested, it would be nice for us if you guys, who know what problems you encounter running with builtin DLLs, could file bug reports in bugzilla for us. That way at least we have a chance to say, hey, that problem's now fixed, consider using builtin OLE (or whatever) in the next release of winetools. Now for specifics. For instance, you use native advpack in all cases, but that's seen some more work recently. What bugs do you encounter if you use builtin instead? Same with ole32. Ideally, each of the apps that has a native override should have a bug report associated with it, what goes wrong if you use the builtin version instead. Also, the default override, "*"="native,builtin" seems wrong. If we don't have a DLL at all, we use a native version of course. I don't think it should be the policy to assume the Wine version isn't up to snuff by default. This could even cause problems, e.g. I don't believe any native version of netapi32.dll will work on Wine, yet you don't specify to use the builtin version. Also, you direct users to http://winehq.org/site/forums. That's fine since this is community support anyway, and it is often the case that winetools knowledgeable people are around (like you guys.) But it would be nicer if you could be clearer about it. Like, that we developers had nothing to do with it, and may be unfriendly to it if we're in a bad mood, or it's a Tuesday :) It'd also be nice (for us, even though no one actually reads anything these days) if you could be clearer about what it does. That it installs MS components, that it uses these instead of the builtin versions sometimes, that you can change how it does this using winecfg, etc. That'd make it easier for us to help folks that have only used winetools that want support, because often the first question we ask is, what version of wine, and what DLLs are you using? --Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

Problem with WineD3D Surface Locking
by Stefan Dösinger Jan. 24, 2006

Jan. 24, 2006

Hello, I've spotted a bug in WineD3D's surface locking, and I have no clue how to fix this. The problem is that unlocking the back buffer causes it to become completely black, no matter what's written to it's memory or what has been there before. I have written a small D3D9 test app which shows this behavior: Compile it with "winemaker .", followed by make, and run it. Pressing ESC will cause it to quit, pressing any other keys makes IDirect3DDevice9::Clear call on the back buffer, with a color value based on the pressed keys. A click anywhere will LockRect() the whole backbuffer, write 0xff into the whole locked memory, and UnlockRect() it. The screen should become completely white, but instead it goes black. With the fglrx driver and 24 bit color depth it shows the correct behavior, but with any other driver(radeon, software rendering) or 16 bit color depth, it doesn't work. The bug is somehow related to some GL calls in UnlockRect(glPixelZoom and glOrtho), but I couldn't find anything specific. I hope you can help me, I am quite stuck here, Stefan

2 4

Winelib debugging with eclipse in fc4
by Michael Ost Jan. 24, 2006

Jan. 24, 2006

A while back I posted a question about how to get debugging working with eclipse in fedora 4. I am having some success, so if anyone else out there is interested here's how it is set up. In regedit: * disabled auto winedbg by renaming AeDebug I changed HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/AeDebug to AeDebug-DISABLED. Without this gdb doesn't seem to be able to get a hold of SEGFAULTs. In eclipse's Run/Debug dialog box: * set the c/c++ application to WINE_SRC/loader/wine-pthread WINE_SRC points to a compiled version of wine. For me, I got the wine src rpm and ran rpmbuild -bb. This is where main() is, which eclipse looks for at start up. * put your .exe.so file on the Arguments tab * choose the GDB Debugger on the Debugger tab * add WINE_SRC on the Source tab as a "Filesystem directory with subdirectories" The only weirdness so far is that sometimes (not always) the debugger suspends when a new thread is created. I just resume (F8) past that. And I am not sure what impact bypassing wine-preload's exec-shield workaround will have on me. More on that if I learn more. But I gotta say that having a functioning IDE with integrated debugging on Linux is a major relief and, for me at least, a long time coming! ... mo PS: I installed FC4, and then did yum update. eclipse is version 3.1.1 updated from the eclipse UI from the version that came with FC4.

2 5

Re: user: Don't drop owned windows in WIN_EnumChildWindows.
by Dmitry Timoshkov Jan. 24, 2006

Jan. 24, 2006

On Tue, 2006-01-24 at 12:56 -0700, Vitaliy Margolen wrote: > ChangeLog: > user: Don't drop owned windows in WIN_EnumChildWindows. > Add few tests to test this. It would be interesting to add IsChild calls in there and see what they return. We have at least one failing test in msg.c, test_DestroyWindow() which shows that our IsChild implementation is not entirely correct. -- Dmitry.

1 0

Re: LostWages: add a note to the WineTools link
by Dmitry Timoshkov Jan. 24, 2006

Jan. 24, 2006

On Tue, 2006-01-24 at 21:01 +0100, Sven Paschukat wrote: > as Vitaly noted it is not always clear that WineTools is not a > requirement for using Wine, so let the users decide if they want to test > or just want to use Wine. > "... or if you want to get best chances of success ..." I'd suggest to remove this wording, that's not (necessary) true. -- Dmitry.

1 0

[patch] riched20 conformance test
by tkho＠ucla.edu Jan. 24, 2006

Jan. 24, 2006

Greetings, I have started writing a conformance test for the rich edit control (riched20). The purpose is for students in UCLA's CS 130 Software Engineering course to first extend this conformance test to test conformance to unimplemented features, and then later implement their chosen features. You can find the patch here: http://www.seas.ucla.edu/~kho/wine/patches/riched20_test_20060119.patch Any comments would be much appreciated! For the curious, you can find background at http://www.kegel.com/wine/sweng/ and http://www.seas.ucla.edu/~kho/wine/ Best, Thomas Kho

3 2

RE: Windows manager
by Phil Lodwick Jan. 24, 2006

Jan. 24, 2006

Ok, I think I solved my own problem. In x11drv/window.c we see that "full-screen popup windows are managed". If I don't rotate the screen we are no longer a "full-screen" pop-up. My bad. Phil -----Original Message----- From: wine-devel-bounces(a)winehq.org [mailto:wine-devel-bounces(a)winehq.org] On Behalf Of Phil Lodwick Sent: Tuesday, January 24, 2006 11:47 AM To: wine-devel(a)winehq.org Subject: Windows manager I have an application that does not seem to appear to the Window Manager. I am using fvwm. To confirm I am running fbpanel which basically does a: XGetWindowProperty(GDK_DISPLAY(), GDK_ROOT_WINDOW, a_NET_CLIENT_LIST, 0, 0x7fffffff, 0, XA_WINDOW, ...); and the window never appears on its list. The strange thing is if I rotate the screen in my XF86Config-4 file, the window DOES appear on the list and I can use fbpanel to select the window, bring it to the front, etc. Anybody have an idea as to what difference rotating the screen would make? Thanks, Phil

1 0

Winhelp - Derive 6
by felix＠derklecks.de Jan. 24, 2006

Jan. 24, 2006

Hi, I have been trying to get the Winhelp to work for weeks now. But I just do not have any success. Derive is using winhelp with an extension RoboEx32 [1]. Derive reports "could not open help" and on the console I see following: # wine ~/.wine/drive_c/Programme/TI\ Education/Derive\ 6/Derive6.exe err:winhelp:HLPFILE_Uncompress3 buffer overflow (0x4169c3f9 > 0x4169c3f5) err:winhelp:HLPFILE_Uncompress3 buffer overflow (0x4169dbbc > 0x4169dbb8) err:winhelp:HLPFILE_Uncompress3 index in phrases 10807/5554 err:winhelp:HLPFILE_Uncompress3 buffer overflow (0x416dc2da > 0x416dc2d3) err:winhelp:HLPFILE_Uncompress3 index in phrases 10625/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10871/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10625/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10625/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10807/5554 err:winhelp:HLPFILE_Uncompress3 index in phrases 10655/5554 fixme:winhelp:HLPFILE_AddParagraph Got an embedded element RoboEx32.dll, WinHelp2000, fixme:winhelp:WHD_GetInfo NIY 8 fixme:winhelp:WHD_Open ("c:/windows/" 2) fixme:winhelp:WHD_LLInfoFromFile () fixme:winhelp:WHD_OpenBag (0xffffffff |SYSTEM 2) fixme:winhelp:WHD_API () fixme:winhelp:MACRO_Search () fixme:winhelp:WHD_Close (0xffffffff) Is winhelp supposed to be able to handle these help files? It is listed in the appdb as gold-supported. There are several other errors I see using derive, but I will have to do some more research. An easy bug is probably that the user just gets a black window after clicking on "about wine". Do you need any other information? Felix [1] - http://www.knopf.com/resources/help/winhelp2k.html

3 3

Regarding Implementation of Microsoft Speech SDK using wine
by Kalpit Shah Jan. 24, 2006

Jan. 24, 2006

Hi, I want to implement the Microsoft Speech SDK using wine on Fedora Core 3. How feasible is this.....can anyone give me an insight on how do i go about doing this..... please give me some orientation..... Waiting for a reply, Regards, Kalpit

3 2

Windows manager
by Phil Lodwick Jan. 24, 2006

Jan. 24, 2006

I have an application that does not seem to appear to the Window Manager. I am using fvwm. To confirm I am running fbpanel which basically does a: XGetWindowProperty(GDK_DISPLAY(), GDK_ROOT_WINDOW, a_NET_CLIENT_LIST, 0, 0x7fffffff, 0, XA_WINDOW, ...); and the window never appears on its list. The strange thing is if I rotate the screen in my XF86Config-4 file, the window DOES appear on the list and I can use fbpanel to select the window, bring it to the front, etc. Anybody have an idea as to what difference rotating the screen would make? Thanks, Phil

1 0