Secondary Master on Primary Controller

[CloudRanger99]

Hello,
I recently purchased a used, working computer. Upon closer inspection, within the Award BIOS, I noticed that the only Hdd was configured as a Master on the Secondary conroller. However, according to the mobo manual, this one and only Hdd is physically connected and jumpered as a Master to the Primary IDE controller and is the only device on a I/O ribbon cable with only 1 connection!

Can this be possible?

I double checked to verify I was reading the correct the mobo manual and looking at the pictures correctly. Infact, the position of the Primary IDE controller is consistent to other Socket7 board layouts. It is an SQ575 mobo by GVM BCM

According to the Hdd spec sheets, the Hdd is jumpered as "Factory default setting" for being the only Hdd. It is a Western Digital 1.6 IDE drive ( WDAC21600 ).

I am having a problem getting a second Hdd recognized on this machine. I don't know where in the BIOS settings to enter in the second Hdd values. I tried configuring it as a Slave on the Secondary controller but it doesn't get recognized and this configuration also halts the MBR from getting seen on the Master Hdd device. (The second Hdd is jumpered as a Slave.)
I also tried configuring the second Hdd as a Slave on the Primary but this also fails. (Can't remember if boot up succeeds in this arrangement.) I am using I/O ribbon cables with 2 connections and rejumpered the original Hdd as "Master of 2 devices" btw.

Regardless, can a Master IDE device on a Primary IDE controller be configured within the BIOS as a Master device on the Secondary controller? And what would be preventing the second Hdd from getting seen and preventing the MBR on the Master from getting found preventing the boot up?

Thanks, Internet Ranger , aka., CloudRanger99

 

[CloudRanger99]

I found out the motherboard manual was wrong and it depicted the Primary controller and Secondary controller in reversed positions. I swapped the Hdd cable and the BIOS's Auto Detect setting saw the hdds as Primaries now.

I also discovered that the second hdd was not jumpered correctly thus halting the boot process. Infact, when troubleshooting and verifying the jumper pin setting was correctly configured as a Slave, I wasn't even looking at the jumper pins! I was looking at some pins used to connect to a hdd diag device. The jumper pins on this hdd were underneath the hdd. After correcting that, I got the boot up resolved.

Another closed case due to bad documentation and user error. See ya.