Date: Fri, 24 Aug 2001 13:27:21 -0700 (PDT) From: "Louis P. Santillan" To: djgpp AT delorie DOT com Subject: Re: TSR/ISR Interaction In-Reply-To: <9003-Fri24Aug2001103401+0300-eliz@is.elta.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 24 Aug 2001, Eli Zaretskii wrote: [SNIP other stuff answered by DJ and Eli] > > Can selectors and offsets be temporarily "mapped" into the ISR's data > > space? I know one can do this with selectors that are created by the app > > itself but I'm not sure if this might work when the selector and offset > > are passed thru a interrupt call. > > Sorry, I don't understand what are you asking here. Could you please > describe the situation in more detail and then tell what do you mean > by ``temporarily mapping selectors and offsets'' into the ISR's data > area? Yes. I should try to be clearer here. I meant, can you have the ISR receive a ptr to structure (say, thru FS:EBX)? This structure will also contain ptrs (sel/off pairs) to data & methods (callbacks). Can these callbacks actually be called? Grabbing data is no problem with farpeek/poke but how do you execute a method outside of the ISR's own cs selector? Would a (NASM style ASM) push/push/retf work? push arg0 ... push methodOff push methodSel retf Or is there some other DPMI approved way of doing this? Thanks Louis