Re: Adding bigger hard drive


"Jaimie Vandenbergh" <jaimie@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:pubne2p1hjlvdktsfqmjrrme2f5of8tut9@xxxxxxxxxxxxxxxxxxxxxxxxxx
On Wed, 23 Aug 2006 02:15:46 +0100, John Jordan <junk@xxxxxxxxxxxx>
wrote:
Jaimie Vandenbergh wrote:
On Wed, 23 Aug 2006 00:34:28 +0100, John Jordan <junk@xxxxxxxxxxxx>
wrote:
Jaimie Vandenbergh wrote:

Nobody mentioned yet that this is wrong? If the cable is an
80conductor one, then the Master must be at the end of the cable, the
Slave in the middle.

Not true. If you have a single device on a two device cable it should
always go at the end, but that's for signal integrity reasons. Otherwise
master/slave are just IDs. Cable select assigns the master ID to the end
device and slave to the middle, but that's just a standard rather than a
requirement.

Have you got a reference for that?

Not sure where I gained the knowledge from originally, but this seems to
be comprehensive:

http://www.storagereview.com/guide2000/ref/hdd/if/ide/confJumpering.html

That says you can put a device anywhere on a 40 conductor IDE cable,
which is fine. When you follow the linky from there to the 80
conductor ribbon page, it says

"Connector Assignments and Color Coding: For the first time, the
80-conductor cable defines specific roles for each of the connectors
on the cable; the older cable did not. Color coding of the connectors
is used to make it easier to determine which connector goes with each
device:

* Blue: The blue connector attaches to the host (motherboard or
controller).
* Gray: The gray connector is in the middle of the cable, and goes
to any slave (device 1) drive if present on the channel.
* Black: The black connector is at the opposite end from the host
connector and goes to the master drive (device 0), or a single drive
if only one is used."

I'll continue to go with that, I think!

Cheers - Jaimie
--
'Rings! Rings! Wherever they may be
I am the Lord of the Rings,' said he
'And I'll find them all, wherever they may be
And I'll bind them all in the dark,' said he

And you are also correct in having the drives as masters and the cds as
slaves...nothing to do with the cds, it is simply better to put each hard
drive on a seperate IDE channel for maximum performance and transfer rates
when moving data between the 2 drives. On programs that are for video,sound
and photo editing for example, the temp folder should be on a different
drive from which the application is installed for maximum performance, and
the temp folder, on a sperate drive, on a seperate IDE channel gives the
ULTIMATE performance.. I quote those 3 types of program only as an example!



.

Relevant Pages

  • Re: Help installing Fedora
    ... Each IDE/ATA channel can support either one or two devices. ... giving each device a designation as either master or slave, ... the reasons why drives don't always "play nicely together" has to do ...
    (comp.os.linux.setup)
  • Re: Upper Lower Filters in XP Registry
    ... I'd just switch the middle and end connectors (moving the drives ... currently have jumpered as Slave should be that way - some drives cannot ... support being a master. ... > the drive to the slave CD and the top connector to the master DVD. ...
    (microsoft.public.win2000.registry)
  • Re: Locked up again! What can I check- Im on another box
    ... >> If you have 2 drives, jumpered as master and slaves, the master drive ... >> slave drive uses the connector at the end of the ribbon. ...
    (Fedora)
  • Re: Windows XP does not detect optical drive connected to secondary slave IDE
    ... I connected the DVD to the secondary IDE channel as slave - the ... Both drives are correctly detected by the BIOS, ... connected to the cable's middle connector. ... a Slave on the Primary IDE channel, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Fedora vs. Ubuntu (hijacked: can I dual boot FC and Kubuntu?)
    ... can't seem to keep master and slave out of each other's hair. ... You could plug something like "master slave ata corruption" in a search at Google and get some interesting reading, ... In the MSWindows universe they were familiar with, there were enough reports of silent corruption they figured it was best to stay with one channel, one drive, particularly when building RAID on ATA controllers. ... I have seen drives fail much earlier than was reasonable, but the failure patterns seemed to be more related to the issue of ATA drives failing to sync the cache to the disk when told to, or maybe even just cheap recording surfaces. ...
    (Fedora)
Loading