home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!yoyo.aarnet.edu.au!dstos3.dsto.gov.au!cej
- From: cej@dstos3.dsto.gov.au
- Newsgroups: comp.os.msdos.programmer
- Subject: Re: using expanded memory
- Message-ID: <1992Sep15.124238.164538@dstos3.dsto.gov.au>
- Date: 15 Sep 92 18:42:38 GMT
- References: <110860002@acf3.NYU.EDU> <1992Sep14.173510.21630@coli.uni-sb.de>
- Organization: Defence Science and Technology Organisation
- Lines: 27
-
- In article <1992Sep14.173510.21630@coli.uni-sb.de>, chbl@sbustd.rz.uni-sb.de (Christian Blum) writes:
- > reznick@acf3.NYU.EDU (Daniel Reznick) writes:
- >> I am interested in utilizing XMS and EMS memory in programs being
- >> developed with BC++ 3.1, written in assembly and C (the plain vanilla
- >> version). If any one can give me and pointers to good references,
- >> otimally with code examples, I would be most appreciative. Either
- >> assember or C would be fine. Also, does the memory model begin used
- >> affect this at all? (im sure it does somewhat..) thanks.
- >
- > Best source of information is Ralf Brown's famous interrupt list.
- > It is available from several BBSs.
-
- You can grab sample code for EMS & XMS functions from the Simtel archives.
- On our Simtel CD-Rom there are 4 or 5 C "units" to let you use one or the other
- or both. (Also a few for TP)
-
- --
- Chris Jones E-mail: cej@dstos3.dsto.gov.au
- CSS/CD/ERL Phone: +61 8 259 6758
- DSTO Salisbury, South Australia Fax: +61 8 259 6328
-
- Disclaimer: The opinions expressed are purely personal and do NOT represent
- the official view of DSTO.
-
- "I'm going to put the shame file in the sludge file! Or is that the sludge
- file in the shame file? Shame, sludge, sludge, shame, ...
- That's life, get nicked.." Derrin Hunch, Fast Forward
-