wine-devel April 2004

wine-devel@winehq.org

138 participants
323 discussions

Re: ShellExecute IE compatibility problems
by Martin Fuchs 09 Apr '04

09 Apr '04

On 09.04.2004 02:03:37 Francois Gouget wrote: > > This patch fixes two IE compatibility problems. > > The first one is a mundane issue. IE calls ShellExecuteEx with a NULL > verb. Our implementation fails when it should use some sophisticated > algorithm described in the MSDN to choose a default verb. Well most of > the time we just want 'open' anyway so that's what this patch does. I've > left it as an exercise to the reader to head over to the MSDN and > implement the series of fallbacks we're supposed to implement. This is what SHELL_FindExecutable() tries to do when enumerating the registry keys. What is wrong with that - doesn't this work for you? I don't think we should go back and use "open" again if the verb parameter is NULL. Please correct the current algorithm, if it's not fully compliant. Regards, Martin

1 0

Re: Workaround a SoundBlaster 16 OSS bug
by Andreas Mohr 09 Apr '04

09 Apr '04

Hi, On Fri, Apr 09, 2004 at 02:27:19AM +0200, Francois Gouget wrote: > Note: AFAIK Andreas' kernel patch has never been applied :-( In fact it has been, fortunately, just about two weeks ago... By Andreas Kies in 2.4.26-pre3. He'd already patched 2.6.x a bit earlier. I've been trying to get the slightest bit of attention about that DoS at that time, but after two very detailed fruitless mails to LKML, I just gave up: http://www.uwsg.iu.edu/hypermail/linux/kernel/0206.0/0087.html http://www.uwsg.iu.edu/hypermail/linux/kernel/0206.2/0033.html Andreas Kies told me that it seemed that they now cared a slight wee bit more about small fringe problems such as DoSes in 2.4.x... </sarcasm> > (now you know how to mount a DOS on these systems!) Ow, watch your words! This can be VERY easily misinterpreted as mounting a DOS partition somewhere!? (in fact I did fall for it the first couple of seconds) > Patch the fragment size if it does not match the current sound > format. This saves us from trigerring a kernel freeze on some OSS 2.4 + > SounBlaster 16 systems. Crap, I thought I'd sent a Wine patch at that time; it would have been the easiest thing to do. Anyway, glad to see it fixed now. Greetings, Andi (been finishing my wireless driver any single day for about 5 months now :))

2 1

Re: Regression
by Ivan Leo Murray-Smith 08 Apr '04

08 Apr '04

> Tried to install on an updated (like 45 min old) CVS version to test it, > seems to get in an endless loop here. Alexandre committed a fix http://www.winehq.com/hypermail/wine-cvs/2004/04/0095.html Everything seems OK again, and hopefully will stay so. Ivan.

2 1

Re: Regression
by Ivan Leo Murray-Smith 08 Apr '04

08 Apr '04

> Tried to install on an updated (like 45 min old) CVS version to test it, > seems to get in an endless loop here. You're wright, it loops :( Ivan.

1 0

Re: Re: inheriting exec-shield avoidance
by chmorgan＠charter.net 08 Apr '04

08 Apr '04

Any idea when the kernel and wine changes will be going in? Then we can start asking people with Fedora to disable exec-shield and prelinking OR upgrade to kernel 2.6.X and the latest wine. There are people everyday that come onto #winehq with problems due to prelinking/exec-shield. Thanks, Chris > > From: "Dimitrie O. Paun" <dimi(a)intelliware.ca> > Date: 2004/04/08 Thu PM 03:10:35 EDT > To: Mike McCormack <mike(a)codeweavers.com> > CC: Peter Riocreux <par+wine_devel(a)silistix.com>, <wine-devel(a)winehq.org> > Subject: Re: inheriting exec-shield avoidance > > On Thu, 8 Apr 2004, Mike McCormack wrote: > > > I've attached the source code. The idea is to run it like this: > > > > wld /home/mike/wine/loader/wine-pthread my.exe > > Cool. One small nit: for consistency, can we name it wineld instead? > Or is it winepreld more apropriate? I'm thinking that wineld will > seem to be the counterpart of winegcc... > > -- > Dimi. > > > >

1 0

RE: Status of TAPI
by Robert van Herk 08 Apr '04

08 Apr '04

> This (dutch..) site provides some TAPI patches for Wine that are not > in CVS: > http://home.wanadoo.nl/wijn/girotel/ > > Since I'm dutch, I'd thought I'd explain a bit on what this site says. Wijn is dutch for wine by the way . The site explains how to patch wine in order to be able to use girotel software. Girotel is a telebanking system using dail up by modem that was quite popular a few years ago. Anyway, now-a-days most people use Internet for telebanking, not dail up modem. Although the site for that specific bank is not mozilla compatible , it can be used from Konqueror. The patches seems to be specially suited in order to use this Girotel system. Greetings, Robert

