From: Bryan J Smith <b.j.smith@ieee.org>
To: Steve Cohen <stevecoh1@comcast.net>
Cc: Mike McCarty <Mike.McCarty@sbcglobal.net>, linux-msdos@vger.kernel.org
Subject: Re: EMM386 not installed - protected mode software already running.
Date: Wed, 20 Oct 2010 08:19:04 -0700 (PDT) [thread overview]
Message-ID: <234830.53737.qm@web110811.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4CBE559F.8090400@comcast.net>
If it's PharLap286, I want to almost say -- for certain -- it's first-gen, Ring
0 gobbling VCPI.
Again, an additional test is to try it on 32-bit NT (4-6) and its NTVDM. If it
doesn't work (try several), then it's not DPMI compatible and taking issue with
something else holding Ring 0. DPMI really addresses all of the shortcomings of
VCPI, and allows multi-tasking (really task sharing, to a point, long story) in
DOS. As such, real, 32-bit Virtual86/Protected386 operating systems (NT/NTVDM,
Linux/DOSEmu, etc...) can then offer DPMI with the same capabilities.
I also mentioned DOSBox. DOSBox can actually emulate Ring 0, including for some
VCPI programs. According to the status page, it seems to be limited to Origin
games, don't know what extender they used. Could be unrelated to PharLap and
most early, VCPI-based implementations. But it's worth a shot.
http://www.dosbox.com/status.php?show_status=1
DOSBox isn't a full DOS in the traditional sense, but a DOS emulator that
doesn't require DOS itself. DOSEmu is more like a virtualized DPMI environment,
and then you run DOS under it -- like NTVDM in NT/Windows, although Microsoft
bundles the required DOS support (DOS kernel, COMMAND.COM instead of NT's native
CMD.EXE, etc...).
-- Bryan
P.S. For several years Concurrent (among others) was marketing itself as a
networked/remote terminal, multiuser DOS solution. Understand these solutions
are based on DR-DOS and DPMI-based DPMS, and will also be incompatible with VCPI
if those services load. Only Real86 DOS without anything using DPMI or an
emulated DOS under another OS, with Ring 0 available (emulated) will work, for
most of those early extenders.
----- Original Message ----
From: Steve Cohen <stevecoh1@comcast.net>
Thanks for this information, Bryan. Unfortunately, it, together with
further investigations into our source code base, convinces me that our
application does indeed depend on the VCPI-based early versions of
PharLap (I didn't know where to look previously) and will ultimately
prove to be incompatible with DOSEmu. Some of the PharLap links are
pretty loose and could possibly be converted to work differently, but
some of the third party stuff like Greenleaf Comms is pretty tightly
linked with PharLap286 and I don't think we want to be changing that.
But that's okay, this little walk down "memory lane" (pun intended)
didn't waste too much time and has given me some other ideas besides
rewrite that may ultimately prove more fruitful.
I'd like to thank all you guys here for your support, Viva Open Source.
A826849D-9CF0-6C1F-CD7C-8D85ADCB8FD9
1.03.01
next prev parent reply other threads:[~2010-10-20 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 13:49 EMM386 not installed - protected mode software already running Steve Cohen
2010-10-19 14:28 ` Steve Cohen
2010-10-19 16:09 ` Frank Cox
2010-10-19 16:16 ` Frank Cox
[not found] ` <4CBDBF81.8010601@sbcglobal.net>
2010-10-19 16:54 ` Steve Cohen
2010-10-19 17:48 ` Bryan J Smith
2010-10-19 19:34 ` Bryan J Smith
2010-10-19 19:43 ` Bryan J Smith
2010-10-20 2:36 ` Steve Cohen
2010-10-20 15:19 ` Bryan J Smith [this message]
2010-10-20 16:14 ` Steve Cohen
2010-10-20 17:00 ` Bryan J Smith
2010-10-20 18:22 ` Mike McCarty
2010-10-20 20:11 ` Frank Cox
[not found] ` <AANLkTinVjXgQaH939Kq1H1B6g=f1ty16bGFdULUqSHDb@mail.gmail.com>
2010-10-20 20:56 ` solarflow99
2010-10-20 21:06 ` Mike McCarty
2010-10-20 23:23 ` solarflow99
2010-10-21 6:42 ` Paul Crawford
2010-10-21 12:29 ` Steve Cohen
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=234830.53737.qm@web110811.mail.gq1.yahoo.com \
--to=b.j.smith@ieee.org \
--cc=Mike.McCarty@sbcglobal.net \
--cc=linux-msdos@vger.kernel.org \
--cc=stevecoh1@comcast.net \
/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