On Wed, Mar 3, 2010 at 1:59 PM, Ken Thomases wrote:
> On Mar 3, 2010, at 12:12 PM, Austin English wrote:
>
>> The main question I have though, is that I can't get winetest to run
>> there. When I run ./wine winetest or ./wine winetest-latest.exe,
>> winetest begins to load, then bails out, saying
Hey guys, would you stop spamming wine-patches? Please never replay to
wine-patches.
Vitaliy.
> Converting the wpkg scripts to appinstall doesn't
> seem like that difficult of a task, mostly just time consuming.
It's harder than it sounds to actually get
a few useful app tests written. Plus there'll
be some work writing up and fixing the bugs
it uncovers.
> That is why I thinking working
Hey folks,
before Maarten goes and implements wine audio
on top of OpenAL, does anyone know of a nice
automated tool for measuring audio latency
that works on multiple APIs? i.e. it'd be cool
if one could plug in a loopback cable,
run an app once, and get a report of the
round trip audio latency w
> + at pwd@
Shouldn't that be "@pwd@" ?
Wouldn't it be easier to pass -1 for the length?
On 8 March 2010 22:25, Yann Droneaud wrote:
> While trying to debug cmd.exe, valgrind found some problem in
> CompareString() calls. Those tests help me to understand how
> CompareString() is excepted to be called:
> when string length is given NUL characters are ignored in this string.
>
I think
Am 08.03.2010 um 22:51 schrieb Ben Klein:
>> Some cards are sold with "enabled special feature X in game Y". The game
>> then looks at the card ID to allow additional configuration options. An
>> example for this is Age of Empires 3 which allows the highest graphics
>> options only for some Gef
On Mon, Mar 8, 2010 at 10:40 PM, Stefan Dösinger wrote:
>
> Am 08.03.2010 um 14:21 schrieb Roderick Colenbrander:
>
>> Hi Luke,
>>
>> We don't want to have all possible GPU models in (there are so many
>> different models). It only gives a hint to apps (yes the proper amount
>> of video memory is
Hi,
If you never run winetest you can skip this email but shame on you ;)
It turns out that one of the advapi32 tests messes up the registry, or
to be more correct doesn't restore an original value. This bug has been
present since the introduction of these specific tests in 2004.
This means
> Is the patch missing some files?
Damn, yes. I thought "git am" would be clever enough to handle that,
but apparently not. Thanks.
--Juan
On 8 March 2010 22:36, Juan Lang wrote:
> Uses implementation from Aaron Gifford,
> http://www.aarongifford.com/computers/sha.html (It's BSD licensed.)
>
Is the patch missing some files?
On Mon, Mar 8, 2010 at 10:41 PM, Stefan Dösinger wrote:
>
> Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
>
>> Hi,
>>
>> Multiple times a day you encounter people who can't get 3D working in
>> Wine. I'm getting so sick of these questions, that I decided to start
>> a new page on the Wiki.
On 9 March 2010 08:40, Stefan Dösinger wrote:
>
> Am 08.03.2010 um 14:21 schrieb Roderick Colenbrander:
>
>> Hi Luke,
>>
>> We don't want to have all possible GPU models in (there are so many
>> different models). It only gives a hint to apps (yes the proper amount
>> of video memory is more serio
Am 08.03.2010 um 13:23 schrieb Roderick Colenbrander:
> Hi,
>
> Multiple times a day you encounter people who can't get 3D working in
> Wine. I'm getting so sick of these questions, that I decided to start
> a new page on the Wiki.
> http://wiki.winehq.org/3DDriverIssues
>
> Feel free to add mo
Am 08.03.2010 um 14:21 schrieb Roderick Colenbrander:
> Hi Luke,
>
> We don't want to have all possible GPU models in (there are so many
> different models). It only gives a hint to apps (yes the proper amount
> of video memory is more serious) but this should be fixed in a
> different way I thi
On Fri, Feb 26, 2010 at 11:31 AM, Erich Hoover wrote:
> I was looking into updating the AppDB with more recent results for PCB
> Artist* and discovered that on a fresh Wine install that the application
> opens and creates new files incredibly slowly (it now takes 23 minutes vs.
> old performance
+ expected = 33; sprintf(fileA, testfile, tmpdir);
+ rc=shell_execute(NULL, fileA, NULL, NULL);
+ todo_wine {
+ ok(rc==expected || (rc>32&& expected>32),
+ "expected %s (%d), got %s (%d), lpFile: %s \n",
+ expected==33 ? "success"
PV> On 03/08/2010 05:42 PM, Juan Lang wrote:
>> Hi Ilya,
>> I like this one rather better, thanks. Especially the use of broken()
>> makes it clearer what's happening.
>>
>> I think you could tidy it up just a little more:
>>
>>> +expected = 33; sprintf(fileA, testfile, tmpdir);
>>> +rc=sh
On 03/08/2010 05:40 PM, Ilya Basin wrote:
JL> Also, those TEST_LPFILE_PARSED_OK macros are ugly, and hard to fix if
JL> one place has a certain behavior, while another has different
JL> behavior. Just use ok directly wherever you're using the macro.
Not convinced. What you say is good for
On 03/08/2010 05:42 PM, Juan Lang wrote:
Hi Ilya,
I like this one rather better, thanks. Especially the use of broken()
makes it clearer what's happening.
I think you could tidy it up just a little more:
+expected = 33; sprintf(fileA, testfile, tmpdir);
+rc=shell_execute(NULL, fileA,
Hi Ilya,
I like this one rather better, thanks. Especially the use of broken()
makes it clearer what's happening.
I think you could tidy it up just a little more:
> + expected = 33; sprintf(fileA, testfile, tmpdir);
> + rc=shell_execute(NULL, fileA, NULL, NULL);
> + todo_wine {
> +
>> JL> Also, those TEST_LPFILE_PARSED_OK macros are ugly, and hard to fix if
>> JL> one place has a certain behavior, while another has different
>> JL> behavior. Just use ok directly wherever you're using the macro.
>> Not convinced. What you say is good for reading, but not editing.
>> If som
On 03/06/2010 07:00 PM, Ilya Basin wrote:
JL> Also, those TEST_LPFILE_PARSED_OK macros are ugly, and hard to fix if
JL> one place has a certain behavior, while another has different
JL> behavior. Just use ok directly wherever you're using the macro.
Not convinced. What you say is good for rea
Hi Luke,
We don't want to have all possible GPU models in (there are so many
different models). It only gives a hint to apps (yes the proper amount
of video memory is more serious) but this should be fixed in a
different way I think e.g. nv-control. I think I might look into that
again soon.
Rode
Hi,
Multiple times a day you encounter people who can't get 3D working in
Wine. I'm getting so sick of these questions, that I decided to start
a new page on the Wiki.
http://wiki.winehq.org/3DDriverIssues
Feel free to add more information to it. I don't want it to give
detailed instructions on h
On 03/07/2010 09:46 PM, Eric Ho wrote:
--- a/programs/cmd/tests/test_builtins.cmd.exp
+++ b/programs/cmd/tests/test_builtins.cmd.exp
@@ -24,3 +24,9 @@ Testing case sensitivity with and without /i option
if seems to default to case sensitivity
if /i seems to work
if /I seems to work
+---
27 matches
Mail list logo
