Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!osu-cis!dsacg1!dsacg2!nor1675
From: nor1675@dsacg2.UUCP (Michael Figg)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice C routine
Message-ID: <199@dsacg2.UUCP>
Date: 8 May 88 12:44:37 GMT
References: <197@dsacg2.UUCP>
Organization: Defense Logistics Agency Systems Automation Center, Columbus, OH
Lines: 70
Keywords: wont go
Summary: The saga continues

In article <197@dsacg2.UUCP>, nor1675@dsacg2.UUCP (Michael Figg) writes:
> I am trying to run a simple program from an old copy of Amazing Computing
> (Vol 2, Num 10 "Quick and Dirty Bobs", by Michael Swinger) on Lattice 4.0
> with no luck. The program is to run under intuition and just display a 
> simple bob. All i get is a blank screen with a close gadget. Here are 
> relevant (hopefully) pieces of the program: 
> 
> 					 Thanks,
> 
> -- 
> "Don't quote me on this!"                      Michael Figg
> 					       DLA Systems Automation Center
> 					       Columbus, Oh.
> 					       (614)-238-9036


Okay, this was a trick question and you all missed it including me. The
problem isn't with Lattice but with expanded memory. NoFastMem worked
like a charm. Why didn't I think of this before presenting my problem in
front of the world? 

Now I'm faced with another challange. Lattice compile options. I've got 
this program to run by compiling with

lc -L swing1

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

lc -ad -L swing1  

or

lc -acd -L swing1

or even 
 
lc -acdb -L swing1

but I keep getting an error on the compile saying 

    option conflict. -b option ignored

even though I am not using the -b option at all. This message is followed
later by a linkage error stating:

Error 510: _IntuitionBase symbol - Reference to unmerged data item
   First Reference in Unit cxovf.o at offset 00000c20 in file 'LIB:lc.lib'
   to Unit swing1.o at offset 00000010 in file 'swing1.o'

in checking the Lattice manual for this error I found a five word explanation
that said much less than what was on the screen. I don't have the manual
with me but I think it said something about an unrecognized symbol. I did
find that cxovf.o is a stack handler routine so I tried uping the stack to
20000. No go. Does this look like a problem with the library or what. And
do I have any control over this? I'm probably making myself look like a
fool again (or still) but inquiring minds want to know. I want to know.

actually two people gave me answers to this chip problem (Mike and Mike, but
not this Mike) and I don't know why I didn't think about it. Inexperience
I guess. Somebody else reccommended crayons for easy graphics!

						Thanks,


-- 
"Don't quote me on this!"                      Michael Figg
					       DLA Systems Automation Center
					       Columbus, Oh.
					       (614)-238-9036