From: Dave Phillips <dlphilp@bright.net>
To: linux-msdos@vger.kernel.org
Cc: Bart Oldeman <bartoldeman@users.sourceforge.net>
Subject: Re: no MIDI input with dosemu ?
Date: Tue, 20 Jan 2004 15:45:31 -0500 [thread overview]
Message-ID: <400D936B.3030701@bright.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0401201533020.1301-100000@pg5.enm.bris.ac.uk>
Bart Oldeman wrote:
>On Tue, 20 Jan 2004, Dave Phillips wrote:
>
>
>
>> The short story so far is that Stas Sergeev has posted a patch that
>>gives MIDI input to CVS dosemu. I don't know whether Stas's patch is
>>included with the new 1.2.0 dosemu, but I imagine it can be compiled
>>against it anyway (Stas, any additional instructions for your patch +
>>1.2.0 ?).
>>
>>
>
>Stas' patch applies against 1.2.0; it is included in CVS HEAD now. It'll
>probably end up in 1.2.1 though, since it looks stable.
>
>Reason is simply that for 1.2.0 I wanted to concentrate on pure bug fixes,
>no new features since 1.1.99.1.
>
>
Greetings:
Stas's patch does apply without problems to the 1.2.0 sources. I
tested MIDI I/O with Sequencer Plus, recording and playback both worked
fine. Cool work, Bart... :)
Best,
++ dp
next prev parent reply other threads:[~2004-01-20 20:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 6:21 Re: no MIDI input with dosemu ? steve.home
2004-01-16 13:27 ` Dave Phillips
2004-01-16 17:32 ` Stas Sergeev
2004-01-16 22:25 ` Ged Haywood
2004-01-16 23:47 ` Robert Komar
2004-01-20 14:16 ` Dave Phillips
2004-01-20 15:50 ` Bart Oldeman
2004-01-20 20:45 ` Dave Phillips [this message]
2004-01-21 4:42 ` Justin Zygmont
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 17:18 Stas Sergeev
2004-01-08 13:53 Stas Sergeev
2004-01-08 15:16 ` Dave Phillips
[not found] ` <3FFD9C0D.90804@aknet.ru>
[not found] ` <3FFDA3E1.5070508@bright.net>
2004-01-09 1:18 ` Stas Sergeev
2004-01-09 8:31 ` Ryan Underwood
2003-12-26 20:17 Is sound in dosemu a myth? JLB
2004-01-08 13:22 ` no MIDI input with dosemu ? Dave Phillips
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=400D936B.3030701@bright.net \
--to=dlphilp@bright.net \
--cc=bartoldeman@users.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.