Comments by "SmallSpoonBrigade" (@SmallSpoonBrigade) on "45 Year Old DOS on a New Intel CPU Without Emulation" video.

That's mostly because John Carmack was smart enough to not just assume that using the processor's ability to pump out frames would be a reasonable method of timing the game. There were other games during the early '90s that would run weirdly if there was too much processing power. I remember one of the King's Quest games, (I want to say IV) didn't have sound for me unless I dropped my Pentium from 75mhz to whatever it was with the turbo button in the right state.
7
@Great-Documentaries It's more complicated than that, there was a lot of cross licensing going on in the past, and Intel practically killed them off with antitrust violations more than once. Intel needs AMD in order to be able to duck out on antitrust enforcement. Far more than AMD needs Intel as now there's a lot of mobile processors by various other companies that are the most widely used ones in mobile devices to protect AMD against excessive antitrust scrutiny. So, Intel can fail and AMD wouldn't have to save them.
2
@warrax111 With good reason, most people couldn't play Doom if the FPS was too high, and a benchmark that is capped would be pretty useless once computers got past a certain point in terms of power.
2
@alerighi IIRC, as long as you were running the OS in 32bit mode, you still could run 16bit code, it's if you're running in 64bit mode that 16bit wasn't available. And, there's a fair amount of software that is 32bit, but depends upon 16bit installers to run at all.
1
@thecount25 Yes, although I'm not sure it's as critical now as it was when Intel tried to get people to switch to Itanium.
1
@michigandersea3485 Crafting the perfect config.sys and autoexec.bat was absolutely mandatory until really people started to move to Win 95 and that first MB of RAM didn't require all the babysitting.
1
They likely could eventually, they tried to do it with Itanium and that failed in large part due to AMD coming up with their AMD64 set that allowed the older X86 instructions to continue working even as new ones with 64bit support were added. It also didn't help that a lot of large corporations had a bunch of software that ran fine on the older processors that needed to be rewritten to handle the new processors. At this point, we're far enough away from those sorts of systems that some combination of emulation and wrappers could deal with whichever instructions are impacted by completely removing those if they want to.
1
Apart from some extremely out of date enterprise software, pretty much everybody else is using some form of DOSBox, DOS running in a VM or FreeDOS for this sort of thing. And even with the enterprise stuff, it probably would be better to be run in that fashion, but it can be a massive headache to make sure it works properly in the new environment and move it to the new set up. At which point, you might as well have just fixed the program to work with more modern OSes anyways.
1