From: Dan Olson <dano@agora.rdrop.com>
To: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: Adventure - the answer to what went wrong?
Date: Thu, 12 Dec 2002 12:27:00 -0800 (PST) [thread overview]
Message-ID: <20021212122436.C57693-100000@agora.rdrop.com> (raw)
In-Reply-To: <1039726339.22174.29.camel@irongate.swansea.linux.org.uk>
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
On Thu, 12 Dec 2002, Alan Cox wrote:
> On Thu, 2002-12-12 at 19:11, Richard Wallman wrote:
> > I put forward the theory that it fails because the two strings are not
> > in the same 64Kb segment. The reason no-one has found this problem
> > before is that so far all of the binaries have been <64Kb in size.
>
> ELKS only supports a max of 64K code / 64K data per app...
>
>
>
> Alan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2002-12-12 20:27 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 [this message]
2002-12-12 20:29 ` Harry Kalogirou
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=20021212122436.C57693-100000@agora.rdrop.com \
--to=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