| 1 |
On Thu, Jul 19, 2012 at 8:55 AM, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 2 |
> On 18/07/12 00:14, Alecks Gates wrote: |
| 3 |
>> |
| 4 |
>> On Tue, Jul 17, 2012 at 3:57 PM, Nikos Chantziaras <realnc@×××××.com> |
| 5 |
>> wrote: |
| 6 |
>>> |
| 7 |
>>> 64-bit Wine cannot run 32-bit Windows applications. You need a 32-bit |
| 8 |
>>> Wine |
| 9 |
>>> for that. And since in 99.9% of Windows software is 32-bit... well, you |
| 10 |
>>> get |
| 11 |
>>> the point :-) |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>> Sure, but 64-bit wine can run either a win32 or a win64 config, and |
| 15 |
>> you have to enable win64 with the "win64" USE flag. I believe this |
| 16 |
>> makes the win64 config default and you have to set WINEARCH=win32 if |
| 17 |
>> you want only 32-bit. |
| 18 |
> |
| 19 |
> |
| 20 |
> Interesting that Wine aims to do the WOW64 thing. That's certainly news to |
| 21 |
> me :-) |
| 22 |
|
| 23 |
Not really surprising. There's an IsWow64Process() in the Windows API |
| 24 |
to allow processes to detect the nature of the environment they're |
| 25 |
running on, since sometimes that's something you need to know. :) |
| 26 |
|
| 27 |
-- |
| 28 |
:wq |
Archives