Oops...I made a mistake, this is the patch.
So sorry :-(
From 4d2eac6fae9614a7f8c20eb3de02b77d85b20d03 Mon Sep 17 00:00:00 2001
From: Jactry Zeng
Date: Sat, 16 Feb 2013 11:35:41 +0800
Subject: Simplified Chinese translation for release 1.5.24
To: wine-patches
Reply-To: wine-devel
---
news/zh-c
I have investigated the following test failure on the new WineTestBot:
urlmon:
protocol.c:1051: Test failed: hrResult = 800401e4, expected:
protocol.c:1056: Test failed: dwError == ERROR_SUCCESS
protocol.c:613: Test failed: expected ReportData
The results from test.winehq.or
writes:
> I believe:
> - SEGPTR should be used everywhere the .spec says;
> - (DWORD_PTR) cast then becomes obsolete.
> Shall I submit a patch?
Yes, SEGPTR would be preferable.
> Furthermore, how to perform a 16bit NULL pointer check?
> waveInUnPrepareHeader16 uses:
> LPWAVEHDR
Hi,
I noticed some dubious differences among winmm16 functions. I believe
there should be none, but perhaps I'm missing some 16bit idiosyncrasies?
Please compare waveOutPrepareHeader16, Unprepare16 and waveOutWrite16:
http://source.winehq.org/source/dlls/mmsystem.dll16/mmsystem.c#L1287
UINT16 WI
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=24416
Your paranoid android
On 02/15/13 15:13, Marvin wrote:
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.
Good news! Thanks to Per Allansson, author of osslsigncode, we know
now that 98C090F33284468D64F30EE7B8C00894135D54C8 is sha1 of Root
Entry unique identifier 84 10 0c 00 00 00 00 00 c0 00 00 00 00 00 00
46.
--
Marc-André Lureau
Hello!
PE signing is already publicly documented by Microsoft, and we have an
open-source tool (osslsigncode) capable of signing PE and Cabinet. A
signed MSI dump easily reveals that the signature is under the
'\005DigitalSignature' stream, and it's a regular pkcs#7 signature,
whose content info t
writes:
> I've prepared a few patches to fix some of these. Generally, I don't know
> what to recommend. Use double floating point intermediates and loose 11 bits
> for the exponent but at least get the magnitude right?
In general there's no reason to use 64-bit at all, GetTickCount should
wor
Hi,
You believe that 64bit integers give you plenty of room and time to avoid
trouble like Y2k and Y2033, don't you?
The trouble is, these large data types make using other large numbers
more attractive than they used to be, e.g. counting time in 100
nanosecond units, representing one second as 1
Nozomi Kodama writes:
> Hello.
>
> I took advantage of this minor patch to clean up and make uniform the
> coding style of this file.
Please don't do that.
--
Alexandre Julliard
julli...@winehq.org
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=24408
Your paranoid android
On 15.02.2013 08:20, Nozomi Kodama wrote:
@@ -721,9 +739,10 @@ D3DXMATRIX* WINAPI D3DXMatrixTransformation(D3DXMATRIX
*pout, const D3DXVECTOR3
@@ -797,69 +821,70 @@ D3DXMATRIX* WINAPI D3DXMatrixTransformation2D(D3DXMATRIX
*pout, const D3DXVECTOR
Those two functions need a speed improvement. No
13 matches
Mail list logo
