<?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 on: Windows Home Server Users: Avoid Latest ForceWare Drivers</title>
	<atom:link href="http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html</link>
	<description>Wireless consumer advocate Christopher Price tackles the rest of tech.</description>
	<lastBuildDate>Sat, 13 Mar 2010 05:06:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yak</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-4782</link>
		<dc:creator>Yak</dc:creator>
		<pubDate>Mon, 02 Feb 2009 19:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-4782</guid>
		<description>The first two links in my previous post that don’t appear to work are properly linked to from in the wegotserved forum post.

Alternatively if you use the search term

brad rutkowski + rdpdd.dll failed to load

in google it is the first link found. In Brad’s Server 2003 blog post there is a link to the nVidia post.</description>
		<content:encoded><![CDATA[<p>The first two links in my previous post that don’t appear to work are properly linked to from in the wegotserved forum post.</p>
<p>Alternatively if you use the search term</p>
<p>brad rutkowski + rdpdd.dll failed to load</p>
<p>in google it is the first link found. In Brad’s Server 2003 blog post there is a link to the nVidia post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yak</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-4781</link>
		<dc:creator>Yak</dc:creator>
		<pubDate>Mon, 02 Feb 2009 19:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-4781</guid>
		<description>I also had the same problems following the Jan 09 WHS updates.

I found a work around using a registry entry from here that should hopefully work for older nVidia cards that can&#039;t use the latest nVidia drivers;

http://blogs.technet.com/brad_rutkowski/ar…ed-to-load.aspx

http://forums.nvidia.com/index.php?showtop…sktop&amp;st=60

Incidentally, when I removed the registry edit and upgraded my nVidia drivers to the latest version, the registry modification also appeared on my WHS.

Have documented more fully the steps I took here

http://forum.wegotserved.co.uk/index.php?showtopic=6162</description>
		<content:encoded><![CDATA[<p>I also had the same problems following the Jan 09 WHS updates.</p>
<p>I found a work around using a registry entry from here that should hopefully work for older nVidia cards that can&#8217;t use the latest nVidia drivers;</p>
<p><a href="http://blogs.technet.com/brad_rutkowski/ar…ed-to-load.aspx" rel="nofollow">http://blogs.technet.com/brad_rutkowski/ar…ed-to-load.aspx</a></p>
<p><a href="http://forums.nvidia.com/index.php?showtop…sktop&amp;st=60" rel="nofollow">http://forums.nvidia.com/index.php?showtop…sktop&amp;st=60</a></p>
<p>Incidentally, when I removed the registry edit and upgraded my nVidia drivers to the latest version, the registry modification also appeared on my WHS.</p>
<p>Have documented more fully the steps I took here</p>
<p><a href="http://forum.wegotserved.co.uk/index.php?showtopic=6162" rel="nofollow">http://forum.wegotserved.co.uk/index.php?showtopic=6162</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liveblogging Windows Home Server: Death &#38; Rebirth &#124; Christopher Price .net</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-3993</link>
		<dc:creator>Liveblogging Windows Home Server: Death &#38; Rebirth &#124; Christopher Price .net</dc:creator>
		<pubDate>Thu, 04 Dec 2008 05:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-3993</guid>
		<description>[...] Wednesday, I was doing some regressive bug testing for Microsoft on a Windows Home Server (WHS) bug. When I flipped the power switch on my power supply, the power supply exploded&#8230; literally. [...]</description>
		<content:encoded><![CDATA[<p>[...] Wednesday, I was doing some regressive bug testing for Microsoft on a Windows Home Server (WHS) bug. When I flipped the power switch on my power supply, the power supply exploded&#8230; literally. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Ankstrum</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-3954</link>
		<dc:creator>Bill Ankstrum</dc:creator>
		<pubDate>Wed, 26 Nov 2008 13:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-3954</guid>
		<description>Oh man, that&#039;s terrible!  Wishing you the best on your system recovery.
  
I uninstalled the nvidia graphics drivers and was able to log in via Remote Desktop. However, now the connector software can&#039;t see the home server.  Man, this is a mess.</description>
		<content:encoded><![CDATA[<p>Oh man, that&#8217;s terrible!  Wishing you the best on your system recovery.</p>
<p>I uninstalled the nvidia graphics drivers and was able to log in via Remote Desktop. However, now the connector software can&#8217;t see the home server.  Man, this is a mess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Price</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-3953</link>
		<dc:creator>Christopher Price</dc:creator>
		<pubDate>Wed, 26 Nov 2008 12:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-3953</guid>
		<description>Well, you can forget about an update any time soon. I plugged my Home Server back in, and the PSU exploded on power-up. And, that&#039;s not getting fixed until after Thanksgiving weekend...</description>
		<content:encoded><![CDATA[<p>Well, you can forget about an update any time soon. I plugged my Home Server back in, and the PSU exploded on power-up. And, that&#8217;s not getting fixed until after Thanksgiving weekend&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Price</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-3949</link>
		<dc:creator>Christopher Price</dc:creator>
		<pubDate>Tue, 25 Nov 2008 19:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-3949</guid>
		<description>At this point, the only resolution I can give is to do a Server Reinstall. Then, do not install 178.24 or any version of ForceWare higher than that.

I would suggest using NVIDIA (or LaptopVideo2Go) driver archives to track down an older version.

But, my personal fix is a lot easier... I just removed my GeForce 6200, and went back to my Intel i865 integrated graphics. Actually, I haven&#039;t tested to see if that fixes the problem on its own... you may still need to do a Server Reinstall.

Edit: Some have suggested reverting to older driver versions does indeed work. I&#039;ll check it out and update, hopefully later tonight.</description>
		<content:encoded><![CDATA[<p>At this point, the only resolution I can give is to do a Server Reinstall. Then, do not install 178.24 or any version of ForceWare higher than that.</p>
<p>I would suggest using NVIDIA (or LaptopVideo2Go) driver archives to track down an older version.</p>
<p>But, my personal fix is a lot easier&#8230; I just removed my GeForce 6200, and went back to my Intel i865 integrated graphics. Actually, I haven&#8217;t tested to see if that fixes the problem on its own&#8230; you may still need to do a Server Reinstall.</p>
<p>Edit: Some have suggested reverting to older driver versions does indeed work. I&#8217;ll check it out and update, hopefully later tonight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Ankstrum</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-3939</link>
		<dc:creator>Bill Ankstrum</dc:creator>
		<pubDate>Tue, 25 Nov 2008 00:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-3939</guid>
		<description>Oh man.  I have been experiencing this since October!  It hadn&#039;t even occured to me that it could be a graphics driver issue.  Wow.  Any resolution to this issue?</description>
		<content:encoded><![CDATA[<p>Oh man.  I have been experiencing this since October!  It hadn&#8217;t even occured to me that it could be a graphics driver issue.  Wow.  Any resolution to this issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nvidia Driver Issue with Windows Home Server &#171; MS Windows Home Server</title>
		<link>http://www.christopherprice.net/windows-home-server-owners-avoid-latest-forceware-drivers-701.html/comment-page-1#comment-3938</link>
		<dc:creator>Nvidia Driver Issue with Windows Home Server &#171; MS Windows Home Server</dc:creator>
		<pubDate>Mon, 24 Nov 2008 18:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.christopherprice.net/?p=701#comment-3938</guid>
		<description>[...] release has no mention of a compatibility issue in their release notes, although fellow enthusiast Christopher Price and myself have experienced this [...]</description>
		<content:encoded><![CDATA[<p>[...] release has no mention of a compatibility issue in their release notes, although fellow enthusiast Christopher Price and myself have experienced this [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
