TLIMONCE@DREW.BITNET (07/20/88)
I am developing a BBS program under Manx's Aztec C. The program does a lot of IPC (homegrown) to lock files, etc and the program can be run multiple times concurently to create a multi-user BBS (one locally, one remotely... more when someone releases a spec for adding multiple serial ports :-) ). Currently, I install it as resident (using ARP, when I get 1.3 I'm sure it'll work with the Pure bit set). I would like to use Aztec's ability to do overlays also. Question #1: Manx doesn't guarantee resident-ness on their code, but it generally works. Does anyone know if they will guarantee it in their next version? (I sort of expect a new version when 1.3 is released) Question #2: If a program compiled with the current version (3.6) uses overlays, can it safely be made resident? Question #3: Has anyone considered making their own overlay library that permits resident code to be cached when multiple processes are using it? How about using using Perry's asdg-low-memory.library (low memory watcher) to help decide what is retained and what is dropped? If someone answers "yes" to #3, I would be willing to licence the code for use in my BBS program. (which will be shipping RSN :-) :-) ) A // Tom Limoncelli -- TLimonce@Drew.Bitnet \ M // "Never trust a person that doesn't know machine language!" \ I \\// /\ G XX "Have you hugged your SO today?" / \ A -------------------------------------------------------------------------- "The above are my views, not those of Drew University or my employer"