From: "Bart Oldeman" <bartoldeman@users.sourceforge.net>
To: John Coppens <john@jcoppens.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Remote control of Dosemu
Date: Sat, 19 Jul 2008 13:14:22 -0400 [thread overview]
Message-ID: <c3d607cc0807191014p64b1250fg948d83348b310f03@mail.gmail.com> (raw)
In-Reply-To: <20080718011954.dc5e47b5.john@jcoppens.com>
2008/7/18 John Coppens <john@jcoppens.com>:
> I need to 'remote control' an old program. I found in the FAQ that it is
> possible to feed keyboard commands into an application.
>
> The problem is that I would need feedback from the program's screen,
> while it is running. Is there any way to get to the screen output? As
> usual, this apps write immediately to the scree (bypasses the BIOS).
You can try running in terminal mode ("dosemu -t") and redirecting
both input and output.
The output will contain lots of escape characters but you might be
able to fish out the output you need (even with direct video writes,
as long as they are characters, not graphics).
Dumb mode is most convenient but does not work with direct video writes.
E.g., this gives you such a file:
echo -e "exitemu\r" | dosemu -t > log
You'll probably have to play a bit with pipes to get the whole thing working.
Bart
next prev parent reply other threads:[~2008-07-19 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 4:19 Remote control of Dosemu John Coppens
[not found] ` <48801E06.9080700@pobox.com>
[not found] ` <20080718135339.75dfae5c.john@jcoppens.com>
2008-07-18 17:21 ` Alain M.
2008-07-18 21:35 ` John Coppens
2008-07-18 22:24 ` Richard
2008-07-19 0:18 ` John Coppens
2008-07-19 0:24 ` Alain M.
2008-07-19 3:54 ` Frank Cox
2008-07-21 14:51 ` Alain M.
2008-07-19 17:14 ` Bart Oldeman [this message]
2008-07-21 18:38 ` Mike McCarty
2008-07-21 22:07 ` John Coppens
[not found] ` <20080721161839.43f36b4c.john@jcoppens.com>
2008-07-22 2:23 ` Mike McCarty
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=c3d607cc0807191014p64b1250fg948d83348b310f03@mail.gmail.com \
--to=bartoldeman@users.sourceforge.net \
--cc=john@jcoppens.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