LOCKOUT
                              v1.0 Beta Test Copy
                          Copyright (c)1994 Roy Coates
                             roy@mechnet.liv.ac.uk



NOTE: This is the first version and is offered for test purposes only.
      It works for me... it should work ok for you. I intend to modify
      the lockout program so that a better, more permanent database of
      allowed users may be kept for later re-use. Please mail comments,
      bug reports, ideas etc to the address above.


LOCKOUT
---------------------------------------------------------------------------
Lockout provides a method for preventing users from logging into the 
network except for users who are specified when lockout is invoked. This is
rather handy when you are trying to develop software on the system and need
to login and logout yourself. Lockout will also allow you to display a message
file to users whose logins are rejected, telling them why the system is not
available.


FILES		Narrative					Location
---------------------------------------------------------------------------
LOGIN.EXE	Replacement for Novell login.exe		SYS:LOGIN
LOCKOUT.EXE	Program to enable/disable logins.		SYS:SYSTEM
LOCKOUT.CFG	Pathname for login (default = F:\LOGIN)		SYS:LOGIN
LOCKOUT.MSG	Message shown to the user if login is rejected.	SYS:LOGIN


INSTALLATION
---------------------------------------------------------------------------
1.	Disable logins at the console.
2.	Rename sys:login\login.exe to xlogin.exe and make it hidden.
3.	Copy the new login.exe to the sys:login directory. Flag read-only!
4.	Copy the lockout program to the sys:system directory
5.	Create the file LOCKOUT.CFG in the SYS:LOGIN directory containing the
	full pathname of the login directory USING A DRIVE LETTER! The default
	if no LOCKOUT.CFG file is used is F:\LOGIN
6.	Enable logins at the console.


MISCELLANEOUS NOTES
---------------------------------------------------------------------------
1.	You MUST have console_operator rights to run the lockout program.
	(Imagine a user getting his hands on this ;-)
2.	SUPERVISOR always has access to the system.
3.	Tested on 2 Novell 3.11 100 User systems so far.
4.	Remember - this is an experimental copy. It is not intended to a
	flawless super-security program - it's just useful.

                              - END -