wine-devel May 2006

151 participants
288 discussions

by Emmanuel Maillard

Hi all, Quartz driver is up to date on Darwine CVS. Winemine is playable on both PPC and x86 but it look fine only on PPC, x86 driver suffer strange rendering bugs. See wiki for building the driver : http://wiki.opendarwin.org/ index.php/Darwine:quartzdrv I will update wiki soon with issues and todo for Quartz driver. Cheers Emmanuel

17 years, 11 months

Re: Re: Wine 1.0 Tasks

by fenix＠club-internet.fr

Hi, >> (Note the #3902 should be renamed as 'DIB Engine rewrite' > >Agreed; done. http://bugs.winehq.org/show_bug.cgi?id=3902 :) >> and i don't think is mandatory for 1.0) > >Probably right. Let's create the next milestone after 1.0, say 1.1, and start >retargeting bugs we don't plan to fix for 1.0. (That's what GCC does; >some bugs they retarget early, some just before the release.) > >> But i think we must fix users most hated bugs as: >> - dsound deadlocks/craps >> - openGL problems (multi contexts, fb/visual configs) >> - lotus problems > >The OpenGL child window bug, >http://bugs.winehq.org/show_bug.cgi?id=2398 >probably won't be fixed for 1.0 because it requires >an X server change. No it must be doable without X changes (But X additions as GLX_EXT_texture_from_pixmap will help a lot). Only problem is to find time to fix it (as lionel, i have no time for now). Anyway i having a simple and downloadable application to reproduce this problem (not lightwave) must help. The only parts who really needs X change are for: - glShareList: sharing fb/visual config between exitings GLX contexts - dinput mouse management >I'm not sure lotus notes problems should block 1.0, as IBM has a native >Linux client now, but if someone wants to fix them (especially the ones >in usp10.dll netapi32.dll, that would be great. agree :) >> Note: it will be interesting to add user votes to wine-bugs (ala kde) to >> better see user needs. > >There are already user votes in bugzilla, that should suffice. >- Dan Oups i never seen it :) Regards, Raphael

17 years, 11 months

Re: winspool/tests: Use 0xdeadbeef as magic Value

by Jeff Latimer

A minor spelling mistake, deaddeef instread of deadbeef. Jeff Detlef Riekenberg wrote: >I was using 0x00dead00 before, but Dmitry suggested 0xdeadbeef, as this > > > >-#define MAGIC_DEAD 0x00dead00 >+#define MAGIC_DEAD 0xdeaddeef > >

17 years, 11 months

wine problems on a 64bit system

by Pavel Troller

Hi! As some of you know, I'm experimenting with my new 64bit systems. I've found that there are problems running a lot of applications, which normally run on a 32bit system. A typical example is IL2 Sturmovik Forgotten Battles game. On a 32bit system, with the latest wine CVS (even compiled on a 64bit system) it runs flawlessly. On a 64bit system, it just prints fixme:seh:check_no_exec No exec fault triggered at 0x6d4d08b0, enabling work-around but the workaround seems to be unefficient, because nothing more happens. With a +relay, it shows that the program is looping, executing 0009:Call msvcrt._except_handler3(7fb2faa0,7fb2fba0,7fb2f7d4,7fb2f714) ret=7bc54d65 0009:Ret msvcrt._except_handler3() retval=00000000 ret=7bc54d65 and nothing more, ad infinitum. The machines are running very similar kernels. Both are hardened with exec-shield, but even disabling it on a 64bit by 'echo 0 >/proc/sys/kernel/exec-shield' doesn't help. The 32bit works even with exec-shield enabled (and doesn't print the no-exec message). Are there chances to fix this issue ? Or is it a system problem ? With regards, Pavel Troller

17 years, 11 months

Text input box with scrollbar

by Augusto Arcoverde da Rocha

Hi all, Where I can find the inputbox drawing code? Some of these box appear with scrollbar when testing Action Request System application under Wine, but not under MS Windows. Thanks, Augusto Arcoverde da Rocha

17 years, 11 months

Wine 1.0 Tasks

by Dan Kegel

If you look at http://bugs.winehq.org/ you'll see a link on the left hand side called "1.0 Tasks", which lists the 1.0 bugs being tracked in bugzilla. Here's the URL it links to http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_s… I suspect a few of these are stale, and a bunch others are missing, but I like the idea of using bugzilla to track our progress to 1.0. What other bugs should be fixed before 1.0? Let's nominate a few bugs to add to the 1.0 task list, discuss them a bit, and see what Alexandre thinks. For instance: I'd like one goal of 1.0 to be "make Windows developers take Wine seriously." To achieve that, I think 1.0 has to support at least some Microsoft development tools well, including their IDEs and debuggers. It's probably unreasonable to require 1.0 to support .NET, so maybe supporting the last pre-.NET versions of Visual C++ (6.2?) and Visual Basic (6.0?) would be a good goal. And I don't think it's that unreasonable anymore; Wine is pretty close to being able to do that. What do y'all think? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

17 years, 11 months

Re: svrapi: add stub implementation

by Robert Shearman

Vitaly Lipatov wrote: >svrapi.dll is exist on Win9X OS and used in some programs. > > What programs? Is it still used even with the winver set to win2k? -- Rob Shearman

17 years, 11 months

Re: wineconsole: Store the font as a DWORD_PTR.

by Detlef Riekenberg

Am Mittwoch, den 31.05.2006, 16:28 +0900 schrieb Mike McCormack: > index 169f4e1..73a0987 100644 > --- a/programs/wineconsole/dialog.c > +++ b/programs/wineconsole/dialog.c > + return GetWindowLongPtr(hWnd, 0); > + HFONT hFont = (HFONT)GetWindowLongPtr(hWnd, 0L); Are 0 and 0L always the same ? (32bit and 64bit) -- By By ... ... Detlef

17 years, 11 months

Re: crypt32: implement CryptBinaryToStringA and CryptStringToBinaryA

by Detlef Riekenberg

Hi Juan Lang. > ChangeLog: implement CryptBinaryToStringA and CryptStringToBinaryA based > on Kai Blin's base64 encoder/decoder The Functions are not Present in every crypt_32.dll. The test will crash on win9x. (The Results from GetProcAddress are not tested) -- By By ... ... Detlef

17 years, 11 months

file timestamps in a git tree

by Saulius Krasuckas

I make an ugly hack in a branch at my git tree. Then I run after following after some git updates: $ git rebase master ugly_hack $ make Makefile is older than Makefile.in configure, please rerun ./configure make: *** [Makefile] Error 1 $ git checkout master $ make Makefile is older than Makefile.in configure, please rerun ./configure make: *** [Makefile] Error 1 Is this behaviour intended? I thought git would reset all the file timestamps once I switch to another (master) branch... Am I wrong?

17 years, 11 months

Jump to page:

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 May 2006