Xref: utzoo alt.msdos.programmer:1315 comp.sys.ibm.pc.programmer:186
Path: utzoo!attcan!uunet!ogicse!mintaka!mintaka.lcs.mit.edu!pas
From: pas@lcs.mit.edu (Paul A. Selkirk)
Newsgroups: alt.msdos.programmer,comp.sys.ibm.pc.programmer
Subject: idling in the interpreter
Message-ID: <PAS.90Mar1120125@saffron.lcs.mit.edu>
Date: 1 Mar 90 20:01:25 GMT
Sender: news@mintaka.lcs.mit.edu
Organization: MIT
Lines: 17


Does anyone know of a bulletproof way for a TSR to tell whether DOS (assume
2.x or 3.x) is idling in the command interpreter, or executing a program?

I have determined, through much pain and disassembly, that DOS uses service
0A (buffered string input) to get the next command, but other programs use that
as well.  I can get by on this knowledge, but I would prefer something a little
more certain.

For the record, I am writing a screen-saver TSR that will only trigger when DOS
is idling.  There are dozens of screen-savers, but I need one that won't kill
a lengthy graphics program.  (Ever try generating the Mandelbrot set on a 4.77 
MHz XT with no FPU?  I thought so.)

Any leads will be duly appreciated.

				paul