On Mon, Jan 12, 2015 at 9:38 AM, Rosanne DiMesio dimesio@earthlink.net wrote:
Do the developers really want to fix bugs caused by setting a 64 bit wineprefix to Windows 2.0?
No, but the prefix arch isn't my primary concern about this scenario.
I do not care about any bug caused by setting the Windows version to something earlier than the default when it isn't necessary. The distinction between "This doesn't work because you set your prefix to a Windows version that doesn't exist." and "This doesn't work because you set your prefix to a Windows version that no one uses anymore." isn't important to me.
If you're setting the Windows version globally to something very old, you should absolutely create a new prefix for it, even if your Wine build is 32-bit, because it will break anything modern you try to run. If you set it for a single .exe, that's probably comparable to windows' "compatibility mode" as described by Stefan, and the damage should be limited to a single app anyway.
I would be in favor of adding old versions back to winecfg at least when filtered to a specific .exe file, with no warnings around it.