Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!sol.ctr.columbia.edu!emory!hubcap!ncrcae!sauron!stevem
From: stevem@sauron.Columbia.NCR.COM (Steve McClure)
Newsgroups: comp.sys.amiga
Subject: Re: 2091 problems (was JrComm 1.0)
Summary: Being addressed
Message-ID: <2235@sauron.Columbia.NCR.COM>
Date: 20 Jul 90 21:00:27 GMT
References: <1500@faatcrl.UUCP> <25990@usc.edu> <1509@faatcrl.UUCP> <26053@usc.edu> <1518@faatcrl.UUCP> <13242@mcdphx.phx.mcd.mot.com>
Reply-To: stevem@sauron.UUCP (Steve McClure)
Distribution: na
Organization: E&M-Columbia, NCR Corp, W Columbia, SC
Lines: 23

In article <13242@mcdphx.phx.mcd.mot.com> stan@teroach.UUCP (Stan Fisher) writes:
+
+I seem to be one of the lucky ones that has had no problems since I 
+followed the procedure for changing which FFS is being used on my 2091...   
+
+My problem, and one I've heard of elsewhere, which doesn't seem to be being
+addressed by Commodore is when you've got multiple fast SCSI devices (drives)
+and do copies between the two drives (physical drives, not just partitions)
+the whole system hangs with the drive access LED stuck on.  The only way out
+is to re-boot and then wait for the validator to do it's thing.
+There seems to be a REAL problem with the SCSI bus arbitration on the 2091!
+Can't someone at Commodore comment on this?
+I already posted this problem to c.s.a.t and heard nothing back.

My dealer quoted a CBM memo that new 2091 firmware was forthcoming to fix
this problem.  Supposed to be here end of July.

Steve
-- 
----------------------------------------------------------------------
Steve		email: Steve.McClure@Columbia.NCR.COM	803-791-7054
The above are my opinions, which NCR doesn't really care about anyway!
CAUSER's Amiga BBS! | 803-796-3127 | 8pm-8am 8n1 | 300/1200/2400