public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: John Coppens <john@jcoppens.com>
Cc: FreeDOS <linux-msdos@vger.kernel.org>
Subject: Re: Somewhat confused with Interrupts/TSRs
Date: Fri, 30 Nov 2007 22:13:12 +0000	[thread overview]
Message-ID: <47508AF8.8090909@superbug.co.uk> (raw)
In-Reply-To: <20071130182911.bcd28090.john@jcoppens.com>

John Coppens wrote:
> 
> Yes... The logger calls Int16, which works fine, except that in that case
> the TSR stops working, because both 'hooks' to 'stimulate' the TSR (Int
> 1C and 28) stop working (see below). Note that both 1Ch and 28h are
> 'voluntary' interrupts, called only when DOS is idle. So while in the
> (BIOS's) Int16, DOS won't be able to call them.

The program does use Int16, function AH=0x10.
You would need to also hook Int16 so that it "stimulates" your TSR program.

> 
> 
> And at F000:C016 is a HLT. I suspect this is part of the mechanism dosemu
> uses to emulate.
> 
That is correct, the HLT causes the dosemu to callout of DOS back into
the dosemu program to process the BIOS call.

I would probably take this approach:
Modify dosemu, or dosbox so that the BIOS call reads keyboard input from
a unix pipe. Then you can simply cat characters into the pipe from a
shell and the dos program will receive them.

Then you would not need a TSR at all!

James




  reply	other threads:[~2007-11-30 22:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 18:12 Somewhat confused with Interrupts/TSRs John Coppens
2007-11-30 18:41 ` Mike McCarty
2007-11-30 21:29   ` John Coppens
2007-11-30 22:13     ` James Courtier-Dutton [this message]
     [not found]   ` <20071130175017.938b2cf5.john@jcoppens.com>
2007-11-30 22:31     ` Mike McCarty
     [not found]       ` <20071130211248.ae41594a.john@jcoppens.com>
2007-12-03 17:00         ` Mike McCarty
2007-12-04 17:21         ` 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=47508AF8.8090909@superbug.co.uk \
    --to=james@superbug.co.uk \
    --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