Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!tada
From: tada@athena.mit.edu (Michael Zehr)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Same problem after patch
Summary: try separate modules for chip memory
Keywords: My problem or compiler's?
Message-ID: <9256@bloom-beacon.MIT.EDU>
Date: 14 Feb 89 21:23:15 GMT
References: <9254@bloom-beacon.MIT.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: tada@athena.mit.edu (Michael Zehr)
Organization: Massachusetts Institute of Technology
Lines: 24

In article <9254@bloom-beacon.MIT.EDU> rlcarr@athena.mit.edu (Rich Carreiro) writes:
>I asked this question about 10 days ago and got a number of
>answers.  Most blamed the problem on the 5.0 bugs.  I have since
>installed the 5.02 patch.  I got the patches from the LBBS on 2/8/89.
> [...]
>The only way I've been able to get the program to work is to use the CHIP
>option to BLINK to force everything into chip RAM.  I do not like
>that solution.  So, what am I doing wrong?

I had similar problems, both with 5.0 and 5.02.  When I called the 
Lattice technical support people, they offered the following fix:

put all your 'chip' declarations in one module, with no non-chip
declarations.

from your other modules, declare the references as 'extern chip ...'

then link everything normally.

i'm not sure it will fix your problems, but it fixed mine.  (i was getting
"not an object module" errors when trying to run things...)

hope this helps...
-michael j zehr