1 |
On Tue, Jul 17, 2012 at 3:57 PM, Nikos Chantziaras <realnc@×××××.com> wrote: |
2 |
> On 17/07/12 19:43, Alecks Gates wrote: |
3 |
>> |
4 |
>> On Jul 17, 2012 11:32 AM, "Volker Armin Hemmann" |
5 |
>> <volkerarmin@××××××××××.com <mailto:volkerarmin@××××××××××.com>> wrote: |
6 |
>> *snip* |
7 |
>> > The only use case that might come up is wine - I don't know anything |
8 |
>> about |
9 |
>> > that beast. Haven't had any use for it in years. |
10 |
>> > |
11 |
>> > -- |
12 |
>> > #163933 |
13 |
>> > |
14 |
>> I use wine daily on 64 bit with no problems. |
15 |
> |
16 |
> |
17 |
> 64-bit Wine cannot run 32-bit Windows applications. You need a 32-bit Wine |
18 |
> for that. And since in 99.9% of Windows software is 32-bit... well, you get |
19 |
> the point :-) |
20 |
> |
21 |
> |
22 |
Sure, but 64-bit wine can run either a win32 or a win64 config, and |
23 |
you have to enable win64 with the "win64" USE flag. I believe this |
24 |
makes the win64 config default and you have to set WINEARCH=win32 if |
25 |
you want only 32-bit. |
26 |
|
27 |
According to the winehq docs[1] the WINEARCH environment variable |
28 |
"Specifies the Windows architecture to support. It can be set either |
29 |
to win32 (support only 32-bit applications), or to win64 (support both |
30 |
64-bit applications and 32-bit ones in WoW64 mode). The architecture |
31 |
supported by a given Wine prefix is set at prefix creation time and |
32 |
cannot be changed afterwards. When running with an existing prefix, |
33 |
Wine will refuse to start if WINEARCH doesn't match the prefix |
34 |
architecture." It is meant to be able to run both 64-bit and 32-bit |
35 |
applications, but I think it's a bit buggy -- I've had some trouble |
36 |
installing microsoft visual c++ runtimes due to running a win64 |
37 |
config, but I could have been doing it wrong. |
38 |
|
39 |
[1] http://www.winehq.org/docs/wineusr-guide/x258 |