Posts by stupid-frakking-handle 17 publicly visible posts • joined 10 Oct 2011
Given that MS has not implemented any runtime checks on the HW compatability stuff (checks only happen during install), I suspect they have a contingency plan to drop these requirements sometime between now and the EOL date for Win10. Much less of a reputational risk for them to have Win11 with some features not fully enabled than a millions of unpatched Win 10 systems.
These days MS only makes money on Desktop OS when the customer buys a new licence, usually in the form of a new PC. I haven't paid to upgrade a Windows license on existing hardware for at least a decade, so uses not upgrading existing machines because of hardware limitations doesn't cost Microsoft a penny.
I suspect that many companies faced ith EOS for Win10 on old hardware may decide that bypassing the install checks (which is trivial to do) and updating Win10 systems to Win11 is something they'll seriously consider. After all, an unsupported system running Win 11 and getting security updates is definitely less of a risk than a Win10 system not getting updates on the same hardware. I've just recently updated a 2012-era Core i3 system to Win 11 with no issues.
I suspect some of the slowness is due to the underlying architecture of NT on RISC-CPUs. At that time NT's paging code had been optimized for the Paged-memory management found in MIPS processors. So, if you wanted to run NT on a RISC CPU that wasn't MIPS, you either had to completely redesign the memory management, or you had to emulate the paging approach used on MIPS CPUs which caused problems for other platforms. I was peripherally (so to speak) involved in the PowerPC and Intergraph CLIPPER ports of NT (I knew the engineers at Intergraph who actually did all the hard work) so I have some inside information ;-)
Immutability of the storage with Veeam is a function of the storage you use, lots of customers don't use a storage system capable of making backups immutable. Similarly, unless something has changed in a recent release, 4-eyes change management is optional and you have to enable it. For large enterprise customers, these features may work, for SMB customers who can't spell immutable and think 4-eyes is about wearing glasses this NOT TRUE, and Veeam should make that clear.
So Windows 11 won't run at all on pre-Nehalem CPUs that are the best part of 16 years old. First from a historical perspective, that would be the equivalent of WIndows 7 (current when Nehalem arrived) not running on 486-era PCs which would have seemed quite reasonable at the time (and probably true, though I can't remember.) Second, how many pre-Nehalem era PCs are still around, I bet it's a tiny, tiny fraction of the PC install base, and an even smaller fraction of that would be people wanting to run Win11 on those boxes.
The remarkable thing here is that Win11 ever ran on hardware that old and it's a testament to the backward compatability of x86 architecture and Win11.
Apparently there is a possibility that the logger has been deliberately installed by the US government, presumably on a need to know basis with the local admins left out of the loop...
http://techzwn.com/2011/10/predator-drone-virus-could-be-internal-monitoring-system-analyst/
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
