Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!caen!elm.engin.umich.edu!zarnuk
From: zarnuk@caen.engin.umich.edu (Paul Steven Mccarthy)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Word for Windows and DOS idle interrupt (INT28)
Message-ID: <1990Dec19.050307.16450@engin.umich.edu>
Date: 19 Dec 90 05:03:07 GMT
References: <1990Dec13.220804.1611@vax5.cit.cornell.edu> <5094@trantor.harris-atd.com> <1537@netmbx.UUCP>
Sender: news@engin.umich.edu (CAEN Netnews)
Distribution: comp
Organization: University of Michigan Engineering, Ann Arbor
Lines: 20

In article <1537@netmbx.UUCP> oeschi@netmbx.UUCP (Johann Deutinger) writes:

> ... If no INT28
>occurs (as in Word for Windows) I don't become called from anywhere. All
>other Windows application I have don't cause that. TeSseRact additionally
>calls INT28 on BIOS keyboard wait, this does not help in Windows which
>does not use the BIOS for keyboard I/O. In WfW, as soon as I pull down
>one of the menus, INT28 calls do occur, they don't show up as long as I
>am in the editing Window. A solution for that is very important to me
>because otherwise I could not send or receive faxes during WfW editing.

WfW must be checking for keyboard input someway (probably hooked directly
into the keyboard interrupt 09h).  You should hook into the timer interrupt,
08h.  You will have to be extra careful about DOS re-entrancy, though.  
You may want to hook into the DOS 21h interrupt just to keep track of
which DOS functions are currently active. 

(The _least_ "well-behaved" code is usually excreted by Micro$oft!)

--- Paul...