Impressive; now, if only we could trick them into considering "privacy" a core feature and add "backward compatibility" for it in newest Windows releases, we'd be golden.
Doesn't matter if they are Microsoft PMs that got this prioritized or nerdy gamers that originally surfaced this issue, or sympathetic programmers that created the "fix" in this form (hey lets just change the default behavior of the memory allocator/de-allocator/whatever)
I'm sure this straight up would not happen at Apple, today, for example. Challenge for the audience to surface counterexamples!
Ross wrote Sim City 2000 https://www.mobygames.com/developer/sheet/view/developerId,7...
The story is indeed about Sim City 2000. Funnily enough this bug is also present in DOS version of the game. Dude who hacked together "DOS32AWE - DOS/4G compatible DOS Extender with Sound Blaster AWEUTIL MIDI synthesizer support for Protected mode,VIASB" https://www.vogons.org/viewtopic.php?f=62&t=83065 rediscovered this independently.
It also manifests when trying to run Sim City 2000 using DOS32A instead of DOS/4GW https://www.vogons.org/viewtopic.php?t=24929
As a commenter over there suggested, you could always use "a modified executable from the Internet".
I'm similarly struggling to see the value in breaking old games because new versions exist.