3 ms·

It's wonderful that code written for Windows 3.1 still works well today

• simonblack 5y ago
  Certainly, if you want to jump through quite a few hoops, that is. Every now and then I find a bit of old software that I hope might work on Windows, only to find That it's not permitted to work, or some weird and wonderful library is missing and therefore the program won't work. I have been known to set up a VM with an earlier version of Windows to run a specific program, temporarily. I'm not blaming Windows alone here, I'm blaming "old" software and old libraries(DLLs). I've had similar problems with Linux/UNIX.
  • phendrenad2 5y ago
    Really? I've had the opposite experience. Every piece of old Windows software (except games) I've tried to use runs perfectly on Windows 10. Not sure why games are the exception. I assume that game development back then was like it is today - hacky and shoddy work - which uses shortcuts and generally uses the win32 API wrongly.
    • mikewarot 5y ago
      To get performance out of the hardware back in the day, you had to use every undocumented trick in the book, and do a lot of direct hardware access. The actual win32 calls probably work just fine, but the ancient hardware isn't there for screen I/O to function properly.