Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!agate!e260-1d.berkeley.edu!c60b-1eq
From: c60b-1eq@e260-1d.berkeley.edu (Noam Mendelson)
Newsgroups: comp.sys.ibm.pc,comp.os.msdos
Subject: Re: Extended memory
Message-ID: <1991Apr6.042556.13225@agate.berkeley.edu>
Date: 6 Apr 91 04:25:56 GMT
References: <1991Apr5.211351.4335@bnlux1.bnl.gov>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Distribution: na
Organization: University of California, Berkeley
Lines: 22

In article <1991Apr5.211351.4335@bnlux1.bnl.gov> kushmer@bnlux1.bnl.gov (christopher kushmerick) writes:
>My IBM AT has a few Mb of extended ram. It is recognized by the 
>virtual disk driver.

I assume you mean VDISK.SYS with the /E option.

>Given this, does it necessarily follow that this ram will be recognized
>by an ems driver, and therefore usefull for such things as ems overlays 
>in turbo pascal etcetera?

No.  Extended memory is _not_ the same as expanded memory.  There are
programs available which emulate expanded memory using extended memory,
but they result in a considerable slowdown of access time (this is due
to the software; extended memory is not inherently slow).
You can also access extended memory directly, but this is a real PITA.
However, if you're developing your own programs you may want to consider
this option.

+==========================================================================+
| Noam Mendelson   ..!agate!ucbvax!web!c60b-1eq | "I haven't lost my mind, |
| c60b-1eq@web.Berkeley.EDU                     |  it's backed up on tape  |
| University of California at Berkeley          |  somewhere."             |