eclam@watmath.waterloo.edu (Edmund C. Lam) (03/02/91)
I have the following problem running QEMM5.11 with Windows 3.0 in
protected mode on a Northgate 386/33 with an AH1542B controlling a Quantum
210S.
It seems that SMARTDRV is clobbering the FAT on my Harddisk. I have
tried the undocumented /B- option with SMARTDRV. I have also tried
changing VirutalHDIrq entry in SYSTEM.INI.
Windows 3.0 functions correctly when QEMM is not loaded. I have tried
changing the options in QEMM with no success (DISKBUF=2). The 1542B is
configured at C800. I have an idea that SMARTDRV is clobbering Himemory
used by QEMM to buffer the 1542B.
Has anyone else run into this problem? I need as much of the base 640K
has possible. I am getting very good a loading DOS, C6, Windows and SDK!
--
-Edmund C. Lam (University of Waterloo)
<eclam@aftermath.waterloo.edu || eclam@aftermath.Uwaterloo.CA>robinro@bomber.ism.isc.com (Robin Roberts) (03/05/91)
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. 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 Usenet: ..!uunet!scorp1!roberts CompuServe: 72330,1244 GEnie: R.ROBERTS10 [At the start of World War I, the Romanian general staff ordered that only officers above the rank of major could wear makeup. -Oxford Military Anecdotes]
jlr1801@aim1.tamu.edu (Jeff Rife) (03/07/91)
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."