From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: App database, libsynth
Date: Sat, 12 Jul 2003 17:40:26 -0500 [thread overview]
Message-ID: <20030712224026.GL1031@dbz.icequake.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307122133310.17723-100000@enm-bo-lt.localdomain>
Hi Bart,
On Sat, Jul 12, 2003 at 09:57:05PM +0100, Bart Oldeman wrote:
> >
> > Are you certain about emulation necessary for 16bit apps? I look at the
> > developer's overview for hammer, and it starts out with:
> >
> > "The x86-64 architecture supports legacy 16-bit and 32-bit applications
> > and operating systems without modification."
>
> look carefully. x86-64 has three modes (instead of the familiar real
> and protected modes) that can only be (normally) switched between
> by rebooting:
> real -- legacy -- long
> 16bit 32bit pm 64bit pm
> 16bit pm 32bit pm (compatibility)
> vm86 16bit pm (compatibility)
>
> dosemu runs in legacy mode but then your x86-64 is just an Athlon on
> steroids and other processes cannot use more than 4GB of memory.
>
> In long mode there is no vm86.
It looked like the long vs legacy mode could be toggled on a per segment
basis in the rest of the information I pasted. What do you think that
refers to?
> DOSEMU is intrinsically a little more difficult to configure (primarily
> because it needs an independent DOS rather than having one built in) and
> no matter how good FreeDOS gets it seems there will always be some who
> really want to run another DOS in it.
:)
> At least xdosemu+freedos should be
> as easy as possible (it's been easy since 1.0.2, it's just that extracting two
> tarballs in one's home directory is a little unusual -- that's why I tried
> to simplify the systemwide compilation and installation from source, so
> making RPMs and DEBs should be easy)
The initial setup at least on Debian is a breeze today, it's just
finding the right settings for some application that tends to be the
annoying part, which hopefully gets solved through the application db.
And, many users don't like to hand edit config files, which is why I write
that script to at least partially automate that.
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
next prev parent reply other threads:[~2003-07-12 22:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 19:02 App database, libsynth Stas Sergeev
2003-07-11 19:59 ` Ryan Underwood
2003-07-11 20:23 ` Bart Oldeman
2003-07-11 22:03 ` Ryan Underwood
2003-07-12 20:57 ` Bart Oldeman
2003-07-12 22:40 ` Ryan Underwood [this message]
2003-07-12 16:30 ` Jan Willem Stumpel
2003-07-12 19:03 ` Ryan Underwood
2003-07-12 20:13 ` Jan Willem Stumpel
2003-07-12 21:56 ` App database, libsynth (now EGA problems) Ryan Underwood
2003-07-12 23:22 ` Paul Eggleton
2003-07-13 0:42 ` Ryan Underwood
2003-07-12 19:19 ` App database, libsynth Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2003-07-17 16:07 Stas Sergeev
2003-07-17 23:09 ` Ryan Underwood
2003-07-14 17:43 Stas Sergeev
2003-07-14 21:06 ` Ryan Underwood
2003-07-15 8:38 ` Paul Eggleton
2003-07-15 10:10 ` Ryan Underwood
2003-07-15 12:26 ` Paul Eggleton
2003-07-15 23:48 ` Ryan Underwood
2003-07-13 19:50 Stas Sergeev
2003-07-13 21:27 ` Ryan Underwood
2003-07-13 2:37 Stas Sergeev
2003-07-13 5:00 ` Ryan Underwood
2003-07-13 0:29 Stas Sergeev
2003-07-13 0:59 ` Ryan Underwood
2003-07-13 0:21 Stas Sergeev
2003-07-13 0:56 ` Ryan Underwood
2003-07-13 0:09 Stas Sergeev
2003-07-12 23:47 Stas Sergeev
2003-07-13 0:50 ` Ryan Underwood
2003-07-10 17:20 App database Stas Sergeev
2003-07-11 17:30 ` App database, libsynth Ryan Underwood
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=20030712224026.GL1031@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=linux-msdos@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