All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: FreeDOS <linux-msdos@vger.kernel.org>
Subject: Re: Remote control of Dosemu
Date: Mon, 21 Jul 2008 21:23:10 -0500	[thread overview]
Message-ID: <4885448E.3090203@sbcglobal.net> (raw)
In-Reply-To: <20080721161839.43f36b4c.john@jcoppens.com>

John Coppens wrote:
> 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

What I had in mind is that DOSEMU probably emulates "PrintScreen" by
sending the output to a Linux printer. You might be able to tell
DOSEMU to send it to a regular Linux file and postprocess that.
There is a BIOS call to send a single character to the printer,
which is INT5, I think. Anyway, trying to get just a file visible
to Linux is more likely to succeed than any number of TSRs doing
junk under the emulated MSDOS, having done a few old popup TSRs
myself.

Mike
-- 
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!

      parent reply	other threads:[~2008-07-22  2:23 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
     [not found]   ` <20080721161839.43f36b4c.john@jcoppens.com>
2008-07-22  2:23     ` Mike McCarty [this message]

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=4885448E.3090203@sbcglobal.net \
    --to=mike.mccarty@sbcglobal.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.