Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!psuvm!cunyvm!rohvm1!rbyaml
From: RBYAML@ROHVM1.BITNET (Aengus Lawlor)
Newsgroups: comp.windows.ms
Subject: Re: Yet Another QEMM problem.
Message-ID: <91084.085441RBYAML@ROHVM1.BITNET>
Date: 25 Mar 91 13:54:41 GMT
References: <1991Mar20.001227.29177@kuhub.cc.ukans.edu>
Organization: Rohm and Haas Company
Lines: 18

In article <1991Mar20.001227.29177@kuhub.cc.ukans.edu>,
2fmmempty@kuhub.cc.ukans.edu says:
>
[stuff deleted]
>So far the only thing that has worked with QEMM is to omit the RAM parameter,
>and use X=B000-B7FF statement.  I have tried excluding this area with the RAM
>statement but no go.  The problem seems to be hardware related then.
??? The RAM statement isn't used to exclude memory, it's used to turn QEMM on.
try using RAM and X=B000-B7FF. You should also try QEMM ANALYSIS MAP at the C:
prompt, and see if there are any other gaps in memory that might be causing
problems. (The E000-EFFF range causes me occasional problems.)
>
>I am using an AT&T 6386 WGS with and extended keyboard, 4 Meg of Ram
>(extended)
>And a V-RAM VGA 512k video card.
>
>So if anyone has any Hardware or Software ideas... I would really love to hear
>them.