Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!wuarchive!emory!rsiatl!nanovx!msa3b!kevin
From: kevin@msa3b.UUCP (Kevin P. Kleinfelter)
Newsgroups: comp.windows.ms.programmer
Subject: Windows and Interrupts
Message-ID: <1459@msa3b.UUCP>
Date: 4 Dec 90 18:51:45 GMT
Organization: Dun and Bradstreet Software, Inc., Atlanta, GA
Lines: 30

I'd like to generate an arbitrary interrupt from within a Windows
program.  Under non-Windows C, I'd just load up a struct with
values for the registers and make an "int86" call.  However,
the Windows doc for DOS3Call and NetBIOSCall imply that IF this
currently works, it may not work in the future.  To quote from DOS3Call's
doc:

   An application can use this function instead of a directly
   coded DOS 21H interrupt.  The DOS3Call function execute somewhat 
   faster than the equivalent DOS21H...

And from NetBIOSCall

   An application should call this function instead of directly
   issuing a NETBIOS 5CH interrupt to preserve compatibiloity
   with future Microsoft products.

I have an XXXXX.SYS driver, which my application communicates
with via an interrupt vector. This works just fine under plain
DOS.  Although I don't mind reworking the .SYS driver, I'd like
to come up with a driver that I could access from BOTH plain DOS
and Windows programs.

Any suggestions or pointers?
   
-- 
Kevin Kleinfelter @ Dun and Bradstreet Software, Inc (404) 239-2347
{emory,gatech}!nanovx!msa3b!kevin

Soon to become {emory,gatech}!nanovx!dbses0!kevin  (But not yet!)