public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "jerryc@innerpeace.org" <jerryc@innerpeace.org>
To: linux-8086@vger.kernel.org, Tim Spalding <dominus@citcom.net>,
	Doug Smith <bdsmith@buncombe.main.nc.us>
Subject: Fwd: Re: pcemu
Date: Tue, 14 Jan 2003 10:16:54 -0500	[thread overview]
Message-ID: <3E2429E6.7060108@innerpeace.org> (raw)
In-Reply-To: 1042545537.18879.83.camel@pearl.tao.co.uk

This is a reply I got from David Given from the PCemu project. Any 
comments on his assessments of emulators would be appreciated.

Also, in doing some research, it became clear to me that even though 
we'll be using old desktop machines, what we're trying to do is very 
much like an embedded system in that what the computer will be doing 
will be very limited and known in advance. Of course, if anybody ever 
wanted to use the computer for something else later, they could just 
install different software.

Jerry:
>>Assuming we'll be using ELKS, would you recommend PCemu, DOSemu, or 
>>ELKSemu?

David Given:
> PCEmu is a software-only interpreter implementing an 8086 that will run
> on anything, if a bit slowly (although on modern machines still way
> faster than the real hardware).
> 
> DOSEmu uses processor tricks to implement a virtual PC at full speed. It
> will, however, only run on an Intel-based machine.
> 
> ELKSemu is a fairly unpleasant hack to allow you to run a single ELKS
> executable on an Intel-based machine as if it was a native executable.
> 
> PCEmu is probably the simplest to set up, but may be a little buggy;
> DOSEmu is the most complete, but is unfortunately rather complicated.
> ELKSemu is useful for developing applications without having to reboot
> ELKS all the time. I'd probably suggest using DOSEmu.



J:
>>One big advantage of using a "nix" based system is that it will help 
>>promote Linux. Promoting something with the name DOS in it has been a 
>>block. The load time won't matter much, and the extra security of not 
>>having all users have root access, as they do in DOS, will be important.

DG:
> *nods*
> 
> Do let me know how you get on; it's been a while since I've done
> anything with ELKS or pcemu, but if I can be of any help don't hesitate
> to ask.




      parent reply	other threads:[~2003-01-14 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E21BDCC.6050605@innerpeace.org>
     [not found] ` <1042455624.15252.11.camel@pearl.tao.co.uk>
2003-01-14  4:28   ` Fwd: Re: pcemu jerryc
     [not found]   ` <3E23727A.2070500@innerpeace.org>
     [not found]     ` <1042545537.18879.83.camel@pearl.tao.co.uk>
2003-01-14 15:16       ` jerryc [this message]

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=3E2429E6.7060108@innerpeace.org \
    --to=jerryc@innerpeace.org \
    --cc=bdsmith@buncombe.main.nc.us \
    --cc=dominus@citcom.net \
    --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