Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!pprg.unm.edu!unmvax!tut.cis.ohio-state.edu!osu-cis!att!ihlpb!psfales
From: psfales@ihlpb.ATT.COM (Peter Fales)
Newsgroups: comp.sys.ibm.pc
Subject: Re: MKS Toolkit question
Message-ID: <10120@ihlpb.ATT.COM>
Date: 3 Apr 89 23:02:34 GMT
References: <465@thor.wright.EDU> <1040012@hprnd.HP.COM> <2031@bingvaxu.cc.binghamton.edu>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 27

In article <2031@bingvaxu.cc.binghamton.edu>, vu0112@bingvaxu.cc.binghamton.edu (Cliff Joslyn) writes:
> 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. 

With all the talk about memory size under ksh, I wonder if someone else
could confirm the results of a test I made.  I wanted to find out how
much memory I saved running with /etc/init as my shell and using the
init/login/ksh process rather than booting command.com and invoking ksh,
so I tried it both ways.

I don't remember the exact numbers, but assuming I did the experiment
correctly, there was almost no difference  between the two.  This 
pretty much cured me of any further desire to use init/login.  I assume
this is because the transient portion of command.com is being discarded
and the resident portion is comparable in size to init.exe.

Any gurus out there to confirm or deny?

-- 
Peter Fales			AT&T, Room 5B-414
				2000 N. Naperville Rd.
UUCP:	...att!ihlpb!psfales	Naperville, IL 60566
Domain: psfales@ihlpb.att.com	work:	(312) 979-8031