August 2004 - Wine-Devel - list.winehq.org

Re: Don

by Ivan Leo Puoti

>Maybe, yes. How long does it take? I didn't time it but it does take some time. >I think I killed it after about 5 >minutes of constant thrashing. Maybe you should just leave it and see how long it takes. >Possibly it's something to do with using the FC2 kernel instead of a >stock one ? I don't know much about the FC2 kernel, maybe you should try with the real thing www.kernel.org Ivan.

Aug. 26, 2004

Re: broken freecell

by Brian Vincent

On Thu, 26 Aug 2004 08:36:03 -0400, gslink <gslink(a)one.net> wrote: > Has anyone noticed that one of the patches in either the July or August > release broke the Microsoft Freecell. It used to be that when the full > screen button was pressed the Freecell window expanded to fill the > screen. Now the fill is only in the vertical. Dragging appears to work Nope.. Believe it or not, whatever patch did that "fixed" freecell. I just tested freecell under Win98 and XP and both of them have the same behavior - "maximize" only maximizes vertically. -Brian

Aug. 26, 2004

Re: Something broke winetest?

by Stefan Leichter

Am Mittwoch, 25. August 2004 14:12 schrieb Paul Millar: > Hi, > > Looks like something broke building cross-compiled tests last night. I now > get: > > [paulm(a)quisquiliae tests]$ make > i686-mingw32msvc-gcc dpa.o imagelist.o subclass.o tab.o testlist.o -o > comctl32_test.exe -lcomctl32 -luser32 -lgdi32 > imagelist.o(.text+0x1077): In function `DoTest3': > /home/paulm/Testing/wine-cross-source/dlls/comctl32/tests/imagelist.c:265: > undefined reference to `ImageList_DrawIndirect(a)4' > distcc[21076] ERROR: compile on localhost failed > make: *** [comctl32_test.exe] Error 1 > [paulm(a)quisquiliae tests]$ > > Which causes comctl32_test.exe not to be built, so the build of > winetest.exe fails. > > Do others get this too? > > Cheers, > > Paul. Hello, the attach patch makes it working for me again. The file replaces the file with same name in the mingw-3.3-8hl.src.rpm (http://mirzam.it.vu.nl/mingw/ packages/mingw-3.3-8hl.src.rpm). But i fear it will not help you. The name of the mingw binary indicates that you are not using the rpms provided by Hans Leidekker. Short howto: 1. install the source RPM 2. replace the file 3. in mingw.spec: change "Release:" (keep old binary) 4. rebuild the rpm from spec file 5. install it Bye Stefan

Aug. 26, 2004

Localizing shell32/shv_item_cmenu.c:ISvItemCm_fnQueryContextMenu

by Tobias Burnus

Hello, if I right click in the file open dialog, select a file and right click, I get a context menu with English menu items. Expected: I'll get a localized menu (e.g. in German). Any idea how to get a localized version? From dlls/shell32/shv_item_cmenu.c ------------------------------------ * ISvItemCm_fnQueryContextMenu() */ static HRESULT WINAPI ISvItemCm_fnQueryContextMenu( [...] _InsertMenuItem(hmenu, indexMenu++, TRUE, FCIDM_SHVIEW_OPEN, MFT_STRING, "&Open", MFS_ENABLED); _InsertMenuItem(hmenu, indexMenu++, TRUE, FCIDM_SHVIEW_EXPLORE, MFT_STRING, "&Explore", MFS_ENABLED|MFS_DEFAULT); } [...] ------------------------------------ Tobias PS: the _InsertMenuItem function, defined in the same file, uses InsertMenuItemA, one might want to change this to InsertMenuItemW.

Aug. 26, 2004

Re: Document dosdevices/unc/ (take 2)

by Tobias Burnus

Hello, seemingly I'm unable to grep 'cause I couldn't find the the "UNC" already present in that file (but not yet on the winehq.org) I therefore added UNC and Universal Naming Convention increasing the chance that one finds it using google/grep. Tobias

Aug. 26, 2004

notes under wine under qemu with the help of pth

by Rafael Ávila de Espíndola

