Newsgroups: comp.sys.ibm.pc.misc
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!kudla
From: kudla@rpi.edu (Robert J. Kudla)
Subject: Re: DesqView 386 Problem
In-Reply-To: jerry@gumby.Altos.COM's message of 4 Apr 91 00:30:56 GMT
Message-ID: <1p-gs!_@rpi.edu>
Nntp-Posting-Host: nuge107.its.rpi.edu
Organization: just say no!
References: <4m.gk.p@rpi.edu> <4773@gumby.Altos.COM>
Distribution: comp
Date: 5 Apr 91 20:56:32 GMT
Lines: 26

In article <4773@gumby.Altos.COM> jerry@gumby.Altos.COM (Jerry Gardner) writes:

   If you have Desqview 386 you also have QEMM386.  Use QEMM's optimize
   feature to put as many drivers, TSR's, etc, into high memory and out
   of the lower 640.

I don't use any TSR's and I think the only driver I use is QEMM itself.

   >By the way, please respond in email.  I don't actually read
   >comp.sys.ibm.pc.misc.  Thanks....

   Perhaps it you did read this newsgroup, you might understand how
   Desqview works...

I understand quite well how DesqView 386 and virtual 8086 mode work; I
didn't know it was an automatic thing with DV386.  All these kludgy
workarounds for getting multitasking to work on a PC are really
frustrating.  Hence the reason I never use them outside of the office.

I'm reading this group now, but probably not for much longer...

Robert Jude Kudla <kudla@rpi.edu>
                                   
No more bars!  No more cages!  Just rollerskating, disco music, and
the occasional light show....