Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!bingvaxu!vu0112
From: vu0112@bingvaxu.cc.binghamton.edu (Cliff Joslyn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: MKS Toolkit question
Message-ID: <2031@bingvaxu.cc.binghamton.edu>
Date: 31 Mar 89 14:51:11 GMT
References: <465@thor.wright.EDU> <1040012@hprnd.HP.COM>
Reply-To: vu0112@bingvaxu.cc.binghamton.edu.cc.binghamton.edu (Cliff Joslyn)
Organization: SUNY Binghamton, NY
Lines: 18

In article <1040012@hprnd.HP.COM> pyt@hprnd.HP.COM (Pierre-Yves Thoulon) writes:
>Note that the Toolkit offers an exec command that allows you to replace
>the shell with the program you want to execute, instead of creating a
>child. This might free up the memory you need. I haven't tried this
>so I can't really tell.

I do this regularly.  I have an 'alias exdos="exec command.com"', and
when I'm tight it works just fine, freeing up the 70K+ differential
between ksh and command.com.  When I then EXIT from DOS again, ksh
reloads itself.  Also, on ^D or 'exit' from ksh, any TSRs loaded after
loading ksh itself (i.e.  not loaded by /etc/inittab before ksh), are
wiped from memory.  Very convenient. 

-- 
O---------------------------------------------------------------------->
| Cliff Joslyn, Cybernetician at Large
| Systems Science, SUNY Binghamton, vu0112@bingvaxu.cc.binghamton.edu
V All the world is biscuit shaped. . .