Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!sunybcs!bingvaxu!cjoslyn
From: cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn)
Newsgroups: comp.sys.ibm.pc
Subject: Some problems with the latest MKS Toolkit
Message-ID: <2905@bingvaxu.cc.binghamton.edu>
Date: 3 Feb 90 03:32:06 GMT
Reply-To: cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn)
Organization: SUNY Binghamton, NY
Lines: 62


This is a simple bug report that I'm sending a copy of to the net. 
Perhaps these problems are in some way unique or sepcial to my
configuration.  In no way is this a general complaint against the MKS
company, which produces some of the finest software available for DOS.

I have MKS Toolkit v 3.1 running in configuration 5.  In 'inittab' I
have 'switch -', then I load a mouse driver, Superkey, and Sidekick
before running the shell.  I set ROOTDIR=c:/mks and run the shell with
the '-R 0' option for partial disk swapping. 

Problems:

1) Most of my scripts break in an annoying yet functional way.  I use
the Sidekick editor for most of my scripts.  For a script like this:

	# junk.ksh
	echo "Hello"

I'd get:

	% junk
	Hello
	junk.ksh 3: : not found

Basically, it's telling me I've got a bad EOF, and it's trying to
interpret a bad line.  Note that I have an extra carriage return
following 'echo "Hello"'.

Now here's the weird part: when I use a different editor, say
MicroEmacs, this doesn't happen.  Further, uEmacs writes the file out
with a size one more than SK, yet the look identical when I look at them
in a hex editor.  Note that ksh doesn't fail in earlier versions,
doesn't fail without that extra line at the EOF, and doesn't fail with:

	% sh -c junk.ksh

2) I have a script 'exdos.ksh':

	# exdos.ksh
	exec $COMSPEC -e:4000

to exec command.com in place of sh.exe.  This worked fine in previous
versions, and when I needed an extra 30-40K of RAM was a cheap fix. 
Then when you exit from command.com:

	C> exit

ksh.exe reloads itself nicely.  This now hangs the machine.

3) A much smaller point: in Emacs editing mode of the shell, in the
previous version typing down-arrow when at the end of the history list
would give a blank line.  Now it gives an error bell.  Perhaps this is a
"feature"?

Any comments? I know that MKS listens in, so I'll hope for a reply
before I call them with this report.
-- 
O------------------------------------------------------------------------->
| Cliff Joslyn, Cybernetician at Large, cjoslyn@bingvaxu.cc.binghamton.edu
| Systems Science, SUNY Binghamton, Box 1070, Binghamton NY 13901, USA
V All the world is biscuit shaped. . .