(SOLVED) 41CL - DOUBLE HEPAX ACCESS and MMU CONFIG
|
08-20-2019, 02:06 PM
Post: #27
|
|||
|
|||
RE: 41CL - DOUBLE HEPAX ACCESS
(08-20-2019 12:53 PM)Podalirius Wrote: ON <--, MEMORY LOSTYou are lucky here that the 41CL keep its RAM content through the ML process (08-20-2019 12:53 PM)Podalirius Wrote: XEQ CFGINIYou are right CFGINI is part of YFNF and it was not mapped in my procedures. You need to use CFGINI only once basically, CFGINI is copying the default MMU configuration table from ROM to RAM. After that, you use the RAM based MMU configuration table with either the 9??? setup with PLUG/PPLUG or RCLCFG/STOCFG 1..F functions to play with configuration sets. Warning: each time you use CFGINI you erase any modification that you may have done with the RAM based MMU configuration table. Also, in my procedure I assumed that you have a properly configured 16K HePaX RAM block located at 0x808 to 0x80B. (08-20-2019 12:53 PM)Podalirius Wrote: XEQ RCLCFG 4Sorry for that, it was late, I was tired and did not double/triple check the procedure. I am at the office right now (GMT-5h) and cannot do any test, but I am pretty sure I know what is going on. Until I am back home and able to test it, an untested tentative solution would be this procedure: Code: MMUDIS // disable MMU Code: MMUEN // enable MMU Code: "YFNX" // 41CL Extreme Functions Code: "HEPX B" // HePaX ROM (1 page 4 banks) (08-20-2019 12:53 PM)Podalirius Wrote: I stopped. I need more help or I am useless at 41CL!!The 41CL is way more powerful than the original HP-41C/CV/CX, but with that level of power comes some complexities. At the moment we are playing with the virtualization part, well a small part of it, which allow us to plug virtual modules into virtual ports through configuration sets. Sylvain |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)