<?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: Well, jeepers.</title>
	<atom:link href="http://habitablezone.com/2012/04/24/well-jeepers/feed/" rel="self" type="application/rss+xml" />
	<link>https://habitablezone.com/2012/04/24/well-jeepers/</link>
	<description></description>
	<lastBuildDate>Thu, 23 Apr 2026 21:07:28 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TB</title>
		<link>https://habitablezone.com/2012/04/24/well-jeepers/#comment-14236</link>
		<dc:creator>TB</dc:creator>
		<pubDate>Wed, 25 Apr 2012 16:41:38 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=14022#comment-14236</guid>
		<description>&lt;p&gt;Oh, I know how it works, and I know what the problem was.&lt;/p&gt;

I had a &quot;spare&quot; boot folder (not operating system files) in my E Drive and, as you say, somehow my system was using that to start up in combination with the system files on the C drive.

I just can&#039;t figure out how things got that way.  I never put any system stuff on data disks.  I never run &quot;multiple system&quot; setups.  And I don&#039;t think something like &quot;format /S&quot; even works nowadays.

I don&#039;t copy, move, or delete system files.  Windows is like a beautiful stack of crystal wine glasses.  If it&#039;s stable, you don&#039;t mess with it.  It&#039;s why I wanted to set up a disk image in the first place.  I&#039;ve got something that works, and if my C drive blows up I&#039;d like to recreate it the easy way.

So I can&#039;t have my operating system spread over two physical drives.

My mistake was assuming this E folder was just a superfluous copy, and switching it off before trying a restart, but looking back on it there probably wasn&#039;t any other way to force the system back to normal.

The Windows installation disk was able to &quot;repair&quot; this either by toggling the system over to use the C drive boot folder, or actually putting new boot files on the C drive so it worked.  I don&#039;t know, it didn&#039;t tell me.  But if I suspect if I hadn&#039;t &quot;broken&quot; it, it wouldn&#039;t have been able to fix it.

After that quick repair, I was able to clean the boot files from the E drive, and now all the working parts are under the hood and none in the trunk.

