On 10 February 2010 09:11, David Gerard wrote:
> On 9 February 2010 18:16, David Laight wrote:
>
>> A 32bit (i386) windows application binary can only run in a 32bit
>> Unix application [1]. In which case the Unix kernel will handle the
>> system call emulation and ensure that the only user-spac
On 9 February 2010 18:16, David Laight wrote:
> A 32bit (i386) windows application binary can only run in a 32bit
> Unix application [1]. In which case the Unix kernel will handle the
> system call emulation and ensure that the only user-space virtual
> addresses the application sees are 32bit (
On 02/09/2010 10:25 PM, Vincent Povirk wrote:
Actually it is fairly "trivial". Of course not from the statistics but from
the source code.
The source code isn't an accurate indication of which issues have been
solved either. If I add a new case to a switch statement or register a
For a lot of
What specific features are your referring? msxml3 isn't complete and has
a lot of problems, but it's considered as ready,
it's enough for msxml4 to just forward to it. If there's a real problem
let's add another forward (as DOMDocument40 already does).
After some more investigate the crash i
> Actually it is fairly "trivial". Of course not from the statistics but from
> the source code.
The source code isn't an accurate indication of which issues have been
solved either. If I add a new case to a switch statement or register a
new CLSID, it'll stop some messages from appearing, but the
On 02/09/2010 08:51 PM, Vincent Povirk wrote:
It would be very nice to know if any of the most reported ERRs, WARNs,
FIXMEs etc. from the _previous_ run is now gone (in other words, that it has
been fixed/implemented)
I don't think that's possible to determine from the statistics. Just
because
On Mon, Feb 8, 2010 at 10:11 PM, Austin English wrote:
> On Mon, Feb 8, 2010 at 2:07 PM, Damjan Jovanovic wrote:
>> Changelog:
>> * ws2_32: warn the user if broadcasts are failing because of a missing
>> route to 255.255.255.255
> diff --git a/dlls/ws2_32/socket.c b/dlls/ws2_32/socket.c
> index 9
> It would be very nice to know if any of the most reported ERRs, WARNs,
> FIXMEs etc. from the _previous_ run is now gone (in other words, that it has
> been fixed/implemented)
I don't think that's possible to determine from the statistics. Just
because we don't see a message, or don't see it as
Hi!
It would be very nice to know if any of the most reported ERRs, WARNs,
FIXMEs etc. from the _previous_ run is now gone (in other words, that it
has been fixed/implemented)
Thanks,
Tomas
On Mon, Feb 08, 2010 at 11:27:07AM +0100, joerg-cyril.hoe...@t-systems.com
wrote:
> The wine64 challenge seems to let 32bit MS-windows apps work even
> though the UNIX side has to manage pointer addresses >2^32, i.e. above
> the lower 4GB address range. Is there some address translation
> involve
Hi Alexandre,
First of all, thank you for your work on this.
On 2/9/10 5:27 PM, Alexandre Julliard wrote:
Jacek Caban writes:
In previous version CRs were lost in their way to wine-patches. Also
this version has a few improvements made together with Dan that should
help writing tests, mo
On 2/9/2010 20:57, Vladimir Pankratov wrote:
Hello all.
changes since try 4:
changed buffer size to 257
Thanks to Nikolay Sivov.
+WCHAR wszSearchText[257]; /* Native uses only first 256
symbols + trailing \0 */
That's not exactly what I meant. Native winhlp32 as I can s
On 01/26/2010 06:31 PM, Henri Verbeet wrote:
+color = getPixelColor(device, 150, 150);
+todo_wine ok(color_match(color, 0x00ff, 1), "color 0x%08x.\n", color);
Hi Henri,
This particular test fails on some VMware and VirtualBox boxes. We've
been through this before about whether bro
Jacek Caban writes:
> In previous version CRs were lost in their way to wine-patches. Also
> this version has a few improvements made together with Dan that should
> help writing tests, mostly no need to care about CRs (they are
> skipped) and better failure messages.
It doesn't work here:
../.
Replying with wine-devel, cause my gmail account reported
failed delivery to Vladimir's mail address. You have a kind of forwarding
or I don't know what.
Original Message
Subject:Re: winhlp32: Improve Tab view [try 3]
Date: Tue, 09 Feb 2010 21:14:04 +0500
From: Vlad
Vladimir Pankratov writes:
> Hello all.
>
> changes since try3:
> changed variables size to MAX_PATH
MAX_PATH doesn't make sense here, this is not a file name.
--
Alexandre Julliard
julli...@winehq.org
On 2/9/2010 16:04, Alistair Leslie-Hughes wrote:
On 9/02/2010 9:21 PM, Nikolay Sivov wrote:
On 2/9/2010 11:50, Alistair Leslie-Hughes wrote:
Hi,
Changelog:
msxml4: Prefer to use the native version
Best Regards
Alistair Leslie-Hughes
Why do you need this?
If a program install msxml4 as part
On 9/02/2010 9:21 PM, Nikolay Sivov wrote:
On 2/9/2010 11:50, Alistair Leslie-Hughes wrote:
Hi,
Changelog:
msxml4: Prefer to use the native version
Best Regards
Alistair Leslie-Hughes
Why do you need this?
If a program install msxml4 as part of it install process, it should use
the native
On 2/9/2010 11:50, Alistair Leslie-Hughes wrote:
Hi,
Changelog:
msxml4: Prefer to use the native version
Best Regards
Alistair Leslie-Hughes
Why do you need this?
19 matches
Mail list logo