1 0

Status of TAPI
by Andreas Rosenberg 08 Apr '04

08 Apr '04

Hi guys! I'd like to run a TAPI based application in Wine (updated from CVS today). I extracted the vendor specific TAPI driver and the registry keys and included both into a Wine setup. Then I tried to do setup the TAPI driver using the telephon.cpl (taken from Win98): wine rundll32.exe shell32.dll,Control_RunDLL telephon.cpl first I had a problem with the Wine implementation of the TAPI32.DLL. err:module:import_dll No implementation for TAPI32.dll.internalConfig imported from L"C:\\windows\\system\\telephon.cpl", setting to 0xdeadbeef ... No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\TELEPHON.CPL' (0x75a70000) Unhandled exception: page fault on read access to 0xdeadbeef in 32-bit code (0x404c5b7e). who had dug in that DEAD BEEF? ;-) Then I took the TAPI32.DLL from a Win98 installation. This gave me another error: fixme:ole:RpcServerRegisterAuthInfoA ((null),10,(nil),(nil)): stub fixme:seh:EXC_RtlRaiseException call to unimplemented function rpcrt4.dll.NdrClientCall (last message repeated several times). At last I took the rpcrt4.dll from a Windows98 installation and tried it again. Then it took quite a time (~15 sec) until the Wine debugger came up. wine rundll32.exe shell32.dll,Control_RunDLL telephon.cpl wine: Unhandled exception (thread 0009), starting debugger... WineDbg starting on pid 8 Can't find file for ELF 'wine-kthread' ((nil)) Loaded debug information from ELF 'wine-pthread' ((nil)) Breakpoint 1 at 0x4000dd60 (_end+0x3fefb8d0) Loaded debug information from ELF '/usr/local/lib/libwine.so.1' (0x40028000) No debug information in ELF '/lib/i686/libpthread.so.0' (0x40040000) No debug information in ELF '/lib/i686/libc.so.6' (0x40091000) No debug information in ELF '/lib/libdl.so.2' (0x401c4000) No debug information in ELF '/lib/ld-linux.so.2' (0x40000000) Loaded debug information from ELF '/usr/local/lib/wine/ntdll.dll.so' (0x401c8000) Loaded debug information from ELF '/usr/local/lib/libwine_unicode.so.1' (0x40238000) No debug information in ELF '/lib/i686/libm.so.6' (0x4032b000) Loaded debug information from ELF '/usr/local/lib/wine/kernel32.dll.so' (0x40460000) Loaded debug information from ELF '/usr/local/lib/wine/rundll32.exe.so' (0x405a2000) Loaded debug information from ELF '/usr/local/lib/wine/user32.dll.so' (0x406c0000) Loaded debug information from ELF '/usr/local/lib/wine/gdi32.dll.so' (0x407f8000) Loaded debug information from ELF '/usr/local/lib/wine/advapi32.dll.so' (0x40878000) No debug information in ELF '/usr/lib/libfreetype.so.6' (0x408b7000) No debug information in ELF '/usr/lib/libfontconfig.so.1' (0x4090d000) No debug information in ELF '/usr/lib/libexpat.so.0' (0x40935000) Loaded debug information from ELF '/usr/local/lib/wine/x11drv.dll.so' (0x40955000) No debug information in ELF '/usr/X11R6/lib/libSM.so.6' (0x4001c000) No debug information in ELF '/usr/X11R6/lib/libICE.so.6' (0x409d3000) No debug information in ELF '/usr/X11R6/lib/libXrandr.so.2' (0x405b6000) No debug information in ELF '/usr/X11R6/lib/libXrender.so.1' (0x409ea000) No debug information in ELF '/usr/X11R6/lib/libXext.so.6' (0x409f2000) No debug information in ELF '/usr/X11R6/lib/libX11.so.6' (0x40a00000) No debug information in ELF '/usr/lib/tls/libGL.so' (0x40afc000) No debug information in ELF '/usr/lib/tls/libGLcore.so.1' (0x40b67000) No debug information in ELF '/usr/X11R6/lib/libXcursor.so.1' (0x410e4000) Unsupported debug information in ELF '/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2' (0x40025000) Unsupported debug information in ELF '/usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2' (0x41131000) No debug information in ELF '/usr/lib/gconv/ISO8859-1.so' (0x408a9000) Loaded debug information from ELF '/usr/local/lib/wine/imm32.dll.so' (0x41150000) Loaded debug information from ELF '/usr/local/lib/wine/shell32.dll.so' (0x4116e000) Loaded debug information from ELF '/usr/local/lib/wine/ole32.dll.so' (0x411f6000) Loaded debug information from ELF '/usr/local/lib/wine/shlwapi.dll.so' (0x4126a000) Loaded debug information from ELF '/usr/local/lib/wine/comctl32.dll.so' (0x412c1000) No debug information in 32bit DLL 'C:\windows\system\rundll32.exe' (0x405b0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x401e0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40490000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x40890000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x40810000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x406e0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40970000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\IMM32.DLL' (0x41160000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x7fb90000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x41210000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x41280000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x412d0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x41190000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x78000000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\TAPI32.DLL' (0x7f960000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\TELEPHON.CPL' (0x75a70000) Unhandled exception: page fault on read access to 0xda62061d in 32-bit code (0x401f999a). In 32-bit mode. 0x401f999a (RtlpWaitForCriticalSection+0x6a [critsection.c:204] in NTDLL.DLL): movl 0x1c(%eax),%eax 204 if ((!crit->DebugInfo) || (!crit->DebugInfo->Spare[1])) continue; The wait time could be an indication that a timeout happened. Anybody has a clue what could be the problem? Regards Andy

4 5

Re: MSYS's sh.exe has trouble reading from stdin on Wine?
by Pouech Eric DMI AEI CAEN 08 Apr '04

08 Apr '04

> wine --debugmsg +all -- sh.exe - does wineconsole -- sh.exe - work ? I fear it's the same old pb of not mapping win32 console semantics on standard unix files without winconsole (anyway, check for the CreateFile which returns 0xffffffff, likely on $CONIN) A+

1 0

MSYS's sh.exe has trouble reading from stdin on Wine?
by Dan Kegel 08 Apr '04

08 Apr '04

Someone's having trouble building my crosstool on msys, so I tried installing msys on my Wine (a home-built 20040213). (This is slightly less crazy than installing Cygwin, I think, but it's still a pretty hard test, I bet.) The installer http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download ran just fine until it tried to run the postinstall shell script. Turns out running msys's sh.exe hangs. Running it with wine --debugmsg +all -- sh.exe - and waiting until the output settles into an infinite repeat, I see the repeating section is 0009:Call kernel32.WaitForSingleObject(00000084,0000000a) ret=7105f927 0009: select( flags=12, cookie=0x4060eea8, timeout=1081401202.858741 (+0.009956), handles={0x84} ) 0009: select() = PENDING 0009: *wakeup* signaled=258 cookie=0x4060eea8 0009:Ret kernel32.WaitForSingleObject() retval=00000102 ret=7105f927 0009:Call ntdll.RtlEnterCriticalSection(710a8b0c) ret=71070c98 0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=71070c98 0009:Call ntdll.RtlLeaveCriticalSection(710a8b0c) ret=71070cb0 0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=71070cb0 0009:Call kernel32.PeekConsoleInputA(ffffffff,4060f150,00000001,4060f12c) ret=7105687a 0009: read_console_input( handle=0xffffffff, flush=0 ) 0009: read_console_input() = OBJECT_TYPE_MISMATCH { read=-1, rec={} } 0009:Ret kernel32.PeekConsoleInputA() retval=00000000 ret=7105687a 0009:Call ntdll.RtlEnterCriticalSection(710a8b0c) ret=71070c98 0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=71070c98 0009:Call ntdll.RtlLeaveCriticalSection(710a8b0c) ret=71070cb0 0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=71070cb0 0009:Call kernel32.WaitForSingleObject(00000084,0000000a) ret=7105f927 So it kind of looks like it's having trouble reading from stdin? Can someone have a look? It'd be so awesome to be able to run msys on Wine... - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

1 0

Re: abnt2 keyboard
by Dmitry Timoshkov 08 Apr '04

08 Apr '04

"Rafael аvila de EspМndola" <rafael.espindola(a)ic.unicamp.br> wrote: > The attached patch fixes the problem that wine has with the abnt2 (Brazilian) > keyboard. The problem was recently discussed in wine-devel. If you still can't provide more arguments as on wine-devel I don't see a reason why the patch can be accepted. Especially taking into account that the patch contains magic numbers without a little bit of explanation what they are. > While reading dlls/x11drv/keyboard.c I notice that wine does a linear search > to convert a virtKey to a keycode. Could this be optimized/simplified by > pre-computing a vkey2keyc[(e->state & NumLockMask)!=0] table? Feel free to send a patch. -- Dmitry.

1 0

← Newer
1
...
23
24
25
26
27
28
29
...
33
Older →

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 April 2004