Hi Michael,
is this up your alley? You've been looking at dsound recently, iirc.
- Dan
export WINEDEBUG=warn+heap
../../../tools/runtest -q -P wine -M dsound.dll -T ../../.. -p
dsound_test.exe.so ds3d.c && touch ds3d.ok
ALSA lib pcm_pulse.c:1008:(_snd_pcm_pulse_open) Unknown field handle_underrun
Yeah, I'm aware of virtual desktop and used to create scripts to
launch applications using wine explorer \desktop=WIDTHxHEIGHT or
whatever the parameters were, it works well. But means that you have
to create always new shell script, and it also can prevent desktop
integration for certain applicati
Hello,
I personally hate when applications decide to change my screen
resolution without asking me, or some applications just won't run
inside window.
So I did fake display interface for the winex11.drv. It allows you to
send any display resolution and frequency to the application, but it
does not
Bernhard Loos writes:
> @@ -825,6 +825,9 @@ int set_process_debug_flag( struct process *process, int
> flag )
> {
> char data = (flag != 0);
>
> +process->create_flags = (process->create_flags & ~(DEBUG_PROCESS |
> DEBUG_ONLY_THIS_PROCESS))
> +| flag;
> +
There was discussion about putting a daily wine build on the ubuntu ppa.
I'd like to put in a word for having it on the development version (currently
oneiric) as well as the stable version (natty).
Right now wine only seems to have a natty ppa.
On Thu, Sep 1, 2011 at 1:01 PM, Henri Verbeet wrote:
> On 1 September 2011 21:02, Henri Verbeet wrote:
>> I have some doubts about this being caused by this patch.
>>
> That said, you may want to give 78289 a try.
I plopped it into the buildbot, and since then no tests have failed.
I hope it's
On Thu, 1 Sep 2011, Octavian Voicu wrote:
[...]
> The patch uses dos line endings, that's why it doesn't apply.
I don't know what happened because the email was generated the same way
as all the other emails for PO file patches. There's something in the
Czech language that causes both alpine and
2011/9/2 Frédéric Delanoy :
> On Thu, Sep 1, 2011 at 23:37, wrote:
>> The Buildbot has detected a failed build on builder runtests while building
>> Wine.
>> Full details are available at:
>> http://buildbot.kegel.com/builders/runtests/builds/208
>> BUILD FAILED: failed shell_3
>>
>> For more i
2011/9/1 André Hentschel :
> It does nothing (except confusing)
> beside that i doubt someone wants to print registry hives
That's not a reason IMHO.
What should be done is fix the printing so it works like on windows
(or put an error box: "not yet implemented", or similar)
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13915
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13910
Your paranoid android
Hi,
While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=13909
Your paranoid android
On 09/02/2011 10:32 AM, Michael Stefaniuc wrote:
Bruno Jesus wrote:
On Thu, Sep 1, 2011 at 18:40, Bruno Jesus<00cp...@gmail.com> wrote:
I don't get the same results here, can anyone help me to understand
why it failed?
10014 = WSAEFAULT and I could not find this return value anywhere
near, may
To be fair, that feature is available on Windows.
2011/9/1 André Hentschel :
> It does nothing (except confusing)
> beside that i doubt someone wants to print registry hives
>
> ---
> programs/regedit/En.rc | 1 -
> programs/regedit/framewnd.c | 77
> --
Bruno Jesus wrote:
> On Thu, Sep 1, 2011 at 18:40, Bruno Jesus <00cp...@gmail.com> wrote:
>> I don't get the same results here, can anyone help me to understand
>> why it failed?
>> 10014 = WSAEFAULT and I could not find this return value anywhere
>> near, maybe due to threading?
>>
>> Thanks,
>> B
Le 01/09/2011 16:22, Francois Gouget a écrit :
On Wed, 24 Aug 2011, Eric Pouech wrote:
[...]
you can safely provide the patches with protecting WriteConsole and friends
with a if (!is_console_handle(???)) return FALSE; line
Would something like the attached patch be ok?
As far as I can see all
On Thu, Sep 1, 2011 at 23:37, wrote:
> The Buildbot has detected a failed build on builder runtests while building
> Wine.
> Full details are available at:
> http://buildbot.kegel.com/builders/runtests/builds/208
> BUILD FAILED: failed shell_3
>
> For more info about this message, see http://wi
17 matches
Mail list logo