Path: utzoo!utgpu!watmath!clyde!att!rutgers!tut.cis.ohio-state.edu!bloom-beacon!gatech!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!unido!fauern!faui44!mlelstv
From: mlelstv@faui44.informatik.uni-erlangen.de (Michael van Elst )
Newsgroups: comp.sys.amiga.tech
Subject: Re: Exec's use of the user stack for a task
Message-ID: <778@faui10.informatik.uni-erlangen.de>
Date: 19 Dec 88 16:18:30 GMT
References: <8812180904.AA24272@postgres.Berkeley.EDU>
Reply-To: mlelstv@faui44.UUCP (Michael van Elst (kdebugger))
Organization: CSD., University of Erlangen, W - Germany
Lines: 14

In article <8812180904.AA24272@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
>
>	Not to begrudge EXEC.  All in all EXEC has only 4 or 5 incorrectly
>implemented items ... >EXEC library base in chip memory).
 In case nobody's figured it out, that's a pretty good record for the core
>of an operating system.
>					-Matt
Yes that is. BTW, EXEC Base is in C00000 memory if you have installed memory there.
Any other memory is noticed after Exec is initialized, you would have to do a complete
warm boot to use it.

				Michael van Elst

E-mail: UUCP: ...uunet!unido!fauern!faui44!mlelstv