Wizzard said:
I have 2 IDEs, one has XP Pro on it. I installed a new SATA which,
thanks to guys here, is now working correctly.
I installed XP on the SATA drive. I then had a multi boot option to
log onto SATA or IDE. I then true imaged the original XP from IDE
drive to it.
Problem now is how to get rid of the original XP and leave the SATA
XP. The boot ini that gives me the option to boot into either is on
the original IDE XP drive.
I hope this makes sense!
Yea you are having the same type of problem I had going from ATA66 to a
shiny new ATA133 nearly four years ago (ATA133 was a big deal then).
Well you have already screwed the pooch so you need to start over. Try
this ...
A cloned copy of the IDE's XP should copy the three bootstrap files XP
needs to boot over to the SATA (boot.ini, ntdlr and NTDETECT.COM). I
haven't used True Image so I don't know if it also does the following
vital things:
1. Copied the MBR from the IDE to the SATA. The comp's bios will invoke
the MBR code on the active partition, you will want this to be the SATA
*not* the IDE. If it can't do this then you will need to repair the
SATA's MBR using your XP CD by doing a fixmbr just before booting it for
the first time.
2. Made the SATA's partition where XP's three boot files reside a
*primary* partition. The Windows (or what ever you called it) directory
with the bulk of XP can reside elsewhere but no MS OS can bootstrap from
an extended partition. I would assume by the very word 'clone' that this
would be so but ...
And thirdly *you* installed any needed SATA drivers into the IDE XP
install and tested that the SATA is perfectly readable from native XP
(not just from some third party app) *before* cloning. You obviously
have done this but it should be noted.
If the above points are true then all you need do is have Acronis make
the boot partition on the SATA (where boot.ini lives) the active
partition, power down and *disconnect* the IDE drive. Its important that
the first boot to the SATA be without the IDE connected so XP can
configure itself to the new SATA drive. It actually records information
about its parent hard drive in the registry and this most likely will
invoke the dreaded activation routine. But that shouldn't be a problem
*if your legit and wait until everything is configured* exactly as you
want it first. If afterward you need to make a phone call just explain
that the old drive went belly up. The resident hackers may post the key
that needs edited ahead of time in the the SATA's XP registry to get
around activation but I suspect you don't care.
You will have to go into your bios to enable the SATA drive to boot (see
your MB manual) and in any event you will need to add the SATA to the
boot chain. My personal preference in the boot chain is floppy first, CD
second and the hard drive with active partition third. I hear that some
people prefer the hard drive be first because they evidently haven't the
wit to actually remove removable media before booting - but thats
another thread.
Now boot into your SATA XP and check that all is OK including testing
all apps. If it won't boot then do an XP fixmbr repair, you can Google
for that. If it still won't boot then SATA drivers may not have been
installed properly, do an F6 repair with SATA drivers at hand on floppy,
you can Google for that as well.
If you intend to use the IDE as a data drive in the same comp, for
insurance, power off and reconnect it but boot from the Acronis CD and
make sure that *none* of the partitions on the IDE drive are marked as
active. Things may or may not work properly with more than one active
partition but just one should always work.
John
