MMUCAT - PowerCL_EXT NONEXISTENT XROM call

[Ángel Martin]

(02-11-2017 05:16 AM)dingebre Wrote:  First, Thank you Ángel for these amazing modules!

Very glad to hear you find the modules useful, that's the best reward for me as the programmer ;-)

Quote:I have:
HP41CL, version 4 PCB, current as of mid January 2017 (I have tried it on two HP41CLs with the same configuration with the same result.)

PGCAT:
3: EXT FCN 3B
4: Library#4
5: Time 3A
6: No ROM (Left open for PIL Box printer)
7: No ROM (Left open for PIL Box mass storage)
8: YFNX 2B
9: PWREXT B3
A: HEPAX'4H
B: HEPAX RAM
C: No ROM
D: No ROM
E: No ROM
F: No ROM

When I execute MMUCAT in the PowerCL_EXT module, it returns "NONEXISTENT" at line 7 which displays "07 XROM 05,31"

I thought that maybe I needed the CCD OS/X ROM and plugged it in (XROM #5?), but that didn't help.

I'm afraid this is a version mismatch issue. Your instincts were correct, indeed the call to XROM 05,31 corresponds to the function WSIZE in the AMC_OS/X module. But this one has had a few versions in the last couple of years that have altered the FAT a little, probably enough to cause this hiccups.

Make sure you use the latest version of the OS/X module; it's a bank-switched version with the "OSX3" for CL id# (to plug it in). BTW the OS/X module is a must-have for me, the extended catalogs and synthetic entry are just amazing.

Quote:I did a CAT2 and "entered" the PWR ROM catalog and MMUCAT is there where it should be. If I "GTO MMUCAT", I get "NONEXISTENT". I can't "COPY" it, or print it. When I go into "PRGM" mode after the error, there is no global "MMUCAT" label. Line 01 is a numeric "2" and I'm stopped at line7 with the "XROM 05,31" call. When I look at and compare to the listing in the manual, there is little resemblance as I step through the code on the calculator which makes me think I am not in the "MMUCAT" code.

I don't understand. What am I missing?

What you're seeing there is a collateral effect of removing the global label from a FOCAL program, replacing it with an MCODE header. This is convenient for a couple of reasons (shorter code, amongst them) but the downsize is that you cannot "GTO" it. To position the PC within it you need to call the function and stop the execution while it's doing its work.

Then the OS misinterprets the MCODE header assigning bogus program line numbers to it, offsetting the count. So the function called should be WSIZE, and it is in line 05 (not 07!) See the complete MMUCAT program listing below:

Code:

1    LBL "MMUCAT"
2    50
3    PTURBO
4    4
5    WSIZE
6    LBL 01
7    "0-0000"
8    ASTO X
9    3,015
10    LBL 02
11    8040
12    ARCLH
13    ARCL Y
14    YPEEK
15    ASHF
16    ATOX
17    ATOX
18    RDN
19    RDN
20    ADRID
21    ARCLH
22    "|-: "
23    -3
24    AROT
25    RDN
26    "|--"
27    PGSIG
28    AVIEW
29    PSE
30    ISG X
31    GTO 02
32    CLST
33    CLD
34    RTN
35    GTO 01
36    END

Let me know if this helps; if the error persists I can send you the latest revisions of the ROM files but I think the CL board you have does already have them.

Quote:Other functions in the other PWREXT module pages seem to be fine, although I haven't even really begun to test them all (love the unit management).

David

Enjoy the ride, there's a lot to explore in there. And don't get discouraged it you run into wrinkles, it's tricky stuff and requires a good grasp of things not to get confused somehow (I get lost frequently ;=) Anyway, help is always an email away.

Best,
ÁM

PS. When you're comfortable with the PWREXT features move on to the TotalRekall_Dare2Compare version) and the CLXMEM modules, these really unleash all the CL potential in my mind.