Path: utzoo!attcan!uunet!samsung!usc!rutgers!netnews.upenn.edu!msuinfo!cpsvax.cps.msu.edu!kaotai
From: kaotai@cpsvax.cps.msu.edu (Kao David Tai)
Newsgroups: comp.sys.ibm.pc
Subject: MKS Toolkit 3.1 and Windows 3.0
Message-ID: <1990Jun10.175101.13487@msuinfo.cl.msu.edu>
Date: 10 Jun 90 17:51:01 GMT
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University, East Lansing
Lines: 39

I have an IBM PS/2 Model 50Z (a 10Mhz 80286 machine with 1MB memory).
Currently, I have MKS Toolkit Version 3.1 installed with Configuration
4. In this configuration, "command.com" is replaced by MKS Toolkit
"init" program, and I can login as an account with different shell
(command.com or sh.exe). I am quite happy with this setup.

However, after I upgraded my Windows/286 to Windows 3.0, I have
following problems:

1. Window 3.0 can not be launched from "sh.exe", while Windows/286
   has no problem with that.

Well, this is quite all right, I can create an account with 
"command.com" as its default shell for running Windows 3.0. But,
this causes the second problem.

2. In standard mode, I have problem in running most of the non-Windows
   applications, including Quick C 2.0, Word 5.0 etc. I can launch these
   applications from Windows, but when I want to return to Windows, the
   system crashes. The same thing happens when I want to start a DOS
   shell from Windows.

I can solve the above problem with either of the two methods below:

1) Remove "init" and set MKS Toolkit in other configurations.

2) Run Windows in real mode.

However, I do not like these two settings and wonder if there is any 
other solution. Any suggestion will be greatly appreciated.




David Kao               Internet   kaotai@cpsvax.cps.msu.edu 
+-------------------+              kaotai@frith.msu.edu
| Proper disclaimer |   BITNET     kaotai@msu.BITNET
|      Applies.     |   UUCP       ihnp4!msudoc!cpsvax!kaotai
+-------------------+   GEnie      D.KAO