Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!tut.cis.ohio-state.edu!ucbvax!UOTTAWA.BITNET!451061
From: 451061@UOTTAWA.BITNET (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Followup to Freeing memory on demand
Message-ID: <8908062214.AA02701@jade.berkeley.edu>
Date: 6 Aug 89 22:07:23 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 20

Bryan Ford <bryan@geo-works.uucp> writes in Message-ID: <2085.AA2085@geo-works>

> Also, would it be good to SetFunction() the AllocMem() function?  Does the
> OS always (or at least usually) allocate memory through this entry point,
> or does it call itself directly?

Yes, the Exec itself always goes through AllocMem() to obtain memory. I myself
have SetFunction()ed the AllocMem(), FreeMem(), TypeofMem() and AllocAbs()
functions and replaced them with similar ones which use semaphores instead of
Forbid()/Permit() combinations. That fixed an incompatibility with my enhanced
Exec. By the way, you can get a full disassembly from a program called ExecDis,
by Markus Wandel. (God bless him) It's been plunged in FishBowl #188.

Valentin
_________________________________________________________________________
"An  operating  system  without         Name:   Valentin Pepelea
 virtual memory is an operating         Phonet: (613) 231-7476
 system without virtue."                Bitnet: 451061@Uottawa.bitnet
                                        Usenet: Use cunyvm.cuny.edu gate
         - Ancient Inca Proverb         Planet: 451061@acadvm1.UOttawa.CA