Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!rutgers!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.hardware Subject: Re: More info on A2091 woes Message-ID: <17706@cbmvax.commodore.com> Date: 17 Jan 91 07:22:49 GMT References: <9696@cica.cica.indiana.edu> <1991Jan14.193336.13387@convex.com> <1991Jan15.155835.5230@javelin.es.com> <17655@cbmvax.commodore.com> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 31 In article greg@travis.cica.indiana.edu (Gregory TRAVIS) writes: >> Explanation of the problem and how to fix it deleted. > >THANK YOU Randell. I'll try your program to test if I've "really" turned You're welcome. Glad to help. >Let me suggest that Commodore do its best to let its dealers know about >this - they seem to be totally in the dark. I can't imagine what the >poor slob without Usenet access who's got the problem is doing. I'll pass the comment on to the US Sales company/etc. >Why didn't Commodore test for this problem? I discovered it the day >I bought my machine. Normal production tests are single-drive. Many multi-drive configurations were tested during development, and they all worked, since WD hadn't changed their part yet. WD made a running change to fix other problems in the non-A part (stuff we didn't use because it didn't work), and the new A part caused this problem. The non-A parts are no longer available, I understand. After the problem was noticed (and once we got a handle on it), we did a full matrix test of all chip revs/driver revs/boyer revs with different SCSI bus configurations. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)