home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!hal.com!olivea!spool.mu.edu!wupost!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!metro!socs.uts.edu.au!kralizec!ixgate!michael.smith
- From: michael.smith@f842.n800.z3.fido.zeta.org.au (michael smith)
- Newsgroups: comp.sys.atari.st.tech
- Subject: Re: getmpb
- Message-ID: <b010d0aa@Kralizec.fido.zeta.org.au>
- Date: 9 Nov 92 07:37:02 GMT
- Organization: Fidonet. Gate admin is fido@socs.uts.edu.au
- Lines: 31
-
- Original to: pcxkrm@unicorn.nott.ac.uk
- In a message of <02 Nov 92 18:12:40>, pcxkrm@unicorn.nott.ac.uk (3:713/602)
- writes:
-
- p> Hi,
-
- G'day!
-
- p> As a person who has spent the last ten years programming almost solely
- p> in BASIC, the ins and outs of memory management are fairly new to me.
- p> I'm currently trying to write a program which needs to know where it is
- p> in memory. My GEMDOS information tells me that the 'C' call getmpb
- p> should do this - but it seems to return only the top of system memory or
- p> something - it gives the same thing every time with no pointer to a
- second
- p> block.
- p> Am I being very thick or is there some other way to find out my
- p> program's basepage? I'm running an STe with 2Mb of memory and TOS 1.62.
-
- Why do you want to find the basepage?? If you are looking for paramters,
- that's the wrong way to do it...
-
- Your library's startup code should define a variable called _baseptr (or
- something similar) that points to it anyway.
-
- p> Keith.
-
- \`miff` /|\
-
- --- ScanMail 0.68 X0501
- * Origin: That Which Is Not, ST in SA. 61-8-232-5722 (3:800/842)
-