Andrew Grillet wrote in a message to Mike Bilow:

 MB> It might be
 MB> worth writing an example VDD that traps CLI, and then offers an option
 MB> in the notebook settings for disabling it.  Is there any legitimate
 MB> reason you can think of for a DOS program running in an OS/2 window to
 MB> actually do CLI?

 AG> I have some stuff that uses the parallel port to emulate
 AG> IEEE488 and other such like things. This needs to CLI to get
 AG> H/W timing right. 

 AG> I run it in a DOS box, cos I havn't had time to port it to
 AG> OS/2 yet. 

You have no business doing things like this under OS/2.  You can't even
grab a hardware interrupt from a DOS box, but can only get it reflected. 
This changes a code path that could be a few bytes long to one that is
hundreds of bytes long, and this blows away your timing constraints anyway.
 Properly, you should do this with a device driver.
 
-- Mike


---