ksh acting weird under SCO Unix

[Tim W Smith]

We obtained the V.3.2 release 2 update recently (I think that's
the one.  Whatever is the latest).  I decided not to install it,
however, because the development system update is backordered.

I extracted ksh from one of the installation floppies, however.
I did this by simply using tar to grab the file and then using
uncompress to get an executable.

When I try to run it, it behaves very strangely.  As long as I
only use shell builtin commands, all is well.  If I try to do
things that run other programs, however, after anywhere from
one to ten or so commands, the shell exits.  Worse, it kills
everything in the process group.  This also happens right away
if I try to run a command that is not found.

If I set the option to ignore EOF, it gets more interesting.
Before exiting and killing the process group, it says

	type 'exit' to logout

The above message is displayed exactly 11 times.  (I told
you that this was going to be strange).

It gets stranger.  After the process group exits, the terminal
is screwed up.

For example, if I do this from the console in single user mode,
after the process group dies, the message comes up that says to
entry the root password for single user mode or enter control-D
for multiuser mode.

An error message is then printed by login (I forget the exact
message (I'm typing this from home), but it is something about
an error on input).

At this point, the console is looping asking for the password
or control-D and then getting the error from login.

Keyboard input to the console does not seem to work at this
point.

Does anyone have any idea what is going on here?  Why does ksh exit
in the first place?  Why does it take the entire process group?  (Note
that this happens even if I run it by typing ksh at the sh prompt, so
it is not the process group leader)  Why does it print the 'exit' to
logout message exactly 11 times before going away?

						Tim Smith