I was trying to run lotus notes under wine under qemu. Unfortunately qemu appears to have some trouble with linuxthreads. For example, consider the following program test.c: #include <pthread.h> #include <stdio.h> void * f(void *oie) { printf("tata\n"); pthread_exit(oie); return NULL; } int main() { pthread_t t; int i; pthread_create(&t,NULL,f,&i); printf("blit\n"); pthread_join(t, NULL); return 0; } I can compile and run it natively: $ gcc -Wall -o test -lpthread test.c $ ./test tata blit but qemu (i386 -> i386) fails: $ qemu-i386 ./teste qemu: Unsupported syscall: 258 Segmentation fault My next attempt was to use pth (www.gnu.org/software/pth) export LD_LIBRARY_PATH=/home/rafael/inst/pth/lib gcc -Wall -o teste -I/home/rafael/inst/pth/include/ -L/home/rafael/inst/pth/lib/-lpthread test.c $ ./test blit tata $ qemu-i386 ./teste blit tata Success with the test program. Wine is able to run putty and notes6 when compiled with linuxthreads. To compile wine with pth I had to create empty pthreadtypes.h and sigthread.h files in the pth include dir and apply the attached patch in wine. When compiled with pth wine is able to run putty (even inside qemu!). Unfortunately it fails to run notes6: wine "c:\lotus\notes\nlnotes.exe" fixme:console:SetConsoleCtrlHandler ((nil),0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler (0x601aa540,1) - no error checking or testing yet fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoCreateInstance no classfactory created for CLSID {4955dd33-b159-11d0-8fcf-00aa006bcc59}, hres is 0x80040154 wine client error:d: version mismatch 0/147. Your wineserver binary was not upgraded correctly, or you have an older one somewhere in your PATH. Or maybe the wrong wineserver is still running? wine client error:d: read: Bad file descriptor wine client error:d: read: Bad file descriptor There was no wineserver running when I started the program and only one was in the path. The log of a successful execution when linked with linuxthreads is: fixme:console:SetConsoleCtrlHandler ((nil),0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler (0x601aa540,1) - no error checking or testing yet fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoCreateInstance no classfactory created for CLSID {4955dd33-b159-11d0-8fcf-00aa006bcc59}, hres is 0x80040154 fixme:hook:NotifyWinEvent (32782,0x10036,-4,2)-stub! fixme:console:SetConsoleCtrlHandler ((nil),0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler (0x601aa540,1) - no error checking or testing yet fixme:ole:CoRegisterMessageFilter stub fixme:console:SetConsoleCtrlHandler (0x601aa540,0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler ((nil),1) - no error checking or testing yet I have followed the instructions present in http://vowe.net/archives/004104.html to install notes. Thanks for any help Rafael

Aug. 26, 2004

Document dosdevices/unc/

by Tobias Burnus

Hello, I found an email by Fergal Daly (http://www.mail-archive.com/wine-devel(a)winehq.org/msg08815.html) which kind of patches configuring.sgml to document dosdevices/unc. I transformed it into a proper patch for configuring.sgml Tobias

Aug. 26, 2004

broken freecell

by gslink

Has anyone noticed that one of the patches in either the July or August release broke the Microsoft Freecell. It used to be that when the full screen button was pressed the Freecell window expanded to fill the screen. Now the fill is only in the vertical. Dragging appears to work but results in a ghost border when the full screen button in Freecell is pushed and the window snaps back to original size in the horizontal.

Aug. 26, 2004

Re: Patch for CreateDIBitmap: Don't create monochrome bitmaps (help wanted)

by Francois Gouget

On Thu, 26 Aug 2004, Michael Kaufmann wrote: [...] > > Test Program (DIB-Testcase.zip): > > --------------------------------- > > > > I've created a test program that shows the problem. It also shows a > > bug in Windows! It displays two bitmaps, both should be black and > > white. WINE displays them red on green (I've set these colors with > > SetTextColor/SetBkColor). [...] > Now I do. CreateDIBitmap() doesn't provoke this, it's LoadImage(). This > function creates a device-dependent bitmap. If it's possible, it creates > a monochrome bitmap. Windows looks at the color tables to check if the > two colors are really black and white. For the right bitmap, this is not > the case, and so Windows creates a color bitmap. > > WINE will do the same with my patch applied. Could you integrate the DIB-Testcase program with the conformance framework? It seems like it would be a valuable addition and a good complement to your patch. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The software said it requires Win95 or better, so I installed Linux.

Aug. 26, 2004

Re: runtime change to WINEDEBUG output

by Diego 'Flameeyes' Pettenò

Mike Hearn wrote: > FWIW I usually find +all traces give too much output for debugging > anything other than startup problems where you have no idea what's > wrong. Beyond a few seconds execution the logs get too big to work with, > especially if you're working blind. And also, as I reported on bug #2393, seems like RelayExclude doesn't work, so the allocate/free heap and the enter/leave critical section messages fills the output so much that it's impossible to use it for debug. Trying to tracing ClrMamePro I'm having a log of 3Gb right after the first window is loaded... -- Diego "Flameeyes" Pettenò dgp85(a)users.sourceforge.net - http://flameeyes.web.ctonet.it/

Aug. 26, 2004