Xref: utzoo comp.os.msdos.apps:775 comp.windows.ms:8003
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!gatech!prism!jgb
From: jgb@prism.gatech.EDU (James G. Baker)
Newsgroups: comp.os.msdos.apps,comp.windows.ms
Subject: Re: MKS Toolkit and DESQView or Windows
Message-ID: <18875@hydra.gatech.EDU>
Date: 19 Dec 90 03:28:49 GMT
References: <1990Dec18.163111.1798@cunixf.cc.columbia.edu>
Followup-To: comp.os.msdos.apps
Organization: Georgia Institute of Technology
Lines: 22

In article <1990Dec18.163111.1798@cunixf.cc.columbia.edu> igb@cunixa.cc.columbia.edu (Isidore G Bendrihem) writes:
>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.

I am a big mks and DESQview fan but had trouble mixing the two.  I wanted a 
ksh (mks) window but I think mks messes with command.com or DOS at the 
DESQview level.  Mks, I believe, uses an undocumented DOS call that allows
the switch character to be "-" instead of "/".  Some programs can handle it
(Norton, I think), but others die.  (This also allows the file system
to use "/" instead of "\".  Note: I was using MKS 2.3 and DV 2.26.

Good luck.

-- 
BAKER,JAMES G - Lab Technician, School of Electrical Engineering
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jgb 
Internet: jgb@prism.gatech.edu