I use Windows because I run a lot of software that doesn&#039;t run on anything else.  Some programs won&#039;t even run on Vista.  But the rest of my family runs Macs.  Only my daughter has a smartphone.  My wife has an IPod that runs software she needs.</description>
		<content:encoded><![CDATA[<p>Oh, I know how it works, and I know what the problem was.</p>
<p>I had a &#8220;spare&#8221; boot folder (not operating system files) in my E Drive and, as you say, somehow my system was using that to start up in combination with the system files on the C drive.</p>
<p>I just can&#8217;t figure out how things got that way.  I never put any system stuff on data disks.  I never run &#8220;multiple system&#8221; setups.  And I don&#8217;t think something like &#8220;format /S&#8221; even works nowadays.</p>
<p>I don&#8217;t copy, move, or delete system files.  Windows is like a beautiful stack of crystal wine glasses.  If it&#8217;s stable, you don&#8217;t mess with it.  It&#8217;s why I wanted to set up a disk image in the first place.  I&#8217;ve got something that works, and if my C drive blows up I&#8217;d like to recreate it the easy way.</p>
<p>So I can&#8217;t have my operating system spread over two physical drives.</p>
<p>My mistake was assuming this E folder was just a superfluous copy, and switching it off before trying a restart, but looking back on it there probably wasn&#8217;t any other way to force the system back to normal.</p>
<p>The Windows installation disk was able to &#8220;repair&#8221; this either by toggling the system over to use the C drive boot folder, or actually putting new boot files on the C drive so it worked.  I don&#8217;t know, it didn&#8217;t tell me.  But if I suspect if I hadn&#8217;t &#8220;broken&#8221; it, it wouldn&#8217;t have been able to fix it.</p>
<p>After that quick repair, I was able to clean the boot files from the E drive, and now all the working parts are under the hood and none in the trunk.</p>
<p>I use Windows because I run a lot of software that doesn&#8217;t run on anything else.  Some programs won&#8217;t even run on Vista.  But the rest of my family runs Macs.  Only my daughter has a smartphone.  My wife has an IPod that runs software she needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>https://habitablezone.com/2012/04/24/well-jeepers/#comment-14233</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Wed, 25 Apr 2012 06:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=14022#comment-14233</guid>
		<description>&lt;p&gt;boot !== OS&lt;/p&gt;

That&#039;s why.

What, you want that in English?

&quot;boot&quot; from &quot;bootstrap&quot; as in raising one&#039;s self by, means your PC boots through a bunch of phases. Just after the BIOS gets the hardware ducks marching in a row, it checks the hard drives for a boot sector (old Windows) or a &quot;/boot&quot; folder (Linux and now, apparently, Windows 7). That boot sector in turn loads the OS, wherever it is.

If you&#039;ve ever set up a PC to boot from multiple operating systems, you messed around at this level. In that case the boot sector/folder knows how to branch to OSes stored on various hard drives depending on which one you pick.

Sounds like your boot folder was located on E and set to boot Windows from C.

Until you kicked your PC squarely in the middle of the boot process--about nut high, if you must--and took out the boot step. Nothing gonna work after that.

Windows, AFAIK, still doesn&#039;t handle it well when you start copying parts of its core files around. Not surprised things went from bad to worse when you started trying to delete system files and reformatting the drive and renaming the boot folder. Don&#039;t do that. With Windows you must simply throw your hands in the air and despair.

You restored from the Windows 7 DVD, if I understand right, and it worked with E: reformatted? Hmmm...I&#039;ll guess that you now have a /boot folder on your C drive. Or maybe it did it with an old-school boot sector. Interesting.

Glad I&#039;m still able to get by on Windows XP. I haven&#039;t had to suffer through any of this stuff.

OTOH, my friendly Sikh delivery guy, who resembles Santa Claus in a blue turban, just brought me a tablet PC running Android (aka Linux). Pretty cool toy, and makes me wonder even more why I should waste money upgrading Windows. I like being off that grid.</description>
		<content:encoded><![CDATA[<p>boot !== OS</p>
<p>That&#8217;s why.</p>
<p>What, you want that in English?</p>
<p>&#8220;boot&#8221; from &#8220;bootstrap&#8221; as in raising one&#8217;s self by, means your PC boots through a bunch of phases. Just after the BIOS gets the hardware ducks marching in a row, it checks the hard drives for a boot sector (old Windows) or a &#8220;/boot&#8221; folder (Linux and now, apparently, Windows 7). That boot sector in turn loads the OS, wherever it is.</p>
<p>If you&#8217;ve ever set up a PC to boot from multiple operating systems, you messed around at this level. In that case the boot sector/folder knows how to branch to OSes stored on various hard drives depending on which one you pick.</p>
<p>Sounds like your boot folder was located on E and set to boot Windows from C.</p>
<p>Until you kicked your PC squarely in the middle of the boot process&#8211;about nut high, if you must&#8211;and took out the boot step. Nothing gonna work after that.</p>
<p>Windows, AFAIK, still doesn&#8217;t handle it well when you start copying parts of its core files around. Not surprised things went from bad to worse when you started trying to delete system files and reformatting the drive and renaming the boot folder. Don&#8217;t do that. With Windows you must simply throw your hands in the air and despair.</p>
<p>You restored from the Windows 7 DVD, if I understand right, and it worked with E: reformatted? Hmmm&#8230;I&#8217;ll guess that you now have a /boot folder on your C drive. Or maybe it did it with an old-school boot sector. Interesting.</p>
<p>Glad I&#8217;m still able to get by on Windows XP. I haven&#8217;t had to suffer through any of this stuff.</p>
<p>OTOH, my friendly Sikh delivery guy, who resembles Santa Claus in a blue turban, just brought me a tablet PC running Android (aka Linux). Pretty cool toy, and makes me wonder even more why I should waste money upgrading Windows. I like being off that grid.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
