From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Adventure - the answer to what went wrong?
Date: 12 Dec 2002 21:15:30 +0000
Sender: linux-8086-owner@vger.kernel.org
Message-ID: <1039727730.22174.36.camel@irongate.swansea.linux.org.uk>
References: <200212121911.gBCJB75G012842@eddie.loc>
	<1039726339.22174.29.camel@irongate.swansea.linux.org.uk> 
	<20021212122436.C57693-100000@agora.rdrop.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-8086-owner@vger.kernel.org>
In-Reply-To: <20021212122436.C57693-100000@agora.rdrop.com>
List-Id: <linux-8086.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Dan Olson <dano@agora.rdrop.com>
Cc: Linux 8086 <linux-8086@vger.kernel.org>

On Thu, 2002-12-12 at 20:27, Dan Olson wrote:
> Also, the file size is 84k, but that doesn't mean that the code segment is
> going to be more than 64k, does it?  Does the whole file get loaded into
> memory and executed, or can there be other "stuff" in that file besides
> executable code that may not get loaded into the code segment?  I haven't
> messed with this stuff in a while, so I don't remember :)

"size" should tell you.

Basically you have code at CS:0 for upto 64K (and possibly shared). Then
you have data at DS:0->n  and stack at DS:[topsize] going down and the
dynamic memory space settable using chmem.