| |||||||||||||
Garrett: Secure Boot and Restricted BootGarrett: Secure Boot and Restricted BootPosted Mar 27, 2013 23:26 UTC (Wed) by s0f4r (subscriber, #52284)In reply to: Garrett: Secure Boot and Restricted Boot by tshow Parent article: Garrett: Secure Boot and Restricted Boot There *will* be bugs in these systems, and some of them *will* slip by QA and Microsoft's certification process even if everyone involved is being both diligent and fair. Bugs happen. They *always* happen, in software, in microcode, in firmware and in hardware. The only question is whether the incentives are in place to convince the manufacturer to fix the problems when they arise. Microsofts certification is extremely rigorous, and the second line is already answered: vendors would not get certified, which means they lose the right to display logos and so on, which is IMHO a huge incentive - that is actually what the hardware vendors want - the "sticker". I do not doubt that Microsoft will take any vendor to court if it is caught illegally displaying the logo.
(Log in to post comments)
Garrett: Secure Boot and Restricted Boot Posted Mar 27, 2013 23:56 UTC (Wed) by tshow (subscriber, #6411) [Link]
> Microsofts certification is extremely rigorous, and the second line is already answered: vendors would not get certified, which means they lose the right to display logos and so on, which is IMHO a huge incentive - that is actually what the hardware vendors want - the "sticker". I do not doubt that Microsoft will take any vendor to court if it is caught illegally displaying the logo.
Right. Which is why WHQL and "Microsoft Hardware" are bywords for quality.
Google "RROD".
|
|||||||||||||