Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!uw-beaver!uw-june!dylan
From: dylan@cs.washington.edu (Dylan McNamee)
Newsgroups: comp.sys.amiga.tech
Subject: A Rad: using only 16 bit memory...
Message-ID: <13089@june.cs.washington.edu>
Date: 20 Sep 90 17:38:16 GMT
Reply-To: dylan@june.cs.washington.edu (Dylan McNamee)
Organization: University of Washington, Computer Science, Seattle
Lines: 25


I am about to bring the 32 bit memory in my system up to 4 megabytes.
This makes me think of creative ways of using the 2 megs of 16
bit memory on my 2091 card.  I'd prefer not to run code from the
16 bit memory, so the idea of a 16 bit RAD: seems natural.  The static
nature of RAD: makes it more handy for this than ram:.  Here's a
first cut at a scheme for doing this:

1)  Allocate all of the 32 bit memory in the system.  (Using the
routines in MTest seems the easiest, although slow.)  I guess this
would be doable by checking the address returned for range in 32 bit
memory space, and freeing it if it weren't.

2)  Create a Rad: disk, which would allocate the 16 bit memory, since
that is all that is around.

3)  Free the 32 bit memory.

This process would only need to be done at system turn on time, since
after that, the memory is fixed in rad:

Comments?  Easier methods?  Mistakes (will this indeed work?)

dylan
dylan@cs.washington.edu