Sylvain Petreolle wrote:
> Applying this patch fixes alsa :
> [repaired] dlls/winmm/winealsa/audio.c
> thanks to Daniel (Tom?) and Jerry.
>
> Now "Common" tests are ok.
> But some interactive tests still fail with winealsa.
Duplicating the IDsDriverBufferImpl_SetVolumePan function from WINEOSS to
"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> It appears that the exports in the spec files for these dll is not
> correct.
Have a look at my today's patch
"Fix some problems found while compiling and linking Wine under Cygwin",
it should help.
--
Dmitry.
It appears that the exports in the spec files for these dll is not
correct.
dllwrap -k --def mshtml.spec.def -o mshtml.dll document.o main.o
mshtml.dll.db
g.o -L../../dlls -luser32 -ladvapi32 -lkernel32 -lntdll
-L../../libs/wine -lwin
e -L../../libs/unicode -lwine_unicode -L../../libs/uuid -lwi
Hi,
Just incase anybody is interested, here is a regression test for
mailslots. There's not much point to include it into Wine until we
support mailslots properly (which I'm working on).
Mike
/*
* Mailslot regression test
*
* Copyright 2003 Mike McCormack
*/
#include
#include
#defin
On Fri, 10 Oct 2003 20:11, Jonathan Wilson wrote:
> IANAL but here are some examples of things that I think are things that the
> law was intended to protect:
> 1.A real-estate database with information on many different houses.
> 2.The database at e.g. amazon.com containing details about a whole b
On Fri, 10 Oct 2003 18:44, Patrik Stridvall wrote:
> > On Wed, 8 Oct 2003 21:53, Patrik Stridvall wrote:
> > > The significant effort requirement is for EACH fact seen by ITSELF.
> >
> > This is certainly not the case in Australia, NZ and the UK.
>
> So you can have protection on collections of tru
> "Martin" == Martin Fuchs <[EMAIL PROTECTED]> writes:
...
Martin> cout << "first call to SetShellWindow(hwnd): " << (ret?
Martin> "SUCCESS": "FAILURE") << "\n";
As plain C programm this could perhpas be included in out test suite...
--
Uwe Bonnes[EMAIL PROTECTE
Applying this patch fixes alsa :
[repaired] dlls/winmm/winealsa/audio.c
thanks to Daniel (Tom?) and Jerry.
Now "Common" tests are ok.
But some interactive tests still fail with winealsa.
I attached the log. (+wave,+dsound,+dosund3d can be provided if necessary)
=
Sylvain Petreolle (spetreoll
Hello Alexandre,
> Yes, if it works under Windows then obviously we need a fix in Wine.
> I think you should investigate exactly how Windows does it, there are
> many places where we could add such checks so we need to find out
> exactly where Windows has them.
OK - wrote a little test program to
Some time ago (about 2 years ago now), Codeweavers developped
winesetuptk, a configuration tool for Wine. It is now listed with other
Wine related files on sf.net.
The problem is that the tool hasn't really followed Wine development
(for example, removal of $VAR-style variables from config file),
--- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote:
> On October 11, 2003 06:40 pm, Steven Edwards wrote:
> > I really dont want to have a ReactOS column in the list as the
> ReactOS
> > project is planning on properly branching winehq cvs when WINE
> reaches
> > reaches 0.9/1.0.
>
> Why would you w
--- Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> > Here are the code examples with binarys
> > http://mail.gleneagle.net/sedwards/gdi/
>
> Could you please either put them on ftp or pack them together in the
> single
> file to make it easy to download it at one go?
>
> wget --mirror http://mail.
On Sun, 2003-10-12 at 13:04, Jerry Jenkins wrote:
> Dimitrie O. Paun wrote:
> > Why do we need the static?
> >
> Had I pasted more source code, you would have known why.
> LONG ALSA_WaveInit(void)
> {
> snd_pcm_t* h = NULL;
> snd_pcm_info_t *info;
> snd_
Jukka Heinonen <[EMAIL PROTECTED]> writes:
> Anyway, even with some performance issues, it looks like
> instruction emulation is needed for supporting some pure
> Win95/98/ME programs. It would seem a bit strange we try very
> hard to support Win31 and WinNT based programs but not those.
Sure, we
Dimitrie O. Paun wrote:
On October 11, 2003 03:01 pm, Alex Pasadyn wrote:
I'm sending this in two parts because I added some files and can't get
cvs diff to have them show up.
Of course, cvs diff will ignore these files. You need to add them manually
to diff. To do so, you do:
$ cvs diff dlls
Ivan Leo Murray-Smith wrote:
Let's hold this open through Friday, and then let's
consider it final.
An the results are?
You can see the results at
http://www.winehq.org/wineconf/wineconf.htm
(click on the 'Total' frame at the bottom;
MS Excel has awful export to the web functions).
I conclude fro
On Sun, 2003-10-12 at 09:17, Lionel Ulmer wrote:
> Well, now that you say it, when I tested the demo for Tomb Raider 3 on Win2K
> (to check some slight graphical corruptions), it crashed at start-up... So
> the game does not even check for Windows version before doing its hacks.
>
> Let's hope we
Dimitrie O. Paun wrote:
Why do we need the static?
Had I pasted more source code, you would have known why.
LONG ALSA_WaveInit(void)
{
snd_pcm_t* h = NULL;
snd_pcm_info_t *info;
snd_pcm_hw_params_t * hw_params;
WINE_WAVEOUT* wwo;
On Sun, 2003-10-12 at 05:19, Sylvain Petreolle wrote:
> Was something like this already applied to CVS ?
> This could explain why I got garbage into winealsa for the device
> names.
>
> > > > +chardevice[] = "hw";
> > > I think it should be
> > > static char
On Sat, Oct 11, 2003 at 05:42:49PM -0700, Alexandre Julliard wrote:
> What changed is that emulation of these instructions was deliberately
> removed ;-)
I should have guessed that they were sacrified due to the DLL separation :-)
> This was done for dll separation reasons, and because they are n
20 matches
Mail list logo
