Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!amdahl!pyramid!prls!philabs!lamont!adam
From: adam@lamont.Columbia.edu (adam levin)
Newsgroups: comp.sys.amiga
Subject: Re: Copying to chip RAM
Message-ID: <447@lamont.Columbia.edu>
Date: 28 Mar 88 13:38:17 GMT
References: <442@lamont.Columbia.edu>
Organization: Lamont-Doherty Geological Observatory N.Y.
Lines: 27
Summary: Hold that snippet!

In article <442@lamont.Columbia.edu>, I,
adam@lamont.Columbia.edu (adam levin) wrote:
> 
> I have a 'C' array which needs to be in chip RAM.  The examples I have found
> declare the array, AllocMem some chip RAM, and copy the array into it.
> This is wasteful if all one has is chip RAM, or if the program was linked
> with Manx's +C option.  I wrote the following routine, and I'd like to know
...

I soon received a message from Dale Luck informing me that:

] ... There already is an exec function call 'TypeOfMem'.
] You pass in the address, and it returns the flag bits associated
] with that memory.
] NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER 
] use fixed addresses for deciding where chip memory is. It is going to
] increase in size with the new chips as well as it may move to a new
] base with new systems.
] From: amiga!boing!dale@prls (Dale Luck)

So never mind!  -Adam

-- 
Phone:  (914) 359-2900 x340
Post:   Lamont-Doherty Geological Observatory / Palisades, NY 10964
USENET: {ihnp4, decvax, seismo} philabs!lamont!adam
ARPA:   lamont!adam@columbia.edu