EPICSERVER and EPICCLIENT - Version 1.05,   July 2000
========================================================
Network interface for multiple EPIC-equipped PCs under
Windows 95 or Windows 98.

=======================================================
FREEWARE by Pete Dowson

DISTRIBUTION: Free distribution is allowed without
prior permission of the author. Please take this note
to be your written permission to upload it to your
favourite site. The author's only "home" sites are
FSFORUM and SIMPILOT on CompuServe. Look there for
the latest version, or on Enrico Schiratti's web site
(www.schiratti.com).

=======================================================

For HISTORY of changes, please see the END of this
document.

Needed:

*  Two or more PC's running Win95/98, with EPIC cards
	installed.
*  EPIC95 already installed for Windows EPIC operation.
*  Local Area Network, with IPX/SPX protocol enabled.
	(You can use a Direct Cable Connection as well).


Files provided:

   EpicClient.Exe
     This program runs on 'client' PCs equipped with EPIC.
	 There can be more than one such PC on the network.
   EpicClient.Txt
     An explanation of the parameters which can be used in
	 controlling EpicClient via its Ini file.
   EpicServer.Exe
     This program runs on the one PC equipped with EPIC
	 which is selected to be the 'server', the centre of
	 control and normally the one running the main
	 simulation program.
   EpicServer.Txt
     An explanation of the parameters which can be used in
	 controlling EpicServer via its Ini file.
   EPIC.VxD
     This is version 5.31 of the Epic.Vxd issued normally
	 in my EPIC95 package. At least version 5.01 is needed
	 for EpicLink operations.
   EPIC95.doc
     The updated version of the Epic.VxD documentation, for
	 version 5.31.
   EpicVxd.inc
	 Revised #include file for use in EPL, containing definitions
	 of new inter-EPIC communications Enque16s, and also a button
	 Toggle command (new to 5.11 but not specific to EpicLink).
   IsEpic95.exe
     An updated version with additional facilities,
	 particularly the ability to capture Enque16, PH and QP
	 values using the same facilities as EpicLink.
   

Installation:

[N.B. UNPACK with a long-filename aware program, such as WinZip or
      ZipMagic. Do NOT use PKUNZIP!]


ON all EPIC-equipped PCs
========================

If you have not previously installed my EPIC95 package, you'll need
to do so first. EPIC95.Zip is available on the EPIC website, on
www.schiratti.com, and in FSFORUM and SIMPILOT fora on CompuServe.

Replace the EPIC.VxD in your Windows\System folder with the version
provided in this package.

Re-boot Windows.


ON the PC which is to be the 'Server'
=====================================

Place EpicServer.exe into a folder of your choice. Drag a shortcut to
it and place it somewhere convenient. 

If you want the EpicLink to be ready to operate at any time, whilst
you have Windows loaded, move this shortcut into the "StartUp" folder
in the 'Start'-'Programs' part of Windows. It will then run automatically
when you load Windows. It will do no harm sitting there in the background.
An icon ("ES") will appear in the Tray (where the clock is, normally). You
can right-click on this to get an option to terminate EpicServer, but
normally there's no need to ever do this.


ON the PCs which are to be 'Clients'
====================================

Place EpicClient.exe into a folder of your choice. Drag a shortcut to
it and place it somewhere convenient. 

If you want the EpicLink to be ready to operate at any time, whilst
you have Windows loaded, move this shortcut into the "StartUp" folder
in the 'Start'-'Programs' part of Windows. It will then run automatically
when you load Windows. It will do no harm sitting there in the background.
An icon ("EC") will appear in the Tray (where the clock is, normally). You
can right-click on this to get an option to terminate EpicClient, but
normally there's no need to ever do this.


Running the System
==================

The IPX/SPX protocol must be installed on all participating Win95/98
machines.

The link is automatic. EpicLink transfers selected QProc, Pigeon Hole and
Enque16 events between the Server and all Clients, and between each Client
and the Server.

For FS98, you should now find that you can actually re-connect hardware
from the Server EPIC to the Client EPIC, load up the *same* EPL in both,
and everything should still work fine. Now you can start optimising the
EPL in each machine to suit whatever is connected to it. This way I 
succeeded in getting twice as much connected and operating with FS98
than was possible before.

For more sophisticated operation, however, you'll want to get the EPL's
in the separate machines communicating. This is done with new facilities in
the Epic.vxd (and #defined in the EpicVxD.inc file provided):

	SendPH0-3, sends the 16-bit value to other Epic's PH96-99.
	SendQP0-9, activates QP190-199 in other Epic.

This always operates Server to ALL Clients, or any Client to the Server.
Different clients cannot talk to each other, only via the Server.

There will be an ini file produced by both EpicClient and EpicServer.
Sections can be added to the ini files to allow complete configuration
of the data being exchanged. For full details of this, please see
the EpicServer.txt and EpicClient.txt files enclosed.


=======================================================================

Support
=======

If you have any questions you may contact me on:

	CIS: 100041,312
	Internet: pete@millhays.demon.co.uk
	
=======================================================================


ADDENDUM: HISTORY
=================

Version 1.03 changes:
=====================

None. This is the first Released version.


Version 1.04 changes:
=====================

Added "OffXPovN" set of POV commands to logging capability,
defaulted the EpicClient POV action to include relaying
these to the Server. (OffXPovN uses Enque16's 0x360-f and
this command is supported in Epic.vxd version 5.31 and
later).


Version 1.05 changes:
=====================

Added facilities for a user-written program to send QPs and
PHs from a Client PC to the Server. The client need not even
be equipped with an EPIC. See the enclosed document

	ClientInterface.txt

for details. Note that this is *only* for programmers who
are familiar with Windows programming!
 
============================================================

Pete Dowson,
Stoke-on-Trent
ENGLAND

5th July 2000
============================================================
