🚀 go-pugleaf

Hi,

I'm currently writing an application with MSC & Windows SDK that communicates
with a TSR-based hardware driver. The TSR writes its data in a shared memory
provided by my application via "GlobalDOSAlloc". To perform functions provided
by TSR one have to use a certain software interrupt. I did this by using the
library function "int86" and for that case it works well. 
But some of the functions of the TSR expect an address to the shared memory
with the segment part of the address in the "es" register. My attempt
was to use the "int86x" function with the "es" register set to the real
mode segment address of the shared memory (as the TSR is executed in real
mode). The result was an UAE, as the library function "int86x" (still running
in protected mode) tries to setup the "es" register with a segment address.
When using a valid selector in the "es" register, the TSR is called, but with
modified contents of the "es" register.

Well, I do know that things are complicated in proctected mode, but I thought
it would work because the int86 functions are still available in dos.h (in
contrast to e.g. _dos_setvect, which is "removed" by #ifndef _WINDOWS etc.).
Maybe I misused a facility provided to process hardware interrupts ? ;-)

MY QUESTION IS: is there an *easy* way to call a software interrupt of a TSR
                by a protected mode Windows application (with the ability to
                set all registers (execpt ss,sp,cs,ip of course!:-)) ???

Perhaps DPMI does the job, but as the documentation of Windows SDK doesn't
contain anything about it, I am rather unfamiliar with it. 

Thanks in advance

   Klaus