Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!apple!fernwood!shograf!jim
From: jim@shograf.COM (jim morris)
Newsgroups: comp.os.msdos.apps
Subject: Re: QEMM, etc Recommendation Sought
Message-ID: <561@shograf.COM>
Date: 23 Mar 91 04:11:38 GMT
References: <1991Mar21.173016.27609@ssd.kodak.com>
Distribution: na
Organization: SHOgraphics
Lines: 27

Well QEMM & 386MAX will both do what you want. But in making
your descision bear in mind that QEMM has one feature that 386MAX
does not. It is one that I think is vitally important....

That is that QEMM "pools" memory, so it will provide expanded or
extended memory to whatever asks for it. This means that you do
not have to decide at boot time how much extended memory to reserve.

Seeing as there is a big mix of extended and expanded memory applications
it is real nice to have BOTH available at any time.

This is especially important if you use windows 3.0 and/or borlands
bcx compiler. With 386MAX you have to dedicate most of your extended
memory to windows or bcx at boot time. This means you have to change
the config file and reboot if you want to then run an app that uses
expanded memory.

This feature alone makes QEMM better. Unfortunately I have been a loyal
386MAX user for years, and have just trashed my new upgrade of 386MAX
to buy QEMM!

Jim

-- 
Jim Morris,	E-Mail: jim@shograf.com    Voice: (415) 903-3887
  _ 
SHO graphics.	Practical PEX