Path: utzoo!mnetor!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.sys.amiga
Subject: Re: Bugs (Hardware?)
Message-ID: <3027@cbmvax.UUCP>
Date: 27 Dec 87 23:37:47 GMT
References: <6284@jade.BERKELEY.EDU>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 29

In article <6284@jade.BERKELEY.EDU> spencer@eris.BERKELEY.EDU (Randy Spencer) writes:
> In article <8712081740.AA03658@jade.berkeley.edu> U613042@HNYKUN11.BITNET (Olaf Seibert) writes:
> 
> ...Move the mouse pointer below the (approx.) 213th line, then move it
> ...horizontally to the left and/or to the right. Not too slowly, please.
> ...You might notice that you see TWO pointers, close to each other.
> ...When you stop moving, there is only only one pointer, as usual.
> 
> Yes, This has been driving me crazy, good to know that I am not the only
> one around here that sees these things.
> 
> ...This seems to be a hardware bug, just like the one that all sprites
> ...below some line on the screen (line 213??) all get the colors of sprite
> ...0. (Note that I have not verified this myself).
> 
> ...So, any hardware type from Commodore wants to comment on this? Thanx!

Lots of things get funny in overscan, especially in interlace mode.  In
some cases, this simply reflects the way the chips work, in other cases
there are software or hardware problems where either the person doing the
work didn't adequately contemplate the impact of overscan or didn't think
it was a major issue.  Hopefully these will get cleaned up in the long run
but for now, overscan is a somewhat excpetional mode of operation that you
can either live with or avoid using.

-- 
George Robbins - now working for,	uucp: {uunet|ihnp4|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)