Andy Goth wrote:
>
> > Best way is to find out what kind it is,but the next best is to look
> > closely at the bottom.and see how many jumpers there are on it,on most
> > drives there's only one,and that will be in the master position
> > already,so just move the jumper over one set of pins and you should be
> > in slave position. Sometimes you run into a drive that has a pin you
> > need to add to slave it,but not all that often.
> > look close for ma/sl/cs near the pins,master/slave/cable select It
> > should get it up and running in no time
>
> I remember seeing six pins, one jumper block, and no text.
>
> What kind of drive was it? The name "Quantum" sounds familiar. I'll
> look up its jumper block diagram (I have a bunch of them in the Ontrack
> help system). Okay... I picked the 170MB one.
>
> Here!
> +-----------------------------------+
> Power ----- � � �
> Connection +-� �
> � �CS SP �
> Data ------ � �| DS| �
> Cable � �| | | �
> Connection � �o o o �
> � �o o o �
> +-----------------------------------+
> Install jumpers on the jumper blocks as follows:
> Master / No slave present � DS
> Master / Slave present � DS or DS, SP
> Slave � None
>
> Next time I open up my computer, I'll verify whether or not it's a
> Quantum drive. If it is, I'll remove the jumper block (see the slave
> setting). I'll look up the other drive's settings and make it a master
> disk.
>
> Also, I'll have to change their location on the data cable. Is that
> right? The middle position is the slave. Right? That means I'll have
> to move things around a little bit in order to make everything fit. If
> possible, I'll free up the second half-height bay (in case I get a 5
> 1/4" floppy disk drive or something).
>
> I also read up on why there needs to be a driver saved in the MBR.
> Well, it's to load the Dynamic Drive Overlay. Quote:
> ^-------^-----^-- [DDO]
> "An Ontrack software driver that eliminates limitations of a system's
> BIOS and
> allows installation of large drives that could otherwise not be
> installed to
> full capacity."
>
> Then why the hell can't I access a large partition!?!
>
> The disk is formatted with the Ontrack Proprietary Format, which is to
> disallow access to the disk until the DDO is loaded. The explanation is
> that the DDO prevents accesses over the 1024th cylinder to wrap around
> back to the first cylinder. The OPF doesn't want to allow that to
> happen, so it makes sure that no ordinary BIOS can touch the disk.
> Must I load the DDO, or should I split up the disk into 1024
> cylinder-sized partitions, forget about the DDO, and use standard BIOS
> formatting? How do I find the size of a cylinder, anyway?
>
> A problem presented by the DDO is "the operating system must not require
> special code in the MBR." LILO?
>
> Perhaps I can put LILO into the primary partition, put DOS and Windows
> into that partition, and put Linux on another partition.
>
> Sorry about the long mail, but I had things I needed to say.
The drive you have drawn out is an ata,which sort of works backwards
from the 'normal' drive on that on you pull all of the jumpers to make
it a slave,and move it depending on whether there is another drive
present.on a 'normal' drive,you'll still have the same set of six
pins,but you'd want to move the jumper to the center set
I looked through my bookmarks,and came up with some hard
drive/jumpersetting places you may want to check out.
www.jps.net/rustyw2/harddriv.htm ,and www.jps.net/rustyw2/jumpers.htm
,or
www.bookcase.com/library/techref/harddrive can't remember if the
second 'd' was uppersase or not on that one.
merc.