On 10 February 2010 09:11, David Gerard wrote:
> On 9 February 2010 18:16, David Laight wrote:
>
>> A 32bit (i386) windows application binary can only run in a 32bit
>> Unix application [1]. In which case the Unix kernel will handle the
>> system call emulation and ensure that the only user-spac
On 9 February 2010 18:16, David Laight wrote:
> A 32bit (i386) windows application binary can only run in a 32bit
> Unix application [1]. In which case the Unix kernel will handle the
> system call emulation and ensure that the only user-space virtual
> addresses the application sees are 32bit (
On Mon, Feb 08, 2010 at 11:27:07AM +0100, joerg-cyril.hoe...@t-systems.com
wrote:
> The wine64 challenge seems to let 32bit MS-windows apps work even
> though the UNIX side has to manage pointer addresses >2^32, i.e. above
> the lower 4GB address range. Is there some address translation
> involve
Andrey_Karpov wrote:
> All about 64-bit programming:
> http://www.viva64.com/articles/64-bit-development/ Articles ,
> http://www.viva64.com/links/64-bit-development/ Articles Reviews ,
> http://www.viva64.com/blog/en/tag/64-bits/ Blog .
To be honest it would be better to start with http://w
-implications-and-wine64-tp27497865p27510882.html
Sent from the Wine - Devel mailing list archive at Nabble.com.
If you look closely at the definitions of MCI_xyz_PARMS in MMSYSTEM.H,
you'll notice that (at least on 32bit systems), despite the different
types (DWORD, LPSTR, UINT) these structures are originally an array of
32bit values. This regular structure is essential, because the
MCI command parser h
joerg-cyril.hoe...@t-systems.com wrote:
> Hi,
>
> I've trouble understanding some of the 64bit issues. Lacking a 64bit
> machine, I'm left asking questions ;-)
>
> My understanding is that wine64 is the effort to make Wine work on
> 64bit UNIX systems, i.e. pointer size = 64bit, isn't it?
> DWORD
Hi,
I've trouble understanding some of the 64bit issues. Lacking a 64bit
machine, I'm left asking questions ;-)
My understanding is that wine64 is the effort to make Wine work on
64bit UNIX systems, i.e. pointer size = 64bit, isn't it?
DWORD_PTR is 64 bit wide on a wine64 system,
32 bit otherwise
