<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Woohoo!</title>
	<link>http://www.kmellis.com/2007/07/09/woohoo/</link>
	<description>Info About and Musings of Keith M Ellis</description>
	<pubDate>Fri, 21 Nov 2008 02:43:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Kevin</title>
		<link>http://www.kmellis.com/2007/07/09/woohoo/#comment-11</link>
		<author>Kevin</author>
		<pubDate>Mon, 29 Oct 2007 22:15:24 +0000</pubDate>
		<guid>http://www.kmellis.com/2007/07/09/woohoo/#comment-11</guid>
					<description>You Rock!  Thank you so much for posting this. Congrats on your restore. We were getting a similar error. Your Idea of hex editor helped us get through our restore. We had renamed the created folders after the backup. While in Hex, we were able to see what the old paths were and correct the path/folder file names.  Thank you again for the idea.</description>
		<content:encoded><![CDATA[<p>You Rock!  Thank you so much for posting this. Congrats on your restore. We were getting a similar error. Your Idea of hex editor helped us get through our restore. We had renamed the created folders after the backup. While in Hex, we were able to see what the old paths were and correct the path/folder file names.  Thank you again for the idea.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Glenn Davey</title>
		<link>http://www.kmellis.com/2007/07/09/woohoo/#comment-22</link>
		<author>Glenn Davey</author>
		<pubDate>Sat, 12 Jan 2008 01:45:06 +0000</pubDate>
		<guid>http://www.kmellis.com/2007/07/09/woohoo/#comment-22</guid>
					<description>Hey thanks for the report. I work as a computer tech and thought I'd lost all chance of recovering someone's data that I'd backed up! Fortunately I was able to brave through the hex editor method and found the appropriate string in the catalog etc and voila! all working :D 

thankyou kindly!
cheers
glenn</description>
		<content:encoded><![CDATA[<p>Hey thanks for the report. I work as a computer tech and thought I&#8217;d lost all chance of recovering someone&#8217;s data that I&#8217;d backed up! Fortunately I was able to brave through the hex editor method and found the appropriate string in the catalog etc and voila! all working <img src='http://www.kmellis.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>thankyou kindly!<br />
cheers<br />
glenn</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Wayne Chicken</title>
		<link>http://www.kmellis.com/2007/07/09/woohoo/#comment-35</link>
		<author>Wayne Chicken</author>
		<pubDate>Tue, 02 Sep 2008 21:29:49 +0000</pubDate>
		<guid>http://www.kmellis.com/2007/07/09/woohoo/#comment-35</guid>
					<description>Keith, I've tried replacing the MediaID.bin string with virtually every reasonable looking sequence in all the catalog files, but to no avail! Having spent another wasted 3 hours this evening, I'm on the verge of giving up. If you ever find the time to methodically test and prove your solution, please let me know!
Kind thanks, 
Wayne.</description>
		<content:encoded><![CDATA[<p>Keith, I&#8217;ve tried replacing the MediaID.bin string with virtually every reasonable looking sequence in all the catalog files, but to no avail! Having spent another wasted 3 hours this evening, I&#8217;m on the verge of giving up. If you ever find the time to methodically test and prove your solution, please let me know!<br />
Kind thanks,<br />
Wayne.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Keith M Ellis</title>
		<link>http://www.kmellis.com/2007/07/09/woohoo/#comment-36</link>
		<author>Keith M Ellis</author>
		<pubDate>Wed, 03 Sep 2008 04:19:09 +0000</pubDate>
		<guid>http://www.kmellis.com/2007/07/09/woohoo/#comment-36</guid>
					<description>Wayne, it can be done.  Try making a small backup on a different medium.  Then, using a hex editor, find within one of the directory mediaid.bin files the same string as the one the root mediaid.bin contains.  That'll give you an idea of what to look for and where.  Be sure to mind the fact that the format of the file's data is two bytes and that, consequently, the string in the directory mediaid.bin will have "00" between each character.  When you find it, copy the new root mediaID.bin you just made to the root of the medium which is missing it.  Using a hex editor (definitely *not* a text editor), overwrite the characters that are there with the characters you found in the directory mediaid.bin.</description>
		<content:encoded><![CDATA[<p>Wayne, it can be done.  Try making a small backup on a different medium.  Then, using a hex editor, find within one of the directory mediaid.bin files the same string as the one the root mediaid.bin contains.  That&#8217;ll give you an idea of what to look for and where.  Be sure to mind the fact that the format of the file&#8217;s data is two bytes and that, consequently, the string in the directory mediaid.bin will have &#8220;00&#8243; between each character.  When you find it, copy the new root mediaID.bin you just made to the root of the medium which is missing it.  Using a hex editor (definitely *not* a text editor), overwrite the characters that are there with the characters you found in the directory mediaid.bin.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
