V
Vormulac
Hi all,
This is probably really simple, but I could use some help.
I rebuilt my system recently and installed a new S-ATA hdd. To minimise the
complexity of trying to install Windows on a new drive, when it already
existed on one of my two bog standard IDE hdds I just unplugged them.
Well today I tried to access them by plugging them back in and setting BIOS
to boot only from HDD-0 (the new one) and disabling boot device seek. In
theory this should make it boot from the new drive and ignore the fact
there's a boot sector on one of the other drives right?
Well, no. If the drive that had the Windows on it originally is installed,
the system crawls through POST and eventually stalls with a "Boot disk
failed, please insert disk and press enter" message. If that is unplugged
and the other one is installed, the system boots normally, but there is no
sign of that drive under Windows.
The old drives are IBM deskstars and I have set the jumpers on them to
'cable select'.
This is just plain wierd!
Cheers all.
This is probably really simple, but I could use some help.
I rebuilt my system recently and installed a new S-ATA hdd. To minimise the
complexity of trying to install Windows on a new drive, when it already
existed on one of my two bog standard IDE hdds I just unplugged them.
Well today I tried to access them by plugging them back in and setting BIOS
to boot only from HDD-0 (the new one) and disabling boot device seek. In
theory this should make it boot from the new drive and ignore the fact
there's a boot sector on one of the other drives right?
Well, no. If the drive that had the Windows on it originally is installed,
the system crawls through POST and eventually stalls with a "Boot disk
failed, please insert disk and press enter" message. If that is unplugged
and the other one is installed, the system boots normally, but there is no
sign of that drive under Windows.
The old drives are IBM deskstars and I have set the jumpers on them to
'cable select'.
This is just plain wierd!
Cheers all.