Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!princeton!njsmu!mccc!dworkin!johns
From: johns@dworkin.Amber.COM (John Silvia)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: I want to see my Blitter in action..
Message-ID: <Pc6023w163w@dworkin.Amber.COM>
Date: 21 May 91 04:37:12 GMT
References: <1991May17.172153.23724@magnus.acs.ohio-state.edu>
Sender: news@dworkin.UUCP
Organization: Labyrinth II BBS
Lines: 28

>    All this talk about the Blitter has got me wondering..  Being a definite
> hardware novice (infant really)..  What is a simple way that I can see and
> compare the actions of my Blitter and '030??  I mean I've got these CpuBlit
> and FastBlit programs and I can't tell if they are doing anything worthwhile.
> 
>    So, offer me an experiment.. not too complex now, it's just curiosity not
> an obsession or lifetime dream..  Let me see my Blitter in action.. Thanks..

If you have CPU BLIT then there is a relativly simple test that will show 
you the speed of the blitter.

(This works nicely on my A3000/16)

If you have a program that supports color text, or can create text that uses 
more than 4 colors, then create a large text file, with lots of full rows 
and full columns, and lots of colors.

Now go into an 8 color workbench and open a shell.  Open the shell window as 
large as possible, and then place another window, much smaller, in front of 
the shell screen.  (I did this in 2.0, I hope you can too)

Now go into the shell, and type out that file behind the other window.

You should see a mess of the blitter slowing down all around that window in 
the middle, and as well, you could end up seeing "color shadows" that happen 
when there is a screen refresh before the entire color bitmap was updated.

Now run CPUBLIT and try it again - a lot better!