From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Olson <dano@agora.rdrop.com>
Subject: Re: Adventure - the answer to what went wrong?
Date: Thu, 12 Dec 2002 12:41:47 -0800 (PST)
Sender: linux-8086-owner@vger.kernel.org
Message-ID: <20021212124110.Y57693-100000@agora.rdrop.com>
References: <200212121911.gBCJB75G012842@eddie.loc>
 <1039726339.22174.29.camel@irongate.swansea.linux.org.uk> 
 <20021212122436.C57693-100000@agora.rdrop.com> <1039724964.1821.28.camel@cool>
Mime-Version: 1.0
Return-path: <linux-8086-owner@vger.kernel.org>
In-Reply-To: <1039724964.1821.28.camel@cool>
List-Id: <linux-8086.vger.kernel.org>
Content-Type: TEXT/PLAIN; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Linux 8086 <linux-8086@vger.kernel.org>

> > 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 :)
> >
> > 	Dan
>
> It is ok for a file to be bigger than 64K since initialized data exist
> in the file along with the code.
>
> Harry

That's what I was thinking, just haven't done any x86 asm for a while.

	Dan