wine-devel

wine-devel@winehq.org

4 participants
84472 discussions

How do I grab the screen contents referred to by an hDC?
by Bill Medland 26 Aug '02

26 Aug '02

Can anyone tell me how I can do this; I am trying to debug a problem with user32.dll under the native NT comctl32.? When drawing a ListView --debugmsg +relay shows three consecutive calls; SetRect (&rect...) FillRect (00000b04,&rect,00000082 (/* I reckon that is GetStockObject(BLACK_BRUSH)*/) DrawIcon (00000b04,0x40,0x60,hicon,...) Now as it stands I get random rubbish in the background of the icons (in the region covered by the mask). If I insert a hack into DrawIcon so that it does a FillRect (b04,the rectangle, GetStockObject (WHITE_BRUSH)) then things work out OK. (Also, the code seems to draw the icon to four hDCs and I can do the same hack on the second hDC to get the same effect but not the third and fourth). Firstly I don't understand how it has a chance of working given that it fills the rectangle with a black brush. So what I want is a way of seeing what the contents of the rectangular region is at the exit from the FillRect and the entrance to the DrawIconEx, based on the hDC. (Something like "give me the pixels of the 32x32 rectangle at this location of this hDC") Also it seems to me that these two function calls are consecutive, so if anything is changing I guess it would be as a result of code within comctl32 itself. Is there any other way that control can come back into the Wine code between a relay exit and entrance? Bill

1 0

Re: Add BiDi infrastructure
by Dimitrie O. Paun 26 Aug '02

26 Aug '02

On August 15, 2002 12:08 pm, Shachar Shemesh wrote: > configure.ac: > Added a check for the existance of the fribidi include file. No > check for the library, as we do not statically link with it. Like any programmer, I usually hate copying stuff around, but in this case isn't it better to simply have a copy of the fribidi heades around? I mean, we do the runtime load and checks anyway, why do we need to have the header around? If we don't use much out of the header, I would say simply include the prototype of the functions we're calling into the dlls/gdi/fribidi.c file directly, and be done with it. No configure, no macros, no ifdefs, no mess. -- Dimi.

4 12

RE: Problems compiling wine with Intel Compiler
by Patrik Stridvall 26 Aug '02

26 Aug '02

> On Mon, Aug 26, 2002 at 05:40:01PM +0200, Patrik Stridvall wrote: > > The Intel compiler like the Microsoft compiler probably > already supports > > __int{8,16,32,64}. > > > > This will have to be changed to > > > > #if !defined(_MSC_VER) && !defined(XXX) > > Or maybe a HAVE_xxx configure check? In general this is the way is should be done. However no rule without an exception. :-) Short explaination: In the header files it can't be done that way because the same header files must support multiple compilers and thus they can't have a shared config.h file.

1 0

RE: Problems compiling wine with Intel Compiler
by Patrik Stridvall 26 Aug '02

26 Aug '02

> I'm getting compiler errors when I try to compile wine with the Intel > C++ 6.0 Compiler. This works fine with the g++ compiler. > > $ icc -c tstwine.cpp -I/usr/include/wine > tstwine.cpp > /usr/include/wine/basetsd.h(27): error: invalid combination of type > specifiers > typedef char __int8; > ^ > > /usr/include/wine/basetsd.h(30): error: invalid combination of type > specifiers > typedef short __int16; > ^ > > /usr/include/wine/basetsd.h(33): error: invalid combination of type > specifiers > typedef int __int32; > ^ > > /usr/include/wine/basetsd.h(36): error: invalid combination of type > specifiers > typedef long long __int64; > ^ > > /usr/include/wine/basetsd.h(36): error: invalid combination of type > specifiers > typedef long long __int64; > ^ The Intel compiler like the Microsoft compiler probably already supports __int{8,16,32,64}. The typedef are protected by a #ifndef _MSC_VER This will have to be changed to #if !defined(_MSC_VER) && !defined(XXX) where XXX is some that indicate that the Intel compiler is used. Check the manual. > /usr/include/wine/winnt.h(59): catastrophic error: #error directive: > You need gcc >= 2.7 to build Wine on a 386 > # error You need gcc >= 2.7 to build Wine on a 386 > ^ > > compilation aborted for tstwine.cpp (code 4) > > It looks like the wine headers need a level of the gcc version for the > compiler, but since I'm not using gcc, there is no gcc version level > set. Presumably the Intel compiler like the Microsoft compiler already defined __cdecl and __stdcall. In that case similar to first problem above the line # elif defined(_MSC_VER) will have to be change to # elif defined(_MSC_VER) || defined(XXX) where XXX is the same as above. > Has anyone built wine with the Intel Compiler? If so, what was > done to get this to work? > > Is any work being done to allow the usage of the Intel > compiler with wine? Not that I know of.

2 1

Try for Thai input
by Supphachoke Suntiwichaya 26 Aug '02

26 Aug '02

hi,all I try modified keyboard.c for thai keymap static const char main_key_th[MAIN_LEN][4] = { "`~_%", "1!ๅ+", "2@/๑", "3#-๒", "4$ภ๓", "5%ถ๔", "6^ุู", "7&ึ฿", "8*ค๕", "9(ต๖", "0)จ๗", "-_ข๘", "=+ช๙", "\\|ฃฅ", "qQๆ๐", "wWไ\"", "eEำฎ", "rRพฑ", "tTะธ", "yYัํ", "uUี๊", "iIรณ", "oOนฯ", "pPยญ", "[{บฐ", "]}ล,", "aAฟฤ", "sSหฆ", "dDกฏ", "fFดโ", "gGเฌ", "hH้็", "jJ่๋", "kKาษ", "lLสศ", ";:วซ", "'\"ง.", "zZผ(", "xXป)", "cCแฉ", "vVอฮ", "bBิฺ", "nNื์", "mMท?", ",<มฒ", ".>ใฬ", "/?ฝฦ" }; but I still can't input Thai char.. err:keyboard:X11DRV_ToUnicode Please report: no char for keysym 0DB4 (Thai_dodek) : err:keyboard:X11DRV_ToUnicode (virtKey=47,scanCode=22,keycode=29,state=2010) err:keyboard:X11DRV_ToUnicode Please report: no char for keysym 0DCA (Thai_sosua) : err:keyboard:X11DRV_ToUnicode (virtKey=BA,scanCode=27,keycode=2E,state=2010) Help Me plz. mrchoke :::: Windows use cp874 for Thai :::: Linux use tis620 for Thai (Std) -- ========================================== Supphachoke Suntiwichaya WWW:http://jedi.links.nectec.or.th/~mrchoke UIN:10509387 TEL:+66-1-5408959 Love Me Love Linux.... ===========================================

1 0

IDA stopped working
by Shachar Shemesh 25 Aug '02

25 Aug '02

Hi all, somewhere back (havn't checked when, yet), some change in WINE made IDA (The Interactive Disassembler) stop working. I am talking about the bought version, have not checked the free one. Initial analysis (using IDA) suggest some heavy anti-disassembler techniques were used in this executable. One thing that is immediatly visible, however, is that the base address (as well as the address IDA is loading under windows) is different than the on in WINE. Wine: Execution starts at 0x006fb000 Windows, as well as static base address: Execution starts at 0x00599000 I believe this may be a hint, together with the fact it is employing some wierd arithmetics on the PC to stop static analysis using tools such as IDA ;-). Before I go through the tiring process of CVSing back and finding the patch that killed it, anyone happens to know who's using 00599000 and causing the conflict? Is there any simple way to check this? Shachar

2 2

extremely simple borland C builder app hangs
by Grzegorz Prokopski 25 Aug '02

25 Aug '02

Hi! This is still the same app, that used previously for testing freereport. How the app works. 0. show main window 1. call simple and meaningless freereport funtions (works now) 2. show [OK] dialog saying what above function returned 3. allow to press [OK] (of course ;-) 4. show main windows until it's closed. The app hangs after or around [2] it seems. Frames of main window and of the dialog show up, hovever their content is not painted and I cannot click/Enter/Esc/space anything. Final part of +relay log is this: 08072028:Ret x11drv.SetWindowPos() retval=00000001 ret=408c83ef 08072028:Ret x11drv.ShowWindow() retval=00000001 ret=408c7690 08072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=408deb6f 08072028:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=408deb6f 08072028:Call window proc 0x418a0fef (hwnd=00010021,msg=WM_USER+ac00,wp=00000000,lp=00000000) 08072028:Ret window proc 0x418a0fef (hwnd=00010021,msg=WM_USER+ac00,wp=00000000,lp=00000000) retval=00000000 08072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=408deb6f 08072028:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=408deb6f 08072028:Call window proc 0x418a0fef (hwnd=00010021,msg=WM_ENTERIDLE,wp=00000000,lp=0001002a) 08072028:Call user32.DefWindowProcA(00010021,00000121,00000000,0001002a) ret=40620e03 08072028:Ret user32.DefWindowProcA() retval=00000000 ret=40620e03 08072028:Ret window proc 0x418a0fef (hwnd=00010021,msg=WM_ENTERIDLE,wp=00000000,lp=0001002a) retval=00000000 08072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=408deb6f 08072028:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=408deb6f 08072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000001,403c53e8,ffffffff,00000000,00000000) ret=408dee6d So it seems that MsgWaitForMultipleObjectsEx doesn't return if it has anything to do (first parameter is number of objects to wait for). It is almost exactly the same, as the "big app", which hangs at this: 08072028:Ret window proc 0x422408ed (hwnd=0001004d,msg=WM_PAINT,wp=00000000,lp=00000000) retval=0000000008072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=408deb6f 08072028:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=408deb6f 08072028:Call window proc 0x42240fef (hwnd=00010021,msg=WM_ENTERIDLE,wp=00000000,lp=00010052) 08072028:Call user32.DefWindowProcA(00010021,00000121,00000000,00010052) ret=40620e03 08072028:Ret user32.DefWindowProcA() retval=00000000 ret=40620e03 08072028:Ret window proc 0x42240fef (hwnd=00010021,msg=WM_ENTERIDLE,wp=00000000,lp=00010052) retval=00000000 08072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=408deb6f 08072028:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=408deb6f 08072028:Call x11drv.MsgWaitForMultipleObjectsEx(00000001,403c7eb8,ffffffff,00000000,00000000) ret=408dee6d It seems, that dll/x11drv/event.c:X11DRV_MsgWaitForMultipleObjectsEx is being called which in turn is calling scheduler/synchro.c:WaitForMultipleObjectsEx (I think). I looked at the code, but ATM it's still black magic for me - too many unknown wine interlans ivolved :-/ Is this known problem? What should I look for while debugging? Any pointers/hints? (I don't mean general wine-developers docs pointers) Regards Grzegorz B. Prokopski PS: I compiled wine from CVS, but not today's version (as it had some problems with compilation) but 2 weeks old.

4 5

REQUEST: symlinks behaviour change
by Raul Dias 25 Aug '02

25 Aug '02

Hi, I would like to suggest a new way for wine deal with symlinks in some situations. The change in wine should be trivial, however I would like to know how do you feel about this. When building a fake windows tree, some files are symlinks to winelib apps in the DLLDIR . e.g. c:\windows\notepad.exe -> /usr/lib/wine/notepad.exe.so c:\windows\system\regsvr32.exe -> /usr/lib/wine/regsvr32.exe.so Some applications tries to replace this files. The way they do this is to open the file for writting. However, if the fake_windows tree is owned by a non-root user (and wine is ran by a non-root user), but the DLLDIR files are owned by root, the open will fail. This is because the user has no writting permition to the symlink destination file. This is a Good Thing, because if wine was run by root, the file in the DLLDIR would probably be replaced. However, some applications needs to replace this files. I noted this with the Internet Explorer Installer (5.01 sp1 and 6.0). If it cannot replace the c:\windows\system\regsrv32.exe file it will abort. However, as the c:\windows\system\regsrv32.exe is a symlink and wine has permition to move/delete this symlink, I would link to suggest that wine first delete the symlink file when an application tries to write on it. This has 2 benefits: 1 - wine will be able to replace files that are symlinks to files it does not have write permition. 2 - root run wine programs will not overwrite files in the DLLDIR if it tries to overwrite the symlinks that points to them. So, what do you think? []'s Raul Dias

2 2

Re: comctl32.dll compile on WinXP
by Steven Edwards 25 Aug '02

25 Aug '02

Hola Sorry about being so late in getting back to you but I've been busy. I'm going to adapt your test for mingw and commit it to the reactos tree so I can test our comctl32.dll. If you are going to do more work on porting the wine dlls to windows please use the diff -u format Thanks Steven --- Zolt�n_Nagy <nagyzoli(a)netelek.hu> wrote: > Dear Wine, > > I made two changes (wine 10.07.2002.) in your wine software > > First: > controls/edit.c > If you select a text area width mouse, then caret is not moved (like Windows). > The follow code solution the problem: > > end of EDIT_WM_MouseMove(): > EDIT_SetCaretPos(hwnd,es,es->selection_end,es->flags & EF_AFTER_WRAP); > return 0; > } > > > Second: > How can I build comctl32.dll (or other dll) with MS Visual C++ .NET (on WinXP)? > This is not problem (tested on WinXP): > > 1. please create a directory (examlpe test1) > 2. please create an INCLUDE directory (examlpe test1\INCLUDE) > 3. please copy the full wine include files here (test1\inlude\*.*) > 3. unzip the full.zip into test1 directory (this changes more include files) > 4. Open width MS Visual C++ .net the test1\dlls\testcomctl32\testcomctl32.sln file > 5. Compile project (F7). No panic, if you see very lot of warning (1679 pc.). (if not success > the compile, then maybe problem width include files) > > But I have a big problem, if I use the testcomctl32.dll from Windows aplication, then > RegisterClass function fail width 1410 error code (Class already exists), therefore I renamed > the name of classes (ex. msctls_progress32 -> wine_msctls_progress32). > > I made two examle, how to use the testcomctl32.dll? > In the BIN directory can be found the TESTCOM.EXE (this use the WINE comctl32.dll) and > TESTCOMWINDOWS.EXE (use the MS comctl32.dll). > > > > Best Regards, > > Zoltan Nagy > form Hungary > > nagy.zoltan(a)drotposta.hu > or > mazli(a)mazli.hu > or > nagyzoli(a)netelek.hu > > ATTACHMENT part 2 application/x-zip-compressed name=FULL.ZIP __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

1 0

Detecting wine
by Fabian Cenedese 24 Aug '02

24 Aug '02

Hi Is there a possibility that a running program can detect if it's running on a real Win OS or if it's on Linux/Wine? I want to use this to disable stuff in my program that maybe won't run (yet) on Wine. Is there a variable in environments? Thanks Fabi

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel