December 2005 - Wine-Devel - list.winehq.org

fixme:font:load_VDMX Failed to retrieve vTable

by Curro Amores

hi my reports are not well displayed on my access97 app. fonts are displayed i anora location and separed I got this fixme fixme:font:load_VDMX Failed to retrieve vTable somebdoy knows how to fix it? thanks all

Dec. 9, 2005

Re: Wine release 0.9.3

by Scott Ritchie

On Fri, 2005-12-09 at 09:19 +0100, rmkml wrote: > Hi, > Wine compiled fail : > gcc -c -I. -I. -I../include -I../include -D__WINESRC__ -Wall -pipe > -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith > -g -O2 -o snapshot.o snapshot.c > In file included from snapshot.c:33: > ../include/winternl.h:2040: parse error before "va_list" > ../include/winternl.h:2212: parse error before "va_list" > ../include/winternl.h:2213: parse error before "va_list" > make[1]: *** [snapshot.o] Error 1 > > no pb compile wine092. > thx for your help > Rmkml Are you certain you have all the build dependencies? (Check configure's output) Thanks, Scott Ritchie

Dec. 9, 2005

Re: Wine release 0.9.3

by rmkml

Hi, Wine compiled fail : gcc -c -I. -I. -I../include -I../include -D__WINESRC__ -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o snapshot.o snapshot.c In file included from snapshot.c:33: ../include/winternl.h:2040: parse error before "va_list" ../include/winternl.h:2212: parse error before "va_list" ../include/winternl.h:2213: parse error before "va_list" make[1]: *** [snapshot.o] Error 1 no pb compile wine092. thx for your help Rmkml On Thu, 8 Dec 2005, Alexandre Julliard wrote: > Date: Thu, 8 Dec 2005 16:20:19 +0100 (CET) > From: Alexandre Julliard <julliard(a)winehq.org> > Reply-To: wine-devel(a)winehq.org > To: wine-announce(a)winehq.org > Subject: Wine release 0.9.3 > > This is release 0.9.3 of Wine, a free implementation of Windows on Unix. > > What's new in this release: > - Many marshalling fixes in rpcrt4. > - Various OLE improvements and fixes. > - Better audio driver management in winecfg. > - Many wininet fixes. > - Several Web browser improvements. > - More dbghelp APIs implemented. > - Directory objects in wineserver. > - Lots of bug fixes. > > Because of lags created by using mirrors, this message may reach you > before the release is available at the public sites. The sources will > be available from the following locations: > > http://ibiblio.org/pub/linux/system/emulators/wine/wine-0.9.3.tar.bz2 > http://prdownloads.sourceforge.net/wine/wine-0.9.3.tar.bz2 > > Binary packages for various distributions will be available from: > > http://www.winehq.org/site/download > > You will find documentation on > > http://www.winehq.org/site/documentation > > You can also get the current source directly from the git or CVS > repositories. Check respectively http://wiki.winehq.org/GitWine or > http://www.winehq.org/cvs for details. > > Patches should be submitted to "wine-patches(a)winehq.org". Please > don't forget to include a ChangeLog entry. If you submitted a patch, > please check to make sure it has been included in the new release. > > Wine is available thanks to the work of many people. See the file > AUTHORS in the distribution for the complete list. > > -- > Alexandre Julliard > julliard(a)winehq.org > >

Dec. 9, 2005

Re: advpack: DoInfInstall test, fix

by Stefan Huehner

On Fri, Dec 09, 2005 at 12:35:29AM +0100, Markus Amsler wrote: > Changelog: > Markus Amsler <markus.amsler(a)oribi.org> > Add test for DoInfInstall and make it pass under wine. > +static void infinstall_test() Hi, could you please use static void infinstall_test(void) for the aboce line, as this in more correct c code and avoids the warning enabled with (-Wstrict-prototypes). Regards, Stefan

Dec. 9, 2005

Re: OLE without TLS libraries

by Cihan Altinay

Quoting Marcus Meissner <marcus(a)jet.franken.de>: > On Thu, Dec 08, 2005 at 12:35:32PM +1000, Cihan Altinay wrote: > > Hi, > > > > having a Xen system my Linux tls library path is not > > in place (renamed to /lib/tls.disabled). > > When I run a program that uses OLE/DCOM (with native > > ole libraries) it crashes immediately. Using > > LD_LIBRARY_PATH=/lib/tls.disabled wine program > > makes it work again. > > I am not sure if this is true for all OLE apps. > > > > Is this known/expected behaviour or a bug? > > Do you have a backtrace of the crash or similar? Just wanted to create one with the latest CVS but it seems it was fixed some days ago. I investigated a bit and to my surprise the problem was in x11drv which was patched 2005-12-06. We had that problem since weeks and were "happy" with the library path solution until I thought I might ask here. So it was quite a surprise that it was fixed just now :-) Thanks anyway, Cihan

Dec. 9, 2005

Re: how do I find where wine itself is segfaulting?

by Peter Berg Larsen

