G
Guest
Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)
Have used the method here:
http://www.mostlycreativeworkshop.com/article11.html
to move several systems to new hardware, with excellent results.
However, the last two times I tried it, after moving the hard drives to
new motherboards, they wouldn't boot. Both gave the NTloader not found
error. The first time, I was moving from one VIA chipset board to
another, so I tried installing an old GHOST image of the system to the
new hardware. It booted and worked fine.
The second time was a more radical hardware change, so after moving the
hard drive and getting the same error, I GHOSTed that system and
immediately reinstalled on the same partition. Glory be, it worked and
booted fine.
Guess my question is, why did that work, and what did GHOST do to make
the thing boot? Would FIXBOOT from the recovery console have done the
same thing?
Have used the method here:
http://www.mostlycreativeworkshop.com/article11.html
to move several systems to new hardware, with excellent results.
However, the last two times I tried it, after moving the hard drives to
new motherboards, they wouldn't boot. Both gave the NTloader not found
error. The first time, I was moving from one VIA chipset board to
another, so I tried installing an old GHOST image of the system to the
new hardware. It booted and worked fine.
The second time was a more radical hardware change, so after moving the
hard drive and getting the same error, I GHOSTed that system and
immediately reinstalled on the same partition. Glory be, it worked and
booted fine.
Guess my question is, why did that work, and what did GHOST do to make
the thing boot? Would FIXBOOT from the recovery console have done the
same thing?