LOGON Version 1.2, by David C. Oshel  (Kaypro 10 version)

Computers with 10 megabytes of hard disk storage are confusing places.

This program is a compromise between the knowledgeable, ten-fingered user
who wants to type on the CP/M command line, and your novice users who are
more comfortable, at least at the beginning, with menus. There is a briefly
implemented password scheme to gently guide the very young out of dangerous
areas on the machine, and for whom "out of sight" is truly "out of mind". 

This program was written for a Kaypro 10.  Command line arguments are fully
supported, but are prompted for one at a time based on information in the
users list.  There may be up to 64 users or applications, like BOB or ZORK,
each with a different startup program and its (possibly user-supplied) list
of parameters.  The whole nasty business of CP/M command lines is largely
avoided, but not ignored.

Modifying this program for MS-DOS should be a breeze, but that is an exercise
for the reader, since I don't have a PC, or enough time at work to mess around
with 16-bit C.  These programs were compiled with Software Toolworks C/80 and
assembled and linked using Microsoft utilities.  The "#include" files and
REL files to which the modules are linked contain proprietary information and
so cannot be released, but these contain nothing mysterious. 

Associated files:  LOGON.COM, LOGUTIL.COM, LOGON.USR



The order of installation is somewhat sensitive:

1.  Install the LOGON suite on your Kaypro 10 hard disk system.  Place the
    LOGUTIL.COM program in user 15, drive A, then run it.  This creates the
    user list, LOGON.USR.

2.  Install three users (the program is self-documenting) named LOGOFF,
    BYE and QUIT, each with the asterisk ("*") password.  The startup program
    for all of these users is SAFETY, located on user 0, drive A.  SAFETY is
    the program that "parks the heads" on the hard disk and locks the keyboard.

3.  Install the LOGON.COM program in user 0, drive A.  LOGON is now safe to
    run.  Without a LOGON.USR file in A15:, LOGON will report an error and
    then hang the system.

4.  Make LOGON an autoboot program, so that it runs when you cold start the
    Kaypro 10.  IF YOU DO NOT HAVE COMLINE.COM, the easiest way to do this
    is to keep two copies of LOGON, one called LOGON.COM and the other called
    MASMENU.COM, and be sure to run Kaypro's YESMENU.COM program.  The alias
    will now run instead of the Kaypro MASMENU program (which you renamed,
    of course).  You may also patch the hard disk system image on drive A,
    using DU.COM.  COMLINE.COM is provided by Kaypro in the Kaypro 10 reload
    kit supplied to authorized dealers. 



There are three levels of user privilege:  PRIVATE, those with passwords;
HIDDEN, those with the * password; and PUBLIC, those not requiring passwords.
Hidden users are really public, but hidden user names do not appear in the
LOGON on-line help.

LOGON does NOT support CP/M intrinsic commands like DIR, TYPE and ERA, unless
the user application is a file which is SUBMIT'd.  User SUBMIT files should
include LOGON as their last command line.

System security is VERY LAX, because this program assumes a normal CP/M 2.2
system with an unmodified CCP.  When the user's application ends, a $$$.SUB
file in the user's user area on drive A becomes active; this file will be
interpreted by the CCP's submit facility, and the result is a chain back to 
LOGON.  This procedure may be interrupted by any keystroke after the warm
boot (user program ending) and before the CCP picks up the LOGON command from
the $$$.SUB file.  Once into LOGON, however, the program is not interruptible,
nor is the process of chaining to the next user's application.

However, "system security" is hardly a primary concern when all you're REALLY
interested in is giving your nephews and nieces some way to run ZORK without
risking their questions about CP/M and the A0> prompt...!