2 ms·
>If the code was old, as it’s been when products like Symantec’s were leaked, this might not be so bad - but it’s not. >http://adamcaudill.com/files/Screenshot
by KwanEsq 14y ago
>If the code was old, as it’s been when products like Symantec’s were leaked, this might not be so bad - but it’s not.
>http://adamcaudill.com/files/Screenshot_4_4_13_10_04_PM.png http://adamcaudill.com/files/Screenshot_4_4_13_10_04_PM.png
>References in the files indicate that the code is from sometime in February - so this is current code.
Given that that image shows dates in 2012, I think the author has made the classic mistake many of us make at the start of the new year, of still thinking it's the old one.
- miahi 14y agoFor firmware, 2012 is actually very new. I don't think manufacturers change the versions too often, even on firmware updates - they usually maintain/patch the original firmware (the version that was used when the hardware launched). A motherboard released in 2012 probably has an older version of firmware than the leaked one.
- mjg59 14y agoMicrosoft's requirements for Windows 8 certified firmware continued changing until surprisingly far through 2012. Code from early 2012 wouldn't satisfy it.