My ASUS-based system has been running XP on the following:
- a SATA-I 160G drive on controller 0
- partitions for C, D and G (E/F are CD-ROM and DVD-ROM)
I added a 500G SATA-II (Seagate) drive on controller 1 and cloned the 3 partitions with Ghost 9, including the MBR on the first partition. I also marked the first partition as active.
When I swap cables and reboot, I get the black XP loader screen, followed by a blue screen with a small WinXP logo, instead of the usual Welcome screen with all the user names.
I've seen variants of this problem in various threads, often in cases where people are trying to upgrade to SATA from IDE. I've done upgrades before - usually IDE-to-IDE - and when I've had a problem it's been due to not copying the MBR or marking the 1st partition as active.
I'm guessing that Windows knows the new drive started life on another controller (1) and therefore doesn't want to load on controller 0 after the cable swap. I suspect that if I leave it connected to controller 1, Windows will still be looking for the first disk on controller 0 and also refuse to boot.
What can I do short of re-installing on the new drive?
- a SATA-I 160G drive on controller 0
- partitions for C, D and G (E/F are CD-ROM and DVD-ROM)
I added a 500G SATA-II (Seagate) drive on controller 1 and cloned the 3 partitions with Ghost 9, including the MBR on the first partition. I also marked the first partition as active.
When I swap cables and reboot, I get the black XP loader screen, followed by a blue screen with a small WinXP logo, instead of the usual Welcome screen with all the user names.
I've seen variants of this problem in various threads, often in cases where people are trying to upgrade to SATA from IDE. I've done upgrades before - usually IDE-to-IDE - and when I've had a problem it's been due to not copying the MBR or marking the 1st partition as active.
I'm guessing that Windows knows the new drive started life on another controller (1) and therefore doesn't want to load on controller 0 after the cable swap. I suspect that if I leave it connected to controller 1, Windows will still be looking for the first disk on controller 0 and also refuse to boot.
What can I do short of re-installing on the new drive?