to recognize the SATA drives unless you have a BIOS setting that allows you to emulate IDE.
Re-install the original SCSI drive as the solitary drive (original configuration) then install the SATA drivers from the motherboard driver disk. Now clone the SCSI to that SATA and it just might become bootable.
Alternatively, SCSI drives are dependable and quick so you might consider just installing the SATA as a second drive and transferring data to the SATA drive to make room on the SCSI drive. You could also uninstall various applications from the SCSI drive then re-install them on the SATA drive.
Last year, I got my mother in law set up with an off-lease PC from a local shop. The bizarre thing about this PC is that the hard drive was a SCSI drive hooked up through a controller card. The PC runs perfectly under its current configuration, but that's where the farytale ends.
The problem is that they are running out of HD space and don't want to remove anything. So I went out and got them a 320 gig SATA HD and figured I would ghost the SCSI drive over to the new SATA.
I was able to successfully create an image of the old drive with Ghost 9 and get it imaged onto the new SATA drive, but the system will not boot to the new drive. If I boot to the old HD with the new one installed, it is showing that the drive is there and has all the data on it. BIOS also sees it. It will boot past POST and act like it is booting to the new SATA drive, but then it hangs there, just a plain black screen.
My only theory is that the installation of Win XP is configured in such a way that it will only function going through the SCSI controller card. Unfortunately, I do not know much about these cards as the only experience I have working with SCSI is what is in my HP DL380 G2 server.
HP Workstation xw4100
Onboard SATA and IDE, SCSI is through PCI controller card.
2 gigs RAM
Old HD 37 gig SCSI
New HD 320 gig SATA
Windows XP SP3