Xref: utzoo comp.sys.ibm.pc.misc:9340 comp.os.msdos.desqview:30
Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!lethe!yunexus!rreiner
From: rreiner@yunexus.YorkU.CA (Richard Reiner)
Newsgroups: comp.sys.ibm.pc.misc,comp.os.msdos.desqview
Subject: Re: Windows/Desqview advice needed
Message-ID: <22649@yunexus.YorkU.CA>
Date: 5 May 91 15:22:02 GMT
Article-I.D.: yunexus.22649
References: <1991May5.131335.25238@cunixf.cc.columbia.edu>
Organization: York U. Computing Services
Lines: 25

stone@cunixb.cc.columbia.edu (Glenn Stone) writes:

>I have a 386-based IBM compatible with 8 megs of RAM on order and I'm 
>thinking about how best to run it.  I have read some about Desqview
>and Windows 3.0 but haven't used them.  What are their relative advan-
>tages, and can they be used together?  Are there other multitasker/
>memory managers I should consider?  Advice & discussion appreciated.

In summary: DV/386 is superb at running multiple DOS applications and
managing their bad behaviour, as well as things like allowing
text-mode and graphics-mode programs to share the screen, and cutting
and pasting text between apps, and provides a rather nice but not too
elaborate API, but does not provide a GUI.  Windows in 386 mode runs
DOS apps less well, but provides a nice pretty GUI and some nice
things at the API level, such as dynamic data exchange.

Solution: get both, and run Windows inside DESQview (the other way
around won't work).  The result is nice clean low-overhead
multitasking of DOS apps, and GUI on demand for applications that use
it.  You also get the benefits of QEMM's improved memory management
for Windows.


//richard