March 2006 - Wine-devel - list.winehq.org

Re: [RESEND] riched20: Fixed crash when the window procedure is called with NULL hWnd
by Alexandre Julliard 16 Mar '06

16 Mar '06

Phil Krylov <phil(a)newstar.rinet.ru> writes: > > ChangeLog: > > riched20: Fixed crash when the window procedure is called with NULL hWnd. You should check that you got a valid pointer from GetWindowLong, NULL is not the only invalid window handle you can get here. -- Alexandre Julliard julliard(a)winehq.org

1 0

My two cents about winetools and the suggestions I read in Issue 308
by Philip V. Neves 16 Mar '06

16 Mar '06

What I'm seeing here with the whole debate with wine and winetools is that its a configuration management issue. The project is getting into the stage where testing needs to be accomodated and so does getting things working. I think whats currently available for managing configurations to wine is innadequate. Even winecfg provides an interface that is innadequate for making many changes in terms of dll overrides. Plus it doesn't provide a mechanism for rolling those changes back. Or even managing multiple configurations or modes so that problems can be issolated. I think whats is comming out of the winetools debate is better tools are needed for configuration management. This isn't very revolutionary. Its a natural part of the software development life cycle. As a project starts emerging from the development phase ways to provide better configuration management start showing themselves. Something that interfaces with the AppDB would be good. It would make things easier. I think, given the complaints given by the developers are also valid but so are the complaints made by the people trying to use the program and even the testers. Most other projects don't need such tools but this one does given what its trying to accomplish and the complexity of whats being accomplished. Besides even windows XP has a roll back feature now to fix problems. Why doesn't wine considering its attempting a bug for bug compatibility with windows. This would be a wise thing to implement just for sanities sake. So I'd like to provide an addition to Jason Greens brain dump * AppDB would have to be extended to be able to get and report this data, and it would make sense for each App's maintainer to be able to manage that information. * Biggest issue here is that this information could have a tendency to change very rapidly, so it might overload the app maintainers if they had to track this for each version of wine. What I think would make sense is to have regular snapshots (every 3 months?) and release a new version of "Winetools Plus" or whatever you want to call this thing a month later to give the maintainers time to update each of their apps based on the frozen version. (I think multiple versions of the AppDB would be useful. Similar to the Release and Release candidate type way of doing things.) * Data needed: AppID, AppVersionID, WineVersionID, Window Version, DLL Overrides, Window settings (fullscreen/windowed - sometimes and issue), Sound options, Video acceleration required, General notes or HOWTO's, etc. You would need separate overrides/settings for Installing vs. Running the app. * AppDB could dump this information to an xml format which "Winetools Plus" could be distributed with. Maybe have an option to download the latest xml file directly from winehq.org. * The 'Winetools Plus' front-end would just be a menu which would query all of the apps in the xml dump. The user picks they app they want to install, and it reads the necessary information, verifies the source installation media, and goes at it. * Applying patches to apps might get tricky (e.g., where wine only successfully runs version 1.5 of the app, but 1.0 is on the CD), but I'm sure it could be worked out. * A Way to roll back DLL overrides. * A Way store roll multiple registry configurations so that we establish a base reference configuration and a test configuration. Or even multiple test configurations. * An AppDB tool that allows changes to the DLL configuration in the AppDB to be made easily. * A way to detect the version of wine and provide configuration changes given that version of wine. * A way to report bugs to the appDB maintainers about configuration problems. A nice to have would be Something that allows the AppDB maintainers to distribute tweeks to the configuration changes in the AppDB to users. So that even if we aren't installing the programs on the system. The tweeks can still be made on the fly. This would eliminate having to blow away the .wine directory all the time. Blowing away the .wine directory is not a desirable. A way for wine developers to distribute a test configuration would also be a useful thing. That way we can test the software with what the developers want us to test rather then shooting in the dark only to see that the bug we reported is the same as some other bug we reported. Such tools would be useful in debugging the entire framework and speed up development. These are suggestions. I hope they help a bit.

