Hi,
With the update of dlls/winex11.drv/opengl.c from revision 1.103 to 1.104,
World of Warcraft no
longer starts in OpenGL mode. WoW complains that my graphics card does not have
"dual-TMU
support". (I have a Radeon R200 with Mesa 7.1)
Cheers,
Chris
___
--- Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Don't #if 0 out the code there
>
> Change it to something like this:
>
> if (pmix > This->buflen)
> WARN("Mixing further ahead then buffer is long\n");
Replacing that code with your suggestion means I get lots and lots of messages
*with* sound.
--- Alex Villacís Lasso <[EMAIL PROTECTED]> wrote:
> You might try the patch with the title "DSOUND: recover from mismatch
> between time spanned by primary buffer being longer than the one spanned
> by secondary buffer", which I sent along with some other patches today.
> It looks somewhat sim
Hi,
I am trying to run the World of Warcraft 1.11.0 (trial) client using Wine
0.9.20 and XOrg 7.1 with
a Radeon 9200 video card. I don't have a guest access code yet, and so I have
only reached
Warcraft's login screen. However, this screen seems to be working fine... until
I press the "Quit"
bu
Hi,
I have just updated my wine installation from CVS, and my OpenGL game is now
crashing:
X Error of failed request: GLXBadPixmap
Major opcode of failed request: 129 (GLX)
Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply)
Serial number of failed request: 441
Current s
--- Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> What program are you using? Could you also attach a log 'WINEDEBUG=+wgl,
> +opengl wine program.exe'?
It was the World of Warcraft Trial(?) Client (US version) 1.11.0, run with the
-opengl parameter,
i.e.
$ wine WoW.exe -opengl
I was also u
Hi,
Ever since (approx) when the winecfg tool became active, a Windows tool that
examined IDE
capabilities has stopped working. Instead, the following messages are being
written into the dmesg
log:
hdc: write_intr: wrong transfer direction!
hdd: write_intr: wrong transfer direction!
hdc is a D
> Check out the content of vga.c (in
> dlls/winedos), you have most of the code you need.
> However, int33 mouse hide/show should cooperate with
> the vga layer.
OK, here's a first draft at a patch. Created with
reference to my old copies of Ralph Brown's Interrupt
List.
Cheers,
Chris
--- Eric Pouech <[EMAIL PROTECTED]> wrote:
> SetConsoleCursorInfo would do (if you're running the
> program under wineconsole).
/**
* GetConsoleWindow [EMAIL PROTECTED]
*/
HWND WINAPI GetConsoleWindow(VOID)
{
FIXME
Hi,
I am almost running an old DOS-based application using
wineconsole, but I am constantly being bombarded by
FIXME messages from the DOSVM's Int33 calls for "Show
mouse cursor" and "Hide mouse cursor".
I have tracked the relevant code down to
dlls/winedos/int33.c, but don't know how the DOSVM
d
10 matches
Mail list logo