On Fri, 9 Dec 2005, Peter Berg Larsen wrote: > Try booting with noexec=off. Replying to myself: I just tried it and it works for me. (My mandrake kernel crashed for lilo's default vga resolution??) Peter

Dec. 9, 2005

Re: how do I find where wine itself is segfaulting?

by Peter Berg Larsen

On Thu, 8 Dec 2005, Bill Medland wrote: > Wrong. It's the kernel choice. It works on the non-smp kernel > and fails on the smp kernel. > (2.6.9-22.EL works; 2.6.9-22.ELsmp fails, both are RedHat > kernels) Try booting with noexec=off. I tried that when I asked wine-devel a month ago, but my mandrake crashed - for some obscure reasons - before reaching a prompt. Peter

Dec. 9, 2005

Re: OpenGL regression

by Raphael

On Thursday 08 December 2005 21:59, Willie Sippel wrote: > Am Donnerstag, 8. Dezember 2005 21:37 schrieb Stefan Dösinger: > > Hello, > > I've just noticed that the opengl render_texture patch caused a > > regression with Counter Strike 1.6 and Mesa(radeon driver and software > > only) rendering. > > I noticed a similar error, probably also related to that patch - tested > DAZ| Studio 1.0.1, latest Nvidia drivers, on a Quadro FX3000. Already filed > a bug report (#4016): > [...] > trace:opengl:wglCreateContext creating context 0x5595c2c8 (GL context > creation delayed) > trace:opengl:wglShareLists (0x5593a820, 0x5595c2c8) > trace:opengl:wglShareLists created a delayed OpenGL context (0x7c2b27a0) > for Wine context 0x5593a820 > trace:opengl:wglShareLists created a delayed OpenGL context (0x7c4cea50) > for Wine context 0x5595c2c8 sharing lists with OpenGL ctx 0x7c2b27a0 > trace:opengl:wglGetCurrentContext () > trace:opengl:wglGetCurrentContext returning (nil) (GL context (nil)) > trace:opengl:wglMakeCurrent (0x2e38,0x5595c2c8) > trace:opengl:wglMakeCurrent make current for dis 0x7c02b698, drawable > 0x300000c, ctx 0x7c4cea50 > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 128 (GLX) > Minor opcode of failed request: 5 (X_GLXMakeCurrent) > Serial number of failed request: 7093 > Current serial number in output stream: 7093 > > > Stefan > > Ciao, > Willie No it's not the same: Stefan crash on glXQueryDrawable while you fail on glXMakeCurrent I can say you crash is normal as i haven't fixed wglShareLists delayed context creation yet (as i have done on wglMakeCurrent). I must to share this code (delayed creation) on a static utility function For Stefan problem i don't understand how it can fail :( Regards, Raphael

Dec. 8, 2005

Re: how do I find where wine itself is segfaulting?

by Bill Medland

On December 8, 2005 02:40 pm, Bill Medland wrote: > On December 8, 2005 09:15 am, Bill Medland wrote: > > On December 8, 2005 03:08 am, Peter Berg Larsen wrote: > > > > --- Bill Medland <billmedland(a)mercuryspeed.com> wrote: > > > > > So I turn on WINDEBUG=+relay to see what is being > > > > > passed. > > > > > > > > > > And wine segfaults. > > > > > > > > > > Anyone know what is going on? > > > > > > On Wed, 7 Dec 2005, Keith Dunwoody wrote: > > > > I'm running into the same problem. File on the > > > > resulting core tells me it was generated from > > > > wine-preloader. I'm using wine 0.9.2 for Fedora Core 3 > > > > from winehq (the i686 version I believe). I'm running > > > > an x86_64, if that matters. > > > > > > You are not the first: > > > > > > http://www.winehq.org/pipermail/wine-devel/2005-November/0 > > >41 98 8.html > > > > > > http://www.winehq.org/hypermail/wine-devel/2005/03/0636.ht > > >ml > > > > > > http://www.winehq.com/hypermail/wine-devel/2005/05/0328.ht > > >ml > > > > > > > > > Wine crashes the first time it enters/uses a > > > entry/function using the debug setup from > > > ntdll/relay.c:RELAY_SetupDLL. (Which happens to be a > > > RtlInitUnicode in > > > kernel/module:GetModuleHandleW) . > > > > So is anyone actively looking into this? I'll make a start > > until someone says that they are already doing it. > > > > > Peter > > So it is looking to me as if it (and my original problem) is > something to do with the cpu or memory. It used to work on my > Celeron with 512MB but it doesn't work on my brand new Dell > Optiplex GX280 with 1GB. (I am currently working to remove > any other differences). > > Does that make any sense to anyone? Wrong. It's the kernel choice. It works on the non-smp kernel and fails on the smp kernel. (2.6.9-22.EL works; 2.6.9-22.ELsmp fails, both are RedHat kernels) -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed

Dec. 8, 2005

Re: how do I find where wine itself is segfaulting?

by Bill Medland

On December 8, 2005 09:15 am, Bill Medland wrote: > On December 8, 2005 03:08 am, Peter Berg Larsen wrote: > > > --- Bill Medland <billmedland(a)mercuryspeed.com> wrote: > > > > So I turn on WINDEBUG=+relay to see what is being > > > > passed. > > > > > > > > And wine segfaults. > > > > > > > > Anyone know what is going on? > > > > On Wed, 7 Dec 2005, Keith Dunwoody wrote: > > > I'm running into the same problem. File on the resulting > > > core tells me it was generated from wine-preloader. I'm > > > using wine 0.9.2 for Fedora Core 3 from winehq (the i686 > > > version I believe). I'm running an x86_64, if that > > > matters. > > > > You are not the first: > > > > http://www.winehq.org/pipermail/wine-devel/2005-November/041 > >98 8.html > > > > http://www.winehq.org/hypermail/wine-devel/2005/03/0636.html > > > > http://www.winehq.com/hypermail/wine-devel/2005/05/0328.html > > > > > > Wine crashes the first time it enters/uses a entry/function > > using the debug setup from ntdll/relay.c:RELAY_SetupDLL. > > (Which happens to be a RtlInitUnicode in > > kernel/module:GetModuleHandleW) . > > So is anyone actively looking into this? I'll make a start > until someone says that they are already doing it. > > > Peter So it is looking to me as if it (and my original problem) is something to do with the cpu or memory. It used to work on my Celeron with 512MB but it doesn't work on my brand new Dell Optiplex GX280 with 1GB. (I am currently working to remove any other differences). Does that make any sense to anyone? -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed

Dec. 8, 2005