Message-Id:	<m0yCf3j-000S2kC@inti.gov.ar>
Comments:	Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization:	INTI
To:	Luke Bishop <lbishop AT calvin DOT stemnet DOT nf DOT ca>, djgpp AT delorie DOT com
Date:	Wed, 11 Mar 1998 09:33:50 +0000
MIME-Version:	1.0
Subject:	RE: Allegro And Alternate Memory Handling
In-reply-to:	<01BD4BB1.447D5140@n072h048.thezone.net>

Luke Bishop <lbishop AT calvin DOT stemnet DOT nf DOT ca> wrote:

> >So: why you don't simply replace malloc/realloc/free from libc?
> 
> Simple, two reasons:
> 	A - I really am not sure how to do so in a decent manner.
> 	B - It fails to solve the problem of the calls to _go32_dpmi_lock_data.
> 
> 	The problem is, the daemon locks all available pages upon startup.  This means that you can lock code, because it can be done 
> before the memory initialize, but you CANNOT lock memory at runtime.  Of 	I 
> hope some solution can be made, because I have actually already tried three 
> times to rewrite Allegro with no success (okay there was progress, but not 
> nearly enough...).

I really don't understand you. The decent manner is just writing a 
malloc/realloc/free and putting it before than libc, it will replace the libc 
ones and you won't need to touch any line in Allegro.
About the way to lock: Lock all, and replace the Allegro macros to lock 
variables by a macro that returns sucess, you just need to modify allegro.h.

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013

- Raw text -