Re: Master/Slave issue
- From: "Timothy Daniels" <NoSpam@xxxxxxxxxxxxx>
- Date: Thu, 8 Nov 2007 12:24:25 -0800
"SonomaAirporter" wrote:
"Timothy Daniels" wrote:
To make a particular HD control booting, it should only
be necessary to reset the Hard Drive Boot Order in the BIOS.
(The HD Boot Order may be called something else in your
particular BIOS.) Completely disconnecting HDs higher in
the HD Boot Order shouldn't be needed.
The BIOS setting for boot sequence is floppy A:, HD C:, CD.
The Hard Drive Boot Order is not the Device Boot Order.
What you refer to above is the Device Boot Order, which prioritizes
the device types. The Hard Drive Boot Order, OTOH, prieoritizes
the hard drives that the BIOS finds, and the MBR of the HD at the
top of that list will be known as "rdisk(0)" by the loader, and it will
get control at boot time. Various BIOSes call the Hard Drive Boot
Order by various names, but it is usually presented on the BIOS's
menu screen as a list of the connected hard drives - which you can
rearrange according to your heartfelt desires.
Removing the PATA C: and WD E:, the SATA becomes C: and
boots properly. When the PATA drive (jumpered for slave) and
the WD are added back, the SATA is still C: and boots properly,
but the PATA & WD show up as UNKNOWN.
Right, I got that. And I asked how the WD hard drive was jumpered
because, as I wrote, the jumpering scheme for Western Digital hard drives
is different from those of other manufacturers. Western Digital even
differentiates between a lone Master on the channel and a Master with
a Slave on the same channel.
Your stated problem may have to do with the differing jumper
modes used by Western Digital and Maxtor/Seagate. You may have
2 slaves on the same IDE channel. Check the HD cases of each HD
to see that they are actually put into differing Master/Slave modes.
Are you saying that you cannot have to slaves on the same channel
(i.e. one must be master and the other slave)?
Yes. That is the purpose of the Master/Slave setting - to differentiate
the two hard drives for the IDE controller.
I even tried adding back only one slave and BIOS setting still shows
up as UNKNOWN on that one slave.
Which HD was it - the Maxtor or the WD - and what did you do
to set it as Slave?
BTW, when you make a clone on F: partition of your C: partition,
remove the HD containing the C: partition before starting up the clone
OS for its first run..........
This is a non-issue since I started up the cloned drive first without its
parent present.
Good. I suggest you obtain and read the User's Manual for your
BIOS to find out how to set the Hard Drive Boot Priority for your
hard drives. It may be called something like "Hard Drive Enabling"
or "Hard Drive Priority" or something else. Look especially for some
mode which may be ONLY for SATA drives and another which
may include SATA drives along with PATA drives. Your BIOS may
be set for the former mode, i.e. enabling SATA and disabling PATA.
Be aware that by altering the Hard Drive Boot Order, you will alter
the meanings in boot.ini of "rdisk()", so if your boot.ini file specifies
booting from "rdisk(0)", disk "0" may become disk "1" when you put
in a 2nd and/or 3rd hard drive. That will be evident by the system
booting from one HD when that HD is the only connected HD, and
some other HD taking over the boot control when you add in other
HDs. It appears from various postings that in some BIOSes, when
you enable a SATA drive, the PATA hard drives are moved down
in the Hard Drive Boot Order. That they aren't recognized by your
BIOS suggests that your current enablement setting disables PATA
HDs. So, get to know your BIOS as well as the WD jumpering
scheme.
*TimDaniels*
.
- References:
- Re: Master/Slave issue
- From: Timothy Daniels
- Re: Master/Slave issue
- Prev by Date: windows locale detection using windows registry Options
- Next by Date: Re: Saving Desktop Settings
- Previous by thread: Re: Master/Slave issue
- Next by thread: Re: Master/Slave issue
- Index(es):
Relevant Pages
|
