Ivan Leo Murray-Smith wrote:
With this change, we can use the 6.3 version of Quicktime
to see streamed video from Wineconf...
This would break Grand Prix Legends and Nascar 2002 (Thats why the patch was
written in the first place), maybe you should contact the author of the patch, a
proper fix woul
"Sami Aario" <[EMAIL PROTECTED]> writes:
> I've determined that version 1.73 of tools/winebuild/spec32.c is what is
> causing this. Reverting to 1.72 cures this particular problem for me. My
> system is a Debian woody installation. Does anyone have any ideas on
> what's going on here?
Do 'make di
Le sam 10/01/2004 à 20:05, Sami Aario a écrit :
>
> - Original Message -
> From: "Sami Aario" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, January 10, 2004 1:55 AM
> Subject: Build fails for current CVS update
>
>
> > Hi,
> >
> > Building with tools/wineinstall fails
- Original Message -
From: "Sami Aario" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 10, 2004 1:55 AM
Subject: Build fails for current CVS update
> Hi,
>
> Building with tools/wineinstall fails with the latest CVS update on my
> system with the following:
>
>
gcc
> With this change, we can use the 6.3 version of Quicktime
> to see streamed video from Wineconf...
This would break Grand Prix Legends and Nascar 2002 (Thats why the patch was
written in the first place), maybe you should contact the author of the patch, a
proper fix would be better, why should w
Jeremy Shaw wrote:
As a result of this patch (which is currently applied in cvs head):
http://www.winehq.com/hypermail/wine-patches/2002/12/0009.html
This also makes the Quicktime player unable to view
streaming video, although I have to confess I do not
know why, except that the bind failure seem
On January 10, 2004 11:27 am, Brian Vincent (C) wrote:
> Also, if anyone is bored and wants to do something easy, it might be
> nice to change all references in the WWN issues from winehq.com to
> winehq.org. I've just recently switched over to trying to be consistent
> on the .org thing. There's
Le mer 07/01/2004 à 11:34, Thomas Brix Larsen a écrit :
> Hi list, just upgraded to 2.6.0 and the NVIDIA driver from minion.de
> and now I get this error when compiling wine:
>
>
> directx.c: In function `IDirect3D8Impl_GetDeviceCaps':
> directx.c:639: `GL_MAX_VERTEX_UNITS_ARB' undeclared (first
On Sat, 10 Jan 2004 06:42:07 +0100, you wrote:
> Heavy based on Chris Morgan's winebrowser i cut/paste a winehh, to use a Unix
> chm-file viewer. It works when there is no space in the path. How to do the
> transform from windows path to Unix path right?
winepath is part of wine:
$ winepath d:
Title: WWN broken
> We scan the XMl with tidy before posting. What is odd is that tidy
> reports the XML is valid, but yet PHP's XML parser barfs on it. Whatever
> the case, I just patched it, so it should be fixed online soon.
Whoops. Sorry about that. I was running out the door when I p
I looked at extending the lock to cover the callback
when it was 32 bit code and The TIME_KILL_SYNCHRNOUS
flag was set but I was concerned about the performance
hit and didn't pursue it further.
Eric Pouech wrote:
> Robert Reif a écrit :
> > Reduce the use of the dsound global variable by
> > pas
ï
Hello again,
I just had a look at some WIN98
shortcut files.They are also in ANSI format, not 16 bit
Unicode:: 4C 00 00 00-01 14 02 00-00 00 00
00-C0 00 00 00 L âÂâ
â0010: 00 00 00 46-1B 00 00 00-00 00 00
00-00 3E EA 22
Fâ >Ã"0020: 0F 7D BD
01-00 98
> Hmm..., I KNOW 'SCF_UNICODE' is NOT 0x1000 in the first place, but why do
> you say it's 0x80 ?
>
> Going by the copyrights, Marcus Meissner and Juergen Schmied did the initial
> job, and perhaps one of them put this value.
> I don't know about Juergen, but I have tremendous faith in Marcus (I
Eric Pouech a écrit :
Could you be more specific on this one ?
timeKillEvent is not 100% thread safe (I'll send a patch later on),
but timeKillEvent in Wine is always synchronous (ie the killer is
killed when timeKillEvent returns).
I mean the _timer_ is killed...
and please forget my first post
Could you be more specific on this one ?
timeKillEvent is not 100% thread safe (I'll send a patch later on), but
timeKillEvent in Wine is always synchronous (ie the killer is killed
when timeKillEvent returns).
I mean the _timer_ is killed...
Robert Reif a écrit :
Reduce the use of the dsound global variable by
passing address to functions. This is in preparation
of supporting multiple DirectSound devices. We can't
remove all uses because an mmtimer callback can be
called even after the timer is killed. Windows has an
mmtimer flag th
16 matches
Mail list logo
