dpayne@isis.cs.du.edu (Dirk Payne) (12/31/90)
I have been having some strange problems running QEMM 5.11 with Windows 3.0. I have a generic 386/33 (that has proven to be very compatible so far), with 8 megs of RAM, an STB EM-16+ VGA board, and a 315 MB ESDI hard disk. The hard disk is partitioned for DOS and Unix. Here is the problem. Quite frequently Windows will go into a long sleep (usually 30 to 60 seconds) when QEMM is handling the memory, but no signs of this when I am running the HIMEM.SYS program that comes with Win3. In both cases SMARTDRV is loaded with similar parameters, except that I finally settled on expanded memory for cache with QEMM. To maximize memory, buffers and DOSED are loaded high. I have experimented with RAM, ROM and some of the other oblique tuning parameters for QEMM to no avail. Here are the CONFIG.SYS and AUTOEXEC.BAT files for the different boot requirements: AUTOEXEC.BAT (normal): @echo off path=C:\WIN30;c:\dos401;c:\bat;c:\tools;c:\bor2;c:\femacs;c:\msc;c:\clip; set lib=c:\clip;c:\msc\lib;c:\tcp\lib; set include=c:\clip;c:\msc\include; dosed keyspeed /e prompt [$p] set TEMP=C:\WIN30\TEMP CONFIG.SYS (normal): buffers=30 files=30 device=\tools\rapidbio.sys device=himem.sys device=\win30\smartdrv.sys 4096 512 shell=c:\dos401\command.com /e:512 /p AUTOEXEC.QDK (QEMM): @echo off path=C:\WIN30;c:\dos401;c:\bat;c:\tools;c:\bor2;c:\femacs;c:\msc;c:\clip; set lib=c:\clip;c:\msc\lib;c:\tcp\lib; set include=c:\clip;c:\msc\include; c:\qemm\loadhi /r:2 dosed keyspeed /e prompt [$p] set TEMP=C:\WIN30\TEMP CONFIG.QDK (QEMM): DEVICE=\QEMM\QEMM386.SYS RAM ROM DEVICE=C:\QEMM\LOADHI.SYS /R:3 \WIN30\SMARTDRV.SYS 2048 512 /a STACKS=0,0 BUFFERS=10/X FILES=25 SHELL=C:\DOS401\COMMAND.COM /E:512 /P Other than the pausing, the system runs well with QEMM. I have not experienced any other problems other than the pausing. Any ideas? I'm out of 'em! AdvTHANKSance Dirk Payne -- =============================================================================== "If at first you don't succeed ... hack, hack again!!" dpayne@isis.cs.du.edu =============================================================================== -- =============================================================================== "If at first you don't succeed ... hack, hack again!!" dpayne@isis.cs.du.edu ===============================================================================
ries@venice.SEDD.TRW.COM (Marc Ries) (01/01/91)
Interesting... I just loaded DR DOS 5.0 on my 386, after running MS DOS 3.3, and I experience the same thing. It is especially noticable when loading graphic images into AMI Pro. About the only thing I am taking advantage of via DR DOS is the HIGHDOS driver, since the manual and the rep. I talked to warn against using their 386 Memory manager along with the Win 3.0 enhanced 386 environment.