floppy_stuttgart wrote:An HP41 with 2 Clonix-D? Interesting. New for me (probably I did not understood the all subject especially banks etc.).
I have one spare Nov64d I will setup it in Clonix-D. I will try. Any advice how the setup should looks like is welcome (however I will try and hopefully come quick to the point).
I used an old ClonixConfig setup, so ROM files used here are not the latest, but for the test it should be ok.
A HP-41CX Halfnut was used to validate this setup.
NoV-64d module #1 → configured as Clonix-D
XROM → LIB4 [n/a] , SMAT [XR=3] , HLMAT [XR=2] , WARP [XR=21]
NoV-64d module #2 → configured as Clonix-D
XROM → AMC-OSX [XR=5] , HP-16C [XR=16]
CAT shows CAT " meaning that CCD extended catalog provided by AMCOSX4 is working.
CAT 2 shows:
- Code: Select all
-EXT FCN 2D
-CX EXT FCN
-TIME 2C
-CX TIME
-SNDMTH'4x4
-FRC
-HYP
-RCLIO
-HL MATH+
-PB/STS
-WARP CORE+
-STKT
-AMC"OS/X
-HP-16C+
-16C STCK
Port based catalogs:
- Code: Select all
CAT 8 → -SNDMTH'4x4 ,...
CAT 9 → -HL MATH+ ,...
CAT A → -WARP CORE+ ,...
CAT B → NO ROM
CAT C → -AMC"OS/X ,...
CAT D → -HP-16C+ ,...
CAT E → NO ROM
CAT F → NO ROM
I have executed some functions from modules and everything seems to work, as I thought it would.
Now more extensive tests are needed to validate this completely but IMHO it should work.
Since bank switching was introduced very late in the 41 life, HP decided that the plugged peripheral was responsible for handling the bank switch of its own hardware.
That is why several hardware manufacturers implemented their own way to do it. (ex.: HP, CMT, Zengrange, etc.)
In Diego case,
Each module handle the bank switching of their own ROMs.
The two module scenario will work as long all ROMs of a bank switched module reside in the same Nov/Clonix module.
Having ROMs from both modules accessing the Library4 located in page 4 of one module works because page 4 is not bank switched here.
If Library4 was bank switched, the above setup would not have worked.
Final note, with the above configuration NoV-64d module #1 can be used standalone, but NoV-64d module #2 need the Library4 located in NoV-64d module #1.
If you try to use NoV-64d module #2 alone, the message "NO LIBRARY" will be displayed, which is expected in this case.
Sylvain
Edit: typos, added the last two paragraphs.