Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!ncrlnk!ncr-sd!crash!pnet01!jca
From: jca@pnet01.cts.com (John C. Archambeau)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Extended Memory
Message-ID: <4228@crash.cts.com>
Date: 19 May 89 01:16:15 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 21

I'm not referring to using a hard drive as expanded memory, I'm referring to
using extended as expanded.  Judging from your experience, you didn't use the
driver to convert extended to expanded, just used it to have your hard drive
emulate expanded.  Faking expanded memory with a hard drive is no great trick
in itself.  But I would like to see how such a driver would perform in the
extended to expanded test.  My guess is that int 15h, func 87h would be used
since that's the only real way to get at expanded memory while in 8086 mode. 
But there's that caveat and price you pay when using extended memory.  You
have to copy it to your 640K base, do your manipulations, and copy it back. 
Cheaper than a hard drive, yes, but not better than LIM EMS 4.0
specifications.  Memory block copying can get fairly expensive, especially if
you're using expanded memory to multitask (i.e. Desqview).  Just a negative
aspect I'd point out.  The best bet is to use the extended as a cache and have
your memory card support both expanded and extended.  But of course, beggers
can never be choosers when dealing with memory prices.
 
 JCA

UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!jca
ARPA: crash!pnet01!jca@nosc.mil
INET: jca@pnet01.cts.com