<?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: Recover from BAD_POOL_HEADER blue screen errors after upgrading hard drive</title>
	<atom:link href="http://www.geektieguy.com/2009/07/27/recover-from-bad_pool_header-blue-screen-errors-after-upgrading-hard-drive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.geektieguy.com/2009/07/27/recover-from-bad_pool_header-blue-screen-errors-after-upgrading-hard-drive/</link>
	<description>News and views from the geek tie guy.</description>
	<lastBuildDate>Fri, 12 Mar 2010 15:29:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Warning when cloning a hard drive &#171; davidtaylorfamily.com &#8211; David Taylor&#8217;s Blog</title>
		<link>http://www.geektieguy.com/2009/07/27/recover-from-bad_pool_header-blue-screen-errors-after-upgrading-hard-drive/comment-page-1/#comment-43736</link>
		<dc:creator>Warning when cloning a hard drive &#171; davidtaylorfamily.com &#8211; David Taylor&#8217;s Blog</dc:creator>
		<pubDate>Sun, 30 Aug 2009 13:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.geektieguy.com/2009/07/27/recover-from-bad_pool_header-blue-screen-errors-after-upgrading-hard-drive/#comment-43736</guid>
		<description>[...] Warning when cloning a hard&#160;drive  I ran into a little tech puzzler this weekend.  I&#8217;m simply documenting it on my website both for me (in case in happens again in the future) and for anyone else who might have the same obscure issue.  I found the solution elsewhere and will link to it here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Warning when cloning a hard&nbsp;drive  I ran into a little tech puzzler this weekend.  I&#8217;m simply documenting it on my website both for me (in case in happens again in the future) and for anyone else who might have the same obscure issue.  I found the solution elsewhere and will link to it here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
