On Jan 12, 2015 12:56 AM, "Ken Sharp" <imwellcushtymelike@googlemail.com> wrote:
>
>
>
> On 11/01/15 11:16, Nikolay Sivov wrote:
>>
>> On 10.01.2015 21:27, Ken Sharp wrote:
>>>
>>> winecfg: Bring back 32-bit Windows versions for 64-bit WINEPREFIXES
>>>
>>> Having a 64-bit WINEPREFIX shouldn't exclude you from selecting 32-bit
>>> versions of Windows.
>>
>>
>> Yes, it should. There's no such thing as 64 bit win2k or winme.
>>
>
> And there's no such thing as 32-bit in Windows 2.0.

That would be 16 bit, but wine doesn't have a concept of 16 bit prefixes (and arguably doesn't need to).

> I shouldn't have to create separate WINEPREFIXES just so I can choose between 32-bit and 64-bit Windows versions for my applications.

Yes, you should. Each WINEPREFIX is an isolated environment. Just as you shouldn't expect a 64 bit application to work on 32 bit Windows.

> How is this going to be handled for ARM? Isn't 400 MB for a single WINEPREFIX enough?

I don't see how thIs matters or is relevant. Please clarify.

> Wine already handles 32-/64-bit, there's no need to deny users access to Windows 2000 just because they've installed Wine using the default settings on the 64-bit machines.

Again, yes there is. Win2k doesn't support 64 bit. It's a nonexistent platform, and allowing it would likely introduce unknown behavior in some applications.