Conference hydra::amiga_v1

Do you have a mountlist entry for the second one and MOUNT it at boot/run time?

The 2090 may just search for the first one it finds. If you have only one
it'll find *it*. If you have 2, it'll find the first one and leave bringing up
the second to you.

JOhn

    I have 2 ST225's running on a 2090a with no problem.  The first drive
    is jumpered as UNIT 0 and the second drive as UNIT 1.  Did you really
    mean to say you jumpered both your drives to UNIT 1?  The cables I made
    are keyed so there is no way to twist them.  You should have 3 cables
    to hook up 2 drives.  If you have one drive working then hook up the 20
    pin cable EXACTLY the same orientation as the working drive.  The other
    cable is a 34 pin cable with 3 connectors, one to the 2090 and 2 to
    attach to the drives.  Hook up the second drive connector EXACTLY the
    same orientation (no twists) as the working drive.  
    
    You should also check to see if the drive has a bus terminator.  Only
    the last drive physically on the 34 pin cable should be terminated.  I
    believe the 2090 manual mentions that.
    
    Good luck,
    
    ...Ed
    
    PS: where did you mount the second drive?  I put mine external in a
        an old RX180 case and build a custom cable to attach it.

    re .0,.1
    
    John's entry also reminded me of one more thing.  You will need a
    mountlist for RES0 and RES1 (plus partitions if you want) before you 
    can PREP the drives.  Once PREPed you can then format DH0, DH1 and mount
    and format any partitions.  No mountlist entrys are needed for DH0 and
    DH1 as they are configured automagically.  This is explained fairly
    well in the 2090 installation manual.
    
    
    ...Ed

    Also, don't forget to make a small 1 cylinder partition on the second
    drive (IT get mounted automaticaly by the A2090 in the OLD file
    system).  Then get your mountlist take care of the rest of the drive in
    the new file system.  Another thing to remember is that DH0 is the name
    of the first partition on the first drive, and DI0 is the name of the
    first partition on the SECOND drive.  Additional partitions can be
    called anything (ie: DEC:, AMIGA:, DRIVE: ...) as long as they match
    the mountlist.
    
    Jean
    

    Re .4:
    
>   ...  Another thing to remember is that DH0 is the name of the first
>   partition on the first drive, and DI0 is the name of the first
>   partition on the SECOND drive.
    
    OOPS!  I recently installed CrossDOS on my A500.  CrossDOS names the
    MS-DOS formatted floppies DI0, DI1 ...  I don't have the problem NOW,
    but someday I might add a second hard disk and I'd like NOT to have to
    punt CrossDOS to do so.

RE: .5

>   OOPS!  I recently installed CrossDOS on my A500.  CrossDOS names the
>   MS-DOS formatted floppies DI0, DI1 ...  I don't have the problem NOW,
>   but someday I might add a second hard disk and I'd like NOT to have to
>   punt CrossDOS to do so.

Look at the mountlist that CrossDOS supplies! You can name the drives A:, B:,
C:, and D: as I did. I ALREADY have a hard disk named DIn: (N=1..5) and this
works just fine for me!

	-SES

>    the new file system.  Another thing to remember is that DH0 is the name
>    of the first partition on the first drive, and DI0 is the name of the
                                                    ^^^
>    first partition on the SECOND drive.  Additional partitions can be
>    Jean
    
Jean, you better come back to the Great White North, all that sun and
stuff down in Florida must be getting to you :-) 
The 1st partition on the 2nd drive is DH1 - you get DIn when you add a 
second controller.

 mark

Thanks - that was a lot of stuff..
There's one thing that's still unclear to me:
If i had preped the two harddisks (RES0: RES1:) - do i have to see all
two drives after the binddrivers command (i.e. assign shows that there is
a device dh0: and dh1:) ?
I was always looking for that - but the second drive was never seen after
the binddrivers command... 
I'm sure all two drives have a bus terminator - maybe this another problem.

Well - i will test it out tonight (and over the weekend if necessary...)

Bernhard

P.S.: RE .2: I also build two custom cables to my external RD 53 - I'm still
      looking for a nice case to put it in...

re: .8

You may not see DH1: until you try and access it.  Try doing a directory of DH1:
from CLI.  On my system I have DH0: and DH1: only on cyl 0-4 and I am running
the FFS on the rest of both disks HD0: and HD1:  I have mount list entries for
RES0:, RES1:, HD0:(FFS partition on drive 0) and HD1:(FFS partition on drive 1).
I do not get an ICON for DH1: as i never access it.  If I remember correctly it
also doesn't show up in CLI>INFO unless I access it first.  May be your DH1: is
already there and working!


Good luck,

...Ed 

    Thanks for all hints and suggestions...
    ...but this was a really strange problem.
    Everything was setup ok - I had the right cables & jumpers
    already installed. But the second drive still wasn't seen...
    So i began to wonder what are those "W1" and "W2" jumpers on the
    RD53 good for. I tried the "W1" - no success...
    Then I set the "W2" jumper and guess what happened - IT WORKED!!!!
    I still don't known what are those two jumpers good for - but it
    seems the "W2" jumper has to be set - or your second HD will never be
    correct recognized.
    
    Bernhard

    Looking at the RD53-A Tech-Infos and Reference-Card, the W1/W2 Jumpers
    should ALWAYS be CLOSED plus the Drive-Select-Jumper you want (in our
    case only DS1 for DH0 and DS2 for DH1)
    
    Ralf
    ====
    
    PS. What about the Termination-pack. Has it to be only on the second
    drive?? And when i want only the first drive must i connect the 5 volt-
    line to the second drive to make sure the bus is correct terminated??

    I run my 2nd ST225 externally on a custom cable powered in an old RX180
    case.  Quite often I have the second drive powered off and have
    suffered no ill effects.  
    
    ...Ed

    FWIW:
    
    I also have 2 ST-506 drives coming from an Adaptec4000a.  I have the
    termination pack in the second drive.  I can run with one drive by just
    turning off the 2nd drive with no ill effects.  I do not think the
    drive bus is properly terminated by doing this but my cable lengths are
    short enough to get away with it.
    
    md