Xref: utzoo comp.os.msdos.apps:795 comp.windows.ms:8079
Path: utzoo!attcan!ontmoh!rwh
From: rwh@ontmoh.UUCP (Russell Herman)
Newsgroups: comp.os.msdos.apps,comp.windows.ms
Subject: Re: MKS Toolkit and DESQView or Windows
Message-ID: <661837112.21091@ontmoh.UUCP>
Date: 22 Dec 90 03:38:32 GMT
References: <1990Dec18.163111.1798@cunixf.cc.columbia.edu>
Organization: Ontario Ministry of Health -- GOMIG BBS, Toronto, Canada
Lines: 30

From article <1990Dec18.163111.1798@cunixf.cc.columbia.edu>, by igb@cunixa.cc.columbia.edu (Isidore G Bendrihem):
> I'm planning on purchasing the MKS Toolkit, and I'd like to run it under
> either Windows 3.0 or DESQView.  Anybody know of any compatibility problems
> between the Toolkit and either of the windowing environments?  I'm concerned
> with the text editor vi (some editors have problems running under 
> DESQView and/or Windows).  Also, how much memory "sh" frees while executing
> other programs?  Thanks. Respond to this account and I'll simmurize.
> 
> Isidore Bendrihem
> igb@cunixa.cc.columbia.edu

Yes, there are some minor problems.  MKS vi, at least the version I have from
6 months ago, is the only text-mode program I've seen that won't run in a
virtualized window.  It just locks up the window and beeps.  The workaround
is to run it unvirtualized.  Or, if you don't need 100% fully compatible vi,
run ELVIS instead.  The other tools run fine in DESQView (I don't run the
shell, but it can be done).  I've been quite happy with the toolkit and
support from MKS.

Russ Herman
lsuc!ontmoh!rwh
-- 

Russell Herman
...!lsuc!ontmoh!rwh
Microcomputer Support Specialist
Ontario Ministry of Health
15 Overlea Blvd., 2nd Fl.
Toronto, ON Canada M4H 1A9
Voice: +1 416 963-3320 Fax: +1 416 963-1878