|Re: NoV-32 issue|
Message #13 Posted by Diego Diaz on 25 Oct 2006, 7:39 a.m.,
in response to message #12 by Vieira, L. C. (Brazil)
Hi all again,
Now at work, (but back in The Canaries, finally... ;-))
Howard, please feel free to place whichever file you consider useful in whichever page you consider helpful for anyone. This has ever been an open project, and that's the way it should be kept.
Luiz, nothing to add to your always kind words... just thanks again :-)
Geir, please note that the managing of the Non-volatile-RAM areas *has-nothing-to-do* with the configuration utility nor the .HEX file neither...
RAM is managed *exclusively* by HEPAX OS.
The swapping between (16k) "plane 0" and "plane 1" is controlled ONLY by the "Least Singnificant Bit" in H'4100. NoV-32 documentation is not accurate on this point as it was written with the "final RAM handling procedure" in mind, regrettably, this (far more flexible and complex) procedure has not been acomplished yet... my fault :-( ... but it will be for sure... granted!! :-))
If you need to "rescue" one (or more) of the RAM pages and set it back into the HEPAX FILE SYSTEM, just use the CLRAM command from the HEPAX module (refer to HEPAX manual for details). Once you've cleared the corresponding page, switch your calc OFF and ON. HEPAX will find the "extra" RAM, will identify it as available (since it's been "zeroed") and will add the 4K to its FILE SYS automatically.
Certainly, HEPAX is a complex and highly versatile module. NOV-32 isn't simple either... Gaining enough expertising in their combined usage obviously takes a while... so... ENJOY!! ;-)) That's what this is all about! Isn't it?
Cheers from the Canary Islands.
Hope this helps.