4 3

build stand alone binaries
by Benjamin Zeller 16 Mar '06

16 Mar '06

Hi there, is it possible to build real elf binaries with winelib? If i go through the tutorial on winehq.org i get only a appname.exe.so and i have to invoke wine to start the application. Is it possible to compile a binary wich can run stand alone? (Sorry for maybe posting this message twice i had some trouble with my email programm) regards benjamin z.

1 0

May be a bad idea to have Winetools in the next SUSE release
by Jan Zerebecki 16 Mar '06

16 Mar '06

Hi. For Andreas Jaeger: I CCed you, because you said on http://en.opensuse.org/Wishlist_Packages_that_are_already_there that Winetools got included for the next SUSE release. I hope you are the correct person to talk to or at least can forward this to someone who is. The following might be usefull information for you: I think a quote from http://www.winehq.org/site/download somewhat sums up the cencus on this list regarding Winetools: "WineTools [is] only recommended if installation or operability of Windows software failed on pure Wine. Since WineTools radically alters your Wine configuration please do not report bugs in programs with WineTools installed. Instead contact the author of WineTools Joachim von Thadden." Some other facts: Winetools is only sporadically updated for new versions of Wine (as http://www.von-thadden.de/Joachim/WineTools/ indicates; this site also contains some warnings regarding the support status). Winetools radically alters some vital Wine settings and thus makes many other apps fail. This leads to many users asking for help in #winehq on freenode. But nobody there wants to support winetools and thus can only suggest them to remove their .wine and redo it without winetools (which usually makes it work). Currently no Winetools developer works closely with the Wine developers to correct problems of interaction between Winetools and Wine. IMHO it would be best to either not include Winetools in a distribution or find a more active developer for it who is willing to support Winetools and cooperate with Wine developers. Or at least put up a big warning where it is read by a user that installs Winetools through the distributions package management. Jan

12 13

Yet Another MS Windows API Emulation - SanOS, an small OS
by agaro 15 Mar '06

15 Mar '06

I don't know if somebody already found this, but may be relevant to wine-devel comunity (google don't found nothing about in this list): http://www.jbox.dk/sanos/ And the code (I haven't really looked much there): http://www.jbox.dk/sanos/source/index.html The code is released under an "BSD style" license. The win32 exception handling implementation is based on Wine code: http://www.jbox.dk/sanos/contributions.htm []s Augusto Arcoverde da Rocha

1 0

re: More dogfood tests
by Dan Kegel 15 Mar '06

15 Mar '06

> I have found very few problems, mainly just images being color-reversed, > and only on PNG of certain types. That sounds like the .gif bug here: http://bugs.winehq.org/show_bug.cgi?id=4529 Can you give the URL of one of the busted PNG's? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

1 0

More dogfood tests
by Segin 15 Mar '06

15 Mar '06

I have also started using Firefox in Wine for everything, namely because native lost a lib, old mozilla and opera and native firefox cause X to malloc() like mad (pkill -9 the broswer to cause X to free() ). I have found very few problems, mainly just images being color-reversed, and only on PNG of certain types. Also, Wine is MUCH faster if you have NPTL as your only threading method in glibc. (think a 15x improvement in speed here...) Wine also seems to know about the XDND X extension, cause it knows what GTK+2 widgets can be dragged and dropped onto, but otherwise the actual drag-and-drop procedure is a null effect. Ahh to hell with it, let's get to the speed tests. time wine firefox.exe, cold cache: real 0m48.895s (about 45s, really) user 0m4.116s sys 0m1.589s hot cache: real 0m9.287s (about 7.5s, really) user 0m3.966s sys 0m1.026s (Please note that the "real" time is off by about 1-2 seconds, to allow for me to quit Firefox.) Here we do the 7-Zip File Manager. Errors: err:listview:LISTVIEW_WindowProc unknown msg 2005 wp=00000001 lp=00000000 err:rebar:REBAR_AdjustBands Phase 1 failed, x=1000, maxx=-4, start=1, end=1 time wine 7zFM.exe, cold cache: real 0m34.815s (about 30s) user 0m1.044s sys 0m0.672s and with a hot cache: real 0m5.105s (about 4s, actually) user 0m0.997s sys 0m0.378s And now we do PuTTY: (no errors) Cold cache: real 0m39.382s (37s) user 0m1.023s sys 0m0.868s Hot cache: real 0m3.170s (no ajustment) user 0m0.978s sys 0m0.395s On a normal Windows system, the cache is always hot (all the core DLLs are always loaded), so the hot cache times actually rival a real Windows system, especially the one for PuTTY (which beats every test on a real Windows box I have done except those on more powerful hardware)

