Linked by Thom Holwerda on Sat 29th Dec 2012 16:37 UTC
Permalink for comment 546689
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2006-12-05
I think you might be mixing UEFI, a modern BIOS replacement, with SecureBoot--Microsoft's purposely crippling UEFI-based technology that just happens to use UEFI as its vehicle and method of execution.
SecureBoot is not a required part of UEFI; it's just another feature that, theoretically, is supposed to be possible to be switched on and off at will (see: probably every single UEFI x86-based machine). It is a required part for OEMs to implement in order to pass the Windows Logo test and obtain official certification from Microsoft. Microsoft is the one requiring that it be enabled on all ARM systems with no way to disable, and therefore it is more of a Microsoft/Windows restriction than anything.
In the way it's being used, I would say that it does in fact have absolutely nothing to do with anything other than Windows, Microsoft's bottom line, and their desire to thwart competition without any real merits.
It's almost 2013 now, and apparently EULAs are no longer enough for these companies; they will stop at nothing to strictly enforce their plans it seems. First an agreement... now technical restrictions built into the hardware.
Edited 2012-12-31 00:04 UTC