3 ms·
Make that 1985 for windows 1.0 Can't find the site again, but someone figured out you can use an older version of the Borland resource editor to convert the em
by iforgotpassword 8y ago
Make that 1985 for windows 1.0
Can't find the site again, but someone figured out you can use an older version of the Borland resource editor to convert the embedded resources to a newer format, than patch the exe header to say it's a windows 2.0 binary and it will run even on windows 10 (32bit version only since of obviously needs the 16bit subsystem).
I was seriously impressed when I saw that.
- digi_owl 8y ago> 32bit version only since of obviously needs the 16bit subsystem And afaik, MS only retired the 16-bit subsystem because AMD64 can't switch between 64 and 16 bit modes. You can either run it in 16/32 or 32/64 modes, but not 16/32/64.
- userbinator 8y agoNot really: https://www.dkia.at/en/node/180 https://www.dkia.at/en/node/180 Interesting enough you can still mark a code segment as 16 Bit and the CPU will execute it in 16 Bit mode. https://www.wine-staging.com/news/2016-02-10-blog-wine-16bit.html https://www.wine-staging.com/news/2016-02-10-blog-wine-16bit... The tricky part is that a LDT entry also contains flags which define if a segment contains 16 bit, 32 bit or 64 bit code. If you change to a segment, the CPU will automatically start interpreting the code inside the segment according to this value. In other words, 16, 32, and 64-bit code can all coexist simultaneously and the CPU can switch between those automatically --- MS just decided not to implement it. Linux with WINE does, however.
- lmkg 8y agoThe following is a video of someone installing Doom II on DOS, upgrading the operating system in-place 11 times, and running Doom on Windows 7 (around 24 years of upgrades). https://www.youtube.com/watch?v=vPnehDhGa14 https://www.youtube.com/watch?v=vPnehDhGa14