<?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: Installed new hardware and now windows won&#8217;t start.?</title>
	<atom:link href="http://cleanupcomputer.net/installed-new-hardware-and-now-windows-wont-start.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://cleanupcomputer.net/installed-new-hardware-and-now-windows-wont-start.htm</link>
	<description>Best Registry Cleaner and Registry Repair Software Review.</description>
	<lastBuildDate>Fri, 17 Jun 2011 18:08:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nathan</title>
		<link>http://cleanupcomputer.net/installed-new-hardware-and-now-windows-wont-start.htm/comment-page-1#comment-9460</link>
		<dc:creator>nathan</dc:creator>
		<pubDate>Sat, 28 Nov 2009 22:17:06 +0000</pubDate>
		<guid isPermaLink="false">http://cleanupcomputer.net/installed-new-hardware-and-now-windows-wont-start.htm#comment-9460</guid>
		<description>Since your brother changed the motherboard. He can&#039;t use the same install of windows. 
Windows is very specific to the hardware address layer (HAL). the HAL is things like the disk manager, the process manager, memory manager. So by switching the motherboard, it requires all new version to tie into the HAL.

the only thing you can do to fix this problem is reinstall windows. There&#039;s no way to hack it back together. You&#039;ll always have the problem of the HAL. 

At the place i work, we have tons of disk images for different type of workstation classes.  I&#039;ve put the wrong disk image on a machine before. This is what happens, because it can not recognize the HAL, and can not use the motherboard. The only way to fix is install windows again. (in our case, put the correct disc image on)</description>
		<content:encoded><![CDATA[<p>Since your brother changed the motherboard. He can&#8217;t use the same install of windows.<br />
Windows is very specific to the hardware address layer (HAL). the HAL is things like the disk manager, the process manager, memory manager. So by switching the motherboard, it requires all new version to tie into the HAL.</p>
<p>the only thing you can do to fix this problem is reinstall windows. There&#8217;s no way to hack it back together. You&#8217;ll always have the problem of the HAL. </p>
<p>At the place i work, we have tons of disk images for different type of workstation classes.  I&#8217;ve put the wrong disk image on a machine before. This is what happens, because it can not recognize the HAL, and can not use the motherboard. The only way to fix is install windows again. (in our case, put the correct disc image on)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

