Backing up and restoring the HP15c user memory

Download the file from Google Drive:
Copy it to your application folder. The first time you may have to open it right-clicking on it and opening - on Sequoya you may need to go Privacy and Security and approve it after having tried to open it. It has been signed and notarized by Apple, though.
Connect your calculator, put it in listening mode ( 'f' + 'ENTER' + 'ON') and you can save or restore your calculator's full memory, including all registers, programs, matrices, stack, comma status, and even CPU registers.
Of course, you can have as many different backups as needed. A good policy is creating different user profiles, depending on the situation and application. These can be thought as "software pacs", since you can reconfigure your calculator for specific applications, and be able to call them to memory when you need these programs. We plan to create some of these software pacs.
The back-up files are just dumps of the user memory area, which is 2048 bytes long, and is organized as shown below. Registers are 8 bytes long, so there are 256 8-byte registers
There are two areas of unknown content so far, the blue areas in the picture: 14 registers at the beginning and 2 registers at the end. These were not present in the original memory of the calculator, and appear only in the emulator.
The original HP15c had 7-bytes registers, while the file registers are 8-bytes long. This means that there is always an empty byte at the end of each HP15c register. (this does not apply to the blue "technical" registers).
The discussion below can be better understood by reading Syhthetic Methods on the HP15c. While the HP15c CE does not accept synthetic methods, the discoveries found using them on the original calculator give us information about how the user memory is distributed - and this is applicable here.
The 32 first registers are the System Registers. Its distribution is the following:
For our purposes, it is important to see that the stack is there, and also registers 0 and 1 (and this is the reason that they cannot be allocated to programs, too. It also may imply that operations done to these registers might be slightly faster than with other registers, where we need to have memory map access):