public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: Dan Olson <dano@agora.rdrop.com>
Cc: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: Adventure - the answer to what went wrong?
Date: 12 Dec 2002 22:29:26 +0200	[thread overview]
Message-ID: <1039724964.1821.28.camel@cool> (raw)
In-Reply-To: <20021212122436.C57693-100000@agora.rdrop.com>


> 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




  reply	other threads:[~2002-12-12 20:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 13:07 ELKS port of Adventure - help needed :) Paul Nasrat
2002-12-11  8:19 ` Phil Goembel
2002-12-11 21:27   ` Richard Wallman
2002-12-11 22:22     ` Richard Wallman
2002-12-11 22:46       ` Richard Wallman
2002-12-11 22:51       ` Paul Nasrat
2002-12-11 23:59       ` Phil Goembel
2002-12-12  7:39         ` Paul Nasrat
2002-12-12  8:18           ` Paul Nasrat
2002-12-12 19:11         ` Adventure - the answer to what went wrong? Richard Wallman
2002-12-12 20:21           ` Harry Kalogirou
2002-12-12 20:52           ` Alan Cox
2002-12-12 20:27             ` Dan Olson
2002-12-12 20:29               ` Harry Kalogirou [this message]
2002-12-12 20:41                 ` Dan Olson
2002-12-12 21:15               ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1039724964.1821.28.camel@cool \
    --to=harkal@gmx.net \
    --cc=dano@agora.rdrop.com \
    --cc=linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox