NoV-64: The Incredible Shrinking HEPAX RAM



#33

Hi folks who know of these things,

I got my NoV-64 and programmer (replacements) from Diego and all seems great. Except for one thing that I am sure is a feature, not a bug, that I fail to understand.

Before I fiddled with any programming I put the module in my calculator, did a CAT 2, saw the HEPAX catalogue, etc. HEPDIR and HEPROOM both reported to me that I had 2610 registers of HEPAX RAM, which is what I would expect.

Then I fiddled--burning the Advantage module, then the PPC, then the SandMath, and each time HEPROOM returned 1957 registers. This condition persisted even when I did a complete module erase in the programmer and burnt back the original configuration that presents itself by default in the NoV-64 page of the configuration utility (i.e., HEPAX-1D in 1-X to 4-X).

I am sure that it is normal to lose that extra HEPRAM when one moves away from the default state in which Diego sends out the module. I am just curious to know who those 653 registers got lost in the first place, and if there is anything (apart from the battery sucking CLR_RAM procedures) to get them back.

Still learning obviously. Thanks in advance for any guidance.

Les

Edited: 25 May 2012, 2:26 p.m.


#34

Hi Les,

I ran into precisely the same problem. I tried a half dozen things to solve the problem including clearing RAM using the Clonix Config tool multiple times. None of them worked. What has happened to you is that you have managed to remove one of your RAM ports from the HEPAX file system leaving you with 25% less RAM than the default configuration. Reading the HEPAX manual eventually lead me to the solution.

First make sure that there is no port/page conflict with the RAM you have installed (nothing in pages 8, 9, A, or B) and then use the HEPAX CLRAM function to clear the last RAM page. To do this place 11 in the X register (11 = x0B) and "OK" in the Alpha register and then XEQ "CLRAM". Follow this with HEPDIR and you should be back in business.

Hope this helps.

Cheers,

-Marwan

EDIT: Note that if you run out of ROM space and HEPAX can't install itself to page 6 or page 7 it might grab the first available page after that which might be page 8. I am not sure of this.

Note 2: The SandMath ROM takes up a minimum of 2 pages (8K version) or I believe 3 pages (12K version), the Advantage ROM takes up 2 pages, and PPC takes up one page. So, if I have all my facts right you are now at 5 (or 6) pages. That is one page too many to fit comfortably with 16K RAM (4 pages). I am guessing that you are using the latest version of the ClonixConfig utility and that you have one of your ROM's assigned to page B.


Edited: 25 May 2012, 3:49 p.m.


#35

Quote:
First make sure that there is no port/page conflict with the RAM you have installed (nothing in pages 8, 9, A, or B) and then use the HEPAX CLRAM function to clear the last RAM page. To do this place 11 in the X register (11 = x0B) and "OK" in the Alpha register and then XEQ "CLRAM". Follow this with HEPDIR and you should be back in business

This operation left me with 1304 registers of HEPAX RAM, but I suspect I may have had those very page conflicts you warn about. Later on I will erase and rewrite the default config and try again and see if the CLRAM operation gets me 2610 registers of HEPROOM.

Thank you so much!

Les


#36

Hi Les,

No problem. After erasing, configuring default, and doing a CLRAM don't forget the HEPDIR function. Per the HEPAX manual that rebuilds the file chain.

Cheers,

-Marwan


Wrong direction! Down to 50% now! You may have to walk the chain backwards doing a CLRAM on each page in order and then a HEPDIR. Maybe you were occupying page A and clearing page B as I suggested made matters worse.

Edited: 25 May 2012, 4:14 p.m.


#37

I didn't write sooner but I wanted to confirm that did indeed seem to lose that HEPAX RAM due to a conflict with physical ROM in port 2--Advantage, I think. Got it fixed as you and Diego advised. In the process learned a lot about the configuration of the module. I find that the technical terms are at first confusing--i.e., keeping straight blocks, pages, banks, chips, etc.--but the concepts they denote are not.

I was using v. 2.5 of ClonixConfig.exe, so now that I have upgraded to v. 3.4 I will have to be extra careful about how I program the module since the newer software confers much greater programming latitude. I think if I say with C, D, E, and F for ROM placement and switch back and forth using the h'4100 control word, I should stay out of trouble.

I really want to learn more about making my own catalog-visible ROMs, starting with FOCAL programs since I haven't gotten into M-CODE yet.

Thanks for everything.

Les


#38

Hi Les,

I'm glad that you got it all worked out and that we were able to help. The various terms are a little bit confusing at first and when writing I have to be really careful about differentiating between PORTS and PAGES in particular. I too would like to get into compiling my own ROMs although for now I simply load my programs into HEPAX RAM. I have also started reading about MCODE in an effort to get started in that direction.

Quote:
...and switch back and forth using the h'4100 control word, I should stay out of trouble...

And here I will offer another plug for the NOVCHAP ROM. It includes a number of functions that make switching pages really easy such as:

N?        Returns current page configuration
N100 Sets ROM bank 1 RAM bank 0 (first RAM bank)
N101 ROM B1, RAM B1
N102
...
N200 ROM B2, RAM B0
...
N203 ROM B2, RAM B3
NX Set Control word by value in X

Cheers,

-Marwan

#39

BTW, you absolutely have to have the NOVCHAP ROM module installed if you want to make the best use of the NoV-64 module.

Remember that if you are using a CL you have to have the NOVCHAP installed on the NoV-64 it can't be run from the CL AND it can't run out of HEPAX RAM. I learned all this the hard way the past two days <g>. You can, however, run the PPC ROM from HEPAX RAM (at least you should be able to--I'm running YFNS-3B out of page B HEPAX RAM). This is one operation, among many, that is made much easier by having the NOVCHAP ROM in place. You can remove HEPAX RAM from the filechain manually using HEXEDIT but it is much easier using the NOVCHAP HKILL function to do so.

Cheers,

-Marwan

EDIT: The NoV-64 in conjunction with the 41CL is an absolute dream! One of the things I love is having YFNS-3B and either CLUTILS-2H or -4H available by simply plugging in the HEPAX module. My CL initialization is now simply:

MMUCLR
MMUINIT

This removes YFNS from page 7 and leaves you using YFNS from the HEPAX module while retaining ALL the capability of the 41CL. You can also easily copy ROMs burned to the NoV-64 to 41CL RAM if you need to.

Edited: 25 May 2012, 3:09 p.m.


#40

I am happy to hear that there are others using the NOVCHAP rom :)


#41

I absolutely LOVE it--wouldn't dream of using the NoV-64 without it! Thank you very much! And my NoV and the CL. Next purchase is the PIL-Box. I would have bought one already but I'm moving and didn't know if it would get here before I moved.

