Currently, memtop allows the top installed bank to be read/updated. You read memtop, and write back with needed banks subtracted from the available count.
This allows a program to allocate banks "off-the-top"
If this ability were available in membot, banks could be allocated from low banks. This would allow the kernal and geos (or other system software) to allocate banks for their own usage and applications would not have to guess how many banks they need to skip off the low end.
By default, the first free bank would be 1. Updated to 10 if geos needed space.
Question
Peter Camilleri
Currently, memtop allows the top installed bank to be read/updated. You read memtop, and write back with needed banks subtracted from the available count.
This allows a program to allocate banks "off-the-top"
If this ability were available in membot, banks could be allocated from low banks. This would allow the kernal and geos (or other system software) to allocate banks for their own usage and applications would not have to guess how many banks they need to skip off the low end.
By default, the first free bank would be 1. Updated to 10 if geos needed space.
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.