Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!psuvm!dxb132
From: DXB132@psuvm.psu.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: Supervisor stack
Message-ID: <90312.153131DXB132@psuvm.psu.edu>
Date: 8 Nov 90 20:31:31 GMT
References: <476100@neabbs.UUCP>
Organization: Penn State University
Lines: 12

The supervisor stack under both 1.2 and 2.0 is 6,144 bytes. It is typically
located at the top of "local" memory, usually the top of chip mem or $C00000
memory. (I think that's correct, or is the s-stack placed in chip mem on
machines with $c00000 memory too? what about the 3000?)

Anyway, chances are an overflow of the s-stack will just write over memory
that is *probably* not being used. It's not too difficult to extend the range
of the s-stack, or to move it to fast memory for that matter (using the
movessp utility but modified to provide more than 6,144 bytes). Hope this
helps a little...

-- Dan Babcock