|HP 41 key assignment file and x memory|
Message #1 Posted by Geoff Quickfall on 14 Aug 2011, 6:59 p.m.
now that I have all the xroms available (almost) on the Cl I would like the capabiltiy, similar to the 71B of saving a keyfile to x-memory. This is due to the fact that some XROM take over the CL and configure the key assignments throwing your personal assignments in the trash. Using SK and RK on PPC allow suspension and reactivation of your personal key assignment but store the assignment strings in the main register memory where they can be corrupted by other program usage. I would like to store the key assignments in x-memory where xroms do not have access to them. That way they are available at any time to recall and reactivate.
Using SK and RK on the PPC seem like a good start. SK (suspend keys) uses two storage registers of your choice to store the key assignments. They can be reactivated by RK (reactivate keys).
The two NNN numbers that SK uses are stored in a user defined register set. For example 0.00 in x; followed by xeq SK; stores the key assignments in R00 and R01.
So you would think it would be an easy thing to create a keyfile for xmemory along the lines of:
the first three lines create the KEY text file to store the R00 and R01 NNN for recall by SK.
"KEYI" only needs to be run once to store the R00 and R01 contents in the x memory location 00 and 01.
"KEYR" should recall the NNN to their respective storage registers for use with RK at any time.
Instead I get nothing but ABS assigned to all keys as opposed to the original keys.
So you have an idea of what I want, surely an XROM has this routine or function built in somewhere. Again the idea is to create a TEXT or DATA file in xmemory which will allow me to reinstall the key assignments that is safe from main memory REG manipulation. The failing of RK and SK is that they rely on the main REGs which may be altered by any number of routines called upon by an XROM whereas the X-memory is safe from that manipulation.
also ran the the above programs treating the R00and R01 registers as data, that is I created a DATA file named KEY in x-memory. But that did not work either!
Edited: 14 Aug 2011, 7:11 p.m.