Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!uwvax!puff!cat9.cs.wisc.edu!schaut
From: schaut@cat9.cs.wisc.edu (Richard Schaut)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview vs Windows?
Message-ID: <4107@puff.cs.wisc.edu>
Date: 18 Dec 89 14:34:11 GMT
References: <1640035@hpspcoi.HP.COM> <640@qvax2.UUCP>
Sender: news@puff.cs.wisc.edu
Reply-To: schaut@cat9.CS.WISC.EDU (Richard Schaut)
Organization: U of Wisconsin CS Dept
Lines: 28

In article <640@qvax2.UUCP> stv@qvax2.UUCP (Steve Vance@ex2499) writes:
| In article <1640035@hpspcoi.HP.COM> kluksdah@hpspcoi.HP.COM (Keith Kluksdahl) writes:
| >                   The better question might be, will anyone
| >out there share their opinion on Desqview vs Windows?
| 
| This is an easy one.  Desqview and Windows both do multi-tasking, and
| both cost about the same.  The big difference is that Desqview will 
| essentially run ANY DOS PROGRAM that you are currently using.  To run
| a program under Windows, you need to have a $pecial Windows version.
| Also, Windows needs a more in the way of system resources in order to
| be able to run.

This isn't entirely correct.  I've run Procomm _in_ a window, and have run
the Turbo C IDE at full screen without any problems at all.  I can't say
that _all_ msdos programs will run under Windows, but I can't think of
any more hostile to the Windows environment than those two.  Also, if you
have a LIM 4.0 memory board, Windows' lust for memory is inconsequential.

From a programmer's standpoint, Windows is definitely the way to go because
of its close relationship to the OS/2 Presentation Manager.  Write a
program for one environment, and you've virtually written a program for the
other.


--
Rick

"Any questions?  Any answers?  Anyone care for a mint?" -- Rita Rudner