Comment Re:And here I'm hoping... (Score 1) 681
You know, maybe if you'd quoted entire sentences, you wouldn't look like an idiot while trying to contradict me.
Just like how 32-bit-only versions of Windows - which describes every version from Windows 95 until XP 64-bit edition - can run 16-bit apps
Win9x had 16-bit pieces, but it required a 32-bit CPU. In the context of this entire thread, that defines it as a 32-bit-only OS. Everything NT6.2 (including XP x64) and forward has supported 64-bit or 32-bit installs, thus is *not* 32-bit-only.
You flunk reading comprehension or something?
Anyhow, anybody running software that old is going to already have a system set up for doing so; they aren't going to be Installing Win9 on those machines most likely anyhow. As for "companies generally load 32-bit OSes on their PCs..." I'll admit that my experience is limited to mostly the more tech-savvy companies out there, but as a consultant I've seen a *lot* of company's computers, and not one of them was running a 32-bit OS as their primary (there was one that still ran XP a year and change back, but it was 64-bit). Of course, I'm working with engineer and developer machines, so maybe that makes the difference. Anyhow, adding an extra thunking/compatibility layer for running 16-bit code on 64-bit OSes sounds logical from an engineering perspective, but it makes very little sense in terms of finances or developer time.