BYE5 information for CP/M Plus users (7/12/86) Please note that with the BYE506 release, most of the functions previously performed by the B5-CPM3.ASM (BYE.COM) program have been moved to BYE506.ASM and that the BYE5 RSX is loaded only when necessary. This new operation is more efficient than previous schemes for RSX removal and system setup and allows the EXFILE logic in BYE5 to operate the same for all CP/M implementations. A major change in BYE509 allows virtually all CP/M Plus implementations to operate with a basic .INS file (i.e. no MDPREP/MDPOSP routines) like CP/M 2 implementations. WHAT YOU WILL NEED: ------------------- - LU.COM and USQ.COM to unpack the distribution library file - The B5-CPM3.ASM file (supplied), which allows CHAINing or RUNning BYE from BASIC and schedules the RSX loader (B5-DRIV3) if necessary. - The B5-DRIV3.ASM file (supplied), which is the RSX driver program - The BYE5nn.ASM file (supplied), which will become the CP/M+ RSX - The B5??-n.INS machine-specific insert (available in BYE5-INS.LBR) - The B5C-CPM3.INS clock insert for CP/M Plus to replace routine TIME: in BYE5nn.ASM - RMAC.COM, LINK.COM, and GENCOM.COM (supplied with CP/M Plus) CONFIGURING BYE5 FOR CP/M PLUS ------------------------------ A single configuration parameter (CPM3) controls CP/M Plus code generation in the BYE5nn.ASM file. Be sure to set CPM3 to YES for CP/M Plus operation. See BYE5.DOC for additional CPM3 controls. You should also use the ZCPR2 "WHEEL" feature to enable and disable SYSOP access to privileged system commands or program options. Set ZCPR2 to YES to allow SYSOP control of the WHEEL byte. Unless your BBS program has full control of the maxuser and maxdrive locations set USEZCPR to NO and the other CCP options to the appropriate values. B5-CPM3.ASM and B5-DRIV3.ASM are necessary for generation and operation of BYE5 for CP/M Plus but do not require configuration or modification on most systems. GENERATING BYE.COM AND B5-DRIV3.COM ----------------------------------- Mimic the following suggested script to generate BYE5 for your CP/M Plus machine: 1 RMAC B5-CPM3 $PZ SZ 2 LINK B5-CPM3[NR] 3 RMAC B5-DRIV3 $PZ SZ 4 LINK B5-DRIV3[NR] 5 RMAC BYE5nn $PZ SZ 6 LINK BYE5nn[OP,NR] 7 RENAME BYE5nn.RSX=BYE5nn.PRL 8 GENCOM B5-DRIV3 BYE5nn 9 RENAME BYE.COM=B5-CPM3.COM 1 - Assemble the caller-visible BYE program source 2 - Build a .COM file from B5-CPM3.REL 3 - Assemble the BYE5 RSX driver module 4 - Build a .COM file from B5-DRIV3.REL 5 - Assemble the configured and patched source file. Note that RMAC, not M80, must be used. 6 - Build a .PRL file from the .REL file generated in step 5 7 - Rename the LINK relocatable output file from BYE5nn.PRL to BYE5nn.RSX for GENCOM processing 8 - Post-process the .COM file to add the RSX just generated 9 - Rename the B5-CPM3.COM file to the familiar BYE.COM The BYE.COM and B5-DRIV3.COM files are now ready to be placed in A0:. B5-DRIV3.COM may be renamed to something other than B5-DRIV3 but B5-CPM3.ASM must be updated to reflect that name change. The B5-DRIV3.COM file should be made a SYSTEM (hidden) file to minimize "accidental" unnecessary loading/ unloading of the BYE5 RSX. Type BYE to start the BYE program the same way a caller will type BYE to reset the system for the next caller. The BYE program will use the CP/M Plus BDOS chain function to load and execute the B5-DRIV3 RSX loader program to perform system initialization. OPERATING WITH BYE5 IN A CP/M PLUS ENVIRONMENT ---------------------------------------------- B5-CPM3.ASM is provided with the BYE5 release. That program can be assembled, linked, and placed in the default directory as BYE.COM. The program exists ONLY to satisfy the requirement that a program named BYE.COM exist on an RCP/M+ system. All processing is performed by the BYE5 RSX. If BYE.COM cannot locate the BYE5 RSX, it will pass the caller's command tail on to B5-DRIV3.COM to initialize the RSX. The B5-CPM3.ASM file is set up to call A:B5-DRIV3.COM which will be acceptable on most systems. The literal (representing the BYE5 RSX driver program name) can be changed or moved as the Sysop requires. The use of this two-file BYE system requires no special configuration. Many RBBS-type programs CHAIN to or RUN the BYE.COM program to cause a disconnect. Most are unaware of CP/M Plus and so simply load the BYE.COM program into the TPA and jump to it. If the program being chained to or run contains an RSX, its first instruction is always RET so the chain or run is in effect ignored. This two-file BYE5 setup allows all RBBS programs to operate as intended by loading the BYE.COM program which has no attached RSX's. That program then uses CP/M Plus or BYE5 functions to load and/or execute the "real" BYE program (usually named B5-DRIV3.COM). In order to save space and make the system operate as required for RCP/M use, a sequence similar to the following is recommended to set up the system prior to BYE use (Do not include the initial BYE call in a .SUB file): 1 LD.COM;psword \ 2 BYE 1 Make sure all unnecessary LD-generated RSX's are removed prior to system access 2 Start up the BYE.COM program which will chain to the B5-DRIV3 program and load the BYE5 RSX. Note that "psword" should be changed to your own system's default password. Use of passwords on files "not for distribution" or not recommended for callers' use can be available for the SYSOP but unavailable to callers. If you are using Jim Lopushinsky's CCPnnn+ in place of the standard CP/M Plus CCP, you won't need to make the files in user zero of your control disk SYStem. Use of that package is recommended for optimum remote operation and security. CCP104+ makes use of features new in BYE509. Jim's Meadowlark RCP/M+ number is 403-435-6579. If you don't use CCP+ and you have enough disk space, place copies of all your online programs (RBBS.COM, DIR.COM, XMODEM.COM, BYE.COM, etc) with SYStem attribute set in user zero of some drive other than A. Then place the .COM files your users typically look for in A0: with attribute DIR. That way, they can do a DIR of A0: and know what is available for execution and still execute them all from any drive/user on the system. BUILDING AN INSERT FOR CP/M PLUS -------------------------------- Any existing insert can be used as a guide from which a new BYE5 insert can be built. CP/M Plus inserts are no different from CP/M 2 inserts. ADDITIONAL SUPPORT SOFTWARE --------------------------- CCPnnn+.LBR and LDnnn.LBR are available in the CP/M Plus section on many RCP/M systems. Those packages, along with BYE509 and above combine to provide an excellent RCP/M+ package for caller and SysOp alike. CONTACT POINTS -------------- George Peace P.O. Box 4344 / Harrisburg, PA 17111 or CompuServe: 71555,1501 or Data only number: 717-657-8699 (300/1200/2400) In addition to the standard contact points listed in the BYE5nn.ASM file, please feel free to use the CompuServe CP-MIG SIG (GO PCS-47), the FOG RCP/M's, and my own system (see telephone number above) to discuss program operating characteristics, report bugs, and, most important of all, to funnel your suggestions and updates to me.