"newbie" <nomail@for.me> wrote in message
news:Id2of.16037$O05.7127@fe09.lga...
> YES!!!  I fixed the problem by editing the boot.ini file.
>
> With the drive in question set up as the slave, I edited it's boot.ini
file
> the easy way, that is, I turned off "hide protected operating system
files"
> in the "Folder options-> view" control panel, found the boot.ini file in
the
> root directory, made it not read-only, and changed the partition number
from
> 2 to 1 in two places.  Then shut down, moved the drive to the "master"
> connector on the cable and booted normally.
>
> The only thing is - WHY did I have to do that in the first place?  Is it
> possible that my original hard drive had a hidden partition, making the
> partition with windows, etc it in #2 ?
>
> I am going to do a fresh archive of the new drive.  If I ever have to
> restore this one, I will see if I run into the same problem.  Hopefully
that
> won't be for a while...
>
>
> "newbie" <nomail@for.me> wrote in message
> news:lq1of.15439$O05.11252@fe09.lga... 
> which 
the[vbcol=seagreen] 
> that 
> however 
a[vbcol=seagreen] 
the[vbcol=seagreen] 
AND[vbcol=seagreen] 
> been. 
I[vbcol=seagreen] 
> run 
> same 
>

Is it possible that you had at some point created an Acronis safe zone on
the HD with the option to boot into it ? Then that partion becomes the
primary one and uses a pointer to boot the O/S off of the now partition #2>

[ Post a follow-up to this message ]