www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/06/04/13:37:27

Xref: news2.mv.net comp.os.msdos.djgpp:4566
From: fmarcos AT jet DOT es (Fernando Marcos)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Getting pre-interrupt registers under a DPMI hw interrupt?
Date: Tue, 04 Jun 1996 07:57:31 GMT
Organization: Servicio IBERNET (Telefonica Transmision de Datos)
Lines: 19
Message-ID: <4p0qdq$rro@artemis.ibernet.es>
References: <4ood1v$880 AT news1 DOT goodnet DOT com>
NNTP-Posting-Host: minfo4.jet.es
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

snarfy AT goodnet DOT com wrote:

>everything changes.  From the code that I have seen from CWS's DPMI,
>the stack is changed (4k locked stack?) making ss and esp invalid, cs
>and eip are obviously invalid, and some of the segment registers are
>changed. (ds and es?).  I'm new to protected mode, and to DPMI, and

If you use _go32_dpmi_chain_protected_mode_interrupt_vector(), once
you get in your protected mode ISR everything is preloaded by the DPMI
host. You just have to run as if it were a normal C function (even
return with RET!). At least CS & DS are preloaded to their proper
values. Keep in mind to lock any virtual memory that you allocate for
use by the ISR to avoid page faults, and thats all!!

	Greets!!

	Fernando


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019