I'm finding conflicting information about XSUB. The CP/M 2.2 manual says:when it passes them through. The answer is probably in the build script, which I have not located. This detail is important in order to know how the CCP behaves when XSUB is active, and whether/when XSUB will detect that $$$.SUB has been deleted.
The XSUB program remains in memory and prints the message "(xsub active)" on each
warm start operation to indicate its presence. Subsequent SUBMIT command streams
do not require the XSUB, unless an intervening cold start occurs.
Which suggests it can only be unloaded by a cold boot. However, the source code shows that if the $$$.SUB is gone when it tries to read a command/line it will unload itself. But the source code is not clear just when it intercepts the bdos calls and
On Friday, February 3, 2023 at 8:38:06 PM UTC-8, Douglas Miller wrote:when it passes them through. The answer is probably in the build script, which I have not located. This detail is important in order to know how the CCP behaves when XSUB is active, and whether/when XSUB will detect that $$$.SUB has been deleted.
I'm finding conflicting information about XSUB. The CP/M 2.2 manual says:
The XSUB program remains in memory and prints the message "(xsub active)" on each
warm start operation to indicate its presence. Subsequent SUBMIT command streams
do not require the XSUB, unless an intervening cold start occurs.
Which suggests it can only be unloaded by a cold boot. However, the source code shows that if the $$$.SUB is gone when it tries to read a command/line it will unload itself. But the source code is not clear just when it intercepts the bdos calls and
Yes like PIP and other utilities, it was probably written in PL1. I know a cold boot fixes it and it looks like it actually resides in low memory below the CCP and not in high memory near the BIOS.
The mystery continues ...
On Saturday, February 4, 2023 at 12:18:37 AM UTC-5, Jack Fenton wrote:and when it passes them through. The answer is probably in the build script, which I have not located. This detail is important in order to know how the CCP behaves when XSUB is active, and whether/when XSUB will detect that $$$.SUB has been deleted.
On Friday, February 3, 2023 at 8:38:06 PM UTC-8, Douglas Miller wrote:
I'm finding conflicting information about XSUB. The CP/M 2.2 manual says:
The XSUB program remains in memory and prints the message "(xsub active)" on each
warm start operation to indicate its presence. Subsequent SUBMIT command streams
do not require the XSUB, unless an intervening cold start occurs.
Which suggests it can only be unloaded by a cold boot. However, the source code shows that if the $$$.SUB is gone when it tries to read a command/line it will unload itself. But the source code is not clear just when it intercepts the bdos calls
Yes like PIP and other utilities, it was probably written in PL1. I know a cold boot fixes it and it looks like it actually resides in low memory below the CCP and not in high memory near the BIOS.
The mystery continues ...XSUB goes resident, and stays resident in CP/M 2.2. Digital Research published a patch DEXSUB.COM which
removed XSUB from memory.
As far as I can tell, XSUB should unload itself when it finishes with the submit file (and it gets deleted) - "$$$.SUB". But, there were vendors that customized or made their own version of xsub, so this might not be the official version. It could alsobe that something about your CP/M setup or BIOS version could be preventing it from detecting/deleting "$$$.SUB".
BTW, XSUB resides below the CCP and in order to do that it needs to assume the length of the CCP. If your system is using a custom CCP that is not the standard length of 0800H then you could be running into problems related to that (unless your XSUBwas special-built for that system).
So, more information would help.
On Friday, February 3, 2023 at 11:20:13 PM UTC-5, Douglas Miller wrote:also be that something about your CP/M setup or BIOS version could be preventing it from detecting/deleting "$$$.SUB".
As far as I can tell, XSUB should unload itself when it finishes with the submit file (and it gets deleted) - "$$$.SUB". But, there were vendors that customized or made their own version of xsub, so this might not be the official version. It could
was special-built for that system).BTW, XSUB resides below the CCP and in order to do that it needs to assume the length of the CCP. If your system is using a custom CCP that is not the standard length of 0800H then you could be running into problems related to that (unless your XSUB
So, more information would help.CP/NET came with its own version of XSUB -- XSUBNET. My R loader accomodates "normal" or CP/NET
CCP to determine if it is safe to allow RET to CCP from transient program. See
https://github.com/ratboy666/r
I've wondered if there is an easier approach?!?
On Saturday, February 4, 2023 at 7:18:52 AM UTC-8, fridtjof.ma...@gmail.com wrote:also be that something about your CP/M setup or BIOS version could be preventing it from detecting/deleting "$$$.SUB".
On Friday, February 3, 2023 at 11:20:13 PM UTC-5, Douglas Miller wrote:
As far as I can tell, XSUB should unload itself when it finishes with the submit file (and it gets deleted) - "$$$.SUB". But, there were vendors that customized or made their own version of xsub, so this might not be the official version. It could
XSUB was special-built for that system).BTW, XSUB resides below the CCP and in order to do that it needs to assume the length of the CCP. If your system is using a custom CCP that is not the standard length of 0800H then you could be running into problems related to that (unless your
developers replicated the original issue the Digitial Research originally designed but never patched the update and DR did.So, more information would help.CP/NET came with its own version of XSUB -- XSUBNET. My R loader accomodates "normal" or CP/NET
CCP to determine if it is safe to allow RET to CCP from transient program. See
https://github.com/ratboy666/r
I've wondered if there is an easier approach?!?Yes, for me, I will need to figure out how to modify it for my system which is actually running NZ-Com with ZSDos Extensions so the CCP is certainly it's own thing here. NZ-COM uses XSUBZ instead of XSUB and yes, it seems to stay resident. I guess the
I assembled and ran the program but although it reported XSub no longer active, the process of restoring the vectors is probably different as I'm still getting the message "XSubz Active" with every warm boot. Not a big deal but thanks for all thatanswered!
On Sunday, February 5, 2023 at 11:22:53 AM UTC-5, Jack Fenton wrote:could also be that something about your CP/M setup or BIOS version could be preventing it from detecting/deleting "$$$.SUB".
I found my issue was I was running a shell on my NZ-Com systems so it was keeping XSUB active. So I have to exit the shell and XSUBZ will properly terminate automatically if there is no $$$.sub in the A0: area on this disk. I was running LSH.
On Saturday, February 4, 2023 at 7:03:19 PM UTC-8, Jack Fenton wrote:
On Saturday, February 4, 2023 at 7:18:52 AM UTC-8, fridtjof.ma...@gmail.com wrote:
On Friday, February 3, 2023 at 11:20:13 PM UTC-5, Douglas Miller wrote:
As far as I can tell, XSUB should unload itself when it finishes with the submit file (and it gets deleted) - "$$$.SUB". But, there were vendors that customized or made their own version of xsub, so this might not be the official version. It
XSUB was special-built for that system).BTW, XSUB resides below the CCP and in order to do that it needs to assume the length of the CCP. If your system is using a custom CCP that is not the standard length of 0800H then you could be running into problems related to that (unless your
the developers replicated the original issue the Digitial Research originally designed but never patched the update and DR did.So, more information would help.CP/NET came with its own version of XSUB -- XSUBNET. My R loader accomodates "normal" or CP/NET
CCP to determine if it is safe to allow RET to CCP from transient program. See
https://github.com/ratboy666/r
I've wondered if there is an easier approach?!?Yes, for me, I will need to figure out how to modify it for my system which is actually running NZ-Com with ZSDos Extensions so the CCP is certainly it's own thing here. NZ-COM uses XSUBZ instead of XSUB and yes, it seems to stay resident. I guess
answered!I assembled and ran the program but although it reported XSub no longer active, the process of restoring the vectors is probably different as I'm still getting the message "XSubz Active" with every warm boot. Not a big deal but thanks for all that
If you are running NZ-Com why not use a Zsystem tool like ZEX instead of SUBMIT (unless you are having TPA issues)? That way XSUB is no longer an issue. ZEX has a very clean way of handling user console input.Yes, I'm using ZEX now. Just a bit of a learning curve but I think I've got it worked out. NZ-COM is very nice. I built my own ZCPR3 system back in the 80s after getting Richard Conn's book. NZ-COM improved on the concepts quite a bit. The old
Lars
I found my issue was I was running a shell on my NZ-Com systems so it was keeping XSUB active. So I have to exit the shell and XSUBZ will properly terminate automatically if there is no $$$.sub in the A0: area on this disk. I was running LSH.could also be that something about your CP/M setup or BIOS version could be preventing it from detecting/deleting "$$$.SUB".
On Saturday, February 4, 2023 at 7:03:19 PM UTC-8, Jack Fenton wrote:
On Saturday, February 4, 2023 at 7:18:52 AM UTC-8, fridtjof.ma...@gmail.com wrote:
On Friday, February 3, 2023 at 11:20:13 PM UTC-5, Douglas Miller wrote:
As far as I can tell, XSUB should unload itself when it finishes with the submit file (and it gets deleted) - "$$$.SUB". But, there were vendors that customized or made their own version of xsub, so this might not be the official version. It
XSUB was special-built for that system).BTW, XSUB resides below the CCP and in order to do that it needs to assume the length of the CCP. If your system is using a custom CCP that is not the standard length of 0800H then you could be running into problems related to that (unless your
the developers replicated the original issue the Digitial Research originally designed but never patched the update and DR did.So, more information would help.CP/NET came with its own version of XSUB -- XSUBNET. My R loader accomodates "normal" or CP/NET
CCP to determine if it is safe to allow RET to CCP from transient program. See
https://github.com/ratboy666/r
I've wondered if there is an easier approach?!?Yes, for me, I will need to figure out how to modify it for my system which is actually running NZ-Com with ZSDos Extensions so the CCP is certainly it's own thing here. NZ-COM uses XSUBZ instead of XSUB and yes, it seems to stay resident. I guess
answered!I assembled and ran the program but although it reported XSub no longer active, the process of restoring the vectors is probably different as I'm still getting the message "XSubz Active" with every warm boot. Not a big deal but thanks for all that
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (0 / 16) |
Uptime: | 111:28:29 |
Calls: | 6,701 |
Calls today: | 1 |
Files: | 12,233 |
Messages: | 5,348,704 |