"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> "However, disassembling NT implementation (WIN32K.SYS) reveals
> that."
> in
> http://source.winehq.org/source/windows/win.c#L845
>
> was introduced in to winehq by the following patch:
> http://cvs.winehq.com/cvsweb/wine/windows/win.c.diff?r1
Steven Edwards wrote:
Hello this line:
"However, disassembling NT implementation (WIN32K.SYS) reveals
that."
in
http://source.winehq.org/source/windows/win.c#L845
was introduced in to winehq by the following patch:
http://cvs.winehq.com/cvsweb/wine/windows/win.c.diff?r1=1.61&r2=1.62
Does th
This patch
http://cvs.winehq.org/patch.py?id=12495
seems to have broken the mingw build, currently getting
i386-mingw32msvc-gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -Wall -pipe -fno-strength-reduce -mpreferred-stack-boundary=2
-fno-strict-aliasing -gstabs+ -Wpoi
> "However, disassembling NT implementation (WIN32K.SYS) reveals
> that."
...
> Does this not violate a clean rooming the implementation? The ReactOS
> code is a derived work of the Wine code in the case and if soon then we
> have to remove it.
Whoa! Slow down there John Wayne! Disassembly
Hello this line:
"However, disassembling NT implementation (WIN32K.SYS) reveals
that."
in
http://source.winehq.org/source/windows/win.c#L845
was introduced in to winehq by the following patch:
http://cvs.winehq.com/cvsweb/wine/windows/win.c.diff?r1=1.61&r2=1.62
Does this not violate a cl
Alexandre Julliard wrote:
> Wililam <[EMAIL PROTECTED]> writes:
>
>> Here is the ChangeLog entry:
>>
>> * dlls/kernel/lcformat.c
>> William Lahti <[EMAIL PROTECTED]>
>>
>> - Implemented the EnumDateFormatsW function and vastly improved upon the
>> EnumDateFormatsA function.
>
> This stuff clea
It appears that Windows NT 4.0 doesn't support MAP_EXPAND_LIGATURES
as discussed in this link:
http://oss.software.ibm.com/pipermail/icu/2001-June/002975.html
That's why I get 65K errors and the huge file.
Dimitrie O. Paun wrote:
On Fri, May 28, 2004 at 07:42:54AM -0400, Robert Reif wrote:
It
On Sat, 2004-05-29 at 11:49 +0200, Rein Klazes wrote:
> Too late:
> http://cvs.winehq.org/patch.py?id=12478
Haha :) Golden rule of Wine hacking: before writing a patch, update!
OK, well at least we didn't duplicate anything hard
On Fri, 21 May 2004 12:58 am, Francois Gouget wrote:
> On Thu, 20 May 2004, Mike Hearn wrote:
> [...]
>
> > This is no longer true. According to a Red Hat kernel engineer, you can
> > use "setarch i386 wine " to switch it back to the 3/1 split while we
> > fix it in the Wine code.
>
> Don't we
On Fri May 28 23:42:14 BST 2004, you wrote:
> Mike Hearn <[EMAIL PROTECTED]>
> Print thread ID in 16-bit snoop traces in the noargs case
Too late:
http://cvs.winehq.org/patch.py?id=12478
Rein.
--
Rein Klazes
[EMAIL PROTECTED]
Am Freitag, 28. Mai 2004 23:59 schrieb Mike Hearn:
> On Fri, 28 May 2004 15:59:23 -0500, Alexandre Julliard wrote:
> > Log message:
> > Initial version of the Wine preloader, used to reserve memory
> > areas at startup. Based on the work of Mike McCormack.
>
[snip]
>
> If you observe any od
On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
> work again. It would even make more sense now that the dust
> settled. Have you perhaps got concrete ideas?
So here is what's left to do:
1. Finish the metadata-in-winetest patch
2. Arrange the reports on WineHQ
3. Maybe add
Chris Morgan <[EMAIL PROTECTED]> writes:
> the winetest results are sent back to winehq and can be
> accessed via http://test.winehq.org/data/ Pretty
> formatting of the results is coming soon ;-)
Do you mean somebody's already working on it or that I
should do it eventually? I'm back from the s
13 matches
Mail list logo
