<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for The Research Buff</title>
	<atom:link href="http://www.researchbuff.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.researchbuff.com</link>
	<description></description>
	<lastBuildDate>Mon, 31 May 2010 08:59:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on VIA M&#8217;Serv S2100*UPDATED by the_buff</title>
		<link>http://www.researchbuff.com/?p=392&#038;cpage=1#comment-88</link>
		<dc:creator>the_buff</dc:creator>
		<pubDate>Mon, 31 May 2010 08:59:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchbuff.com/?p=392#comment-88</guid>
		<description>I considered whether Exchange would be too much of a hog for the liitle M&#039;Serv, so the first thing I did was install a fresh copy of 2008 R2 and then Exchange 2010.  My experience with Exchange is &quot;limited,&quot; but it appeared to run just fine.  At an idle, it was using a little over 1 Gb of RAM.  

Once that appeared to work, I thought I would run the Hyper-V server manager as a base install that way I could play with different operating systems without having to redo the little guy everytime I got bored with the current build.  

I&#039;ll add my last email exchange with &quot;tech support&quot; at VIA soon.  Pure frustration.</description>
		<content:encoded><![CDATA[<p>I considered whether Exchange would be too much of a hog for the liitle M&#8217;Serv, so the first thing I did was install a fresh copy of 2008 R2 and then Exchange 2010.  My experience with Exchange is &#8220;limited,&#8221; but it appeared to run just fine.  At an idle, it was using a little over 1 Gb of RAM.  </p>
<p>Once that appeared to work, I thought I would run the Hyper-V server manager as a base install that way I could play with different operating systems without having to redo the little guy everytime I got bored with the current build.  </p>
<p>I&#8217;ll add my last email exchange with &#8220;tech support&#8221; at VIA soon.  Pure frustration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VIA M&#8217;Serv S2100*UPDATED by evi</title>
		<link>http://www.researchbuff.com/?p=392&#038;cpage=1#comment-87</link>
		<dc:creator>evi</dc:creator>
		<pubDate>Sun, 30 May 2010 17:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchbuff.com/?p=392#comment-87</guid>
		<description>Virtualization probably isn&#039;t a good idea on this little box with just one core and 3 Gb RAM. Exchange is a resource hog it would be interesting to see if it runs native.</description>
		<content:encoded><![CDATA[<p>Virtualization probably isn&#8217;t a good idea on this little box with just one core and 3 Gb RAM. Exchange is a resource hog it would be interesting to see if it runs native.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VIA M&#8217;Serv S2100*UPDATED by evi</title>
		<link>http://www.researchbuff.com/?p=392&#038;cpage=1#comment-86</link>
		<dc:creator>evi</dc:creator>
		<pubDate>Sun, 30 May 2010 15:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.researchbuff.com/?p=392#comment-86</guid>
		<description>Hi, 

I have the same issues with the M&#039;Serv S2100 running Windows 2008 R2. The BIOS only recognizes 3 Gb(!) and Windows shows 2.97 Gb RAM is available with 4 Gb installed.

Hyper-V installation succeeds but I am unable to start a VM; I keep getting the following error:

[Window Title]
Virtual Machine Connection

[Main Instruction]
The application encountered an error while attempting to change the state of &#039;WinVM&#039;.

[Content]
&#039;WinVM&#039; could not initialize.

Failed to create partition: Unspecified error (0x80004005)

[Expanded Information]
&#039;WinVM&#039; could not initialize. (Virtual machine ID 0EF6BDEE-6095-41FB-95C8-EEAA24C5F5AB)

Failed to create partition: Unspecified error (0x80004005)

I share your frustration in that there is almost no documentation and no information available.</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>I have the same issues with the M&#8217;Serv S2100 running Windows 2008 R2. The BIOS only recognizes 3 Gb(!) and Windows shows 2.97 Gb RAM is available with 4 Gb installed.</p>
<p>Hyper-V installation succeeds but I am unable to start a VM; I keep getting the following error:</p>
<p>[Window Title]<br />
Virtual Machine Connection</p>
<p>[Main Instruction]<br />
The application encountered an error while attempting to change the state of &#8216;WinVM&#8217;.</p>
<p>[Content]<br />
&#8216;WinVM&#8217; could not initialize.</p>
<p>Failed to create partition: Unspecified error (0&#215;80004005)</p>
<p>[Expanded Information]<br />
&#8216;WinVM&#8217; could not initialize. (Virtual machine ID 0EF6BDEE-6095-41FB-95C8-EEAA24C5F5AB)</p>
<p>Failed to create partition: Unspecified error (0&#215;80004005)</p>
<p>I share your frustration in that there is almost no documentation and no information available.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
