Clonix issue with built-in HEPAX

[Diego Diaz]

Hi Jürgen, Sylvain,

Sorry to get so late to the party.

As usual, Sylvain tests and result presentation are impeccable.

Some doubts about the built-in HEPAX behaviour arises:

Since real HEPAX use volatile SRAM, it should be erased every time the battery is removed from the HP-41CX. So there will be no need to CLRAM its contents.

Once the power is restored, the initialization program will allocate HEPAX code (usually into page #6 if no HP-IL or 82143A printer is present) and will build the HEPAX File System in the available memory assigning the usual XROMs B, C, D & E to pages 8, 9, A & B respectively.

@Jürgen, did you checked this without Clonix-(41/D) installed? This could help to confirm if the built-in HEPAX is behaving properly. BTW, the type of Clonix used (-D, -41 or -41d) will make no difference; or NoV-64(d) configured as Clonix-D for that matter...

@Sylvain, just a configuration hint, when using just one of the ROM banks in a Clonix-D (or NoV-64d) you can just mark the "Join Blocks" box to get the ROMs available regardless the port you plug the module in. This saves the need of programming both blocks with the same images.

Apart from that, I've also checked the proposed configuration (almost):
- ADV HEPAX but v.1D not 1C (real module) -> Port 1
- Clonix-41d: SKWIDBC pg. #C, ZENROM3B pg. #D -> Port 3

And found no problem at all.

Also intrigued by the unusual File System links described by Jürgen on his last post.

Please comment if you find the cause.

All the best.

Diego.