From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "jerryc@innerpeace.org" <jerryc@innerpeace.org>
Cc: linux-8086@vger.kernel.org
Subject: Re: New Member VERY hot on 8086's
Date: 12 Jan 2003 23:28:56 +0000 [thread overview]
Message-ID: <1042414135.16288.52.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3E21D8FC.1050305@innerpeace.org>
On Sun, 2003-01-12 at 21:07, jerryc@innerpeace.org wrote:
> We did plan to do this project with FreeDOS, but feel that using ELKS or
> Minix would help in the promotion of linux, and would rather go that route.
FreeDOS is probably the most predictable environment. ELKS might buy you
something if you wanted networking, but due to CPU limitations it can't
buy you anything on the security front really.
> In order to get this working, we will need a good 8086 emulator to run
> on current versions of linux. I read you had an elksemu. Does it work?
> What emus would you recommend.
elksemu runs elks binaries on linux - it works. DOSemu will run FreeDOS
or ELKS itself.
> Would stripping out some of the unneeded things make it run faster?
Only if your application needs more space than you have RAM. Otherwise
it is down to the app alone and the compiler you use. ELKS can do
swapping (thanks to Harri) but you've got a whole 400K or so of memory
free to play in - which in text mode is a *lot* of space!
Alan
next prev parent reply other threads:[~2003-01-12 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 21:07 New Member VERY hot on 8086's jerryc
2003-01-12 23:28 ` Alan Cox [this message]
[not found] ` <3E2220A6.7050500@innerpeace.org>
[not found] ` <1042470345.18624.17.camel@irongate.swansea.linux.org.uk>
2003-01-14 4:27 ` jerryc
2003-01-13 19:43 ` Dan Olson
2003-01-14 4:15 ` jerryc
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=1042414135.16288.52.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jerryc@innerpeace.org \
--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