Conference hydra::amiga_v1

    
>    P.S.  where should I connect harddisk light on 2090?  Can't get it to
>    work either, tried "LED" and "SCSI" on 2090, both polarities;  the way
>    it is now (can't remember which) it is on at power-up, goes off when
>    binddrivers starts - and then above problem.

The 2090 has a small bug with the LED and SCSI drives - It only turns on the
LED during zorro bus DMA which is so quick that you never see the LED
turn on.

When I had a 2090 I built a circuit that stretched the pulse so that 
you could see it. The schematic is at WJG::AMIGA:LED_PULSE.PS


john

    Thanks John.  I'll give it a shot.  Are you using a 2090, and if so,
    what's the polarity of the "SCSI" pins for the led (I guess I could try
    both ways)?
    
    Just thought, I have RES0: and DH0: entries in my mountlist file before
    the RES2: and DH2: entries.  Could it be that when binddrivers runs and
    finds the board, it attempts to mount the RES0: and DH0: partitions for
    the absent ST-506 drive, and just sits there waiting for a response? 
    (I'll try removing those entries tonight).
    
    Is it true that RES2: and DH2: are automatically mounted?
    
    Thanks,
    
    John

I don't use a 2090 anymore, I have a gvp hardcard.

If I remember right, you need to mount the RESx: partitions only
for prep. After that,the first DOS partition must be Old File System
and it is mounted automatically by the 2090 roms.

Make sure you set the SCSI ID's right (scsi id 0 == res2: I think)


What happens if you warm boot while binddrivers is hung?

I heard in another note that the 2090 is being worked on at Commodore.

john

    I still have a RES0: and DH0: in my mountlist and still
    use a A2090(A) with a SCSI (DH2:).
    1) Yes DH2: get mounted "OLD FILE SYSTEM ONLY" automaticaly.
       (If the HDdisk drawer is in your expansion drawer, obviously)
    2) You should make DH2: only a few cylinders to boot, then
       mount the second partition in FFS, right after the mount
       assign all your directories (C:, LIBS:, fonts:,SYS: etc..) to 
       the second partition that now will act as your boot disk.
    
    That is the way the A2090 works (Til' WB2.0 comes out at least).
    
    Have fun,
    Vince,

    Here's a summary of the problem that I'm sending to CBM; maybe they
    know about it.
    
	This problem occured after the installation of a 2090 hard disk
controller with a Conner CP3100 104 Meg SCSI drive.  It occurred only after the
drive was Preped and formatted.  

	The startup process after power-up or warm boot halts during the
execution of the BindDrivers command.  The system does not crash.  The command
interface will echo carriage return characters, but does not respond to break
(^C).  At a very low rate of occurence, this will not happen, and the system
will boot normally; all of the hard disk partitions are mounted, and all
function properly.

	When the problem occurs, if the drive data cable or power cable is
removed and the system reset, the machine boots normally, except, of course,
that the drive's partitions are not found.  If the data cable is reconnected
without resetting, the partitions may be mounted manually, and all such mounted
partitions function properly.

actions taken:

1. cleaned controller card fingers - no change.
2. re-seated controller card's socketed components -no change.

	I beleive that there is an anomolous drive/controller interaction such
that the BindDrivers command hangs when it attempts to mount the RES2: and DH2:
partitions.

This is what I'm going to try tonight:
    
	The 2090 documentation states that only the first SCSI drive's reserved
partition (RES2:) and first partition (DH2:) are automatically mounted.  If the
hypothesis is correct, and the system can be reconfigured such that no
partitions are automatically mounted, perhaps the problem can be avoided.   

	The drive will be reconfigured as SCSI unit 1, which is Amiga unit 3,
the mountlist entries for the drive's partitions changed accordingly, and  an
entry for the first partition added.  Commands to mount the reserved and first
partition will be added to sys:s/startup-sequence.  

    
    John

    Solution - don't use the Conner drive w/ A2090.  Found that Quantum 80S
    works fine.  Looking into Conner problem, it be nice to be able to use
    it, any suggestions welcome.
    
    Thanks,
    
    John

    it sounds like the Conner is taking too long to be ready for the A2090
    to access.  That's a "feature" of some SCSI harddisks.  The trick is
    to find out if there is any way to increase the timeout time in the
    A2090 software.
    
    As to if this is a "feature" of this particular model, I have no idea.
    It could just be a flakey harddisk.
    
    Dave

    Just recieved the Conner manual.
    
    Start time	typical: 15 seconds
    		maximum: 20 seconds
    
    	You might be right Dave.  I tried delaying BindDrivers to no avail,
    but maybe if I powered the drive before the system it would work.
    
    John

    I have a Conner CP3200.  My hard drive has always been powered
    separately from the cpu, but I know that it takes a long while to
    come "ready".  Since the drive is in an external case, I power it up
    first and allow it to complete its self-test and load heads, then power
    up the amiga.
    
    md
    

    re: .8
    
    Where did you send to get the Conner manual?
    
    john
    

    I called Conner's Ma. office in Walpole:
    
    Conner Peripherals Inc.
    1600 Providence Highway
    Walpole, Ma. 02081
    Tel 508-660-1088
    Fax 508.668.2208
    
    for those on the left coast:
    
    3081 Zanker Road
    San Jose, Ca. 95134
    Tel 408-456-4500
    
    Japan: (81)3-597-8321
    
    Europe: (49) 89-811-2097