HP 75 Cat?

[rprosperi]

(03-08-2017 08:07 PM)J-F Garnier Wrote:  This procedure will not work exactly as described on my Emu75, because the port numbering is not managed in the same way. The cat ':rome' ...':romh' will have to be changed for other identifiers between ':roma' and ':romp' , just experiment to find out the right ones !
[hint: for the first plug-in ROM in the emu75.ini file: ':romm', ':rome', ':romi', ':roma' ]

For those playing along at home, in addition to extending the CAT command, these are the keywords in the PODPMSC1 LEX file, though since it was hacked from the original PODCMDS LEX file, it's not yet clear if/how most work, what inputs and outputs are, etc.:

Code:

=========================================
20483 a  STMT: BUILD           PODPMSC1 LEX file
20483 a  STMT: PRIVATE
20483 a  FNC#: CHECKSUM($)
20483 a  FNC#: ROMAVAIL($)
20483 a  FNC#: ROMID($)e.g.    ROMID$(":romf") rtns decimal ID of the rom in bank f
20483 a  FNC#: ROMSIZE($)      ROMSIZE(":romf") produces "ERROR" on EMU75
20483 a  FNC#: PMSREV          PMSREV returns 2 on EMU75, even when PMS is not enabled in the .ini file
=========================================

With only the I/O ROM in Port1, results (in EMU75) are:

:rome
iorom2 L 8168 bytes

:romi
iorom3 L 8164

:romm
iorom1 L 8166

Adding VisiCalc into Port-2 adds:

:roma
vcassem1 PL 8169

:romf
vcassem3 PL 4802
vcbasic3 PB 3289

:romj
vcbasic4 PB 8067

:romn
vcassem2 PL 8169

Quite a non-intuitive rom-mapping scheme. Seems like there are 4 sets of 4 rom banks, though they appear to be loaded/assigned in some unexpected order. I will check further with a real 75C. Why does EMU75 allocate ROMs in different order than a real 75, does'n that mean you had to re-write a lot of code to do the ROM mgmt?

Also, it appears that the PMSCMDS and PODPMS1C LEX files cannot be resident at the same time in EMU75. I installed the latter (with the former already loaded), and upon restart of EMU75, I get an "ERROR" display and the LCD display output is disabled. It took a few moments to realize the LEX files conflict, but upon PURGEing PMSCMDS, EMU75 normal behavior was restored. Is this an EMU75 issue or does the conflict also exist in real h/w (I don't have a PMS yet)? I'd guess that when Bob Bradley (or whoever) hacked the original LEX, perhaps he didn't change the LEX ID.

[Update 1]

On a real 75D (rom aaaaaa) with a VisiCalc ROM in Port1, results are:

:rome
vcassem3 PL (same files sizes as above)
vcbasic3 BL

:romf
vcbasic4 PB

:romg
vcassem1 PL

:romh
vcassem2 PL

So, on a real 75, it appears the ROM banks are be allocated like this:

PMS:
4 x 8KB RAM/ROMs, :roma, - :romd

Port1:
4 x 8KB ROMs, :rome - :romh

Port2:
4 x 8KB ROMs, :romi - :roml

Port3L
4 x 8KB ROMs, :romm - :romp

Will update this after checking out a 75 in a POD (which plugs-in to Port3).

Anyone - Please correct the above if you know more/better

Thanks