🚀 go-pugleaf

In article <93012.101937KDW103@psuvm.psu.edu> <KDW103@psuvm.psu.edu> writes:
>  Hello,
>    I'm having trouble trapping IRQ11 or IRQ12 under windows.  I am trying to
> write a device driver.  The problem isn't really with trapping the interrupt.
> I found some sample code that helped me do that.  The problem is that anytime
> that the IRQ line is enabled and I switch focus to anything other than the
> program that uses the driver.  Windows crashes.  I've seen it crash 6 totaly
> different ways, and I'm getting tired of it.  Does anyone have any idea what
> is going on?  


If you could clarify a little more, making suggestions would be easier.
How are you trapping the interrupt? Are you writing a VxD or grabbing
the interrupt from a DLL? 

Are you having the problem if you change focus after an interrupt
or only if you get an interrupt after changing focus? Are you changing
focus to aDOS app (Which will change the current VM?) 


> Is windows changing the interrupt vector table w/o telling me?

The interrupt vector table always points to the VPICD, even if you
get ownership of the IRQ in a VxD, so this should not be a problem.

>
>  Thanks,
>     Keith (kdw103@psuvm.psu.edu)

Tom Hill