I keep trying to convince myself that there are actually calculators out there better than the HP41 (and it's derivatives) but have never quite managed to move on! Sure I play with other "toys" but I *ALWAYS* come back to my trusty 41--a machine I have been using for 32 years!

Cheers,

-Marwan

Edited: 25 May 2012, 3:17 p.m.

#42

I don't have a CL but I will check out the module.

Les

#43

Quote:
BTW, you absolutely have to have the NOVCHAP ROM module installed if you want to make the best use of the NoV-64 module.

Where is it best to place it in the module? (I don't have a CL, just a CV and CX.) Moreover, does one need to have a copy in each ROM block so that when one switches back and for with N@ commands one will alway have the NOVCHAP accessible?

I can't see any recommended configuration in Geir's manual.

Les


#44

Hi Les,

It does not really matter in which page you install it (#C, #D, #E, #F) but it has to be installed in the NoV-64 itself so having a CL does not help here. And it can't be installed in a RAM page emulating ROM. And, yes, it does have to be installed in each ROM bank if you wan't to used the N@ command to switch pages. I chose to put it in page #D in each ROM bank.

Here is my current setup:

ROM Bank 1
----------
AMC-OSX #C
NOVCHAP #D
--FREE-- #E (Allows a physical module (e.g. Card Reader in PORT 4)
CLUTILS 2H #F


ROM Bank 2
----------
Library#4 #4 (If I understand correctly this requires a CX (CL))
AMCOSX4 #C
NOVCHAP #D
CLUTILS 4H #F

Note that page #E is still free for physical module.

RAM Bank 1 & 2
--------------
YFNS 3B #B

I can get any other 4K module I need from those available in the CL and plug it into page #E.

When HP-IL is not plugged in I can also use page #7 (and with ClonixConfig 3.4 so can you if you don't use HP-IL).

You can also use any unused RAM pages for ROM modules as I did with the YFNS 3B ROM. This is easy to do although it is a multistep process. Here is the procedure from memory (keeping in mind that I have only done this a couple of times).

Burn the ROM you want in memory to the NoV-64 (example below assumes page #F)
Plug in NoV-64

11 HKILL (Take page #B out of the file system
15 ENTER 11 COPYROM (Copies the ROM you had in page #F (15) to page #B (11)
Remove NoV-64 and replace image in page #F with whatever you want

Hope all this helps.

Cheers,

-Marwan


#45

Marwan, this is extremely helpful.

I burned NOVCHAP to page #D in each ROM bank. I have used the COPYROM procedure to get favourite ROMs into RAM pages 8, 9, and A on the first two chips, leaving what's left of the HEPAX FS for my back-up WA files and programs, and I have a full 2610-register file system in the other two chips for future use. I have never been one to use assigned keys but I do now, with the NX, HEPAX, and HEPDIR commands, among others, mapped to the top row of keys so I can always check where I am.

I am wrapping my brain around the fact that there are 12 potential configurations--000, 001, 002 ... 203--and the challenges of keeping control of it all! On challenge is making sure that dependent programs "live" in the same configuration. For example, I have a user program that resides in page C of the second RAM chip, that calls a program living in B on that same chip. I used HP-IL and READROM and WRTROM to copy my page C over to another RAM chip, but it couldn't find the program it needed. Things like that. I suppose that it is important to judiciously use redundancy as you have.

I am an avid HP-IL user since getting a PIL-Box, so I know to keep out of page #7. I have also learned that port 2 on the calculator maps to page A, so I put only the HP-IL module in there to save me the disruption of my HEPAX file systems. I also believe that the IR module maps to 7, not A, but I haven't checked. I have both a CV and CX (I actually like the former, a full nut , for its crisper screen), so I will explore Library#4 in time.

Thanks for your thoughtful and detailed reply.

Les


#46

Hi Les,

One thing to consider: The Time Module is another module that does not take over a page from the port it is plugged into. It uses page #5. In my setup I leave the Time Module in port 1 and the NoV in port 2. That takes care of "protecting" pages #8, #9, #A, and #B at all times from conflicting with a physical ROM even when I am away from my HPIl devices.

I am looking forward to obtaining a PIL-Box but have to wait until I get moved at the end of the month and settled into our new home. My first priority then will be to order a PIL-Box!

I just saw your post about trouble accessing the 3rd RAM bank. I would love to hear more when you have a chance.

Cheers,

-Marwan


#47

Actually, it's the fourth RAM bank, counting 0 as the first.

What I basically did was this.

I used HEXEDIT to change h'4100 contents to h'003. Within a second--I didn't even have to leave HEXEDIT--NONEXISTENT started flashing. I did NOT remove the battery this time--instead, I executed the ENTER-double ON manoeuvre and found myself with a normal display. I did NOT turn off the calculator--I simply executed CLRAM for 11 down to 8, and, voilà, on turning the calc on and off I am able to point myself to RAM chip 3 by changing h'4100 to any of the configurations that do so.

Of course, I lost everything, such as it was, in the 4 pages of HEPAX RAM in chip 3, but considering that I believed I had physically damaged the memory, this is a small inconvenience.

Les

Edited: 28 May 2012, 10:17 p.m.


#48

Ah, yes, of course, it is the fourth. Too much wine--couldn't count <g>.

And thanks for the description of how you recovered.

Cheers,

-Marwan


Edited: 29 May 2012, 7:47 a.m.

#49

Hi Les,

Another thing to consider is that if you use HPIL with printer enabled HEPAX will not be able to assign itself to page #6 or page #7 and it will have to go searching for a higher numbered page (will it use page #5 on a CV without a Time Module?). At any rate, I try to leave page #E available in all my configurations so that HEPAX will have somewhere to assign itself to if pages #6 and #7 are in use.

I have not experimented a lot with how HEPAX responds to various pages being in use. In my setup it generally takes over page #6 since I don't have the printer enabled. But when I get hold of a PIL-Box that will change so I should probably experiment some in preparation for that.

Cheers,

-Marwan

#50

Hi Les,

I cannot reproduce the behavior you've depicted, but I think I can help in bringing the HEPAX RAM of your File System back to its default size.

Just to point it out, the amount of HEPAX RAM available for File System has nothing to do with and should not be altered by the configuration of the extra ROM pages in the NoV modules.

Conversely, once the amount of RAM in the File System has been altered (for whichever the cause), re-programming the NoV module with its default (only HEPAX emulation) configuration won't turn the "missing" RAM back.

The following is a simple procedure to, first, find out if your RAM is available and, second, recover it to the File System in case you need it.

1- To check if RAM chip is properly accessible from the NoV module please execute HEPAX 002. You'll see a list of every page with a descriptive label of its contents. "HEPAX RAM" should fill pages #8, #9, #A & #B. Please note that the amount of HEPAX RAM used by HEPAX File System (the amount showed up by HEPROOM command), does not necessarily match the total amount of available RAM. See HEPAX manual for details on the File System configuration, as well as File System Chain integrity details.

2- You can repeat the abobe checking for the remaining three chips by changing control word at address h'4100 to h'001, h'002 & h'003 respectively by means of HEXEDIT command.

In order to get one 16K chip of HEPAX RAM back to the File System, and get the 2,160 registers count, HEPAX provides an easier method than the CLR_RAM configuration.

3- Assign CLRAM command to a key of your convenience, place "OK" into ALPHA register, enter 11 to X register and execute CLRAM, then 10 & CLRAM, 9 & CLRAM and 8 & CLRAM. Power cycle your HP-41 once finished. Now HEPROOM will show your 2,610 registers as expected.

4- Repeat the process for chips 001, 002 and 003 if required.

Just to clarify, CLR_RAMn utilities do not draw more battery than any other operation. The need of a fresh set of batteries does not come from the current drain requirements but from the voltage expected to run the continuous writing/reading process. This is beacuse this particular utility runs while the HP-41 is OFF therefore, the internal power supply is not working and the only available voltage is the one in the batteries less a diode drop.

Despite of this, this utility is currently of little to no real usage since the latest NoV modules version all include the Crash Recovery Feature which allows total RAM erasing by following the steps 3 & 4. See the NoV-64 module user's manual for details.

Hope this helps.

All the best from Caribbean Sea.

Diego.

Edited: Typos.


Edited: 25 May 2012, 4:32 p.m.


#51

Hi Diego,

A more complete explanation!

I did find that if a page is already occupied by a module (this on a regular CV with the X-Functions module in port 2) the RAM for the conflicting page is removed from the file chain. That is why I suggested that perhaps having too many pages in ROM caused the problem to begin with.

It sounds like Les has written more than 5 pages of ROM (how I don't know--but Sandmath takes 2 pages, Advantage takes 2 pages plus 1 extra bank, and PPC takes 1 page (5 pages?). If he wrote any of those to a page location between x08 and x0B wouldn't that act just like a regular plug-in module and break the file chain?

Cheers,

-Marwan


#52

Hi Marwan,

Although burning more than four extra pages in a single ROM block is not possible using the ClonixConfig utility; the latest version allows any page address to be used, therfore, a simple extra click could lead to a coflict between RAM and ROM addressing. My advice would be to leave the page address field assigned by default until the user gets fully understanding of every configuration detail.

I assumed that Les did program his NoV-64 in sequence with the different ROM's not all at the same time...

Obviously, once the File System has lost part of its chain, you cannot get it back by re-programming the ROM's, and need to go thru the procedures described in the HEPAX manual (abstracted avove) to rebuild the Fyle System Chain integrity.

As a personal note, I don't know if the HEPAX File System is of much real use currently, with the amount of possibilities available: CL, Library#4, NoVChap... but, this is of course a user's decision.

Cheers.

Diego.


#53

Hi Diego,

I understand. I think that a page conflict of some sort must have resulted. Maybe Les has a physical ROM plugged into port 1 or 2? I offered much the same solution in my first posting (above) but assumed that he was only missing page #B. Following my advice he ended up with only 50% memory so I have to assume that the conflict was with one of the other 3 ports. Hence my follow-up that he walk the chain backwards (as you suggested in much better detail) doing a CLRAM on each.

I actually really like having that HEPAX RAM since it is non-volatile. I use 1 page for a ROM image and might assign a second RAM page to that purpose at a later date. I use the rest of RAM to run programs that I can move back and forth between my machines by simply plugging/unplugging the NoV-64. Also, while the 41CL RAM is retained as long as there is power to the machine any loss of power will lead to memory loss while NoV-64 RAM retains it's data. I think that the two used to complement each other results in a fantastic machine.

Cheers,

Marwan

#54

Quote:
1- To check if RAM chip is properly accessible from the NoV module please execute HEPAX 002. You'll see a list of every page with a descriptive label of its contents. "HEPAX RAM" should fill pages #8, #9, #A & #B.

You won't see those pages (#8, #9, #A, #B) if there is a conflict with another ROM module.

I just confirmed this by plugging my NoV-64 into my CV which had a conflict with the Advantage ROM physically in port 2 (pages #A and #B). Those two pages did not show in BLCAT or HEPAX 002.

When I plugged the NoV-64 back into the CL I was missing 1 page of RAM--taken out of the file chain due to the conflict on the CV. It *DID*, however, show up in BLCAT and HEPAX 002 on the CL since there was no longer a page conflict. Note that the reason I was missing 1 page and not 2 is because I have a page taken out of the file chain and assigned as "ROM" holding the YFNS-3B ROM image.

Using:

Alpha
"OK"
Alpha
10
XEQ "CLRAM"
ON
ON

Restored my file chain. XEQ "HEPDIR" prior to power off/power on did not regardless of what the HEPAX manual says. I believe that there is also a function in the NOVCHAP ROM to help restore the file chain.

Cheers,

-Marwan

Edited: 25 May 2012, 5:26 p.m.


#55

Hi again,

And thanks for your kind words about NoV-64 functionalities and usefulness, appreciate... :-)

A few details which may not be as clear as I could imagine:

Quote:
You won't see those pages (#8, #9, #A, #B) if there is a conflict with another ROM module.

Years of involvement in maintenance makes me write things assuming that some common maintenance procedures are observed: My fault.

When it comes to *test* it is regular use that the system under test contains just the parts suspictious to cause the problem, thus isolating them from any external interference.

In NoV's case any external module plugged into ports 1 and/or 2 can be considered (and in fact it is) an "interference" in terms of RAM testing, and NoV's modules are advised to be plugged into port 1 in order to help avoiding such conflicts (at least partially).

RAM shadowing allows the usage of physical ROM pacs without crashing your calc, but if you operate your File System while any ROM is interrupting the FS chain, HEPAX will rebuild the chain reducing its size to make it consistent with the current memory status.

Most any 4K ROM pac plugged into port 2 will cause page #A to be taken off the FS chain, and it will not be recovered after removing the ROM pac.

Quote:
XEQ "HEPDIR" prior to power off/power on did not [recovevr the FS] regardless of what the HEPAX manual says.

I don't recall what exactly HEPAX manual says, but certainly the CLRAM command does not initialize RAM pages, it just erases (Zeroes) it.

Therefore, you *need* to power cycle your HP-41 in order to allow HEPAX recognize and initialize the RAM. Further more, at this point you don't have the FS structure initialized, just the HEPAX RAM; you *need* to execute a File Sytem command (like HEPROOM or HEPDIR) for the HEPAX to actually build the File System Chain and show up the available register count.

My best advice at this point is reading the relevant manuals cover to cover, and do not hesitate in asking whatever you consider doubtful or unclear.... ;-)

All the best from Dom. Republic.

Diego.

Edited: Typos.

Edited: 25 May 2012, 10:02 p.m. after one or more responses were posted


#56

Hi Diego,

Thank you for your response.

Quote:
Years of involvement in maintenance makes me write things assuming that some common maintenance procedures are observed: My fault.

Makes sense to me but I often make the mistake of assuming too much knowledge like when I wrote earlier "You may have to walk the chain backwards doing a CLRAM on each page" (your explanation was so much more complete) so I wanted to clarify that if there is a physical module in place or if a ROM was written to page #8, #9, #A, #B the results would appear different.


Quote:
RAM shadowing allows the usage of physical ROM pacs without crashing your calc, but if you operate your File System while any ROM is interrupting the FS chain, HEPAX will rebuild the chain reducing its size to make it consistent with the current memory status.

Thank you for that clarification. So, if understand correctly, if I install the NoV-64 in the 41CV (with known conflict) do a BLCAT (or HEPAX 002) unplug it and move it back to the CL (with no conflict) the memory chain should still be there--very interesting. But if I do a HEPROOM (or HEPDIR or some other FS function--I actually performed a HEPROOM) the FS is reconfigured to match the current status.


Quote:
Most any 4K ROM pac plugged into port 2 will cause page #A to be taken off the FS chain, and it will not be recovered after removing the ROM pac.

Yes, except for a couple (e.g. Zenrom I believe). I started with the assumption that Les had assigned a ROM module to #B. Why I made that assumption I don't know. Maybe because that is how I am operating--assign "virtual modules" to high page to leave the low page free for physical modules. As I read on I came to the conclusion that this assumption was incorrect and in fact did not have much to recommend it in the first place. My mistake!


Quote:
I don't recall what exactly HEPAX manual says, but certainly the CLRAM command does not initialize RAM pages, it just erases (Zeroed) it.

Therefore, you *need* to power cycle your HP-41 in order to allow HEPAX recognize and initialize the RAM. Further more, at this point you don't have the FS structure initialized, just the HEPAX RAM; you *need* to execute a File Sytem command (like HEPROOM or HEPDIR) for the HEPAX to actually build the File System Chain and show up the available register count.


I think that this is what the manual meant about rebuilding the FS. Makes sense now when I think some more about it.


Quote:
My best advice at this point is reading the relevant manuals cover to cover, and do not hesitate in asking whatever you consider doubtful or unclear.... ;-)

I have been steadily working my way through all the manuals. Lots and lots of reading with all these new toys. And I am sure that I will need to keep going back to them for a while yet. As for asking questions, I will be sure to do so. And please allow me to once again thank you and all the others that have been so helpful in my exploration of these latest HP41 accessories.

Cheers,

-Marwan


#57

Hi there,

My pleasure. After all, finding answers to some other's questions have make me learn a lot along the years... not only about HP calcs BTW.

That's something many others here know for sure.... ;-)

Best wishes and enjoy your 41's toys!

Diego.

PS: The other upper page 4K module I'm aware of, apart from ZENROM, is the AUTOST/Duplication module. If there's any other one(s) I'll be happy to learn about it(them).

#58

Afraid I´m going to throw another log to the fire, but we can all learn more from this (me the first one)

Quote:
you *need* to execute a File Sytem command (like HEPROOM or HEPDIR) for the HEPAX to actually build the File System Chain and show up the available register count.

Well, Diego´s comment was of course absolutely correct... until the advent of the CLUTILS. As you probably know the CL and MLDL2k implementations of the HEPAX ROM disables the auto-relocation capability, thus a manual version was prepared by Howard Owen - and I added some augmented capabilities to it as well.

The function HEPINI will effectively restore the HEPRAM chain, with or without cleared RAM pages. It may also be used to reconfigure it to a fewer number of actually available RAM pages, if so desired. Obvioulsy that can always be undone, so to get them all back in the chain.

HEPINI prompts for two parameters: HEPINI _ - _

The first parameter is the (DECIMAL) number of RAM pages you want configured, and ranges from 1 to 9 (yes, this is only used on the CL).

The second parameter is the (HEX) page# the chain starts from, and ranges from 7 to F (for when there's only ONE).

Holding the key on the last one will NULL the entry. Using back-arrow on the first one will also cancel it out.

Once both parameters are entered the function will follow its course and will write the key control words into the appropriate locations of all blocks involved - be there RAM or ROM, in which case it obviously won't work.

In my experience the real HEPAX (both in original chip or in Nov_RAM) RESPECTS the settings made with HEPINI, even during power-cycling the calculator.

More details available on pages 13/14 in the CLUTILS_2H manual, available at Monte's web site:

http://systemyde.com/pdf/CLUTILS_Man2H.pdf

HEPINI was a tough function to write. As I mentioned it uses Howard Owen's HEPYX as basis for the implementantion - so all I did was to enhance his already superb work.

Hope this help,

Cheers,
'AM

Edited: 26 May 2012, 2:19 a.m.


#59

Hi Ángel,

Nothing to add to your comments.

My previous description on the functionality of HEPAX/NoV was exclusively referred to the behaviour of the modules alone, without any other "external help" like CLUTILS.

Keep up the good job... :-)

Best wishes from Caribbean.

Diego.

#60

Hi Ángel,

I had read the description of HEPINI in the CLUTILS manual but had assumed that it would only work with CL RAM. If I am reading your post correctly this is not the case? It will in fact work with NoV-64 HEPAX RAM (I am having trouble understanding how) or are you saying that it will configure CL RAM to be used by the NoV-64?

I am going back to re-read the manual entry for HEPINI but any insights that you can offer would be appreciated.

Cheers,

-Marwan


#61

Quote:
It will in fact work with NoV-64 HEPAX RAM?

Yes indeed. It will work with anything that has RAM addressed to those pages, like for instance:

- Real HEPAX module

- NoVRAM, NoV-32, Nov-64

- MLDL2k

- 41CL

- even on V41...

Just try it, it's compatible with the existing content of the HEPRAM pages so it won't be lost. (famous last words).

Mind spinning? No worries, I know the feeling! :-)

Edited: 26 May 2012, 3:41 p.m.


#62

Hi Ángel,

I guess this means that CLUTILS is working with page addresses and not RAM addresses? Otherwise how would you differentiate between CL RAM and HEPAX RAM?

Anyway, thanks for the info. I'll give it a try next time I need to make a change to my HEPAX configuration.

Cheers,

-Marwan


#63

Quote:
working with page addresses and not RAM addresses?

As far as I know they are the same thing, right? Unless you NoV-64 useres have other conventions I´m not aware of.

Or maybe you're referring to the CL physical addresses - the location in the CL-sRAM. Well, HEPINI does NOT use those at all, only the calculator page addresses.

HTH!


#64

Hi Ángel,


Quote:
Or maybe you're referring to the CL physical addresses - the location in the CL-sRAM. Well, HEPINI does NOT use those at all, only the calculator page addresses.

Exactly what I was referring to. And that is what I assumed after reading your earlier post. Once again, thank you for the response and confirmation!

Cheers,

-Marwan


Possibly Related Threads...
Thread Author Replies Views Last Post
  42S with nonvolatile RAM Lyuka 5 354 12-13-2013, 08:52 AM
Last Post: Lyuka
  HP-41 Clonix&NoV's SW Update. (For the non-Primer's guys out there... :-) Diego Diaz 21 752 11-13-2013, 09:00 AM
Last Post: Ángel Martin
  Best way to test HP-71B RAM modules (the 32K/96K ones etc.)? Philippe Lasnier 4 377 09-25-2013, 09:54 AM
Last Post: Philippe Lasnier
  HP 2225D+ RAM failure/replacement Luca 4 290 09-10-2013, 01:46 PM
Last Post: Luca
  Questions about building a RAM card for hp 48 Waon Shinyoe (China) 0 159 07-09-2013, 09:53 PM
Last Post: Waon Shinyoe (China)
  HP-41CL & NoV(-64): Race condition? Geir Isene 11 573 05-03-2013, 01:59 PM
Last Post: Diego Diaz
  HEPAX Revisited: Revision 1E available Ángel Martin 4 251 05-03-2013, 01:57 PM
Last Post: Diego Diaz
  Latest Clonix/NoV's SW update. Diego Diaz 5 283 02-15-2013, 12:12 PM
Last Post: Ángel Martin
  [Clonix/NOV] NoV-64 backwards compatibility Doug (NYC) 0 145 01-20-2013, 11:21 AM
Last Post: Doug (NYC)
  NOVRAM 64 / HEPAX bug? M. Joury 2 189 11-03-2012, 02:49 PM
Last Post: M. Joury

Forum Jump: