From: John Coppens <john@jcoppens.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Remote control of Dosemu
Date: Mon, 21 Jul 2008 19:07:15 -0300 [thread overview]
Message-ID: <20080721190715.3bb5aa00.john@jcoppens.com> (raw)
In-Reply-To: <4884D7BB.5020307@sbcglobal.net>
On Mon, 21 Jul 2008 13:38:51 -0500
Mike McCarty <Mike.McCarty@sbcglobal.net> wrote:
> Another possibility is that it might have a mode to display output
> to the printer. Then you can likely capture INT5 (IIRC) and intercept
> the BIOS interrupts to control the printer, or redirect the printer
> output from DOSEMU. If that's not possible, you could try simulating
> the keypress to force a screen capture to the printer PrintScrn key.
> I recall a program KEYFAKE which I may have lying around which might
> be able to do something like that.
No possibility to change, as far as I can see. A little surprised though,
because the program works on Hercules and CGA screens, so there should be
some kind of selection mechanism. I suspect it is automatic.
I remember 'keyfake'. In fact, I wrote a TSR program that fakes
keypresses. I hadn't thought about PrtScr though. I believe there was an
interrupt called when PrtScr was pressed. But, I seem to remember
it prints directly, so I suspect it'll be easier to modify the TSR to
make it read the screen memory directly.
Thanks for the suggestions!
John
next prev parent reply other threads:[~2008-07-21 22:07 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
2008-07-21 18:38 ` Mike McCarty
2008-07-21 22:07 ` John Coppens [this message]
[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=20080721190715.3bb5aa00.john@jcoppens.com \
--to=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