www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/04/03/09:50:06

Message-Id: <m0wChzG-000S1uC@natacha.inti.edu.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT edu DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT natacha DOT inti DOT edu DOT ar>
Organization: INTI
To: "Bertel k. Brander" <bertel AT post4 DOT tele DOT dk>, djgpp AT delorie DOT com
Date: Thu, 3 Apr 1997 11:50:22 +0000
MIME-Version: 1.0
Subject: Re: Interrupts and locking code

"Bertel k. Brander" <bertel AT post4 DOT tele DOT dk> wrote:

> 1. 
> I have two interrupts, 
> Is there a simle way to lock all this data and code? 
Consult the FAQ, there are a CRT0 flag to lock all, I use that. In addition if you can 
choose the DPMI server for the application use PMODE/DJ or CWSDPMI Ring 0 
version, you'll loose the Virtual memory but you'll gain:
1) Speed.
2) No need for locking.
  Additionally you can take a look to Allegro, Shawn made a very usefull work 
there to make the lock part much more easy.
  Or you can wait a little until DJ release GCC 2.7.2.2 for DJGPP with some 
patches that will make the locking procedure much more easy.

> When i lock memory for 
> functions how do i then know the size of the function?
Take a look at Allegro, basically Shawn puts labels (created with dummy 
functions) around the function to lock.
 
> 2. i must call the 
> orignal dos handler once for every 109 timer tick interrupt. How do i do that?
  Allegro can simplify your life again, the Allegro interrupt wrapper was 
designed with that in mind, the interrupt routine can chain to the original, or 
not, according to the returned value.

Greetings, SET 
--------------- 0 --------------------------------
Salvador Eduardo Tropea (SET).
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013

- Raw text -


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