Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!uwvax!rhesus!uwmacc!vms.macc.wisc.edu!plutchak
From: plutchak@vms.macc.wisc.edu
Newsgroups: comp.sys.atari.st
Subject: Re: Pexec cookbook! (w/ Lattice C)
Message-ID: <1792@uwmacc.UUCP>
Date: Wed, 19-Aug-87 12:11:44 EDT
Article-I.D.: uwmacc.1792
Posted: Wed Aug 19 12:11:44 1987
Date-Received: Sat, 22-Aug-87 00:56:54 EDT
References: <816@atari.UUCP>
Sender: news@uwmacc.UUCP
Reply-To: plutchak@vms.macc.wisc.edu
Organization: UW-Madison Academic Computer Center
Lines: 23
Keywords: Lattice, Metacomco

In article <816@atari.UUCP> apratt@atari.UUCP (Allan Pratt) writes:
>All GEMDOS programs are started with the largest block of OS memory 
>allocated to them...  The point is that your
>program has probably been allocated ALL of free memory.  In order to
>make memory available for a child process, you have to SHRINK the
>block you own, returning the top part of it to GEMDOS.  The time to
>do this is when you start up.

   Does anybody know exactly how I do this using Lattice C?  The documentation
(for version 3.04) is less than clear on this point, and everything I've
tried hasn't worked.  I have never really *needed* to give the extra 700K
or so of memory back, but the sheer wastefulness of it annoys me (:-), and
someday I may want to use that memory.  I'd appreciate any pointers on the
subject.
   And while I'm asking advice on Lattice C, is there any special startup
module needed to link a program used as a desk accessory, as there
(apparently) is with other C's?
--
  Joel Plutchak

  Arpanet: plutchak@vms.macc.wisc.edu
  Bitnet:  plutchak@WISCMACC
  uucp: Who knows-- it's Eunice; try ...ihnp4!uwvax!uwwircs!plutchak