Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!purdue!haven!decuac!shlump.nac.dec.com!hpspwr.enet.dec.com!simon
From: simon@hpspwr.enet.dec.com (Curiosier and curiosier...)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DESQview 386 problem
Message-ID: <12972@shlump.nac.dec.com>
Date: 29 Jun 90 15:02:45 GMT
Sender: newsdaemon@shlump.nac.dec.com
Organization: Digital Equipment Corporation
Lines: 29


In article <12971@shlump.nac.dec.com>, reisert@ricks.enet.dec.com (Jim Reisert) writes...
>In article <268acbc5-65comp.sys.ibm.pc@oneb>, kmcvay@oneb (Ken McVay) writes...
> 
>>DV's install seemed to work - ie DV's setup ran, and I configured it as I
>>wanted it - but when I added QEMM to the mix, DV locked up tighter'n a
>>witch's....aw, you  know....
> 
>I had a similar problem.  It turned out that QEMM was mapping already-mapped
>video ROM to RAM.  What I believe happened was that video ROM at address
>C000-C7FF was mapped to RAM at E000-E7FF by the system.  QEMM thought that
>E000-E7FF was free (it didn't know about the mapping), so it loaded DESQview
>there.  And the system hung.  The solution was to EXCLUDE E000-E7FF in the
>QEMM.SYS line and everything was fine after that.
> 

You should also check if your system does ROM (both system and video) 
shadowing.  If it does, you should disable it and let QEMM do this task. 
You may have a conflict between the system and QEMM trying to use the 
same segments. 


---------
Leo Simon			simon@pwrvax.enet.dec.com

Who is not liberal when young, does not have a heart.
Who is not conservative when old, does not have a brain.

						-- W. Churchill