When I have two hard drives on my primary IDE port and I remove the one at
the far end then my BIOS recognises the drive in the middle but then it
stops booting and says
"Primary Master Hard Disk fail".
Is there some sort of terminator I can put on the end of the ribbon cable to
fool the BIOS that the primary master drive is there?
"John Smith" <som...@microsoft.com> wrote in message
news:407bf379$0$81990$c3e...@news.astraweb.com...
To use cable select with two drives, you need specially modified cable. It
is not uncommon to damage an IDE cable with frequent use.
-Kent
--
Conor
If you're not on somebody's shit list, you're not doing anything
worthwhile.
Aren't all 80 conductor cables effectively "cable select" with the master at
the far end and the slave in the middle?
This would explain the original poster's problem. He pulls the master
off the cable and wonders why the computer won't boot. The answer is
because there is no master.
Jeff
--
Remove "no" and "spam" from email address to reply.
If it says "This is not spam!", it's surely a lie.
No. You can have master/slave anywhere on a normal cable. The reason master
is indicated at end is to minimize signal reflections in one drive systems.
In two drive system you should use master/slave jumpers or cut a wire in
cable between connectors.
> I often move my hard drives around between my home PCs.
Why ?
> I use 80-conductor ribbon leads. All my
> hard drives are configured for Cable Select.
> When I have two hard drives on my primary IDE port and
> I remove the one at the far end then my BIOS recognises
> the drive in the middle but then it stops booting and says
> "Primary Master Hard Disk fail".
Thats what it should say, there is no primary master hard drive.
Thats not necessarily a problem tho, many systems will
boot any hard drive visible. Not a terrific idea to have the
unterminated stub on a high speed 80 conductor cable tho
because you will get reflections off the unterminated stub.
> Is there some sort of terminator I can put on the end of the ribbon
> cable to fool the BIOS that the primary master drive is there?
Nope the poll for hard drives requires a specific response
from the hard drive to the Identify command etc.
You can obviously put a hard drive there, one that wont be
used for anything except keeping the bios drive poll happy.
Makes a lot more sense to not furiously move drives around tho.
"John Smith" <som...@microsoft.com> wrote in message
news:407bf379$0$81990$c3e...@news.astraweb.com...
--
DaveW
"John Smith" <som...@microsoft.com> wrote in message
news:407bf379$0$81990$c3e...@news.astraweb.com...
They should be.
>
>
Nope, just a standard 80-conductor cable.
Yes.
> You can have master/slave anywhere on a normal cable.
Define 'Normal'.
> The reason master is indicated at end is to minimize signal reflections in one
> drive systems.
Nope, "master is indicated at end" because of how the cable is keyed for
Cable Select.
You can perfectly mount a slave at the end connector in a one drive per cable
situation.
> In two drive system you should use master/slave jumpers or cut a wire in
> cable between connectors.
Clueless, but then what else can you expect from someone who can't even setup
his newsclient properly.
>
>
Nope.
> He pulls the master off the cable and wonders why the computer won't boot.
> The answer is because there is no master.
Right, so has nothing whatsoever to do with cable type nor connector location.
>
> Jeff
Nor would that have anything to do with the message displayed.
You probably set the drive to manual in BIOS and it now expects to see it.
Set it to auto. Bios will then skip it.
>
> Is there some sort of terminator I can put on the end of the ribbon cable to
> fool the BIOS that the primary master drive is there?
You usually call that a harddrive.
>
>
>
Have a peek between the cable and the connector bodies. You will find
that pin #28 is missing from the middle connector. Hence there is no
need for a cut in the wire, as the cable is already wired for "cable
select". In fact, if you did cut the wire, then you would have to cut
it at the end. This would make the middle connector the master, which,
in a single drive system, would result in the reflections you are
trying to avoid.
- Franc Zabkar
--
Please remove one 's' from my address when replying by email.
> and composed:
Interesting word choice in his case.
>
> > >
> > > Aren't all 80 conductor cables effectively "cable select" with the master
> > > at the far end and the slave in the middle?
> > >
> >
> > No. You can have master/slave anywhere on a normal cable. The reason master
> > is indicated at end is to minimize signal reflections in one drive systems.
> > In two drive system you should use master/slave jumpers or cut a wire in
> > cable between connectors.
>
> Have a peek between the cable and the connector bodies.
By dismantling it.
> You will find that pin #28 is missing from the middle connector. Hence
> there is no need for a cut in the wire, as the cable is already wired for
> "cable select". In fact, if you did cut the wire, then you would have to cut
> it at the end. This would make the middle connector the master, which,
> in a single drive system, would result in the reflections you are
> trying to avoid.
Nope, not if you connect it to the end connector.
>
>
> - Franc Zabkar
"John Smith" <som...@microsoft.com> wrote in message
news:407bf379$0$81990$c3e...@news.astraweb.com...
Why not just move the secondary drive to the master position?
Or tell the BIOS to "Auto" all drives ...
RwP
> No. You can have master/slave anywhere on a normal cable.
Err..not when using Cable select you can't.
You don't want to do that with that manual setting.
>
> Or tell the BIOS to "Auto" all drives ...
Hey, that sounds familiar, now where did I see that first.
>
> RwP
>
>
Hey Ron, here's another one.
>"Franc Zabkar" <fza...@optussnet.com.au> wrote in message news:rllp70do5g3guvtvp...@4ax.com
>> On Tue, 13 Apr 2004 10:50:07 -0700, "Kent_Diego" <No...@Nomicrosoft.com> put finger to keyboard
>
>> and composed:
>
>Interesting word choice in his case.
>
>>
>> > >
>> > > Aren't all 80 conductor cables effectively "cable select" with the master
>> > > at the far end and the slave in the middle?
>> > >
>> >
>> > No. You can have master/slave anywhere on a normal cable. The reason master
>> > is indicated at end is to minimize signal reflections in one drive systems.
>> > In two drive system you should use master/slave jumpers or cut a wire in
>> > cable between connectors.
>>
>> Have a peek between the cable and the connector bodies.
>
>By dismantling it.
Nope, just lift the cable slightly. That's what "peek" means. If I had
wanted you to dismantle it, I would have said so.
>> You will find that pin #28 is missing from the middle connector. Hence
>> there is no need for a cut in the wire, as the cable is already wired for
>> "cable select". In fact, if you did cut the wire, then you would have to cut
>> it at the end. This would make the middle connector the master, which,
>
>> in a single drive system, would result in the reflections you are
>> trying to avoid.
>
>Nope, not if you connect it to the end connector.
The point I was making was that a drive at the end of such a cable
would identify itself as the slave, if it was jumpered for CS mode.
Funny that, coming from you who obviously has never been to the SCSI group.
That is supposing you can read, which your other post shows you incapable of.
Clueless, totally missed the point, in several respects.
> Funny that, coming from you who obviously has never been to the SCSI group.
So because I don't post in a SCSI group that means I know nothing about
it? Don't you suppose that in the past 14 years or so I've been
building PCs and installing/setting up servers I may just have come
across them once or twice? Hell the first CD writer I ever saw was
SCSI.
Do you really have a clue?
They made it idiot proof now. Blue goes to mobo, black is for master
and grey is for slave.
No, you still haven't made any point.
> was that a drive at the end of such a cable would identify itself as the slave,
> if it was jumpered for CS mode.
So, what IS your point?
All you have done is making observations that apparently would have to do with
the point you are trying to make but still haven't made it. Let's hear your point.
>
>
> - Franc Zabkar
Obviously you have zero understanding of the concept of cable select.
"Conor" <conor_...@hotmail.com> wrote in message
news:MPG.1ae864486...@news.claranews.com...
> In article <pLVec.6143$ab3.889@fed1read02>, No...@Nomicrosoft.com
> says...
>
> > No. You can have master/slave anywhere on a normal cable.
>
> Err..not when using Cable select you can't.
When using a normal cable, you can't use Cable Select anyway ...
Or is your definition of "normal" a bit different from everyone
else's?
RwP
"Conor" <conor_...@hotmail.com> wrote in message
news:MPG.1ae92f786...@news.claranews.com...
> Strangely on my cable the end one is the master.
>
> They made it idiot proof now. Blue goes to mobo, black is for master
> and grey is for slave.
Not quite - I've seen idiots swap them end for end.
But that's not the first cable select cable design - Compaq, back in
the bad old days, used to use (at first go!) the middle connector as master
(since it was wired to the motherboard), then they'd lift the cable select
wire (28, IIRC) so that the END connector was slave.
Didn't believe that until I saw such a cable. Hopefully, there
weren't but about a dozen or so make ... sigh.
RwP
No, really ??? Wow !
Reading sure isn't one of your strong points, is it!
Or maybe you have very short memory:
read one sentence, read another and - boom!, gone is the first.
>
> They made it idiot proof now.
Obviously they must have had the likes of you in mind when they designed it like that.
1. He said 'normal' cable.
2. He said "cut a wire".
How much indication do you need that obviously (in his mind) he wasn't
talking about Cable Select cables?
3. Which was quite strange given the remark that he was commenting upon.
Anyone who answers to such a post as if it made perfect sense is clueless.
>
> Do you really have a clue?
Yes, do you?
Hey, you said that, not me, but you won't hear me disagree.
Try to read and apprehend, oh mighty clueless one.
> Don't you suppose that in the past 14 years or so I've been building
> PCs and installing/setting up servers I may just have come across
> them once or twice? Hell the first CD writer I ever saw was SCSI.
All that but still can't read or apprehend.
If you had ever been to the SCSI group you would have known that I am one
of THE experts in the SCSI group and you wouldn't have made that stupid
"You obviously know nothing about SCSI" statement that you now snipped.
> > Don't you suppose that in the past 14 years or so I've been building
> > PCs and installing/setting up servers I may just have come across
> > them once or twice? Hell the first CD writer I ever saw was SCSI.
>
> All that but still can't read or apprehend.
>
> If you had ever been to the SCSI group you would have known that I am one
> of THE experts in the SCSI group and you wouldn't have made that stupid
> "You obviously know nothing about SCSI" statement that you now snipped.
>
I've not snipped anything in order to hide it. I've snipped irrelevent
quoted text as required by good usenet posting. You might want to try
it. It saves you quoting several messages and a hundred lines of text
just to add a sentence.
It was a stupid, dishonest snip. You saved a whopping one sentence,
where you accuse Folkert of knowing nothing about SCSI. Then you
pretend like his response to your accusation was a claim that YOU know
nothing about SCSI, when the issue at hand, obviously, was Folkert's
knowledge level. Are you logically handicapped, or simply dishonest?
> It was a stupid, dishonest snip. You saved a whopping one sentence,
> where you accuse Folkert of knowing nothing about SCSI. Then you
> pretend like his response to your accusation was a claim that YOU know
> nothing about SCSI, when the issue at hand, obviously, was Folkert's
> knowledge level. Are you logically handicapped, or simply dishonest?
>
No, just fukcing tired after working 15 hour days. You do know what
work is?
It must be nice to be "expert" enough to pat yourself on the back. What an
unfulfilled husk of a human being.
Rita
"Conor" <conor_...@hotmail.com> wrote in message
news:MPG.1aea37b5b...@news.claranews.com...
> In article <p100801eabaacfqij...@4ax.com>,
> chr...@nospam.invalid says...
>
> > It was a stupid, dishonest snip. You saved a whopping one sentence,
> > where you accuse Folkert of knowing nothing about SCSI. Then you
> > pretend like his response to your accusation was a claim that YOU know
> > nothing about SCSI, when the issue at hand, obviously, was Folkert's
> > knowledge level. Are you logically handicapped, or simply dishonest?
> >
> No, just fukcing tired after working 15 hour days. You do know what
> work is?
>
There's no reason to justify yourself to that path little person who's sole
purpose is to bitch about other people's choice of browsers.
Rita
Just for an FYI to the group, all the 80 wire, ATA66 and faster cables
have to be cable select cables. It is part of the spec. Doesn't mean you
can't use the jumpers, just that cable select also has to work, with the
end drive being connecter being master, middle slave.
JT
> There's no reason to justify yourself to that path little person who's sole
> purpose is to bitch about other people's choice of browsers.
>
I take it you've previous experience of them?
Folkert, just a hint--arguing in the manner in which you are doing here does
not convey information of any kind, it does not shed enlightenment, it does
not create good Karma, it does absolutely nothing except annoy people.
He stated his point clearly and he did make his point and if you want to
claim otherwise that merely makes you look illiterate, not clever.
You seem like a sharp guy in a lot of ways but you seem to have this blind
spot with regard to the manner in which your statements will be percieved,
and it's a shame because this sort of thing makes you look trollish and
gets you killfiled, so people who otherwise could gain the benefit of your
superior technical knowledge will not gain such benefit.
Now, rather than thinking about this, I'm sure that you're going to apply
the "ready, fire, aim" response characteristic of rebels without clues, so
I'm going to tell you in advance to not waste your time.
>> - Franc Zabkar
--
--John
Reply to jclarke at ae tee tee global dot net
(was jclarke at eye bee em dot net)
My remarks were addressed to those people who wish to understand *how*
things work and *why* things are done in a certain way. OTOH, there
are those pathethic, plodding, pseudo-technicians such as yourself who
will continue to survive in the industry armed with only rote
knowledge, good colour vision, and a Phillips head screwdriver.
So here is my response from Monday, April 19, 2004 1:13 AM to the rest of
the newsgroups. (Followup-To now set back to the original set of newsgroups).
"J. Clarke" <jcl...@nospam.invalid> wrote in message news:c5r68...@news1.newsguy.com
> Folkert Rienstra wrote:
> > "Franc Zabkar" fza...@optussnet.com.au> wrote in message news:ouut7052m8m57d46h...@4ax.com
> > > On Wed, 14 Apr 2004 23:24:52 +0200, "Folkert Rienstra" <see_re...@myweb.nl> put finger to keyboard and composed:
> > > > "Franc Zabkar" fza...@optussnet.com.au> wrote in message news:rllp70do5g3guvtvp...@4ax.com
> > > > > On Tue, 13 Apr 2004 10:50:07 -0700, "Kent_Diego" <No...@Nomicrosoft.com> put finger to keyboard
> > > >
[snip]
> > > > > This would make the middle connector the master, which,
> > > >
> > > > > in a single drive system, would result in the reflections you are
> > > > > trying to avoid.
> > > >
> > > > Nope, not if you connect it to the end connector.
> > >
> > > The point I was making
> >
> > No, you still haven't made any point.
> >
> > > was that a drive at the end of such a cable would identify itself as the
> > > slave, if it was jumpered for CS mode.
> >
> > So, what IS your point?
> > All you have done is making observations that apparently would have to
> > do with the point you are trying to make but still haven't made it. Let's
> > hear your point.
>
> Folkert,
Leaky killfile, John?
> just a hint--
A hint, from you John?
Aren't you the one that is about to say that giving
hints "does absolutely nothing except annoy people"?
> arguing in the manner in which you are doing here does not convey
> information of any kind, it does not shed enlightenment, it does not
> create good Karma, it does absolutely nothing except annoy people.
>
> He stated his point clearly
Nope.
> and he did make his point
Clearly not.
> and if you want to claim otherwise that merely makes you look
> illiterate,
Funny that *you* of all people should say that, John.
You, who only believes in the "school of hard knocks".
> not clever.
No John, that actually makes you look quite stupid. I could have said
look as stupid as Frank except that he hasn't answered yet, so maybe
he got the hint and realized in time that he had no point and bailed out.
It's obvious that you failed to take up on that hint and that you "appear"
to "know" that having a slave as a single drive on a cable is some kind of
a problem. I have to say "appear" as even you avoid "making that point".
And you want to accuse me of trolling? Pot and kettle, John.
>
> You seem like a sharp guy in a lot of ways but you seem to have this blind
> spot with regard to the manner in which your statements will be percieved,
Well you may be quite right, especially the folk that write 'perceived'
as 'percieved' and have the same apprehension problems as yourself.
> and it's a shame because this sort of thing makes you look trollish
> and gets you killfiled, so people who otherwise could gain the benefit
> of your superior technical knowledge will not gain such benefit.
Well John, if they don't want to learn, that is *their* choice.
That doesn't bother me at all.
>
> Now, rather than thinking about this, I'm sure that you're going to apply
> the "ready, fire, aim" response characteristic of rebels without clues, so
> I'm going to tell you in advance to not waste your time.
John, "just a hint"--what makes you think that YOU are of any importance
whether I post a reply or not. Just like you didn't post this message for
my benefit I'll just post it for someone else's.
>
>
> > > - Franc Zabkar
Speaking of "rote" knowledge, I think that someone who fails to make his
point but apparently wants us to believe that having a slave as a single dri-
ve on a cable is a bad thing may well find himself to be in that same ballpark.
>
>
> - Franc Zabkar
Of course, none of this infighting over the corncob wouldn't be necessary if
SCSI were used in this situation. No need to worry about Master/Slave with
SCSI. Oh well, some people never learn.
Rita
I wrote no such thing, nor did I imply it. Clearly, English is not
your first language. And my point was made several times, with
diagrams for those who feel challenged by the written word.
Franc, please stop feeding the trolls.
Rita
Exactly, you chickened out when I asked you to explain (make your point)
when you said:
"
> > >This would make the middle connector the master, which, in a single
> > > drive system, would result in the reflections you are trying to avoid.
> >
> > Nope, not if you connect it to the end connector.
> >
> The point I was making was that a drive at the end of such a cable
> would identify itself as the slave, if it was jumpered for CS mode.
"
> nor did I imply it.
Ofcourse you did, you failed to respond to
news:c5n9b5$3nfrp$2...@ID-79662.news.uni-berlin.de
http://groups.google.com/groups?as_umsgid=c5n9b5$3nfrp$2...@ID-79662.news.uni-berlin.de
so yes, imply is all what you left behind.
> Clearly, English is not your first language.
Not making one's point is universal in any language.
> And my point was made several times, with diagrams
> for those who feel challenged by the written word.
Not in here (comp.sys.ibm.pc.hardware.storage) you did.
Even someone as challenged as you should have noted that, especially
when I let know that that little creep Clarke had set a Followup-To.
And *no*, you little weasel, you just fled to alt.comp.hardware.homebuilt
spewing your little tirade and then showing diagrams of how CS
is implemented, something that wasn't at all disputed by me.
You just cowardly avoided to clearup your last statement because
you suddenly realized that you were just a "pathethic, plodding,
pseudo-technician who will continue to survive in the industry
armed with only rote knowledge, good colour vision, and a Phillips
head screwdriver" *yourself* and that is what you fell back at.
The centre of dispute obviously was "reflections" on a "one drive
on a cable situation" where you clearly implied that having a slave
at the end of the cable somehow was to be a problem when first
you noted that making it master would cause reflections and
second, by avoiding that and attaching it at the end would make
it a slave. You don't say that unless you mean something by it.
I gave you an opportunity to explain yourself but you just
cowardly disappeared.
> Of course, none of this infighting over the corncob wouldn't be
> necessary if SCSI were used in this situation. No need to worry about
> Master/Slave with SCSI. Oh well, some people never learn.
>
>
>
> Rita
Let's not even attempt to list all the problems with setting unique scsi
device ID's and all the poor attempts to set them automatically. It's not
like IDE drives have a monopoly on poor configuration designs.