1 0

Re: Francois Gouget : user32: Handle WM_ENDSESSION in DefWinProc().
by Rein Klazes 15 Mar '06

15 Mar '06

On Fri, 24 Feb 2006 14:29:45 -0600, you wrote: >Author: Francois Gouget <fgouget(a)codeweavers.com> >Date: Fri Feb 24 15:34:09 2006 +0100 > >user32: Handle WM_ENDSESSION in DefWinProc(). >DefWinProc() should call PostQuitMessage() on WM_ENDSESSION if the >shutdown is proceeding. Hi Francois, This patch is causing a problem in Pegasus Mail. Closing some dialogs cause termination of the complete program. Here is a part of SPY++ log when run under win2000, when I close the edit new mail dialog: |<00202> 00130A82 S ..........................WM_SYSCOMMAND uCmdType:SC_CLOSE xPos:672 yPos:121 [wParam:0000F060 lParam:007902A0] |<00203> 00130A82 S ...........................WM_CLOSE wParam:00000000 lParam:00000000 |<00204> 00130A82 S ............................WM_QUERYENDSESSION nSource:1 (End Task from Task List dialog) [wParam:00000001 lParam:00000000] |<00951> 00130A82 R ............................WM_QUERYENDSESSION fShutdownIsOk:True [lResult:00000001] ... |<00952> 00130A82 S ............................WM_ENDSESSION fEndSession:True [wParam:00000001 lParam:00000000] |<00953> 00130A82 R ............................WM_ENDSESSION lResult:00000000 The WM_QUERYENDSESSION and WM_ENDSESSION are sent by the program: |0009:Call user32.SendMessageA(00030024,00000011,00000001,00000000) ret=0040641d How did you check the behavior of the Windows DefWindowProc? If I put a DefWindowProc(hwnd, WM_ENDSESSION, 1, 0); some where in a windows program nothing happens, while a PostQuitMesage certainly closes the app. Rein.

3 4

Vista compatibility page
by Mike Hearn 15 Mar '06

15 Mar '06

Potentially this is old news, but via Raymond Chen we learn of this page: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnlong/htm… Which talks about Vistas application compatibility. Interesting points that stand out: * They are dropping WinHelp and CHM support. You'll have to install it from their website for it to work (my first thought: wtf?) * IsBadReadPtr/IsBadWritePtr are now "banned". I wonder what that means. Presumably it just means they don't use them internally for the APIs anymore. * Windows will now silently fail to modify certain protected system files even if you're the administrator (basically the STATUS_ACCESS_DENIED error is suppressed to stop installers tripping up). * They dropped D3D RM. Not many apps use this but I think at least my fathers sailing game does. So there we have it - this appears to be the first release in which they simply started dropping APIs.

4 4

ie6sp1 install failure
by Samium Gromoff 15 Mar '06

15 Mar '06

