LUX v100 5 March 1987 LUX - Library Utility eXtension (supports KMD, MBKMD and NUKMD) NOTE: The M80 assembler is needed for this pgm, also the L80 linker. If using KMD, you likely can just use the program 'as is'. If using MBKMD or NUKMD, change the correct equate then assemble and link. A submit file is included to simpli- fy doing this: A>EX15 MAKELUX1 This uses M80, L80 and the included MAKELUX1.COM files to automatically generate a new LUX.COM. (Thanks to whomever wrote this 'merging' pgm.) LUX is a remote (RCPM) library utility that allows a caller to manipu- late archive (.ARC or .ARK) and library (.LBR) files and use simple commands to type or send member files. LUX may only be used on Z80 systems as it is NOT coded for 8080 CPUs. It places itself under CCP (or BYE5) as a form of RSX. LUX v100 is placed on A0: with your other normally-used .COM files. Options in the source code file allow placing the support files on any drive/user area you wish. However, these are also usually placed on A0: so they may be used for normal purposes as well. These are: * CHEK.COM (current is CHEK15.COM, included, see below) LCHEK.COM (current is LCHEK11.com, included) DIR.COM (your SDxxx.COM renamed to DIR, not included) TYPE.COM (can type squeezed or cruched files, included) UNARC.COM (used as TYPE or DIR for .ARC and .ARK, included) ------------------------------------------------------------------------ QUICK INSTALLATION: ------------------ If using KMD, all you will likely need to do is the following: a) remove the member files. b) place the following files on A0: 1. CHEK.COM (not used with LUX, see '*' area below) 2. LCHEK.COM 3. LUX.COM 4. TYPE.COM (in place of your current TYPE.COM pgm) 5. UNARC.COM c) ready to use, all finished. This should work equally well on a small floppy system with two drives or on a 100 Mb system with 12-14 drives, regardless how many user areas are allowed. d) if using MBKMD or NUKMD you will need to use your editor to change an equate in the LUX source code, reassemble and con- vert to a .COM file using the method mentioned in the NOTE, above. ------------------------------------------------------------------------ * Not used with LUX, but of value on your system to allow users to get the CRC of any program to check against the CRC they get for the same program on their own system, after completing the download. (This is actually CHEK15.COM, which you may already have on A0:) Thiis nicely complements the LCHEK.COM which per- mits running a CRC check on a library member. LCHEK is used with LUX but may also be used as a stand-alone program on your system. The only transfer options listed are those available in LUX which are the KMD S, KMD SK, or SEND or SENDK options. Since MBKMD and NUKMD are now using the KMD routines for extracting .ARC and .ARK files in addi- tion to .LBR files, an assembly time option is included to select KMD, MBKMD or NUKMD programs. Since MBKMD and NUKMD have been regularly adopting features added to KMD, futher comments regarding KMD will in most cases also be pertinent for MBKMD or NUKMD. KMD fully supports the 1k packet protocol used in IMP, MEX114, Pro-YAM and nearly all current MS-DOS modem programs. This is a much more effi- cient way to send data at 2400 baud or ANY speed if using a satellite tele-service with delays. KMD also supports YMODEM type batch transfers (used by IMP, MEX-PLUS and nearly all MS-DOS modem programs. This feature is not used within LUX however as batch mode is not available if downloading library members. LUX.COM as distributed was assembled from the LUX100.Z80 source code file which is included. There are virtually no optins which might need to be changed. A SUBMIT type file is included for use with the M80 / L80 assembler-linker pair. EX15.COM is included in the library. You would first edit any changes into the LUX100.Z80 source code file (if any are needed) and then automatically assemble and link using this line: B>EX15 MAKELUX1 A few minutes later you will have a LUX.COM file ready to use on your RCPM. A number of ready-to-use files are included, which enhance the versa- tility of the LUX program. These are dual purpose and normally would be placed on A0: drive, then used for general purpose as well as for LUX: TYPE.COM LCHEK.COM UNARC.COM NOTE: You also need a conventional DIR.COM program with $L capability to show members of a .LBR file. This is usually SDxxx.COM renamed to DIR.COM. Since this changes so frequently, and has so VERY many options to individually set, this file was not included. Most people are currently using SD116A.COM on A0: renamed DIR.COM. (Both SD118 and SD120 have been seen on various RCPM systems.) The TYPE.COM program that is included in this file is a general-purpose program that can display normal, squeezed or crunched files - or any of those three types in a .LBR file. This is a modified version of LT18 written by Steven Greenberg and C. B. Falconer in December 1986. If you have a TYPE.COM program on A0: that you prefer, ignore this one. (You might want to try this one in place of your own first, however. It is not dependent on wheel byte or user area.) The LCHEK.COM program is actually LCHEK11.COM (written by Sigi Kluger in January 1984). It can be used for general purposes as well as for LUX. (It is likely the only way RCPM users can get a CRC check on a member file of a library since they are not allowed to use LU310 or NULU152.) This program has not changed for three years but many RCPM systems are apparently unaware it exists and have not had it available in the past. (You may also want to get CHEK15.COM, rename it to CHEK.COM and put it on A0: if not already in use. This allows anyone to make a CRC check of any program (or programs as wild cards are accepted) on your system and nicely complements LCHECK11.COM which is only used on library members.) UNARC.COM is used to display member contents of an .ARC or .ARK file. Again it can be used for a general purpose program as well as for LUX. This is wheel dependent - if the wheel is set for the SYSOP, he can then use the program to extract files from .ARC or .ARK libraries. Check addresses 010Ah and 010Bh for the wheel byte. These will normally be 3Eh and 00h since the wheel byte is normally at 003Eh on most systems. If your wheel is at FE0Eh, for example, those bytes would be 0Eh and FEh. NOTE: Be sure UNARC.COM has 16h at 0103h, not 08h. This compensates for the 43 records in the LUX100.COM file as a RSX sitting under BYE5. (Not all 43 are moved under CCP/BYE5, though.) NOTE: ARC and .ARK compression methods are still undergoing development so make sure you are using the latest current version of UNARC.COM on A0: A current version as of this date is included with this group of files. COMMENT: ------- This program has been ready since early September 1986 (except for the MBKMD and NUKMD options neither of these supported extraction of .ARC or .ARK files until 01 Feb 87. KMD has supported this since April 1986 when Bob Freed made his routines exclusively available to KMD able for this purpose.) It has been in use on a selective basis for testing on various RCPM systems while waiting on the NOAH program to create .ARK files with CP/M systems. - notes by Irv Hoff, based in part on comments by Norman Beeler in his LUX52 and LUX53 releases.