Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!dogie.macc.wisc.edu!uwvax!puff!gumby!pochron
From: pochron@gumby.cs.wisc.edu (David Pochron)
Newsgroups: comp.sys.amiga.tech
Subject: How do you restore the CList vector... (Was: Re: Fast Scrolling)
Keywords: copper, multitasking, hogging the system
Message-ID: <3909@puff.cs.wisc.edu>
Date: 30 Nov 89 20:58:32 GMT
References: <6072@ucdavis.ucdavis.edu> <7182@cbnewsm.ATT.COM>
Sender: news@puff.cs.wisc.edu
Reply-To: pochron@gumby.cs.wisc.edu (David Pochron)
Organization: U of Wisconsin CS Dept
Lines: 16

All this talk reminded me of a question I have had for a while...
I was doing some experimenting with the Copper list and wanted to create
a whole new Copper list (like in the Hardware ref. guide.) That was no
problem, however, when I tried to restore the screen to the original display,
it never came back!  ReThinkDisplay(), et al. doesn't seem to do it, even
opening a new screen doesn't seem to work once I have written directly to
the Copper list vectors.  Does anyone know what structs (and fields) the
lowest-level copper list vectors are stored by the OS which eventually get
written to the hardware copper vectors? It seems the only way to get the
display back is to just re-write them manually after I'm done stealing the
chips.


       -- David M. Pochron  | "Life's a blit,
                            |  and then you VBI."
 pochron@gumby.cs.wisc.edu  |