Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.misc
Subject: Re: Possible hardware prob with A3000
Message-ID: <22038@cbmvax.commodore.com>
Date: 30 May 91 08:24:59 GMT
References: <1991May22.040952.7767@bronze.ucs.indiana.edu>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 21

In article <1991May22.040952.7767@bronze.ucs.indiana.edu> tagreen@lothario.ucs.indiana.edu (Todd Green) writes:

>The screen does not correctly draw itself quite frequently. That is if
>if move a WB window garbage sometimes is left on the screen where the
>window used to be (or the window itself gets corrupted).  I have not
>had any problems with programs doing this under 2.0.3, just WB itself.
>Actually I take that back.  The clock program that C= provides also
>leaves artifacts on the screen when it updates its hands. If I select
>"ResetWB" the screen corrects itself.

That sure sounds like a bad Agnus chip to me.  Many moons ago, we had some
early prototype 512K Agnus chips, back before the A500 and A2000 were out,
that did that.  I don't know of anything else that could cause it.  I guess
a poorly socketed Agnus might do that 1:10,000 times or so....



-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"This is my mistake.  Let me make it good." -R.E.M.