public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: various dosemu comments and hacks (sound, delays)
Date: Tue, 25 Feb 2003 22:47:21 +0300	[thread overview]
Message-ID: <3E5BC849.9050001@yahoo.com> (raw)

Hello.

Ryan Underwood wrote:
>> Just wondering where can it be
>> used besides dosemu? 
>  Various other adlib-related things, like Sierra AGI/SCI interpreters that
>  are ported, plugins for sequencer software, etc.  Of course one could 
>  always link in AdPlug or the mame opl2, but the server would simply be a
>  concurrent-execution method of accessing the same functionality so the
>  adlib-client program can simply forward the writes and worry no more 
>  after that.
Yes, that can be usefull. The
downside of that approach is
that the program can itself keep
the /dev/dsp busy (like dosemu does)
and your adlib server will conflict
with an app trying to output the
sound. Of course for the cards that
allows multiple streams this is not
a problem, but for others (like the
pc-speaker:) this can be troublesome.
Perhaps the only solution would be
to make dosemu to use some sound server
and to make your adlib server to use
the same. By linking dosemu with mame
opl emu and implementing the mixing
(which is necessary for dosemu anyway)
doesn't have the aforementioned problem.
The alternative could be to implement
the entire SB in a separate server.
DMA needs to be in another thread/process
anyway, so nuking the SB out of dosemu
and to a separate server process can
be great I think.

> I copied over my Win-OS2 install, which is a hacked WFWG3.11 from IBM for
> use with OS/2, that is a DPMI client instead of VCPI.  But, I couldn't 
> get it to run yet. :(
Probably you have to try 3.1
instead of 3.11.

> Its weird though.  It seems like doing this is turning dosemu into what 
> plex86 tried to be. :)
I don't know much about plex86, but
the power of dosemu is in its great
integration in a linux environment,
i.e. ability to work with the mounted
filesystems, networking etc. Also
dosemu has a good speed due to running
the progs natively rather than emulating
the CPU (emulating only the privileged
instructions is not a big slowdown).
Does the plex86 have all that?

>> simx86 and implement some missing
>> features to it rather than using a
>> bochs as a CPU-emu server as you suggested.
>  Interesting, I will take a look at it.
To make your life easier here is a
patch that resurrects a real-mode part
of simx86 (prot mode is still broken but
it was functional in the past)
https://sourceforge.net/mailarchive/forum.php?thread_id=1662943&forum_id=8386


             reply	other threads:[~2003-02-25 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 19:47 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 19:55 various dosemu comments and hacks (sound, delays) Stas Sergeev
2003-02-24 23:14 ` Ryan Underwood
2003-02-24 17:48 Stas Sergeev
2003-02-24 18:41 ` Ryan Underwood
2003-02-24 14:37 Stas Sergeev
2003-02-24 15:46 ` Ryan Underwood
2003-02-24 19:18 ` Ryan Underwood
2003-02-24  3:35 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=3E5BC849.9050001@yahoo.com \
    --to=stssppnn@yahoo.com \
    --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