Ghosted my install to a new HD but can't boot

[Bullhonkie]

My current windows boot drive is a Cheetah 15k running off a LSI Logic U160 SCSI adapter.

I ghosted that drive's contents to a brand new Barracuda 7200.9 ATA drive which I would like to use now as the windows boot drive.

However when I unplug the Cheetah and plug in the 'cuda I only get a 'disk boot failure, insert system disk' after POST.

Do I need to edit my boot.ini or otherwise make some kind of change for Windows to be able to recognize the 'cuda as a system disk that it can boot from?

Or is what I'm trying to do even possible since I'm switching my boot drive from SCSI to ATA 'on the fly' without reinstalling windows?

Edit: Ok after some brainstorming I think the problem is my settings in the boot.ini. It currently reads as:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

I'll have 3 HDs attached after removing the Cheetah, 2 on primary IDE and 1 on secondary as slave. The 'cuda I want to boot from now is attached as slave on the secondary IDE channel. What should I change here to reflect that?

 

[Bullhonkie]

Nevermind I got it sorted out. It was a 1D-10-T error.

Turns out I had 'boot from IDE' set to off in my BIOS. 😱

 

[spikespiegal]

🙂