EPIC4 Version 1.0.1 (VMS Edition) Release Notes
                    and Installation Instructions
              -------------------------------------------
                   Preview Release #2: 10-MAY-2003
                      --------------------------

This is the third version of the release notes for PR #2.  The only change
in this version is documentation on using the self-extracting BACKUP
archive.
            
1. Installation.
1.1. Distribution.

  This release of EPIC4 consists of one file:

	Name:     EPIC4-1_0_1-VMS-PR2-10-MAY-2003.AXP_EXE
	Size:     957408 bytes, 1870 blocks
	MD5:      0b9f62f540242ab4cdb5b112e5317594
	CHECKSUM: 2362461731

  This file may be downloaded from:

	<http://www.2mbit.com/~larne/>

1.1. Installation requirements.
    
  Compilation of EPIC4 from source code requires a C compiler and either the
  MMK or MMS build systems.  This release of EPIC4 has been tested using MMK
  with DEC C V6.0-001 on OpenVMS Alpha V7.2.  The installation requires 
  approximately 2,300 blocks of free disk space.  SYSTEM access is desirable
  but not required for the installation.  The GPG utility is required to
  verify the integrity of the source archive.

1.2. Installation procedure.

  1) Run the self-extracting archive:

	$ RUN EPIC4-1_0_1-VMS-PR2-10-MAY-2003.AXP_EXE

     This files EPIC4-1_0_1-VMS-PR2-10-MAY-2003.BCK and EPIC4-1_0_1-VMS-PR2-10-MAY-2003_BCK.SIG
     should be created.

  2) (Optional) Verify the integrity of the source archive.
     The source archive has been signed with the following key:

	pub  1024D/9DE23F15 2003-05-10 Edward Brocklesby <ejb@lythe.org.uk>
	Fingerprint=8AD6 2E2F 0A7A 7B3E 1336 F996 303F CD50 9DE2 3F1

     This key may be obtained from the key server with the following command:

	$ gpg --keyserver wwwkeys.pgp.net --recv-keys 9DE23F15

     Use the following command to verify the integrity of the archive:

	$ gpg --verify EPIC4-1_0_1-VMS-PR2-10-MAY-2003_BCK.SIG EPIC4-1_0_1-VMS-PR2-10-MAY-2003.BCK

      The output should be similar to the following:

	gpg: Signature made Fri May  9 21:48:43 2003 EST using DSA key ID 9DE23F15
	gpg: Good signature from "Edward Brocklesby <ejb@lythe.org.uk>"

  3) Execute the following command to extract the source archive:

	$ SET FILE/ATTRIBUTES=LRL=32256 EPIC4-1_0_1-VMS-PR2-10-MAY-2003.BCK
	$ BACKUP/LOG EPIC4-1_0_1-VMS-PR2-10-MAY-2003.BCK/SAVE_SET []

      The directory [.EPIC4-1_0_1] will be created.

  4) Change the default directory to the top-level EPIC directory:

	$ SET DEFAULT [.EPIC4-1_0_1]

  5) Execute the following command to begin the installation:

	$ @INSTALL

     The installation procedure will ask you the following questions
     during the build:

	* Continue with build [Y/n] ?
	  Enter 'y' to build and install EPIC, or 'n' to abort the installation
	  procedure.

	* Build system [MMS/MMK] ?
	  Enter the name of the build system (either MMS or MMK) that should be
	  used to build the EPIC binary.

	* Location for installed file?
	  Enter the full path to the top-level directory into which EPIC
	  should be installed; for example DISK$SOFTWARE:[EPIC].  This
	  directory does not have to exist.
	  Any %CREATE-I-EXISTS messages during this part of the installation
	  may be ignored.

	* Install CLD into system DCLTABLES [Y/n]?
	  If EPIC is being installed as the SYSTEM user, it is preferable
	  to install EPIC's Command Definition files into the system
	  DCL tables, to enable all users to run the EPIC program without
	  any per-user configuration.  If this is the case, answer 'y'
	  to this question.  If EPIC is not being installed as the SYSTEM
	  user, or installing EPIC's Command Defintions into the system DCL
	  tables is not desired, answer 'n' to this question.  The installation
	  will then ask the following question:

	* Add these lines to SYS$LOGIN:LOGIN.COM now [Y/n]?
	  (This question is only prompted if the previous question was answered
	   with 'n')

	  If EPIC should add commands required to run to the user's LOGIN.COM
	  file, so that they will be executed on login, answer 'y' to this
	  question.

  Installation of the EPIC4 client should now be complete.

2. Support.
  Support for the EPIC4 client may be obtained from the author, either via
  email to <ejb@lythe.org.uk>, or via IRC (nick "larne").

  A brief summary of options may be obtained by running "EPIC/HELP".

  PLEASE NOTE: The VMS release of the EPIC4 IRC client is NOT supported
  by the epicsol group, and requests for support should NOT be directed to
  them.

3. Known bugs, missing features and miscellaneous notes.

3.1. /LOAD
  The /LOAD command has been modified to correctly support VMS-style pathnames.
  The /SET LOAD_PATH variable has been changed to use "," as a delemiter, instead
  of ":" as on Unix (observe that ":" is a possible character in a VMS pathname).

3.2. Paths containing ~/
  EPIC will not currently handle a path which begins with "~/" correctly.  The most
  likely result from using such a path is that EPIC will construct an invalid pathname
  and the operation with fail.

3.3. Other filesystem functions.
  No other built-in functions relating to filenames have been modified in this release
  of EPIC.  It is likely that some will not function correctly without further
  modification;  any such problems should be reported to the author.

3.4. Command line arguments.
  EPIC has been modified to use VMS-style command line arguments in favour of Unix
  "getopt()"-style flags.  Note that because of this, EPIC may not be invoke as
  a DCL foreign command;  its CLD *must* be installed into DCL.

4. Modification history.

  EPIC4 1.0.1 PR2:
	- Apply a fix from upstream EPIC for a security vulnerability
	  relating to CTCP handling.

	- Add "Known bugs" section to release notes.

	- No other changes.

  EPIC4 1.0.1 PR1:
	Initial release.

Edward Brocklesby,
10 May 2003.