On Sun, Dec 16, 2012 at 2:31 PM, Austin English wrote:
> --
> -Austin
Wrong macro, please ignore.
--
-Austin
Hello, Caron! GTX 660 and GTX 660 Ti are different cards, and 0x1183 is the
device code of GTX 660 Ti. You may view my patch:
http://source.winehq.org/patches/data/92545 .
Best regards!
Jiang Yike
> - Original Message -
> From: Caron Jensen
> Sent: 12/15/12 12:01 AM
> To: wine-patches
Stefan Leichter wrote:
> +BYTE buffer[MAX_PATH];
This should be WCHAR if you decided to test unicode version of the API
(although testing ANSI variant would be much easier), that will help
to avoid all those casts, and protect from insufficient buffer size.
Also please use a font that exist
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=23439
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=23440
Your paranoid android
Dont know what's happened, need to investigate further - Had 100% pass rate
in job 23438 only to fail on submission... Needs some investigation so will
work on it later in the week
Jason
On Fri, Dec 14, 2012 at 2:01 PM, Caron Jensen wrote:
> CARD_NVIDIA_GEFORCE_GT630M = 0x0de9,
> CARD_NVIDIA_GEFORCE_GT640M = 0x0fd2,
> CARD_NVIDIA_GEFORCE_GT650M = 0x0fd1,
> +CARD_NVIDIA_GEFORCE_GTX660 = 0X1183,
> CARD_NVIDIA_GEFORCE_GTX670 = 0x1189,
It seems that no matter what the Windows side program choose for
DirectSoundCreate, the DSound subsystem initialize itself with the higher
spec sound available (for example 48Khz Float32, or 48kHz Int16 if no
Float32 available).
While not a big deal on current linux PC, using this on ARM device ki
