<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>mcBachmann.de TechBlog &#187; registry</title>
	<atom:link href="http://blog.mcbachmann.de/tag/registry/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.mcbachmann.de</link>
	<description>Der Blog zur Website ;-)</description>
	<lastBuildDate>Wed, 11 Jan 2012 21:12:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Windows Bluescreen: 0x0000007B INACCESSIBLE_BOOT_DEVICE</title>
		<link>http://blog.mcbachmann.de/linux/windows-bluescreen-0x0000007b-inaccessible_boot_device</link>
		<comments>http://blog.mcbachmann.de/linux/windows-bluescreen-0x0000007b-inaccessible_boot_device#comments</comments>
		<pubDate>Sun, 21 Jun 2009 08:25:47 +0000</pubDate>
		<dc:creator>Sven Bachmann</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[registry]]></category>
		<category><![CDATA[rescue]]></category>

		<guid isPermaLink="false">http://blog.mcbachmann.de/?p=322</guid>
		<description><![CDATA[After my yesterdays blog entry Edit Windows Registry from Linux I could see the error windows showed me in a bluescreen: 0x0000007B INACCESSIBLE_BOOT_DEVICE. This was after I changed the motherboard and the CPU. My first thought was &#8216;Oh no, I&#8217;ll have to reinstall it&#8217; &#8211; but it went all good. If you do the things [...]]]></description>
			<content:encoded><![CDATA[<p>After my yesterdays blog entry <a href="http://blog.mcbachmann.de/linux/edit-windows-registry-from-linux">Edit Windows Registry from Linux</a> I could see the error windows showed me in a bluescreen: 0x0000007B INACCESSIBLE_BOOT_DEVICE.</p>
<p>This was after I changed the motherboard and the CPU. My first thought was &#8216;Oh no, I&#8217;ll have to reinstall it&#8217; &#8211; but it went all good. <span id="more-322"></span></p>
<blockquote><p>If you do the things described here you are at your own risk &#8211; it could damage your system permanently. If you decide to do it anyway, please use copy &#038; paste to not miss anything.</p></blockquote>
<p>On notice at first: your motherboard needs to support a normal IDE mode &#8211; we just reset the normal IDE drivers so Windows can boot and you can later reinstall some S-ATA drivers.</p>
<p>So lets start, first you need to boot some Linux which is able to <strong>write NTFS</strong> partitions and has the tools <strong>chntpw</strong> and <strong>cabextract</strong> (I had a multiboot with Ubuntu, so it was no problem).</p>
<p>First, lets mount the NTFS partition (we assume its the first partition on the first harddisk):</p>
<blockquote><p><code>mkdir /mnt/windows<br />
mount /dev/sda1 /mnt/windows<br />
cd /mnt/windows</code></p></blockquote>
<p>Next we need to go to the Driver Cache and extract standard IDE drivers from some cabinet files:</p>
<blockquote><p><code>cd `ls | grep -w -i windows`<br />
cd "`ls | grep -w -i "driver cache"`"<br />
cd `ls | grep -w -i i386`</code></p></blockquote>
<p>These <em>`ls &#8230; | grep &#8230;`</em> things are necessary, because the case of the directory name can differ &#8211; so we workaround this.</p>
<p>The knowledge base article from Microsoft is a bit outdated, because the get all needed files from <strong>driver.cab</strong>, but in my case <strong>Service Pack 2</strong> was installed and the files were in a slightly different location: <strong>sp2.cab</strong>.</p>
<p>So to be sure to extract <strong>all</strong> files (even with Service Pack 3), do the following extractions:</p>
<blockquote><p><code>DEST="../../`ls ../../ | grep -w -i system32`"<br />
cabextract -d $DEST -F atapi.sys driver.cab sp2.cab sp3.cab<br />
cabextract -d $DEST -F Intelide.sys driver.cab sp2.cab sp3.cab<br />
cabextract -d $DEST -F Pciide.sys driver.cab sp2.cab sp3.cab<br />
cabextract -d $DEST -F Pciidex.sys driver.cab sp2.cab sp3.cab</code></p></blockquote>
<p>Last step is updating the registry. Unfortunately its not possible with <strong>chntpw</strong> to import <em>reg</em>-Files &#8211; but to not enter all registry keys by hand, I wrote a chntpw-script to set the necessary values. You can download it here: <a href='http://blog.mcbachmann.de/wp-content/uploads/2009/06/mergeide.chntpw'>chntpw-mergeide script</a>.</p>
<p>To apply it, save the script on your desktop and do the following steps:</p>
<blockquote><p><code>cd $DEST<br />
cd `ls | grep -w -i config`<br />
chntpw -u Administrator system < ~/Desktop/mergeide.chntpw</code></p></blockquote>
<p>Thats all, you can now unmount the windows partition and reboot. Make sure your BIOS is set to standard IDE emulation.</p>
<blockquote><p><code>cd ~<br />
umount /mnt/windows</code></p></blockquote>
<p>Links I used:</p>
<ul>
<li><a href="http://support.microsoft.com/kb/314082">KB: ...Stop 0x0000007B error after you move the Windows XP system disk...</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.mcbachmann.de/linux/windows-bluescreen-0x0000007b-inaccessible_boot_device/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Edit Windows Registry from Linux</title>
		<link>http://blog.mcbachmann.de/linux/edit-windows-registry-from-linux</link>
		<comments>http://blog.mcbachmann.de/linux/edit-windows-registry-from-linux#comments</comments>
		<pubDate>Sat, 20 Jun 2009 15:27:33 +0000</pubDate>
		<dc:creator>Sven Bachmann</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[registry]]></category>
		<category><![CDATA[rescue]]></category>

		<guid isPermaLink="false">http://blog.mcbachmann.de/?p=315</guid>
		<description><![CDATA[Its a pity when Windows just does one thing: reboot. You have the chance to see the bluescreen for just some milliseconds but not more &#8211; but how disabling the autoreboot when Windows doesn&#8217;t let you edit the settings? There is help with Linux and the tool chntpw&#8230; Mount the Windows device in Linux and [...]]]></description>
			<content:encoded><![CDATA[<p>Its a pity when Windows just does one thing: reboot. You have the chance to see the bluescreen for just some milliseconds but not more &#8211; but how disabling the autoreboot when Windows doesn&#8217;t let you edit the settings? There is help with Linux and the tool <strong>chntpw</strong>&#8230; <span id="more-315"></span></p>
<p>Mount the Windows device in Linux and do the following commands (this is for disabling auto-reboot, you can also edit all other registry values!):</p>
<blockquote><p><code><br />
cd Windows/System32/Config<br />
chntpw -u Administrator system<br />
> cd ControlSet001\Control\CrashControl<br />
> ed AutoReboot<br />
-> 0<br />
> q<br />
Write hive files? (y/n) [n] : y<br />
</code></p></blockquote>
<p>Hint: Instead of typing <em>cd ControlSet001</em> you can also type <em>ls</em> to find out which other control sets exists and you may need to change.</p>
<p>Links I used:</p>
<ul>
<li><a href="http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_Vista/Q_24015966.html">EE Forum &#8211; Prevent Auto Reboot on BSOD from CMD</a></li>
<li><a href="http://books.google.de/books?id=YaSWlOOxshsC&#038;pg=PA264">Knoppix Hacks</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.mcbachmann.de/linux/edit-windows-registry-from-linux/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

