Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!mcdphx!phx.mcd.mot.com!teroach!stan
From: teroach!stan@phx.mcd.mot.com (Stan Fisher)
Newsgroups: comp.sys.amiga
Subject: Re: 2091 Interface
Message-ID: <13946@mcdphx.phx.mcd.mot.com>
Date: 1 Nov 90 23:23:40 GMT
References: <5357@crash.cts.com> <13925@mcdphx.phx.mcd.mot.com> <15515@cbmvax.commodore.com>
Sender: listen@mcdphx.phx.mcd.mot.com
Reply-To: teroach!stan@phx.mcd.mot.com (Stan Fisher)
Organization: Motorola Microcomputer Group
Lines: 31
Summary:
Keywords:

In article <15515@cbmvax.commodore.com> andy@cbmvax.commodore.com (Andy Finkel) writes:
>Since the cause of the data loss is an extra interrupt during the SCSI
>reselect, turning off reselection on all drives will reduce the
>occurance of the problem to zero.

That's interesting...  I still get SCSI buss hangs, just not near as
often.

>You are incorrect.  The problem is that Western Digital came out with
>a *new* revision of their chip that works slightly differently than
>the old one; its only the new chips that show the problem.  Their
>low level SCSI state machine has changed; since we may be the only
>ones using their low level command set, and the only ones who
>are using (or want to use) reselection on disk drives, 
>(as well as supporting multitasking so you could initiate two copies)
>we got bit by the new chip.

Dang!... It never fails... as soon as I believe I've gathered all the facts
and then let myself get rialed up and make flames with them, I get crow served
for lunch :^)   I really was going on what I'd been told by dealers and other
Commodore personel.  Sorry.   (guess I gotta refrain in the future)

>andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
>Commodore-Amiga, Inc.

Flames withdrawn..   but I still don't like being charged for bug fixes.

Stan

  Stan Fisher -  stan@teroach.phx.mcd.mot.com  -  asuvax!mcdphx!teroach!stan
  Motorola Microcomputer Division, Tempe, Arizona   -   Voice (602) 438-3228