Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ttidcb.UUCP
Path: utzoo!linus!philabs!ttidca!ttidcb!josephs
From: josephs@ttidcb.UUCP (Bill Josephs)
Newsgroups: net.micro.pc
Subject: Who issued the int 16???
Message-ID: <489@ttidcb.UUCP>
Date: Tue, 22-Oct-85 09:36:25 EDT
Article-I.D.: ttidcb.489
Posted: Tue Oct 22 09:36:25 1985
Date-Received: Wed, 23-Oct-85 08:17:27 EDT
Organization: TTI, Santa Monica, CA.
Lines: 25


Does anyone know (rhetoric question -- more correct: who knows and who
will tell me) how, an interrupt routine which is monitoring int 16
BIOS calls (a la the desk program in last month's byte magazine) can
tell whether COMMAND.COM issued the call or some other resident pro-
cess?

     My problem is this: I can't take the memory cost of Superkey and
other pop up macro programs when all I need is a couple of canned
playback macros and a screen blank procedure.  Using the Byte pro-
cedure, I've constructed my own which takes all of 600 bytes (in lieu
of 50K).  It monitors interrupts 8 and 9 for screen blanking and 16
for keyboard requests (being careful, of course, to handle ah=0 and
ah=1 cases properly).  However, Superkey knows if COMMAND.COM issued
the int 16 or some other process -- (it only saves "commands" in the
command stack -- user input in not saved).  My question, How?

     Thanks in advance.

Bill Josephs
CITICORP/TTI
3100 Ocean Park Blvd.
Santa Monica, Ca. 90405
(213) 450-9111