Path: utzoo!attcan!uunet!munnari.oz.au!csource!david From: david@csource.OZ.AU (david nugent) Newsgroups: comp.sys.ibm.pc Subject: Re: DESQview 386 problem Keywords: desqview,qemm Message-ID: <548@csource.OZ.AU> Date: 1 Jul 90 12:23:26 GMT References: <268acbc5-65comp.sys.ibm.pc@oneb> Organization: Unique Computing Pty Ltd, Melb, Aust. Lines: 40 In <268acbc5-65comp.sys.ibm.pc@oneb> kmcvay@oneb (Ken McVay) writes: >I recently installed DV386 (2.26) on a 386/25MHz machine with a Quadtel >BIOS and 2048k of RAM - the top meg's extended in BIOS. > >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 eliminated everything that I didn't need - no ansi.sys, etc. and moved the >video and system from shadow RAM to ROM, in an attempt to eliminate sources >of address conflict - I loaded QEMM.SYS in a variety of ways: > >device=qemm.sys >device=qemm.sys RAM >etc... > >QEMM loads, but no matter how I set things up, DV won't run without locking >up - what would seem to be a clear sign of conflict. There's unfortunately no real short-cut; it takes a *lot* of trial and error on some machines. Your best bet is trying to contact QuaterDeck to see if they know of anyone who's been there before. I'm surprised it didn't work without the RAM statement in there though; I've only ever come across one machine where QEMM just plain refused to run. It had a 1989 AMI BIOS, though I don't recall which revision off- hand. Never found out why, though 386^MAX from Qualitas worked fine. BTW, if you run a VGA, try it with a CGA or EGA card. If it works, then it's pretty obvious where the conflict is. QEMM seems to have problems with some, particularly some Genoa cards. david -- _______________________________________________________________________________ Unique Computing Pty Ltd Melbourne Australia - Communications Specialists david@csource.oz.au 3:632/348@fidonet 28:4100/1@signet