Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!psuvm!dxb132
From: DXB132@psuvm.psu.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: resident tags
Message-ID: <91030.144705DXB132@psuvm.psu.edu>
Date: 30 Jan 91 19:47:04 GMT
References: <91030.201910GHGAQA4@cc1.kuleuven.ac.be>
Organization: Penn State University
Lines: 18

>use them to make my program go resident, and everything works just fine as
>long as all the code and all the other memory kept resident is in CHIP RAM or
>in the address area $c00000 upto $c7ffff. (Expansion board on a A500).
>However, if I install my program in FAST MEM ($200000 upto $3fffff) then the

Expansion memory has not been configured at the time your KickMemPtr memory
is AllocAbs'ed, so this behavior is normal. If you have a large amount of
stuff that can't fit into chip RAM, then set up a module via KickTagPtr with
a priority < expansion.library, and AllocAbs the stuff (in fast memory) in
your module's initialization routine. (There's more to this, but this should
be enough).

Hopefully someone from Commodore will update this information for 2.0 if
it needs updating. (Please!) In particular what does the strange note in
the 2.0 compatibility doc about some of this changing/breaking in 2.0 refer
to?? (must be fairly subtle)

-- Dan Babcock