Yes, it was a combination of a simple mistake and not compiling wine
again before issuing the make test.
I very much doubt it's a failing of wine, anyway I have posted the
patches in my other thread about xinput if you still think there's a
problem with wine.
Regards,
Andrew
On Sat, Oct 25, 2008
On Sat, Oct 25, 2008 at 8:10 AM, Alan Nisota <[EMAIL PROTECTED]> wrote:
> Very cool. Here is what I did:
> In linux (host):
> use shm_open and ftruncate to create a shared-memory region (this will be at
> /dev/shm/ in linux)
> use mmap to map that into memory
> create a socket to use as a semaphor
Eric Pouech wrote:
>
> A+
> ---
>
>
Eric:
Was this patch rejected or pending approval?
James McKenzie
Paul Vriens wrote:
> Hi,
>
> We were basically passing "C:" to SetCurrentDirectoryA and that doesn't
> work. Probably needs it's own test in kernel32 or so.
>
> Changelog
> Fix a test for systems with %TEMP% only one level deep
>
> -
2008/10/25 Stefan Dösinger <[EMAIL PROTECTED]>:
> The difference is (among others) that the first parameter is passed in the
> ECX register instead of the stack
>
No, that would be thiscall. The main difference between stdcall and
cdecl is who's responsible for popping arguments from the stack
(cal
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wine-devel-
> [EMAIL PROTECTED] On Behalf Of Andrew Fenn
> Sent: Saturday, October 25, 2008 6:43 PM
> To: Juan Lang
> Cc: wine-devel@winehq.org
> Subject: Re: DWORD help
>
> Thanks Juan. It's fixed now.
Are you sure? If the calling c
> > I have written the following but when I have dwUserIndex as 0,1,2,3
> or
> > any number, doesn't really matter, it always returns
> > ERROR_BAD_ARGUMENTS.
>
> Not sure why it's not returning ERROR_DEVICE_NOT_CONNECTED for you.
> I'll just point out:
Probably the calling convention is wrong. Us
Thanks Juan. It's fixed now.
On Sat, Oct 25, 2008 at 5:13 PM, Juan Lang <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
>> I have written the following but when I have dwUserIndex as 0,1,2,3 or
>> any number, doesn't really matter, it always returns
>> ERROR_BAD_ARGUMENTS.
>
> Not sure why it's not retu
Hi Andrew,
> I have written the following but when I have dwUserIndex as 0,1,2,3 or
> any number, doesn't really matter, it always returns
> ERROR_BAD_ARGUMENTS.
Not sure why it's not returning ERROR_DEVICE_NOT_CONNECTED for you.
I'll just point out:
> DWORD XInputGetState(DWORD dwUserIndex, XIN
I have written the following but when I have dwUserIndex as 0,1,2,3 or
any number, doesn't really matter, it always returns
ERROR_BAD_ARGUMENTS.
DWORD XInputGetState(DWORD dwUserIndex, XINPUT_STATE* pState)
{
FIXME("Stub - Controller: %d \n", dwUserIndex);
if (dwUserIndex >= 0 && dwUserIn
Dan Kegel wrote:
For starters, have you tried CreateFileMapping in wine, and
mmap on the same file in the native bit?
Sadly, linux does not use tmpfs by default, so the backing
store writes would probably hurt performance.
But it would be interesting to hear whether this worked at all.
Very
On the theory that having a really small subset of
wine would help me bring up the new patchwatcher
faster, I tried building just ntdll and its tests.
I had to bring in a few dependencies... but the killer
was wineboot. It brings in the kitchen sink.
So much for that dream!
I suppose a dummy wine
12 matches
Mail list logo
