🚀 go-pugleaf

After reading your background routine code, I have some general questions:

	1) there are 3 absolute addresses defined at the start (ssp, ccpmain
and log_dsk).  Where are these addresses?  are they somewhere in the guts of
CPM.SYS?  On my system I can't use absolute addresses.  The Stride 400
series (as well as the older Sage II and IV) use two levels of BIOS - one is
CPMBIOS and is linked into CPM.SYS, the other is the Stride BIOS which is
separate and comes in two flavors:  Single-User and Multi-User.  I am
running the Multi-User Stride BIOS, setup for three CP/M users (each has its
own copy of CPM.SYS core resident, at different places in memory with
different TPA boundaries).  Thus these addresses are not static.  Also on my
system CPM.SYS is not absolute, relocatable.  The bootstrap program does a
relocatable load - I don't have to relocate CPM.SYS if I reconfigure the
system (add memory, more/fewer users, different size TPA for each user, run
in SU mode, etc.).  Also, each user task actually loads the SAME CPM.SYS
file in different places with different TPA limits.

	2) how are these routines linked?  with an application program or
with CPM.SYS?  Or are they just linked as a module of their own?

I'd like to be able to use these background routines with two programs I
have now: Mince and UNaXcess (a bbs system originally for UNIX). I'd like to
hace Mince do the sort of stuff you are doing with uEmacs (compiling a file
with the compiler output going to a buffer). UNaXcess under UNIX has the
posiblity of running either a shell or some random UNIX editor (ie vi,
emacs, etc.) instead of the dumb built-in editor (much like the usual bbs
editor), as well as forking off kermit or lmodem for file upload/download.
In the verision I have running, all of the system(), pipe() and exec() calls
are disabled.


					Robert Heller