[Coco] Program won't stay loaded under NitrOS9/OS9

[Bill Pierce]

Did you "load" the file before executing it? or just 'run' the file?
Even calling another module from within a program, it must be loaded first to keep it residing in memory and unloaded when finished or it stays in memory even after you exit your program.
There is also another 'undocumented" method of loading that allows you to load a module without it's data space being assigned and it will only use up the amount of memory equal to the size of the module (as opposed to the 8k OS9 assigns on 'load'). It uses the "NMLoad" call which is used the same as load. This actually a low level call and has been there for a long time, but was never documented in any of the docs. A sister call of "NMLoad" is "NMLink" which does the same, but links the file, again, using less memory.
I also have "external" versions of these commands "NMLoad" & "NMLink" which are used like "Load" & "Link" from the command line.

 

 


Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com


 

 

-----Original Message-----
From: K. Pruitt <pruittk at roadrunner.com>
To: Coco <Coco at maltedmedia.com>
Sent: Sat, Jan 2, 2016 10:59 am
Subject: [Coco] Program won't stay loaded under NitrOS9/OS9

What conditions would cause a module to not stay loaded but remove itself from memory after it is executed one time? I'm not generating an error of any sort and the system does not destabilize.In my code I am halting the interrupts and turning them back on when I am done. Would that cause such a scenario to occur? -- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco