Article View: comp.os.ms-windows.setup
Article #1125QEMM and Windows 3.0
From: John P. Mechalas
Date: Fri, 20 Nov 1992 16:19
Date: Fri, 20 Nov 1992 16:19
53 lines
3005 bytes
3005 bytes
I never bothered to upgrade from QEMM 5.1x and Windows 3.0 to the newest and
latest versions, so I relaize these are outdated questions, but....
When I first installed QEMM many moons ago, I couldn't get it to work
properly with Windows 3.0 ... Windows would load and run in 386 enhanced
mode okay, but trying to run a DOS application, full creen *or* windowed
would end up in a "Violating System Integrity" error. At the time, I
didn't want to mess with it, so I created two config.sys files, and booted
the appropriate one to load Windows (without QEMM) when necessary.
Well, now I want to run QEMM all the time, as I get tired of re-booting
constantly, and want to stick with one config.sys file. So, I dragged out
some of the tech. refs. from the win3 directories at cica, looked in some
books, and various other sources, to try and congifure QEMM correctly. I
have done everything the books and tech support have told me to do...the
proper EMMExcludes, NOSHAD NOSORT etc... switches, the RAM switch... and
no dice...I keep getting the "Violating System Integrity" when I run a DOS
app under QEMM...
Can somebody help me out? Anyone manage to get this to work? Here is my
config.sys:
device=c:\qemm\qemm386.sys ram nosort nofill
device=c:\qemm\loadhi.sys /r:1 virus\virstop.exe
device=c:\qemm\loadhi.sys /r:2 \bin\zansi.sys
device=c:\qemm\loadhi.sys /r:1 dmdrvr.bin
files= 30
buffers=1
stacks=0,0
device=c:\qemm\loadhi.sys /r:1 c:\windows\smartdrv.sys 1024
DEVICE=C:\QEMM\LOADHI.SYS /R:1 C:\STACKER\STACKER.COM
C:\STACVOL.000 D:\STACVOL.001
And my autoexec.bat:
echo off
PATH= etc...
c:\qemm\loadhi /r:1 c:\qemm\buffers=15
prompt $P$G
c:\qemm\loadhi /r:1 mouse
The system is a 386/25 with 5MB RAM running QEMM 5.1x and Stacker 1.x.
The mouse driver is for a Logitech BUS Mouse, version 3.42 (I have 6.x
if it makes a difference). Remember this is still Windows 3.0, and not
Windows 3.1.
PLEASE do not tell me to upgrade! I *know* I can upgrade. I just can't
afford to do that right now.
Thank you in advance....
--
John Mechalas "I'm not an actor, but
mechalas@gn.ecn.purdue.edu I play one on TV."
Aero Engineering, Purdue University #include disclaimer.h
Technical Details
Message-ID:
<1992Nov20.161958.19338@gn.ecn.purdue.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!ornl!rsg1.er.usgs.gov!darwin.sura.net!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu!gn.ecn.purdue.edu!mechalasShow Full Headers
Complete Article Headers
Newsgroups: comp.os.ms-windows.setup Path: arc1-ca.pugleaf.net!sparky!uunet!ornl!rsg1.er.usgs.gov!darwin.sura.net!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu!gn.ecn.purdue.edu!mechalas From: mechalas@gn.ecn.purdue.edu (John P. Mechalas) Subject: QEMM and Windows 3.0 Message-ID: <1992Nov20.161958.19338@gn.ecn.purdue.edu> Organization: Purdue University Engineering Computer Network Date: Fri, 20 Nov 92 16:19:58 GMT Lines: 53