Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga
Subject: Re: Quetsions about the 3000...
Message-ID: <15007@cbmvax.commodore.com>
Date: 9 Oct 90 23:35:54 GMT
References: <90276.132159IO91461@MAINE.BITNET> <14916@cbmvax.commodore.com> <1791@shodha.enet.dec.com>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 24

In article <1791@shodha.enet.dec.com> ridder@elvira.UUCP (Hans Ridder) writes:
>In article <14916@cbmvax.commodore.com> daveh@cbmvax.commodore.com (Dave Haynie) writes:

>Except a bit of SCSI bus bandwidth is wasted, right?

I suppose...

>>A new device driver will apparently fix this, going to the fixed high
>>level commands in the new chip.

>So, does this mean that the 2091 (and 3000) using the new driver will or
>won't support reselection?  From your description, it sorta sounds like
>the problem was fixed by just not doing reselection in the driver....

The problem was circumvented by not doing reselection, programmable via
mountlist or RDB parameters.  That's not a fix.  A new device driver with
the now-working Western Digital high level SCSI commands should be a fix,
not a work around, to this problem.

>  Hans-Gabriel Ridder			Digital Equipment Corporation
-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	Standing on the shoulders of giants leaves me cold	-REM