Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!cbmvax!carolyn
From: carolyn@cbmvax.cbm.UUCP (Carolyn Scheppner CATS)
Newsgroups: comp.sys.amiga
Subject: Re: 64k tables & Manx?
Message-ID: <1799@cbmvax.cbmvax.cbm.UUCP>
Date: Thu, 30-Apr-87 12:07:08 EDT
Article-I.D.: cbmvax.1799
Posted: Thu Apr 30 12:07:08 1987
Date-Received: Tue, 5-May-87 04:36:23 EDT
References: <18567@ucbvax.BERKELEY.EDU>
Reply-To: carolyn@cbmvax.UUCP (Carolyn Scheppner CATS)
Distribution: na
Organization: Commodore Technology, West Chester, PA
Lines: 30

In article <18567@ucbvax.BERKELEY.EDU> robinson@renoir.Berkeley.EDU (Michael Robinson) writes:
>I have a program I am writing as a C/assembly hybrid for which I have need
>of a 64k (2^16, 65536) byte table.
>
>I have a program which generates the table, and can modify said program
>to generate the output in any format desired.
>
>I have the Manx 3.4 commercial package.
>
>I would like to get the whole table loaded cleanly into the final executable
>with a symbol pointing at the center so I can access all 65536 bytes using
>register indirect with index addressing (small style).
>[]

   Not sure if this is appropriate, but my suggestion is to use AllocMem()
to allocate the memory for the table.  You can then set up whatever kind
of pointer you want to point at whatever spot you want.

   If the created table must be saved for loading by another program,
just Write() the whole thing to a file.  This would only require a single
Write().  The other program could use a single Read() to bring the table
back into its own AllocMem()'d contiguous area.   


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Carolyn Scheppner -- CBM   >>Amiga Technical Support<<
                     UUCP  ...{allegra,caip,ihnp4,seismo}!cbmvax!carolyn 
                     PHONE 215-431-9180
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=