3 ms·
> my trusty engineering software wouldn't install on Windows 8 or 10 due to some of Microsoft's many backwards-incompatibilities. I have seen nearly no softwar
by alkonaut 10y ago
> my trusty engineering software wouldn't install on Windows 8 or 10 due to some of Microsoft's many backwards-incompatibilities.
I have seen nearly no software that doesn't work in a backwards compatible way on windows. Tha's the thing microsoft does best of all.
What was it that became incompatible with Win8 that meant a piece of software that installed on Win7 now wouldn't install?
The last app that stopped working for me was some 16bit vb apps I had but those run just fine in a virtual 32bit XP I can fire up (and in the "xp mode" when that was availble).
- vertex-four 10y agoIt tends to happen with really poorly written niche industry-specific software that Microsoft don't realise exists, so can't test.
- alkonaut 10y agoYes, I'm in exactly that situation (making industry specific windows desktop software) so I'm very interested in hearing about the specific issues here. Obviously any developer can screw up and do thigs like "if !winVersion.StartsWith(...)" and there is not much microsoft can do about that, apart from naming windows 9 windows 10... But even broken and buggy API's tend to be maintained by microsoft just because they can't test all the software floating around that depends on it. So it's usually very very hard to accidentally make a program run on Windows version N but not on Windows Version N+1
- coldpie 10y agoThere's one game that depends on winmm callbacks being called on a separate thread because the game actually calls SuspendThread() from within the callback! During the mmdevapi move around Vista/7, MS switched to calling the callbacks from the application thread and the game now deadlocks. It does work in compatibility mode, though. https://bugs.winehq.org/show_bug.cgi?id=3930#c71 https://bugs.winehq.org/show_bug.cgi?id=3930#c71
- vertex-four 10y agoOccasionally, bugs get fixed despite programs depending on those bugs. They do not guarantee complete bug-compatibility between releases, or even within the same release - to do so would imply they could never fix a bug without writing a new function for the bugfix and persuading all developers to use the new function and release an update, then convincing everyone to use the updated software, even when there's no known software which depended on the buggy function's behaviour. It used to be that when Microsoft found that a specific program was getting in the way of a bugfix, they'd detect the program and perform the buggy behaviour, or they'd patch the software on-the-fly. I have no idea if they still do this.
- alkonaut 10y agoDon't forget that they can also modify any API in a way that fixes the bug but also behaves in the legacy way under "compatibility mode".
- thehardsphere 10y agoWine sometimes has additional backwards compatibility issues because they don't implement some of the bugs in previous versions of Windows that people write their application code around. I think the most notable example of this was some time zone handling bug in The Sims 3, that made that game unplayable with Wine if you were in certain time zones. The problem was that Windows XP didn't actually report DST information correctly to the version of Mono embedded in it, and the Mono devs dealt with it by basically not validating the value returned from XP. So Mono would crash when it got correct time zone information from Wine and from later versions of Windows, thus crashing Sims 3. Looking at their bugzilla for the issue, it seems as if someone went through and deleted old comments. There were many whiners demanding that Wine fix something that they didn't break. https://bugs.winehq.org/show_bug.cgi?id=18991#c43 https://bugs.winehq.org/show_bug.cgi?id=18991#c43
- ooqr 10y agoI feel like software engineers get access to an odd, exclusive source of humor in things like these.
- kozak 10y agoDirect3D Retained Mode was removed with no backward compatibility option: https://support.microsoft.com/en-us/help/969150/direct3d-retained-mode-removed-from-windows-vista https://support.microsoft.com/en-us/help/969150/direct3d-ret...