Threaded Mode | Linear Mode

Ángel Martin · (This post was last modified: 12-17-2017 07:52 AM by Ángel Martin.)

Hi Peter, - it's all working correctly; let's see these one at a time:-

(12-17-2017 06:14 AM)PeterP Wrote:

Code:

Memory Lost TURBO50................want this to go fast MMUDIS..................disable MMU MMUCLR..................clear the MMU "YFNX"....................“41CL Extreme Functions” ID into alpha PLUGH....................plug it to the logical page 7 (HP-IL reserved location) “804040-8120”........“Lib#4” physical location YPOKE....................plug Lib#4 into page 4 (PowerCL Ext needs it) “PWRX”...................“PowerCL” ID into alpha PLUG1L...................plug it page 8 MMUEN...................enable MMU

After this I can do a XCAT - "G" to see that everything is properly plugged in. I get the following info:

Quote:4: Lib#4 R44
5: Time 3A
6: no rom
7: YFNX 2C
8: PWREXT B3
rest 'no rom'

So far, so good.

Indeed that looks alright, everything as expected.

(12-17-2017 06:14 AM)PeterP Wrote: Now, when I try to an XEQ "PGCAT" I get the message NONEXISTENT!

This seems strange to me, but maybe this is how it is supposed to be, namely that I can not enter the function PGCAT directly, but only via the launcher.

Question 1: Is this behavior expected?

Yes it is, PGCAT is a sub-function in one of the two auxiliary FATs that are in this module, and therefore needs to be accessed using any of the several sub-function launchers.

If you want to do it by spelling their names, there are two of these launchers in the PWRX module, named "XQ$1" and "XQ$2". Their index refer to the corresponding sub-FAT they start the search with, but either one will eventually search on both (and even on all main FATs if the name isn't found in the sub-FATs...)

This is the "manual" approach, in which you spell the sub-function name at the launcher prompt. This is identical to the "HEPAXA" function in the HEPAX module, which you'd call to then spell "BCAT" at its prompt - i.e. the original "Block Catalog" - that I renamed as PGCAT in the PWRXT. Do you see the equivalence now?

(12-17-2017 06:14 AM)PeterP Wrote: The functions that I really care about are for banks, namely BANKED and BANKS?. Again, I can't launch those functions directly via XEQ. But I can get to them via the launchers: XEQ "XCAT" [SHIFT] "B" executes the function BANKED. Now here is the next surprise: The display shows as answer 5! Only 5!

Even though the PowerCL_EXT is in page 8 and seems clearly bankswitched, it is not listed.

Question 2: Is this behavior expected? What am I doing wrong?

Not quite. First off, here too you're dealing with sub-functions (BANKED, BANKS?, BFREE, BUSED...) and as such you need to use a sun-function launcher to access them by their names. This you're doing well: XCAT, SHIFT invokes IOBUS, and then "B" triggers the sub-function BANKED.

But definitely BANKED should report the PowerCLExtreme itself in the list of results, that's an anomaly.

Try BUSED, does that show the page used by the PWRXT ?
This could be a version mismatch, try XEQ "XQ$2" "REV" ; which string does it return?

(12-17-2017 06:14 AM)PeterP Wrote: The underlying task I am trying to accomplish is to copy bank-switched physical modules to the PC for further analysis. For that, I have to find out which modules are actually bank-switched and with how many banks.

Unfortunately the function that I need for that, CPYBNK does not reside in the PowerCL_EXT, but has to be taken from the "CL ExpMem", which requires the "AOS/OSX" as well. And then I need the HEAPX and at least one page of RAM also, making the calc pretty full. If only Angel could squeeze the CPYBNK function into the PowerCL_EXT...

The AMC_OS/X is not really needed if all you want to use from the CL_XPMem module is the CPYBNK function. (although I'd always recommend you have it plugged in... it tucks away in page#6 and thus doesn't use any of the upper pages so they'll all fit).

(12-17-2017 06:14 AM)PeterP Wrote: It would be really helpful if I could assign the functions BANKED and "BANKS? to a key, but when I try this, I get the NONEXISTENT message again.

Question 3: Is there a way to assign these functions to a key?

No, it's not possible to assign sub-functions to a key because they are not in the main FAT and thus the OS knows nothing about them. By the same token they cannot be accessed by the standard XEQ anyway.

That's why the main "sCL" (s: sigma) and the other "launchers" (like IOBUS) facilitate things immensely, as the sub-functions are pre-assigned to hot keys. There are several of these launchers that group many sub-functions by categories. All of them launchers can be triggered from the main launcher sCL, so it's pretty much an alternate keyboard at your fingerprints...

Really sCL is your best friend and probably will cover all your needs - you should assign it to the Sigma+ key and experiment with it a bit, it opens the door to all the many different layers within the module.

(12-17-2017 06:14 AM)PeterP Wrote: Anyways, it would be great to hear from the experts on what I am doing wrong and how to fix it.

As always, thank you so much!

Hope these pointers help you get the gist of things, it's really simpler than it seems once you grasp the difference between normal functions in the main FAT and sub-functions in the sub-FATs...

Cheers,
ÁM