Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!pikes!boulder!ncar!asuvax!mcdphx!mcdchg!ddsw1!karl
From: karl@ddsw1.MCS.COM (Karl Denninger)
Newsgroups: comp.unix.xenix
Subject: Re: SCO 2 Harddisk controllers
Summary: What FEATURE LEVEL is that 1006 card?
Keywords: SCO DISKS CONTROLLERS
Message-ID: <1989Oct2.222253.25134@ddsw1.MCS.COM>
Date: 2 Oct 89 22:22:53 GMT
References: <180@promark.UUCP> <1176@ispi.UUCP>
Reply-To: karl@ddsw1.MCS.COM (Karl Denninger)
Organization: Macro Computer Solutions, Inc., Mundelein, IL
Lines: 30

(lockup problems)

In article <1176@ispi.UUCP> jbayer@ispi.UUCP (Jonathan Bayer) writes:
>I did essentially the same thing, although I modified a 1006V-MM1 for the 
>alternate interrupt and address.  I tried it with a Seagate 4051 (40 meg drive)
>and had the identical problem.  I think that there is something in the
>controller card (my guess only) that may be dying.  I did notice that
>when the system died the drive hooked up to the second card was
>permenantly selected (I had the drive led on the computer hooked up to
>the second controller card, and it went on and stayed on.)  My feeling
>is that this seemed to occur during periods of heavy io.
>
>
>If the Adaptec card works could you let me know?

If you have a Feature 5 level card, make sure you have it jumpered for
NON-LATCHED mode.  If not, you need to do yet another mod.

The F5 cards WILL lock up like this if you have them running in latched
mode.  We went back to a Feature 3 card, and the problem disappeared.  I
haven't thoroughly checked the F5 card with the jumper installed, but it
_appeared_ to solve the problem.

Yes, it is a controller glitch.

--
Karl Denninger (karl@ddsw1.MCS.COM, !ddsw1!karl)
Public Access Data Line: [+1 312 566-8911], Voice: [+1 312 566-8910]
Macro Computer Solutions, Inc.		"Quality Solutions at a Fair Price"