<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SMIs Are EEEEVIL (Part 1)</title><link>http://blogs.msdn.com/b/carmencr/archive/2005/08/31/458609.aspx</link><description>As a quick introduction, SMIs were introduced to the x86 world by the 386SL. It was created to allowed systems designers to have access to the CPU while unspecified software of any type was running. The reasons for this are obvious when you look at the</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title> Dr HardwareBlog SMIs Are EEEEVIL Part 1 | home lighting</title><link>http://blogs.msdn.com/b/carmencr/archive/2005/08/31/458609.aspx#9779825</link><pubDate>Fri, 19 Jun 2009 08:45:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9779825</guid><dc:creator> Dr HardwareBlog SMIs Are EEEEVIL Part 1 | home lighting</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://homelightingconcept.info/story.php?id=805"&gt;http://homelightingconcept.info/story.php?id=805&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9779825" width="1" height="1"&gt;</description></item></channel></rss>