Rejected patches in dmloader and dmime
Hi, Whats is wrong with http://www.winehq.org/pipermail/wine-patches/2005-October/021445.html http://www.winehq.org/pipermail/wine-patches/2005-October/021446.html http://www.winehq.org/pipermail/wine-patches/2005-October/021447.html and http://www.winehq.org/pipermail/wine-patches/2005-October/021448.html They were first time send in September. Peter
Re: Fwd: wingcc link problem
В сообщении от 4 Ноябрь 2005 03:17 Vincent Béron написал(a): Le jeu 03/11/2005 à 18:46, Vitaly Lipatov a écrit : Really I just had not libwinecrt0.a installed in system. Now it compile without -lwinecrt0. Looks like our messages crossed :) :) At first I thought there was one because I could reproduce it in a build tree, but it was because I didn't give winegcc/winebuild the proper paths for finding libwinecrt0.a (-L.../dlls). Do you know why you didn't have libwinecrt0.a installed? Yes, I had not packed it in rpm package :) Thank you for help. Vincent -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru
relay debuggin crashes wine at startup
Hi, It seems that for some time, that whenever I enable relay debugging, wine crashes at startup e.i: /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relay /usr/local/bin/wine 0009:Call kernel32.__wine_kernel_init() ret=7bec1599 Segmentation fault /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relayfoo /usr/local/bin/wine Wine 0.9 Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --versionOutput version information and exit /mnt/windows/Programmer/Railroad Tycoon 3 Am I missing something? I haven't tried wine older than 2 months. Is it my system? /mnt/windows/Programmer/Railroad Tycoon 3 uname -a Linux 2.6.12-12mdk #1 Fri Sep 9 18:15:22 CEST 2005 i686 Intel(R) Pentium(R) M processor 1.86GHz unknown GNU/Linux /mnt/windows/Programmer/Railroad Tycoon 3 rpm -qa glibc glibc-2.3.5-5mdk /mnt/windows/Programmer/Railroad Tycoon 3 Peter
Re: relay debuggin crashes wine at startup
I was using it just last week, while testing Anarchy Online, so I think it might be specific to your machine. Does it happen when you try to debug programs other than RT3? -Jesse Peter Berg Larsen wrote: Hi, It seems that for some time, that whenever I enable relay debugging, wine crashes at startup e.i: /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relay /usr/local/bin/wine 0009:Call kernel32.__wine_kernel_init() ret=7bec1599 Segmentation fault /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relayfoo /usr/local/bin/wine Wine 0.9 Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --versionOutput version information and exit /mnt/windows/Programmer/Railroad Tycoon 3 Am I missing something? I haven't tried wine older than 2 months. Is it my system? /mnt/windows/Programmer/Railroad Tycoon 3 uname -a Linux 2.6.12-12mdk #1 Fri Sep 9 18:15:22 CEST 2005 i686 Intel(R) Pentium(R) M processor 1.86GHz unknown GNU/Linux /mnt/windows/Programmer/Railroad Tycoon 3 rpm -qa glibc glibc-2.3.5-5mdk /mnt/windows/Programmer/Railroad Tycoon 3 Peter
Re: relay debuggin crashes wine at startup
On Sat, 5 Nov 2005, Evil wrote: Does it happen when you try to debug programs other than RT3? Note, that I am not even giving wine a program argument, I just call wine. (RT3 has a stack overflow which was why I needed relay; I just expriemented in the RT3 path. This is not related to RT3) /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relay /usr/local/bin/wine 0009:Call kernel32.__wine_kernel_init() ret=7bec1599 Segmentation fault /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relayfoo /usr/local/bin/wine Wine 0.9 Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --versionOutput version information and exit /mnt/windows/Programmer/Railroad Tycoon 3
Re: relay debuggin crashes wine at startup
Ah, I didn't notice you were calling wine without a program, at first glance. It must be particular to your system; I just tried the exact same thing on mine and it appears to be working fine. Maybe someone else here can give you an idea as to why this might happen only when you have +relay debugging enabled. Can you give the specifics of your system/distro? -Jesse Peter Berg Larsen wrote: On Sat, 5 Nov 2005, Evil wrote: Does it happen when you try to debug programs other than RT3? Note, that I am not even giving wine a program argument, I just call wine. (RT3 has a stack overflow which was why I needed relay; I just expriemented in the RT3 path. This is not related to RT3) /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relay /usr/local/bin/wine 0009:Call kernel32.__wine_kernel_init() ret=7bec1599 Segmentation fault /mnt/windows/Programmer/Railroad Tycoon 3 env WINEDEBUG=+relayfoo /usr/local/bin/wine Wine 0.9 Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --versionOutput version information and exit /mnt/windows/Programmer/Railroad Tycoon 3
Problem with showing arabic script
Hello All, I compiled Wine-0.9 with ICU to support BiDi. And I used LC_CTYPE to choose the appropriate character map. The Arbic letters are shown in the right order (from right to left), but they are shown separated and not connected. Any Idea to fix this problem? Thank you in advance. Yaser..
Re: [dxdiagn] DirectXFiles + bug fixes
Todo: - find a way to provide wanted informations on containers (logical drivers, sound drivers, display drivers, ...) - fill DirectShowFilters (Christian have you an idea how to do that ?) Well, I don't know which filters should be enumerated here but you can use devenum (see EnumMatchingFilters of IFilterMapper2 interface). Christian
Re: killing wine dregs
On Tue, 01 Nov 2005 11:50:17 +0100, Francois Gouget [EMAIL PROTECTED] wrote: On Mon, 31 Oct 2005, [EMAIL PROTECTED] wrote: [...] I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier. pgrep wine|while read p; do kill -9 $p ; done; You should try out pkill to simplify it even further. [...] in fact it seems even cant clean up some times. Besides the zombie processes mentionned before, some processes may be stopped (e.g. by the debugger) and won't die until you send them a CONT signal. Thanks for all the replies, wineserver -k usually works but I still get some processes I cant kill: 15015 pts/5Tl 0:01 /usr/bin/wine-preloader /usr/bin/wine-pthread natspeak kill -9 15015 kill -9 15015 kill -9 15015 is not able to kill this. closing the xterm did in this case lay it to rest. Thanks again.
Re: killing wine dregs
On Tue, 01 Nov 2005 11:50:17 +0100, Francois Gouget [EMAIL PROTECTED] wrote: On Mon, 31 Oct 2005, [EMAIL PROTECTED] wrote: [...] I find killing it by hand labourious so I used the following command to clean up and have now defined it as an alias to make life easier. pgrep wine|while read p; do kill -9 $p ; done; You should try out pkill to simplify it even further. [...] in fact it seems even kill -9 cant clean up some times. Besides the zombie processes mentionned before, some processes may be stopped (e.g. by the debugger) and won't die until you send them a CONT signal. After an untidy exit I get stuck with the following. I took it right down and even logout out of the initial login console using cntl-D bash-3.00#killwine kill -9 16322 kill -9 16406 bash-3.00#wineserver -k Segmentation fault bash-3.00#pgrep -l wine 16322 wineserver 16406 wine-preloader It really seems like all I can do here is init 0 !!
Re: New eject command issue
On 11/1/05, Christian Costa [EMAIL PROTECTED] wrote: I tried to use the new eject command and this does not seem to work. Odd thing here as well. Fedora Core 4. This is wine CVS as of a few days ago, I don't think anything has changed in this area. If dosdevices contains a normal: lrwxrwxrwx 1 vinn vinn 18 Nov 5 15:37 d: - /media/cdrecorder/ Then wine eject doesn't work the first time I try it. The second time I run it, it works fine. Debugging output shows this the first time I try it: [EMAIL PROTECTED] dosdevices]$ WINEDEBUG=+eject wine eject trace:eject:eject_cd ejecting d: warn:eject:eject_cd IOCTL_STORAGE_MEDIA_REMOVAL failed with err 170 warn:eject:eject_cd IOCTL_STORAGE_EJECT_MEDIA failed with err 21 Then the second time: [EMAIL PROTECTED] dosdevices]$ WINEDEBUG=+eject wine eject trace:eject:eject_cd ejecting d: warn:eject:eject_cd IOCTL_STORAGE_MEDIA_REMOVAL failed with err 170 -Brian
Re: New eject command issue
On 11/5/05, Brian Vincent [EMAIL PROTECTED] wrote: Then wine eject doesn't work the first time I try it. The second time I run it, it works fine. Maybe I'm just unclear on the usage. It appears the first time it unmounts the drive and then the second time it actually ejects it. Is that intended behavior? -Brian
Re: versionunspecified
On Fri, 28 Oct 2005 20:15:06 +0200, Paul Vriens [EMAIL PROTECTED] wrote: On Fri, 2005-10-28 at 19:53 +0200, [EMAIL PROTECTED] wrote: I have an app that tests the version number of certain dlls it uses on startup. The first seems to be riched20.dll If I run it on 20050524 it starts and works. If I run from the same installation after installing wine-0.9 (or just about any winecfg based version) it starts throwing errors like: riched20.dll versionunspecified was found, this program requires at least. I then have to pull in a native dll and tell wine to go native when in fact the buildin functions work perfectly. bug or feature? I guess this was done intentionally or is a result of an intentional change and seems related to winecfg becoming active. What is the best way to deal with this? It seems a shame to install native dlls when the wine code does the job. TIA Hi, don't have time (yet) to do stuff in Wine, but have a look at http://www.winehq.org/pipermail/wine-patches/2005-September/020423.html this shows you how to add version stuff to a dll. cheers, Paul To bring this upto date: I have moved wine to 0.9 with this app and have got the native dll count required in winecfg down to 4. Two of these appear to be simply due to the lack of version_info in the built-in dll. riched20 : req = 5.30.22.2300 mscvrt : req = 6.1.8637.0 I have not worked out how to rebuild the dlls with version info hacked in under Gentoo, so I cannot state these will work but strongly suspect they will. Thanks again for your help.
Dragon v7 pref on wine 0.9
Hi,
I have managed to get this app working on 0.9 with just four dlls in
winecfg.
Two I believe to br trivial problems due to lack of version info in the
buildin dlls.
The two giving real, ugly issues are ole32 and rpcrt4. Symptoms are
similar.
I would like to attack ole32 first since the rest of the ole stuff works
and oleaut32 seems to have work very nicely now compared to 20050524,
great news there.
Things go well at first then I get the following output:
trace:loaddll:load_builtin_dll Loaded module
Lc:\\windows\\system\\oleacc.dll : builtin
fixme:oleacc:AccessibleObjectFromWindow 0x10070 0
{618736e0-3c3d-11cf-810c-00aa00389b71} 0x7876e504
trace:loaddll:load_native_dll Loaded module LC:\\Program
Files\\ScanSoft\\NaturallySpeaking\\Program\\chartp.dll : native
trace:loaddll:MODULE_FlushModrefs Unloaded module LC:\\Program
Files\\ScanSoft\\NaturallySpeaking\\Program\\DgnMyCmds_enu.dll : native
trace:loaddll:load_native_dll Loaded module LC:\\Program
Files\\ScanSoft\\NaturallySpeaking\\Program\\DgnMyCmds_enu.dll : native
err:ole:RPC_StartRemoting Couldn't register endpoint
L\\pipe\\OLE_0016002a
trace:loaddll:load_native_dll Loaded module
LC:\\windows\\speech\\vcmshl.dll : native
trace:loaddll:load_native_dll Loaded module
LC:\\windows\\system\\rpcltc1.dll : native
err:ole:ClientIdentity_QueryMultipleInterfaces
IRemUnknown_RemQueryInterface failed with error 0x800706ba
err:ole:ClientIdentity_QueryMultipleInterfaces
IRemUnknown_RemQueryInterface failed with error 0x800706ba
err:x11drv:X11DRV_CreateWindow invalid window height 571100824
err:x11drv:X11DRV_CreateWindow invalid window width -1592141001
err:ntdll:RtlpWaitForCriticalSection section 0x7befd264 loader.c:
loader_section wait timed out in thread 0019, blocked by 002d, retrying
(60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7befd264 loader.c:
loader_section wait timed out in thread 002b, blocked by 002d, retrying
(60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7befd264 loader.c:
loader_section wait timed out in thread 0028, blocked by 002d, retrying
(60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7befd264 loader.c:
loader_section wait timed out in thread 0027, blocked by 002d, retrying
(60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7befd264 loader.c:
loader_section wait timed out in thread 0024, blocked by 002d, retrying
(60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7befd264 loader.c:
loader_section wait timed out in thread 002c, blocked by 002d, retrying
(60 sec)
^X
[1]+ Stopped WINEDEBUG=+loaddll wine natspeak
The app. get part way through starting but the main window remains part
drawn and the app locks up. I need to ctnl-Z the CLI to break in.
This leaves two processes running. wineserver -k takes out the server but
leaves a zombie wine-preloader that I have to powerdown to kill!
Can anyone suggest how to pin this error down?
TIA .
Re: Dragon v7 pref on wine 0.9
[EMAIL PROTECTED] wrote: This leaves two processes running. wineserver -k takes out the server but leaves a zombie wine-preloader that I have to powerdown to kill! Can anyone suggest how to pin this error down? Yes, I already told you that it's a kernel bug. If you use the latest Linux kernel 2.6.14 (unpatched) it won't happen. It's been fixed for me since 2.6.7. Mike
Segmentation Fault in wine cvs after 0.9
before submitting this as bug, some advice please... on slackware 10.2 (gcc 3.3.6) i compile wine cvs, and it has worked so far. last version working is around or exactly 0.9. now, it compiles/installs fine, but any program, including starting just wine, notepad or anything else, ends up quickly with Segmentation fault. this is my simple custom buildscript... PKGDATE=`date +%Y%m%d` CHOST=i686-pc-linux-gnu \ CFLAGS=-march=athlon-xp -O2 -pipe -fomit-frame-pointer -m3dnow -msse -mmmx \ CXXFLAGS=$CFLAGS \ ./configure \ --disable-debug \ make make depend \ checkinstall -S --pkgname=wine --pkgarch=athlonxp --pkgversion=$PKGDATE -y also, tried removing ~/.wine and creating new one, it starts automatic configure but compiled wine also segfaults. then, changed processor optimizations to much more conservative -O2 -march=i486 -mcpu=i686 and it it works like a charm. athlon-xp optimizatins used in the first place are from http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are safe cflags, and it worked until couple days ago, then something is definetly wrong, right?
Re: Segmentation Fault in wine cvs after 0.9
zhilla [EMAIL PROTECTED] wrote: then, changed processor optimizations to much more conservative -O2 -march=i486 -mcpu=i686 and it it works like a charm. athlon-xp optimizatins used in the first place are from http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are safe cflags, and it worked until couple days ago, then something is definetly wrong, right? When somebody plays with compiler flags it's definitely wrong. If you are brave enough to use custom compiler switches you are must be qualified enough to cope with any problems caused by that. Feel free to debug it on your own. It's most likely that -fomit-frame-pointer is the culprit. -- Dmitry.
Re: Segmentation Fault in wine cvs after 0.9
zhilla wrote: http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are safe cflags, and it worked until couple days ago, then something is definetly wrong, right? This is the wrong type of question for wine-devel, and better asked in Gentoo forums or wine-users. Mike
WINE Regression due to patch 18110: Font size issues in MS Word dropdowns
This is a NON-FATAL, merely cosmetic regression. The application in question still functions. I have just finished regression testing WINE according to these instructions: http://www.winehq.com/site/docs/winedev-guide/x1344 In Microsoft Word 2000, in WINE prior to Monday, June 13, 2005, 05:01:32 CDT, when you moved your mouse over the dropdown boxes in the standard toolbar which allow you to select font size, font face, etc. the boxes become embossed like they're supposed to. However, after patch 18110 was applied, all that happens when you mouse over these boxes is that the text suddenly gains several sizes and cuts off at the first letter, makes the box either inconvenient or entirely unusable. The patch that caused this problem is the following: http://cvs.winehq.org/patch.py?id=18110 An image illustrating this process is below: http://img.photobucket.com/albums/v11/arrenlex/wineexamples.png Is it possible to fix this annoying regression? Thank you for your time! _ Designer Mail isn't just fun to send, it's fun to receive. Use special stationery, fonts and colors. http://join.msn.com/?pgmarket=en-capage=byoa/premxAPID=1994DI=1034SU=http://hotmail.com/encaHL=Market_MSNIS_Taglines Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.
