Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!rochester!uhura.cc.rochester.edu!ub!zaphod.mps.ohio-state.edu!ncar!hsdndev!cmcl2!acfcluster.nyu.edu!jqg9462
From: jqg9462@acfcluster.nyu.edu
Newsgroups: comp.os.msdos.apps
Subject: Re: QRAM VS. QEMM
Message-ID: <1991Feb7.075045.1@acfcluster.nyu.edu>
Date: 7 Feb 91 12:50:45 GMT
References: <26661@uflorida.cis.ufl.EDU> <26662@uflorida.cis.ufl.EDU> <kusumoto.665695974@chsun1>
Sender: notes@cmcl2.nyu.edu (Notes Person)
Followup-To: comp.os.msdos.apps
Distribution: usa
Organization: New York University
Lines: 14
Nntp-Posting-Host: acf7.nyu.edu

In article <kusumoto.665695974@chsun1>, kusumoto@chsun1.uchicago.edu (Bob Kusumoto) writes:
> QEMM manages high RAM memory in 4k chunks while QRAM manages high RAM memory
> in 16k chunks.  QRAM runs ontop of your Expanded/Extended memory manager
> while QEMM incorporates it.  QRAM is basically a high RAM manager.  In QEMM,
> it's possible to disable it as an extended or expanded memory manager and
> run something else.  You can also try the HIMEM.SYS from MS-windows rather
> than use QEMM to see if it helps (it does help getting the latest version
> of QEMM386 as well, v5.11 I think).

I think HIMEM.SYS will only convert 64K exTended memory to High Mem.
It will convert the rest exTend memory to XMS.
QEMM can fill the High Mem gaps with exTended memory.

Jun