Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uwm.edu!bionet!ames!uhccux!waikato.ac.nz!comp.vuw.ac.nz!munnari.oz.au!csc.anu.edu.au!manuel!ccadfa!prolix!dac
From: dac@prolix.ccadfa.oz.au (Andrew Clayton)
Newsgroups: comp.sys.amiga
Subject: Re: Multitasking at home (Was Reality check: ....)
Message-ID: <188738c5.ARN09828@prolix.ccadfa.oz.au>
Date: 15 Jan 91 11:44:37 GMT
References: <37101@cup.portal.com> <41689@ut-emx.uucp> <127515@linus.mitre.org> <15355@sdcc6.ucsd.edu> <178@lsw.UUCP>
Reply-To: ccadfa.cc.adfa.oz.au!prolix!Dac
Followup-To: comp.sys.amiga.misc
Organization: I'm not an Organization - I'm a person!
Lines: 21

In article <178@lsw.UUCP>, Greg writes:

> > I don't beleive this is actually true.  I think there may be an
> > arbitrary limit (20 sounds like a familiar number) of CLI/Shells that
> > you can open, but I beleive that the number of tasks that Exec can
> > handle is limited only by RAM.  The static limit on CLIs is arbitrary;
> 
> I have an Amiga 2500 with 3 megs of RAM and yet I can only have about
> 20 processes running.  I have experimented with this and found it to be
> be very true...  If you open a CLI and type "run clock" 19 times and then 
> open another CLI and try to "run" anything then you can't do it! You can't
> even run anything from WB!!

Get 2.0. It's wonderful, and removes the '20 cli' restriction.

However, I would question your sanity in wanting to run 20 different CLI's.

I'm that type of guy. :-)

Dac
--