Path: utzoo!utgpu!watserv1!watmath!att!cbnewsl!rl
From: rl@cbnewsl.att.com (roger.h.levy)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Extended Memory Configuration
Summary: maybe Turbo EMS
Message-ID: <1990Jun13.170709.6803@cbnewsl.att.com>
Date: 13 Jun 90 17:07:09 GMT
References: <1990Jun5.172609.2820@murdoch.acc.Virginia.EDU> <41834@conexch.UUCP>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 22

In article <41834@conexch.UUCP>, rob@conexch.UUCP (Robert Collins) writes:
> In article <1990Jun5.172609.2820@murdoch.acc.Virginia.EDU> jw2b@watt.acc.Virginia.EDU (Sara J. Wagner) writes:
> >I have upgraded my work computer from an IBM XT to a WIN TurboAT,
> >                                The problem came when I discovered
> >that the drivers for the extended memory seem to be taking up some 
> >of the original 640K, to the point that programs like Ventura 
> >Desktop Publishing (which requires 512K free) would not run.  I 
> >
> >DEVICE=C:\EXMM.SYS -r3 -e1400
> 
> If you use an expanded memory manager on a '286, it must take up som of
> system memory.  On a '386 this isn't necesary, it can use other means of
> memory mapping to accomplish bank swapping for expanded memory.
> 
I posted a question asking about some of these issues recently.  One response
came from the author of Turbo EMS.  He says that all expanded memory simulators
(i.e. simulate expanded with extended) will grab about 72K from base memory
(64K for the simulated expanded memory pages and about 8K for the driver).
Turbo EMS does however have a command to return the 64K to active use when
needed so only a small amount of memory remains unavailable.  Don't know if
other like programs have this feature and haven't bought Turbo EMS yet to see 
how well it works.