wine-devel

wine-devel@winehq.org

2 participants
84479 discussions

RE: Close X after one hour and half
by Robert Yaklin 02 Jun '02

02 Jun '02

The problem may be a memory leak in Wine. Try running top while your Wine application is running and keep an eye on the amount of memory Wine is using. If you are using the latest Wine from CVS you may notice that you application runs longer, thanks to a bug-fix by Andreas Mohr. Robert You Wrote: > Hello friends > > a run my applicationwith wine and xinit like: > > xinit wine myapp.exe -- :0 > > running very well, but after one hour and half this broken my X > session and back to text console... > > i not see a messagem that refer to this problem in the screen and > logs are equal > > I dont understand what happen with X to make... > > anybody help me..? > > > Marcelo

1 0

Keyboard layout detection not working??
by Shachar Shemesh 02 Jun '02

02 Jun '02

Hi all, I am using Debian SID with KDE. In KDE, I defined two keyboard layouts (US and IL). I tried to add Israeli keyboard detection using the attached patch (layout.diff). When trying to test that patch, however, I perform the following task: I type in the command as suggested in the docs (wine --debugmsg +key,+keyboard >& key.log). Attached are two run attempts. key.log is with the US keyboard selected, key2.log is with the Hebrew keyboard selected. Comparing the two outputs, several things become evident: 1. The Israeli keyboard is not detected. It fails to match even the non-Hebrew characters (such as the '/' instead of lower case 'q'). It's as if WINE did not notice that a non-English keymap was installed. On the other hand, there are some differences between the two runs. What's going on? 2. The dvorak keyboard has 0 mismatches???? I noticed that the code has some different virtual mapping of the keyboard. I am not aware that dvorak keyboards generate a different scan code mapping. Am I missing something here? 3. There does not appear to be any code that detects layout changes in X11, and sends the apropriate WM_INPUTLANGCHANGE message. I understood that implementing an event trigered by X layout change is a difficult matter, but it is highly necessary for my BiDi support (many programs, including Office, know the current direction, and have visual representation when it changes. Not implementing this message may prove to be problematic in that respect). I currently don't have the capacity to go after this particular problem, but if it remains unsolved by the time it becomes crucial to me, I will. If anyone has any leads on solving this problem, please let me know. I have entered bug #735 on this issue. Many thanks for your input, Shachar Index: dlls/x11drv/keyboard.c =================================================================== RCS file: /home/wine/wine/dlls/x11drv/keyboard.c,v retrieving revision 1.1 diff -u -r1.1 keyboard.c --- dlls/x11drv/keyboard.c 30 Apr 2002 21:16:39 -0000 1.1 +++ dlls/x11drv/keyboard.c 28 May 2002 13:20:04 -0000 @@ -531,6 +531,15 @@ "zZ","xX","cC","vV","bB","nN","mM","öÖ","çÇ",".:" }; +/*** Israeli keyboard layout */ +static const char main_key_IL[MAIN_LEN][4] = +{ + "`~","1!","2@","3#","4$","5%","6^","7&","8*","9(","0)","-_","=+", + "/Q","'W","÷E","øR","àT","èY","åU","ïI","íO","ôP","[{","]}", + "ùA","ãS","âD","ëF","òG","éH","çJ","ìK","êL","ó:",",\"","\\|", + "æZ","ñX","áC","äV","ðB","îN","öM","ú<","õ>",".?" +}; + /*** VNC keyboard layout */ static const WORD main_key_scan_vnc[MAIN_LEN] = { @@ -600,6 +609,7 @@ {"Latin American keyboard layout", 28591, &main_key_LA, &main_key_scan_qwerty, &main_key_vkey_qwerty}, {"Lithuanian (Baltic) keyboard layout", 28603, &main_key_LT_B, &main_key_scan_qwerty, &main_key_vkey_qwerty}, {"Turkish keyboard layout", 28599, &main_key_TK, &main_key_scan_qwerty, &main_key_vkey_qwerty}, + {"Israeli keyboard layout", 28598, &main_key_IL, &main_key_scan_qwerty, &main_key_vkey_qwerty}, {"VNC keyboard layout", 28591, &main_key_vnc, &main_key_scan_vnc, &main_key_vkey_vnc}, {NULL, 0, NULL, NULL, NULL} /* sentinel */

4 14

PATCH: DragQueryFileW (shellole.c; shell32)
by Sander van Leeuwen 02 Jun '02

02 Jun '02

Hi, There appears to be a little bug in DragQueryFileW. According to MSDN pFiles is the offset in bytes. Did somebody make a mistake or was the LPWSTR cast added on purpose? Sander Changelog: - Fixed wrong cast; MSDN says lpDropFileStruct->pFiles is offset in bytes (regardless of ascii/unicode) Author: Sander van Leeuwen (sandervl(a)xs4all.nl) --- shellole.co Sun Mar 17 11:20:10 2002 +++ shellole.c Sun Jun 2 13:15:54 2002 @@ -627,7 +627,7 @@ if(!lpDropFileStruct) goto end; - lpwDrop = (LPWSTR) lpDropFileStruct + lpDropFileStruct->pFiles; + lpwDrop = (LPWSTR) ((LPSTR)lpDropFileStruct + lpDropFileStruct->pFiles); i = 0; while (i++ < lFile)

1 0

Shlwapi and user32 question
by Steven Edwards 02 Jun '02

02 Jun '02

Hola, The only thing keeping me from building shlwapi is that its import the non-win32 call wvsnprintfA and wvsnprintfW from user32 to implement wvnsprintfA and wvnsprintfW. I did a search of the wine source tree and nothing else seems to depend on these functions being exported from user32. Can they be moved somewhere else or removed? Thanks Steven "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson

2 1

Possible minor bug in bin2res
by Steven Edwards 02 Jun '02

02 Jun '02

Hola, I have been working on a small project that I am going to be submitting to the wine tree that used binary resources under windows and when I went to convert the files with bin2res I get this error "rename: File exists" It dumps the right wine resource information to the resouce-tmp file but when it goes to unlink the tmp file is when the error happens and the information must be manualy added to the rsrc.rc I traced it down, made sure that all other tmp file acces works in bin2res and and I think the problem is on line 245 if (rename(tmpfile, g_lpstrInputFile) == -1) { perror("rename"); unlink(tmpfile); return 0; } return 1; I have followed the directions on www.winehq.com for creation of a rsrc.rc to dump the resource information so I don't think I'm doing anything wrong. Can someone check this on windows to make sure I'm not just on the crack rock again? Thanks Steven "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson

2 1

User (developer ?) friendly execution trace
by max 01 Jun '02

01 Jun '02

I find tracing a wine problem with wine --debugmsg for large programs unpractical. Usually you can know about exactly when a program hangs or behaves badly, but there's no way to activate/deactivate tracing after program start (afaik...) Being also a windoze (sigh) programmer, I find very useful some utilities like winspy that presents a window log in which you can start/stop tracing or logging of wine messages, system calls and so on, and activate/deactivate filters on the fly. This would allow spotting the bug when it arises instead of having tenths or hundreds of mbyte of logs. I could implement it as a filter taking input from wine, but I guess it'll slow downn much apps, having to parse wine output on the fly. Much better would be an internal implementation.... Some comments about ? Regards Max

3 2

DOS memory Question..... or How to increase base memory for DOS apps
by Christian Costa 01 Jun '02

01 Jun '02

Hi, Many DOS apps needs a lot of base memory even if EMS or XMS memory are used. The first 64K of memory being lock to catch null pointer, the DOS memory must start at 0x10000 as you can see in the code below (msdos/dosmem.c) : /*********************************************************************** * DOSMEM_InfoBlock * * Gets the DOS memory info block. */ static dosmem_info *DOSMEM_InfoBlock(void) { return (dosmem_info*)(DOSMEM_dosmem+0x10000); /* 64K */ } /*********************************************************************** * DOSMEM_InitMemory * * Initialises the DOS memory structures. */ static void DOSMEM_InitMemory(void) { /* Low 64Kb are reserved for DOS/BIOS so the useable area starts at * 1000:0000 and ends at 9FFF:FFEF. */ Changing this value to the end of the BIOS DATA area (0x500) does the job and things work as expected (at least for DOS apps). But I was told that this causes problems for others apps. Probably for Win16 ones that use DOS3CALL and not int21h via DPMI. If it's true, a solution could be to initialize DOS memory differently for pure DOS apps by modifying the DOSMEM_Init function. DOSMEM_Init is called at 3 different places : - process_attach in dlls/kernel/kernel_main.c - DOSVM_Init in dlls/winedos/dosvm.c - MZ_InitMemory in dlls/winedos.dosvm.c and acts differently the first and second calls. Since I don't know wine internals enough and the "flow of execution", I have no idea how to do it in a clean way that do not break everything. If someone can help me or give me hints? A+ Christian

3 3

How to fix SizeOfImage when loading a builtin dll ?
by Laurent Pinchart 01 Jun '02

01 Jun '02

Hi everybody, I noticed that, when a builtin dll (.so) is loaded, the SizeOfImage field in the OptionalHeader is not updated and stays equal to page_size (see winebuild, spec32). I need to get the correct value in SizeOfImage. I thought about updating that field in map_dll(a)library/loader.c, but don't know how to get the size of the image. Could anyone help me ? I'm not familiar with the PE loader. Thanks in advance, Laurent Pinchart

5 12

translating docs
by Damian Wojslaw 31 May '02

31 May '02

Hello I just posted similiar thing on wine-users, but Anriy Palamarchuk said, that he intend to say something about it here. I thought I might as well give him a good opportunity and ask: what about translating docs? Those at WineHQ and within Wine tree? What I would like to know is, which of them would you like to see translated first (as for now, I am, unfortunately, the only person I know of, that intends to do this)? What about user interface? How do you want to distribute it - want to have it at your site, or ony host a link? And so on, and so forth, and whatever... :)))) -- Damian Wojslaw

1 0

Re: wine can't find regedit.exe.so when it is not on the path
by Alexandre Julliard 31 May '02

31 May '02

Andriy Palamarchuk <apa3a(a)yahoo.com> writes: > I can't start just installed regedit manually, > wine gets confused by symbolic links in the windows > directory: > regedit.exe -> /usr/local/bin/regedit > regedit.exe.so -> /usr/local/bin/regedit.so These symlinks should be removed too, they are no longer necessary. -- Alexandre Julliard julliard(a)winehq.com

2 4

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