🚀 go-pugleaf

In <47875u$3fb@homer.alpha.net>, syndesis@beta.inc.net (John Foust) writes:
>In article <46tglp$a1c@panix.com>, fishman@panix.com (Harvey Fishman) says:
>>
>>I have a somewhat similar setup (Micronics system board, different number
>>of drives, and internal external), but your problems are the classic
>>symptoms of bad termination.  The AHA-2940 is ____****EXTREMELY****____
>>finicky about having that spot on.  I have been using SCSI since 1989, but
>>most of that was with an AHA-1542B.  When I moved to the AHA-2940 earlier
>>this year, it was like starting over learning from scratch.  You MUST have
>>perfect cables and terminations.  It is a great card, but it is fussy.
>
>Grumble-fritz...  I'm having trouble with a 2940 in a new Endeavor
>Pentium 133 under WinNT 3.51.
>
>Everything appears to be fine except for random
>"bad data" errors when backing-up to an external Exabyte 8500,
>but it's also reported that it couldn't read from internal
>hard disks when backing-up, too; and WinNT nicely took the
>drive offline and kept running.
>
>I've double-checked the termination resistors on the three
>internal HDs and one internal CDROM.  With any external
>device, either the 8500 or a Sony 920 CD-R, I have to set
>the Ctrl/A adapter termination the *wrong* way (termination on)
>for the system to boot...  otherwise it hangs after the boot-up
>SCSI bus scan.
>
>The external 8500 is on a short 3 foot external cable, 
>my only theory is that the internal ribbon may be a bit long..
>
>Does any of this ring a bell?  I think I'll invest in a
>nice SCSI-view cable, and active terminators...
>
>How can I check the version number of the Adaptec's driver,
>and how can I get an update?
>
>- John

I've had similar problems with an older hp hard disk.  It turns out
that many scsi devices don't handle disconnect very well.  My
solution was to disable disconnect and everything started working
great.

Joe