home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!Germany.EU.net!sbsvax!coli-gate.coli.uni-sb.de!sbustd!chbl
- From: chbl@sbustd.rz.uni-sb.de (Christian Blum)
- Newsgroups: comp.os.msdos.programmer
- Subject: Re: using expanded memory
- Message-ID: <1992Sep14.173510.21630@coli.uni-sb.de>
- Date: 14 Sep 92 17:35:10 GMT
- References: <110860002@acf3.NYU.EDU>
- Sender: news@coli.uni-sb.de (Usenet news system)
- Organization: Studenten-Mail, Rechenzentrum Universitaet des Saarlandes
- Lines: 26
-
- 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.
-
- XMS is accessed by a FAR call to an address that is given to you
- by an INT 21h call (dunno which, look it up). There are several
- functions to allocate XMS memory and copy data from lower 1meg
- address space to XMS and vice versa.
-
- EMS can be accessed via several calls to INT 67h (hope that's correct...)
- and normal read/write operations to a 64k window in lower 1meg address
- space.
-
- --
- ---------------------------------------------------------------------
- Christian Blum Universitaet des Saarlandes, Germany
- Friedrich-Ebert-Str. 50 chbl@stud.uni-sb.de
- W-6685 Heiligenwald chbl@sbustd.rz.uni-sb.de
- Germany Tel (+49) (0) 6821 67476
-