Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!sol.ctr.columbia.edu!src.honeywell.com!skyler.mavd.honeywell.com!rlb
From: rlb@skyler.mavd.honeywell.com (Randal L. Barnes)
Newsgroups: comp.os.os9
Subject: Re: linking to absolute addresses
Message-ID: <1991Jan28.063537.68@skyler.mavd.honeywell.com>
Date: 28 Jan 91 12:35:37 GMT
References: <1991Jan24.162635.1742@yogi.fhhosp.ab.ca> <1991Jan28.022859.24393@ncsuvx.ncsu.edu>
Lines: 18


edstrom@elmer.hsc.ucalgary.ca (John Edstrom) writes:

> Is there anyway to link a module to an absolute address?

kdarling@hobbes.ncsu.edu (Kevin Darling) writes:

> Well, you could hardcode the memory address in your program <yuk>.

We had a similar problem with our Heurikon 68030 boxes.  We used the OS/9
f$permit call to give the application access to the area of memory in question
(this got rid of the 102 error).  It is not a pretty solution, but it does help
get the work done by Friday ;-)

-- 
Randal L. Barnes                    rlb@skyler.mavd.honeywell.com
Tea, Earl Grey, HOT!                Honeywell Military Avionics Division
                                    612/542-5021