Try this patch. DirectSoundCreate should be called with the GUID of
the device or NULL for the default device, not the GUID of the COM
object interface.
Raphael wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
I have tried Unreal2 and now we have an regression into dsound code.
Un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
I have tried Unreal2 and now we have an regression into dsound code.
Unreal2 Create an dsound device since introduction beginning and after (the
introduction) the games wants to initialize dmusic (what i'm trying to fix
since a lot of tim
Hello,
--- Wolfgang Schwotzer <[EMAIL PROTECTED]> wrote:
> > Index: dlls/commdlg/filedlg.c
> + // return needed size in first two bytes of lpstrFile
Please remove the C++ style comment.
Thanks
Steven
__
Do you Yahoo!?
Win a $2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 01 May 2004 18:28, Gerald Pfeifer wrote:
> Raphael,
Hi Gerald,
> the following change to dlls/d3d8/utils.c
> actually causes a new problem with XFree86 4.3.0 and Mesa 3.4.2:
>
> utils.c:1306: warning: implicit declaration of function
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 28 April 2004 20:21, Lionel Ulmer wrote:
> > That seems really overkill. It's OK to define some symbols ourselves
> > when they have well-known values, but I don't think shipping the full
> > headers is really necessary; and I don't see ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 03 May 2004 05:35, hatky wrote:
> Today's cvs crashes the X2 game benchmark and so does cvs "1 day ago" while
> "2 days ago" works, I got no lead, it has nothing usfull on the messages,
> the backtrace shows it crashes in the X2 exe file.
Today's cvs crashes the X2 game benchmark and so does cvs "1 day ago" while "2
days ago" works, I got no lead, it has nothing usfull on the messages, the
backtrace shows it crashes in the X2 exe file.
Any one can hand me a lead to find the patch that couses it?
--
Hatky,
Worshiper of
> Is it possible that the
> recent file access changes have caused this case to be handelled
> incorrectly, causing the file not to be found?
To find the patch that caused the regression, you can use CVS regression
testing. A howto is in the devel guide.
Ivan.
Bill Medland wrote:
On May 1, 2004 08:50 am, Duane Clark wrote:
> Bill Medland wrote:
(Yes, I know 20031118 is a little old)
Anyone any ideas what is going on here or any simple tests I can do?
I am trying to get our company's software running on Red Hat Enterprise
Linux 3 Update
