Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!petro!texbell!nuchat!moray!urchin!p6.f506.n106.z1.fidonet.org!Bob.Stout
From: Bob.Stout@p6.f506.n106.z1.fidonet.org (Bob Stout)
Newsgroups: comp.lang.c
Subject: Re: Expanded/Extended memory use in MSC 5.1
Message-ID: <10730.25B733B8@urchin.fidonet.org>
Date: 18 Jan 90 11:54:07 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/506.6 - Fulcrum's Edge, Spring TX
Lines: 16

In an article of <16 Jan 90 17:27:08 GMT>, kaleb@mars.jpl.nasa.gov (Kaleb Keithley) writes:

 >>   4) WHEN IS SOMEONE GONNA MAKE IT EASY TO USE EXPANDED AND EXTENDED 
 >>      MEMORY IN NORMAL MSC C LANGUAGE? (no violins please).
 >   
 >I have said this before, and while I'm not in any way endorsing them or 
 >their products, Microsofts' MS-DOS encyclopedia is one of the best 
 >resources around for DOS programming.  There are articles in there 
 >complete with code, that explain the care and feeding of ext/exp memory.

  Zortech C/C++ 2.0 includes functions for directly working with extended  
and/or expanded memory. It also includes a new pointer type, supported at the  
compiler level, for handling almost any type of memory, including disk-based  
virtual memory. Note that the current release only supports extended and  
expanded memory, but the way it's written, full virtual memory support can't  
be too far off. Then, there's OS/2...