Hi
I have just built a new XP 32 system,and all works fine. What I thought I WOULD do to finish off was to connect my old system DISK ´´Seagate Barracuda 7200.7´´ to my new system just to be able to access the data files, and copy them over to the new set up. I have done this before without any grief. I know that the old XP OS is still on there, but I did not think it would boot from it without me TELLING the system to do so.
I thought things were suspicious when I checked the BIOS and it only seemed to see the IDE disk, which the seagate is. The seagate is connected to the MOBO through the IDE plug.
The other two disks, including the new system disk, are connected via the SATA ports on the MOBO. When the IDE disk is not connected the system boots from the new C system disk, when the seagate IDE disk is connected the system boots from it.
I´m sure I´m missing something really obvious, but its not obvious to me.
Can anyone give me some advice as what settings to adjust so I can just access the data on the seagate disk and stop my pc from BOOTING from the wrong disk? Just ran Belarc system audit, and for some reason my printer is being detected as a hard DRIVE! Does this mean things are well wrong?
MOBO Asus P5SD2-VM
Thanks for your time in reading
Kwisj Printer is being detected as hard drive...


First, reset your CMOS, because your BIOS is evidently wonky and is not enumerating your USB devices properly.
www.youtube.com/watch?v=Pdp_L5IxaNI


Next, set your desired boot order.
pcsupport.about.com/od/fixtheproblem/ss/bootorderchange.htmyou might have to change the little jumper on the hard drive to set it as slave

[regaining space - attachment deleted by admin]Hi guys
Thanx for the replies. I did remove the jumper, as according to the seagate web site instructions, removal of it told the disk to act as a slave. Also the instructions on the disk said the same. This made no difference. In the BIOS, with the seagate plugged in the only disk that was detected was the seagate!
In the end I have just copied the data over my network to the new PC, from the old one. Which was no big deal. Obviously the problem arises from the fact that the seagate is an IDE (very old), and that when, previoulsy, i plugged an old system disk into a new set up, that disk was a SATA, and as I have read, the problem that I have been experiencing wont occur if all the disks are SATA. And as its now virtually impossible to buy an IDE disk, I should not have this problem again.
Take it easy
KwisjQuote

only disk that was detected was the seagate!