Xref: utzoo comp.sys.ibm.pc.misc:9372 comp.os.msdos.desqview:51
Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!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: <22671@yunexus.YorkU.CA>
Date: 7 May 91 13:28:17 GMT
References: <1991May5.131335.25238@cunixf.cc.columbia.edu> <22649@yunexus.YorkU.CA> <1991May7.092600.21136@daffy.cs.wisc.edu>
Organization: York U. Computing Services
Lines: 25

bodoh@cat7.cs.wisc.edu (Daniel Bodoh) writes:

>If you mean interprocess communication, DV also provides dynamic data exchange
>with mailboxes.

Yes, I mean IPC, and I know that the DV API provides mailboxes;
however, there are actually large numbers of Windows apps that *use*
DDE (this is the Windows term for their IPC facility), whereas only a
very few things, some of which I've written myself, use the DV
mailboxes for anything.

>I have used DV/386 for about 6 months now, and I find it absolutely great.
>Quarterdeck did it right - DV is much, much smaller than Windows and, for the
>serious computer user, has much more utility.

I tend to agree.  However, since one can run win /s under DV, there is
no reason to have to choose.  My usual working environment is DV, but
for CorelDraw and (real soon now) WordPerfect for Windows, it is easy
enough to start up Windows within DV.

I wish DV would give us finer tuning control at the .DVP level,
though: I'd like to be able automatically to tailor DV's screen saver
behaviour, and system time-slicing and swapping characteristics, to
the aplication mix currently running.  I also wish the screen saver
were properly mouse-aware.