Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!decvax!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice C routine
Message-ID: <499@sas.UUCP>
Date: 10 May 88 22:54:13 GMT
References: <197@dsacg2.UUCP> <199@dsacg2.UUCP>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 15
Keywords: wont go

In article <199@dsacg2.UUCP> nor1675@dsacg2.UUCP (Michael Figg) writes:
>Now I'm faced with another challange. Lattice compile options. I've got 
...
>and running NoFastMem but I should be able to shove this image data into
>chip memory at compile time. I've tried compiling with options similar to

You can probably fix this by simply BLINKing the old executable with the
CHIP option on:

BLINK oldname TO newname CHIP

This will force all code and data hunks into CHIP ram.

The 'Reference to unmerged data item' problem occurred because you were
trying to use SMALLDATA on BLINK to combine your data hunks into a single
hunk, but some of your data was marked CHIP and some FAST.