                              DRLOGIN V3.5
                              August 4, 2023

	  V3.5 - Ported to run on OpenVMS x86_64. Removed usage of several
		 builtins.

	  V3.4-1 - Includes a fix for exit messages on I64.
	  V3.4 - Includes a couple of minor aesthetic changes.

	  Ported to OpenVMS I64 by Hunter Goatley <goathunter@goatley.com>
	  Only a couple of simple changes were needed for clean compilation.

                            February 3, 1995
          Reimplemented by John Delgado, <j_delgado@farber.harvard.edu>
                      Dana-Farber Cancer Institute
	  Additional work by Lou Bergandi <bergandi@cpva.saic.com>

          Ported to OpenVMS AXP by Hunter Goatley <goathunter@WKUVX1.WKU.EDU>
                      Western Kentucky University

          Originally written by Anthony C. McCracken, <ACM@NAUVAX.BITNET>
                     Northern Arizona University
          with mods by Hunter Goatley <goathunter@WKUVX1.BITNET>

DRLOGIN allows remote interactive login over DECnet, providing similar
functionality to the RLOGIN TCP/IP utility. DRLOGIN uses non-transparent
task-to-task DECnet communication to establish a link to a remote task
which runs the DRLACP image. DRLACP uses the FT pseudo-terminal driver
introduced with VMS V5.4 to create an interactive process on the remote 
node.

With version 3.0, DRLOGIN and DRLACP were rewritten in C from the original
MACRO-32 implementation. DRLACP is also based more on LOGGER.C, a session
logging facility written by Forrest A. Kenney, Digital Equipment Corporation,
as an example demostrating the use of a pseudo terminal, than on the original
DRLACP implementation.

To use DRLOGIN, DRLACP.COM must be modified to point to the DRLACP.EXE
image.  Both files should be copied to the appropriate directories on the
remote DECnet node.  A DECnet object must be defined for DRLACP on the
remote node using commands like the following:

	$ MCR NCP
	NCP> DEFINE OBJECT DRLACP FILE DRLACP.COM NUMBER 0
	NCP> SET OBJECT DRLACP FILE DRLACP.COM NUMBER 0
	NCP> EXIT
	$

To establish the remote login, just define a symbol on the local node:

	$ drlogin :== $dev:[dir]drlogin.exe

Any account having a DECnet proxy on a remote node can log in using:

	$ drlogin node

where "node" is the remote DECnet node name.

If proxies are not enabled, you can log in to the remote node using:

	$ drlogin node"user *"

When "*" is specified as the password, DRLOGIN prompts you for the actual
password.
