home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.advocacy:11443 comp.os.ms-windows.advocacy:3628
- Path: sparky!uunet!ogicse!cs.uoregon.edu!majestix.cs.uoregon.edu!tracer
- From: tracer@majestix.cs.uoregon.edu (Roger M. Wilcox)
- Newsgroups: comp.os.os2.advocacy,comp.os.ms-windows.advocacy
- Subject: Re: How programs get DPMI memory (was Re: FCC (sic))
- Message-ID: <1993Jan3.042137.29882@cs.uoregon.edu>
- Date: 3 Jan 93 04:21:37 GMT
- Article-I.D.: cs.1993Jan3.042137.29882
- References: <1992Dec25.181732.15997@donau.et.tudelft.nl>> <1992Dec25.210652.29221@grebyn.com> <1992Dec26.114101.22372@donau.et.tudelft.nl>
- Sender: news@cs.uoregon.edu (Netnews Owner)
- Followup-To: comp.os.ms-windows.advocacy
- Organization: University of Oregon Computer and Information Sciences Dept.
- Lines: 15
-
- >richk@grebyn.com (Richard Krehbiel) writes:
- >
- >>What DOS programming language or environment allows a program to wade
- >>about in EMS/XMS/DPMI in the same way as conventional memory, without
- >>any special knowledge or treatment?
-
- Windows.
-
- GlobalAlloc ... { GlobalLock ... Global Unlock ... } GlobalFree.
- Easy as 3.14. Memory is memory is memory. Even virtual memory.
-
- --
- Roger *M.* Wilcox (aka Jeff Boeing)
- tracer@majestix.cs.uoregon.edu
- Aleph null bottles of beer on the wall, aleph null bottles of beer, ...
-