public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: FreeDOS <linux-msdos@vger.kernel.org>
Subject: Re: Somewhat confused with Interrupts/TSRs
Date: Fri, 30 Nov 2007 12:41:38 -0600	[thread overview]
Message-ID: <47505962.8060304@sbcglobal.net> (raw)
In-Reply-To: <20071130151225.691a424b.john@jcoppens.com>

John Coppens wrote:
> Hello people.
> 
> I accepted the task of trying to get a very old datalogging program
> working for a friend. It is needed to read an older sensor, and
> apparently no other software is available.
> 
> It's a bit large (170 kB exe) to disassemble completely, but cursory
> investigation shows it was written in Turbo Pascal. Apparently the CRT
> unit was included, which makes executable use internal keyboard access
> instead of MsDOS functions.
> 
> All this is important, because I want to simulate keypresses and the TSR
> doesn't seem to work with any CRT using Pascal program.

I don't understand this statement. Do you mean that there is another
TP program which uses the CRT module and which must run with this
TSR, but does not?

> I followed the program to be using Int16 for key input, which probably
> explains why no Int28 or Int1C calls are made anymore (needed for the
> TSR to work)...

I also don't follow this. The Int16 BIOS calls don't disturb the
clock interrupts, AFAIK. I've used them many times.

> I tried to follow where 16h goes to, but, using debug in DOSemu, this
> leads to a HLT instruction...

Sounds like the TSR may be trying to guard itself against debug. I wrote
some device drivers 'way back on contract, and the people I worked
for wanted to prevent them from running when debug was being used.

> Does anyone know of this (TSR) problem or can anyone suggest a solution?

You could try stuffing the BIOS type-ahead buffer. Is there a reason
you don't have source? Also, ISTM that you may have uncovered
an incompatibility. Are you running actual MSDOS, or freedos?
You might try running actual MSDOS rather than freedos, still
using dosemu.

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 can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!

  reply	other threads:[~2007-11-30 18:41 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 [this message]
2007-11-30 21:29   ` John Coppens
2007-11-30 22:13     ` James Courtier-Dutton
     [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=47505962.8060304@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox