New Engine (v2.01) File Suite
-----------------------------

ENGV201S.ZIP

Back up \WGSERV\MAJORBBS.EXE.  Then, unzip this .ZIP, overwriting
MAJORBBS.EXE.

ENGV201C.ZIP

Have user back up \WINDOWS\SYSTEM\GCSPCLI.DLL.  Then, have him unzip this
new .DLL over it.

Usage

Create a file in your main server directory: GALDLINK.OPT.  Put in it one
line:  the channel number to monitor.  (This is the hex channel number as
it appears on the main console.)  When the server is brought up with this
file properly set up, it will confirm that it is set to log interactions on
that channel.  This means that any C/S user who connects on that channel
will have all data (in and out) logged to GALDLINK.LOG (in the main server
directory).  If that user has the new .DLL installed (above), his client
will also log all data (as it sees it) into GALDLINK.LOG in his main
Worldgroup Manager directory.  This is the best set-up, allowing both the
client and server ends of the link to be logged.

The ideal use of this package...  Install ENGV201S.ZIP on the server.  Have
the user install ENGV201C.ZIP.  Create GALDLINK.OPT with a particular
channel number.  Bring the server up.  Have the user immediately connect on
that channel.  Have the user replicate the problem.  Bring the server down.
Delete GALDLINK.OPT.  Collect GALDLINK.LOG from both the server and the
client and e-mail to your tech support contact with information on what
problem showed itself during the test.  Given what went wrong and how, the
log files should shed more light on what's going on.
