New drive not booting with old drive as slave 2

[Synapse5444]

When I instally my new hard drive as the master, my computer boots off of the old drive that is set as slave.

My BIOS has a feature that allows this. Basically it searches for any bootable medium.

I can not figure out why it will not use the drive that the BIOS sees as Prim Master as the boot drive.

The new drive is a clone of the old. Anyone have any ideas?

 

[wolluf]

1. Is the bios seeing the new drive (can you access it after booting from slave)

2. Does the new cloned drive boot on its own (ie, with slave disconnected)? If it does, what happens if new drive is primary master and old drive is secondary master?

3. Are you sure you've got master and slave right way round?

 

[rookieatit]

What setting do yoou have for jumpers?
CS will set the last drive on the IDE channel as the master and the one in the middle as the slave.
As indicated earlier have you tried to boot off each drive indiviually. ie:without the other drive on the channel.
Either could be the reason.
additionally have you checked the windows explorer to see if both drives are being detected. also check disk manager W2K NT XP. Just some thoughts. rookieatit@hotmail.com

 

[Synapse5444]

I can see the disk from BIOS.

yes the drive will boot on its own.


If new drive is pri master it boots from slave. (this is my problem in general)

I haven't tried moving the new disk to slave and seeing if it will boot that way.

 

[wolluf]

My suggestion was putting both drives on separate IDE channels, both as masters (disconnect CD drive(s) or slave them to hard drives for this test). Machine should boot from Primary master.

 

[rookieatit]

Just a thought do you have an option at startup for dual boot? rookieatit@hotmail.com

 

[Synapse5444]

No, the system is not dual boot.


I will try that. I did think of that as well. I am going to try it now. But really what does that tell me?

That my system can't recognize the fact that the drive I specify by jumper should be the master? Strange indeed. I have done this in the past with multiple drives but this is the first time I have ever had this problem.

 

[Synapse5444]

Also, just another interesting side, is the OS is not booting fully on the new, cloned drive.

It gets to the WinXP Logon screen but with no place to enter user info, and remains there.

 

[wolluf]

login problem - does hitting Ctrl+alt+del twice give you a login box?

Original problem - another poster had similar several months ago, thread I posted on. He tried lots of different things (can't remember if he actually cracked the boot order problem - he did get a workable system at one point - I might take a look see if I can find the thread).

 

[eastender]

Only one partition should be marked "Active," which most likely is your original/old drive. The bios will look for the active partition. Use FDISK to view the partition information, chances are your new drive does not have an active partition.

 

[jerryd3001]

Mine did the exact same thing because I was ignoring the message to Reboot when Windows located the new hard drive set up as I rebooted from copying the partitions. When I clicked on Yes to reboot the next time I restarted, everything worked as it should. So, what you need is two reboots to get proper recognition of the new hard drive setup. Hope this works for you.

 

[Synapse5444]

What I did was make sure I got my jumpers correct (I did), and turn off my BIOS setting to boot any possible drive if the ones listed do not boot.


Thanks for all the advice

On the second problem: No the computer was not waiting for login, it was just before that point. My system was set to require a Ctrl-alt-del. But I went ahead and started with a fresh install. So much better that way