Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!helios!aim1!jlr1801
From: jlr1801@aim1.tamu.edu (Jeff Rife)
Newsgroups: comp.windows.ms
Subject: Re: Yet another QEMM5.11 problem with Windows.
Message-ID: <13133@helios.TAMU.EDU>
Date: 7 Mar 91 06:28:43 GMT
References: <1991Mar2.000056.29955@watmath.waterloo.edu> <1991Mar04.183739.16426@ism.isc.com>
Sender: usenet@helios.TAMU.EDU
Organization: City of College Station, Texas
Lines: 31

In article <1991Mar04.183739.16426@ism.isc.com> robinro@bomber.ism.isc.com (Robin Roberts) writes:
>It has been my experience that when using QEMM 5.11 and Windows 3.0
>together that smartdrive, if used, should NOT be loaded "high" by 
>QEMM's loadhi.  I have gotten many UAE's when smartdrive was loaded high.


I don't have any problem loading SMARTDRV high, but I guess I am lucky.

>
>Also I have given up on using QEMM when using windows in real mode.  I just
>use a different config.sys file and load up EMM386 instead.  Since I only 
>use real mode to run one pre-Win 3.0 program it isn't a burden ... yet.
>-- 
>Robin D. Roberts                                      robinro@ism.isc.com

Try one of two things...

1) Run W3 with the command line `win /n' or `win /x' (I never can remember
   the undocumented switches :-) to make it use the EMS that QEMM creates
   in a better way.

2) From within Windows in 386Enh mode, run a exclusive, full-screen DOS box.
   Type `win /r' and run your WIN 2.X app in *that* Windows session.  I once
   had two real mode Windows sessions each running inside their own window
   out of a parent 386Enh Windows session.

--
Jeff Rife   P.O. Box 3836   |   "Because he was human; because he had goodness;
College Station, TX 77844   |    because he was moral they called him insane.
(409) 823-2710              |    Delusions of grandeur; visons of splendor;
jlr1801@aim1.tamu.edu       |    A manic-depressive, he walks in the rain."