You've never seen it run on a 286 or 386 AT processor.
No, but I have seen Win95 on a 386SX...

(not very useful, performance was horrible)
Also, windows actually contains a -huge- amount of legacy drivers (I think the current library is 100.000+), exactly so legacy compatibility shouldn't be a problem. Windows 8.1 still contain floppy drivers for example. I know of several IT departments that would have microsofts head, if they didn't support 10+ year old hardware. In fact you could argue that microsoft still supports the hardware, you just need to use the x86 version of 8.1. Which would likely be no great loss on such old hardware.
The other way round is more difficult, because there can be situations where you
need modern hardware to run ancient OS's (thank god for virtualization). F.x. if you have some critical hardware that for some reason don't have drivers for never then f.x. Win98 or software that relies on a specific windows version which you can't upgrade because you don't have access to the source code and the manufacturer has gone out of business...
The whole point is simply, that 8.1 is more of a service pack, then a full-on upgrade of 8. I don't think its OK for microsoft to arbitrarily change system requirements with what is more-or-less a glorified service pack. If we had been talking 8 vs 9, that's another matter.
my 2c... :whiste:
Its actually the other way around. MS's 64bit compiler emits the 3DNow! PREFETCH/PREFETCHW instructions because there were no EM64T CPUs at the time and MS found them useful. Cedar Mill NOPs them, but Prescott users are SOL.
Ah, so that's why. Good to know. :thumbsup: