- Wine-Devel - list.winehq.org

Try for Thai input
by Supphachoke Suntiwichaya Aug. 26, 2002

Aug. 26, 2002

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 Aug. 25, 2002

Aug. 25, 2002

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 Aug. 25, 2002

Aug. 25, 2002

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 Aug. 25, 2002

Aug. 25, 2002

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 Aug. 25, 2002

Aug. 25, 2002

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 Aug. 24, 2002

Aug. 24, 2002

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

Wine Win98 setup problems...
by Steve M Aug. 24, 2002

Aug. 24, 2002

Hi, I am having problems getting Wine to startup right. I would like to know, is there a way you can use Windows 98 Second Edition setup CD from within Wine, or does it have to be pre-installed? (e.g. I did it with wine --winver win98 setup.exe) and here are the errors it came up with: fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:reg:GetSystemInfo noy yet supported on this system wine: Unhandled exception, starting debugger... err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x2811563e I loaded the program using KDE 3.0, included in FreeBSD 4.6 Stable. Basically, this is the wine that came "out of the box"(as opposed to the tarball). I have checked other posts and I have corrected my .wine/config file for my cdrom, but it still comes up with the same error(This was based on the GetSystemInfo error msg). The only thing I changed was my config file and the error that complained about the SHAREDMEMLOCATION variable, which I copied from the source tarball(Wine-20020804.tar.gz). I tried to compile that source which is the same one on the CD, but to no avail. --------------------------- checking Wine base files --------------------------- 001. Checking for file "wine"... OK. 002. Checking for correct .so lib config (please wait)... Read on closed filehandle <LDCONF> at ./winecheck.pl line 225. Use of uninitialized value at ./winecheck.pl line 232. DEBUG: found libwine: OK. ----------------------------- checking config file ----------------------------- 003. Checking config file access... OK. >>> Checking drive A settings: 004. Checking Path option... OK. 005. Checking Type option... OK. 006. Checking device /dev/fd0... OK. 007. Checking Filesystem option... OK. --> OK. >>> Checking drive C settings: 008. Checking Path option... OK. 009. Checking Type option... OK. 010. Checking Filesystem option... OK. --> OK. >>> Checking drive D settings: 011. Checking Path option... OK. 012. Checking Type option... OK. 013. Checking device /dev/acd0c... OK. 014. Checking Filesystem option... OK. --> OK. >>> Checking drive E settings: 015. Checking Path option... OK. 016. Checking Type option... OK. 017. Checking Filesystem option... OK. --> OK. >>> Checking drive F settings: 018. Checking Path option... OK. 019. Checking Type option... OK. 020. Checking Filesystem option... OK. --> OK. --------------------- checking system devices used by Wine --------------------- 021. Checking sound device /dev/dsp... CRITICAL (no kernel driver for /dev/dsp?). - ADVICE: module loading problems ? Read /usr/src/linux/Documentation/modules.txt. 022. Checking audio mixer device /dev/mixer... OK. 023. Checking MIDI sequencer device /dev/sequencer... BAD (no kernel driver for /dev/sequencer?). - ADVICE: module loading problems ? Read /usr/src/linux/Documentation/modules.txt. ----------------------- checking registry configuration ------------------------ 024. Checking availability of winedefault.reg entries... OK. 025. Checking availability of windows registry entries... CRITICAL (entry "Default Taskbar" not found). - ADVICE: Windows registry does not seem to be added to Wine, as this typical Windows registry entry does not exist in Wine's registry. Thi lete original Windows registry entry set will *not* be available with a no-windows install, of course, so you'll have to live with that.. 25 tests. 0 suspicious, 1 bad, 2 critical, 0 failed. Wine configuration correctness score: 68.64% ... Any hints on how to correct these errors? Also, my /dev/dsp is symlinked to /dev/dsp0. I have a Sound Blaster Live, which comes up as follows: bash-2.05a# dmesg | grep pcm pcm0: <Creative EMU10K1> port 0xe000-0xe01f irq 11 at device 12.0 on pci0 ... Anything to make this thing work right, is worth a try! Thanks for your time! __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com

2 1

RFC: 'test' bugzilla keyword
by Francois Gouget Aug. 24, 2002

Aug. 24, 2002

