Path: utzoo!mnetor!uunet!yale!letsch-david
From: letsch-david@CS.YALE.EDU (David Letsch)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Windows Anyone?
Message-ID: <27922@yale-celray.yale.UUCP>
Date: 26 Apr 88 05:52:20 GMT
References: <4490012@hpcvca.HP.COM> <1097@neoucom.UUCP> <798@netxcom.UUCP> <4778@cup.portal.com>
Sender: root@yale.UUCP
Reply-To: letsch-david@CS.YALE.EDU (David Letsch)
Organization: Yale University Computer Science Dept, New Haven CT  06520-2158
Lines: 20
Keywords: MS Windows 386 Desqview


  The continued attacks on Windows/386 seem unjustified.  I have used
MS Windows 2.03 and find it seriously limited,  but Windows/386 is
really a fantastic product.  It does use an incredible amount of
memory,  and imposes slightly more overhead than Desqview,  but you
get a low more from it.  Windows/386 does a much better job of handling
"misbehaved" programs (Brief or Wordstar 4.0 in 43-line mode, Autocad
Release 9, etc.) than Desqview does,  especially if one is using VGA
mode.  Windows/386 also does a better job of scaling applications down to
fit into a window than Desqview.  While I'll admit that Desqview's
ability to control time slicing has advantages,  I don't consider them
to be too critical.  Also,  before I'm attacked on this,  I use both
products regularly - I'm a college student with a Model 80 in my room
(Windows/386)  and a Zenith Z-181 laptop for library work (Desqview).
And,  like it or not,  Windows/386 has considerably more claim to the
future (OS/2 PM, IBM SAA, etc.) than Desqview - it might help ease the
transition.  The real point of this article is that most of the
complaints about Windows/386 that I see in this newsgroup are valid
really only for Windows 2.03 (except for the Terminal program -
doesn't work for me, either.)