Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Chip and Fast and Lattice 4.0
Message-ID: <45406@sun.uucp>
Date: 14 Mar 88 21:31:47 GMT
References: <3518@watcgl.waterloo.edu> <263@stsci> <3625@bloom-beacon.MIT.EDU> <45205@sun.uucp> <5425@well.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 22

In article <5425@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>	You forgot Copper lists, Chuck...  (or does that account for the
>other 1%?)

Definitely in the other 1%. When you get to building Custom Copper lists 
you should know everything that depends on being in chip RAM. 

When asked once why I didn't think the Atari programs, that stuff the
color registers in real time, were 'competition' for the Amiga I answered,
"Simple, because they use up the most of the available CPU cycles to achieve
 those effects, whereas on the Amiga there is a chip, the Copper, that was
 *designed* to play those kinds of games behind the CPUs back."

When I start describing what the Copper can do, these same people stop
wondering why one might want a custom coprocessor to handle these things.
I suspect as more people become aware of it's abilities, the more interesting
displays will be appearing. May take this moment to encourage everyone who is
going to DevCon to go to the Blitter/Copper talk. 

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.