I tried to install IE6SP1 under wine 0.9.9, in order to allow .NET framework to be installed, and it failed like this: deepfire(a)betelheise:/mnt/etherstorm/win32$ wine ie6setup.exe fixme:advapi:CheckTokenMembership ((nil) 0x7fd3b6b0 0x7fbefd78) stub! fixme:advapi:DecryptFileA "C:\\windows\\temp\\IXP000.TMP\\" 00000000 wine: Unhandled page fault on read access to 0x0000000e at address 0x7e69c1ba (thread 000b), starting debugger... WineDbg starting on pid 0xa Unhandled exception: page fault on read access to 0x0000000e in 32-bit code (0x7e69c1ba). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:1007 GS:0033 EIP:7e69c1ba ESP:7fbdeff0 EBP:7fbdeff8 EFLAGS:00210212( - 00 - RIA1) EAX:00000002 EBX:7e6ad280 ECX:00000000 EDX:00000000 ESI:00000002 EDI:00000001 Stack dump: 0x7fbdeff0: 00000001 00000002 7fbdf01c 7e69d8bc 0x7fbdf000: 00000001 7fd43120 0000000b 7fbdf018 0x7fbdf010: 7e6dec3c 7fbdf788 7fd43120 7fbdf7cc 0x7fbdf020: 7e6daa8a 7fbdf788 00000001 7fbdf7ab 0x7fbdf030: 00000005 7fbdf7b0 7fbdf07c 00000000 0x7fbdf040: 7fbdf788 7fbdf7b8 7fbdf7b4 7fbdf7b0 0200: sel=1007 base=7fe4a000 limit=00001fff 32-bit rw- Backtrace: =>1 0x7e69c1ba in setupapi (+0x1c1ba) (0x7e69c1ba) 2 0x7e69d8bc SetupGetStringFieldA+0x2c in setupapi (0x7e69d8bc) 3 0x7e6daa8a in advpack (+0xaa8a) (0x7e6daa8a) 4 0x7e6db2df TranslateInfStringA+0xff in advpack (0x7e6db2df) fixme:dbghelp:sffip_cb NIY on 'ie6wzdex.pdb' 5 0x01016f73 in ie6wzd (+0x16f73) (0x01016f73) 6 0x010199e4 in ie6wzd (+0x199e4) (0x010199e4) 7 0x00000000 (0x00000000) 0x7e69c1ba: cmpl 0xc(%eax),%edx Modules: Module Address Debug info Name (74 modules) PE 0x01000000-01034000 Export ie6wzd ELF 0x7bf00000-7bf03000 Deferred <wine-loader> ELF 0x7e154000-7e15c000 Deferred librt.so.1 ELF 0x7e675000-7e6c8000 Export setupapi<elf> \-PE 0x7e680000-7e6c8000 \ setupapi ELF 0x7e6c8000-7e6e0000 Export advpack<elf> \-PE 0x7e6d0000-7e6e0000 \ advpack ELF 0x7e7f7000-7e83c000 Deferred riched20<elf> \-PE 0x7e810000-7e83c000 \ riched20 ELF 0x7e83c000-7e850000 Deferred riched32<elf> \-PE 0x7e840000-7e850000 \ riched32 ELF 0x7e934000-7e98c000 Deferred shlwapi<elf> \-PE 0x7e950000-7e98c000 \ shlwapi ELF 0x7e98c000-7ea51000 Deferred shell32<elf> \-PE 0x7e9a0000-7ea51000 \ shell32 ELF 0x7ea51000-7ea82000 Deferred uxtheme<elf> \-PE 0x7ea60000-7ea82000 \ uxtheme ELF 0x7eac6000-7eaca000 Deferred libxfixes.so.3 ELF 0x7eaca000-7ead3000 Deferred libxcursor.so.1 ELF 0x7ead3000-7eaef000 Deferred imm32<elf> \-PE 0x7eae0000-7eaef000 \ imm32 ELF 0x7eaef000-7eaf2000 Deferred libxrandr.so.2 ELF 0x7eaf2000-7eafa000 Deferred libxrender.so.1 ELF 0x7eafa000-7eb01000 Deferred libdrm.so.2 ELF 0x7eb01000-7eb67000 Deferred libgl.so.1 ELF 0x7eb67000-7ec4d000 Deferred libx11.so.6 ELF 0x7ec4d000-7ec65000 Deferred libice.so.6 ELF 0x7ec65000-7ece4000 Deferred winex11<elf> \-PE 0x7ec70000-7ece4000 \ winex11 ELF 0x7ece4000-7ed03000 Deferred libexpat.so.1 ELF 0x7ed03000-7ed31000 Deferred libfontconfig.so.1 ELF 0x7ed31000-7ed45000 Deferred libz.so.1 ELF 0x7ed45000-7edae000 Deferred libfreetype.so.6 ELF 0x7edae000-7edcc000 Deferred iphlpapi<elf> \-PE 0x7edc0000-7edcc000 \ iphlpapi ELF 0x7edcc000-7ee14000 Deferred rpcrt4<elf> \-PE 0x7ede0000-7ee14000 \ rpcrt4 ELF 0x7ee14000-7eea0000 Deferred ole32<elf> \-PE 0x7ee30000-7eea0000 \ ole32 ELF 0x7eea0000-7eeb9000 Deferred version<elf> \-PE 0x7eeb0000-7eeb9000 \ version ELF 0x7eeb9000-7ef6d000 Deferred comctl32<elf> \-PE 0x7eec0000-7ef6d000 \ comctl32 ELF 0x7ef6d000-7ef8b000 Deferred mpr<elf> \-PE 0x7ef70000-7ef8b000 \ mpr ELF 0x7ef8b000-7f0ad000 Deferred user32<elf> \-PE 0x7efb0000-7f0ad000 \ user32 ELF 0x7f0ad000-7f0b7000 Deferred libgcc_s.so.1 ELF 0x7f0b7000-7f0cb000 Deferred lz32<elf> \-PE 0x7f0c0000-7f0cb000 \ lz32 ELF 0x7f1a0000-7faa3000 Deferred gdi32<elf> \-PE 0x7f1e0000-7faa3000 \ gdi32 ELF 0x7faa3000-7fae0000 Deferred advapi32<elf> \-PE 0x7fab0000-7fae0000 \ advapi32 ELF 0x7fbe2000-7fce0000 Deferred kernel32<elf> \-PE 0x7fc00000-7fce0000 \ kernel32 ELF 0x7fce3000-7fcf0000 Deferred libxext.so.6 ELF 0x7fe02000-7fe05000 Deferred libxau.so.6 ELF 0x7fe05000-7fe0f000 Deferred libnss_files.so.2 ELF 0x7fe0f000-7fe18000 Deferred libnss_nis.so.2 ELF 0x7fe18000-7fe2d000 Deferred libnsl.so.1 ELF 0x7fe2d000-7fe36000 Deferred libnss_compat.so.2 ELF 0x7fe36000-7fe3b000 Deferred libxxf86vm.so.1 ELF 0x7fe3b000-7fe40000 Deferred libxxf86dga.so.1 ELF 0x7fe42000-7fe4a000 Deferred libsm.so.6 ELF 0x7fe4d000-7fe6f000 Deferred libm.so.6 ELF 0x7fe6f000-7ff66000 Deferred libwine_unicode.so.1 ELF 0x7ff66000-7ffe0000 Deferred ntdll<elf> \-PE 0x7ff80000-7ffe0000 \ ntdll ELF 0xb7df1000-b7df4000 Deferred libdl.so.2 ELF 0xb7df4000-b7f23000 Deferred libc.so.6 ELF 0xb7f23000-b7f35000 Deferred libpthread.so.0 ELF 0xb7f4a000-b7f64000 Deferred libwine.so.1 ELF 0xb7f67000-b7f7d000 Deferred ld-linux.so.2 Threads: process tid prio (all id:s are in hex) 0000000a (D) C:\windows\temp\IXP000.TMP\ie6wzd.exe 0000000b 0 <== 00000008 00000009 0

3 2