Hi, I think that conformance test failures should generally be easier to analyze and fix than general application failures. Thus I think we may get a community of contributers interested in specifically tracking these issues to fix them, and that some in this community may not otherwise be interested in tackling the complex diagnosis of general application failures. In other words, if we make it easy to track conformance test issues in Bugzilla, we may get new contributers (sure I realize it's not a magic bullet either). Thus I propose to add a 'test' keyword to make it easy to find such issues in bugzilla for people specifically interested in conformance tests. This keyword would apply to reports concerning a conformance/regression test that: * fails to pass on Windows * fails to pass on Wine * fails to pass on specific architectures (e.g. FreeBSD, Solaris, etc.) Note that this would be different from the regression keyword which only applies to reports describing something that used to work and no longer works. Obviously, if a conformance test used to pass in Wine but no longer does, then both keywords would apply to the report. So for instance, if one finds that a conformance test passes on Win98 but not on NT4, then one would create a bug report with the keyword 'test' and OS 'Windows NT'. If a conformance test fails to pass on Solaris systems, then the report would have the 'test' keyword and the OS would be 'Solaris'. Comments / Objections / Better names for the keyword? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

1 0

broken input
by sauer＠studcs.uni-sb.de Aug. 23, 2002

Aug. 23, 2002

i succeded to run the game "Wizardry 8" with original wine. Now the input is broken, almost every event is handled twice (e.g. i hit a and 2 a's appear, clicking with mouse results in doubleclick) and it does not seem to be a problem with dlls/x11drv/[event.c|keyboard.c|mouse.c]. Also the windows/input.c sends all requests only once! to see this insert in windows/input.c line 113 (the queue_raw_hardwar...): if (message == 0x0100) printf("request KeyDown\n"); if (message == 0x0101) printf("request KeyUp\n"); here, 0x0100 is WM_KEYDOWN, 0x0101 is WM_KEYUP now, i've added to scheduler/client.c line 745 (the wine_server_call): if (req->u.req.send_message_request.msg == 0x0100) \\ printf("sending KeyDown\n"); if (req->u.req.send_message_request.msg == 0x0101) \\ printf("sending KeyUp\n"); In most cases this results in two send_requests per action (mouse also) and sometimes (nondeterministic) i've got only one WM_KEYDOWN => only one keypress (at the end of the mail is some output). I'm stuck now at this point and do not know how to debug furhtermore. It's obvious that wine_server_call gets called twice (once from windows/input.c and the second time from ?!?). Can someone help me and tell me how to continue. What do I have to do now to find the bug ? mIc P.S.: Yes, beeing addicted to computer games make's me debug wine!!!!! Output: request KeyDown sending KeyDown sending KeyDown request KeyUp sending KeyUp sending KeyUp request KeyDown sending KeyDown sending KeyDown request KeyUp sending KeyUp request KeyDown sending KeyDown sending KeyDown request KeyUp sending KeyUp sending KeyUp request KeyDown sending KeyDown request KeyUp sending KeyUp sending KeyUp request KeyDown sending KeyDown sending KeyDown request KeyUp sending KeyUp sending KeyUp

1 1

freereport initialization crash - cups problem?
by Grzegorz Prokopski Aug. 23, 2002

Aug. 23, 2002

Hi! I finally narowed down the problem with crashing freereport app while it is initializing freereport dll. I got a workaround, but real fix should be trivial for someone who knows a bit more about wineps driver. App was crashing int wineps/init.c:PSDRV_UpdateDevCaps at: physDev->horzSize = (physDev->horzRes * 25.4) / physDev->logPixelsX because physDev->logPixelsX == 0 In wineps/init.c:PSDRV_CreateDC I see: physDev->logPixelsX = physDev->pi->ppd->DefaultResolution; physDev->logPixelsY = physDev->pi->ppd->DefaultResolution; in turn ppd->DefaultResolution is filled in wineps/ppd.c:PSDRV_ParsePPD where it scans for "*DefaultResolution" or "*DefaultJCLResolution" in ppd file. For me it was /etc/cups/ppd/lp.ppd (HP DeskJet 694C, Foomatic + cdj550) Unfortunatelly there was NO "DefaultResolution" information in it. For now, because the app has more problems with running (now it hangs) I just added: "DefaultResolution: 20" to this file. But long term solution would be IMO to check in either ppd.c or CreateDC if adequatly ppd->DefaultResolution or physDev->LogPixels* are not 0. If they are... hm... no idea - maybe we can somehow calculate some values for that? Surely it shouldn't stay as it is now. Dividing by zero in wine's code is Bad Thing(tm). Anyone would propose "the right fix" for this? Regards Grzegorz B. Prokopski

2 2