Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Intuition/Chip memory question
Message-ID: <19993@sun.uucp>
Date: Fri, 29-May-87 00:43:03 EDT
Article-I.D.: sun.19993
Posted: Fri May 29 00:43:03 1987
Date-Received: Sat, 30-May-87 10:03:38 EDT
References: <2120@husc6.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Distribution: world
Organization: Sun Microsystems, Mountain View
Lines: 18
Keywords: Image structure, Chip Memory
Summary: Blink it into memory

In article <2120@husc6.UUCP> may@husc4.UUCP (Jason May) writes:
>                                  ...it is stated that Image data
>must be loaded into Chip memory.  Is there a way I can selectively
>load this data into Chip memory, without having to Allocmem() and
>copy within the program, or use something like FixHunk, or Hide?
>					Jason

Yes it is. There are two ways to do it. If you are using the Lattice
C compiler (version 3.10) then you can put that data in a different
module and use the -ad switch when compiling it. That says that the
data segment of this object module should be loaded into Chip memory.
If you already have a .o file the ATOM utility available on the 
developers tools disk will force that module to load into Chip memory.
And of course you can use FixHunk to force all data into chip memory.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.