https://bugs.winehq.org/show_bug.cgi?id=45753
Josh DuBois duboisj@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |duboisj@codeweavers.com
--- Comment #8 from Josh DuBois duboisj@codeweavers.com --- (In reply to Dmitry Timoshkov from comment #6)
(In reply to Rosanne DiMesio from comment #5)
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
I imagine you're right, but both the wineprefixes in question were set to XP and I did not change that. Forced upgrades did not come to Windows until Windows 10.
I'm afraid that using Wine implies the continues forced upgrade... Anyway, this needs a retest before throwing even more speculations, and the retest should be done with default Windows 7 configuration.
Is this really what Wine has always done, or what it should do? I would have hoped that an existing WinXP prefix would not receive a configuration change which would break a previously working prefix / application.
Is it simply too complicated to avoid (either in this case or in general)?