<?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>New Spec Under OSP - Windows Management Interface to Viridian - Hypercall API</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api.aspx</link><description>Warning, geek-central posting: A year ago Microsoft moved the Virtual Hard Disk format under the Open Specification Promise. (Funny...another data format...hmmm...but I digress) The point of that announcement was to enable anyone interested in looking</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; New Spec Under OSP - Windows Management Interface to Viridian - Hypercall API</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api.aspx#5788655</link><pubDate>Wed, 31 Oct 2007 03:55:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5788655</guid><dc:creator>MSDN Blog Postings  » New Spec Under OSP - Windows Management Interface to Viridian - Hypercall API</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api/"&gt;http://msdnrss.thecoderblogs.com/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>94files  &amp;raquo; Blog Archive   &amp;raquo; New Spec Under OSP - Windows Management Interface to Viridian &amp;#8230;</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api.aspx#5797657</link><pubDate>Wed, 31 Oct 2007 15:12:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5797657</guid><dc:creator>94files  » Blog Archive   » New Spec Under OSP - Windows Management Interface to Viridian …</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://94files.cn/?p=2304"&gt;http://94files.cn/?p=2304&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Interesting Finds: October 31, 2007</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api.aspx#5798900</link><pubDate>Wed, 31 Oct 2007 17:04:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5798900</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>re: New Spec Under OSP - Windows Management Interface to Viridian - Hypercall API</title><link>http://blogs.msdn.com/jasonmatusow/archive/2007/10/30/new-spec-under-osp-windows-management-interface-to-viridian-hypercall-api.aspx#5945388</link><pubDate>Wed, 07 Nov 2007 01:20:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5945388</guid><dc:creator>Dave S.</dc:creator><description>&lt;p&gt;The Office product documentation license said the license was void if the licensee sued Microsoft. I take it that means that MS could use any licensee's patents without recourse by the licensee, except to give up whatever MS IP the licensee had used. This effective means a forfeit of license rights to MS in exchange for the aggreement not to sue. &lt;/p&gt;
&lt;p&gt;Is the VHD license under the same terms? &lt;/p&gt;</description></item></channel></rss>