Dear Wollongong Customer,

This file describes the new PathWay for DOS/Windows patch procedures 
introduced with PathWay Runtime 2.0, PathWay Access 3.0, and PathWay 
API 2.0.


GENERAL
=======
Between major releases, Wollongong sometimes generates software 
changes to the shipping product in order to correct specific problems
discovered with the software.  Initially, a "test fix" is generated;
this may be an actual fix to the software, or it may be a "debug"
module intended to test a certain hypothesis.  Once it is verified
that a particular test fix corrects the specific problem for which
it was designed, (oftentimes based on customer feedback), a "patch"
is generated.  Each patch generated is made available to our customers.


PATCH PROCEDURE FOR PATHWAY ACCESS 3.0, RUNTIME 2.0 and API 2.0
===============================================================
Previously, patches were made to each PathWay module (file) as necessary.
The modules were then made available to customers as separate entities;
i.e., different modules were not combined together, although, where several 
different patches were made to the same module, each newer version 
of the module included all the previous change(s) made to that module.  
However, there was no way to distinguish (except by date and size) which 
version of a module was installed on a given system.  It is for these 
reasons that a new patch procedure has been introduced.

NOTE:  The procedures outlined in this document assume that you are using
       Wollongong's PathWay Runtime (as opposed to another vendor's network
       transport with Windows Sockets version 1.1 support), and that you have 
       installed all of your PathWay products in the SAME directory.  If you 
       are not using Wollongong's PathWay Runtime, or you have not installed 
       all your PathWay products in the same directory, please contact 
       Wollongong's Product Support Department via telephone at 415-962-7140, 
       or fax at 415-969-5547, or e-mail to support@twg.com.

Patch Files
===========
With this release, patches are no longer standalone modules; they are 
bundled together by their respective diskette. For example, all modifications
made to modules contained on the PathWay Runtime "Drivers" diskette since 
the release of the current shipping product will be distributed in one 
self-extracting file named "pchdrv.exe". 

Therefore, at any one time, customers may apply all of the most current 
PathWay modules to their base line product by downloading all the
self-extracting files, and installing them using the installation script 
provided with PathWay Runtime, described later in this document.  This script, 
PWPATCH.BAT, and a file named PWVER.EXE, are both distributed as part of the 
PathWay Runtime product.  They are located on the PathWay Runtime Setup 
diskette, and thereby placed in the PATHWAY directory during the installation 
of this product.  Both files have been provided as part of this new patch 
procedure.

All self-extracting patch files are available on Wollongong's Bulletin Board
Service (BBS), but are individually passworded.  If you do not have a password, 
or, you receive a "Warning! Incorrect password for file:" message when running 
the installation script, please log a call with Wollongong's Product Support 
Department via telephone at 415-962-7140, or fax at 415-969-5547, or e-mail to 
support@twg.com.

The BBS also contains text files which describe the patches that have been
made to PathWay Runtime, Access, and API.  These descriptions are contained
in the files "run-fixes.txt", "acc-fixes.txt", and "api-fixes.txt" for
Runtime, Access, and API respectively.  If you experience problems locating
these text files, please contact Wollongong's Product Support Department.

Verifying Whether Patches have been Applied
===========================================
In order to verify whether your system is running the most up-to-date
versions of all PathWay modules, a file named "pwver.dat" must be down-
loaded from our BBS.  This file is located in both the "PC DOS/Windows File 
Area (#3)" on Wollongong's BBS, and in the ANONYMOUS FTP "pub/dos" directory.  
This file can be downloaded as follows:

1.  Connect to Wollongong's BBS; the BBS may be accessed via modem at
    415-965-3601 (login:bbs), or, via ANONYMOUS FTP to bbs.twg.com 
    (149.38.1.9).  For details on setting up an account on our BBS when 
    accessing it via modem, please refer to the chapter in your Support 
    Services User Guide, "Other Support Services".  This guide is located in 
    your PathWay documentation binder.

2.  When successfully connected to the BBS, please perform one of the following:

    If you are using ANONYMOUS FTP, issue these commands:

	a.  ftp> cd pub/dos
	b.  ftp> get pwver.dat (Please note that this filename must be 
	         specified in lowercase.)
	Skip to Step 3.

    If you are using a modem, issue these commands (from the specified 
    locations):

	a.  From the MAIN: menu, select <F>ILE
	b.  From the FILE: menu, select <3>
	c.  From the DOS/Windows FILE: menu, select <P>rotocol
	d.  When prompted for Protocol, enter the protocol that you wish to
            use; it must be one of the following: X/Y/ZModem, or Kermit.
	e.  From the DOS/Windows FILE: menu, select <S>end
	f.  When prompted for the file to download, enter: pwver.dat (Please
	    note that this filename must be specified in lowercase.)
	g.  Finally, when prompted for, enter the specific local command to 
	    tell your PC to accept this file.

3.  After pwver.dat has been obtained, log out/disconnect from the BBS, and
    perform the following steps:

	a.  Copy PWVER.DAT to your PATHWAY directory, or the directory 
	    containing your PathWay software.
	b.  Change to your PATHWAY directory, or the directory containing your 
	    PathWay software.
	c.  Execute the following command:

	    C:\PATHWAY> PWVER *.* /c PWVER.DAT
	Where,
	    C:\PATHWAY is the location of your PathWay software,
	    /c is the "compare" parameter,
	    PWVER.DAT is the most current version identification file from our
	              BBS.

	If the output from executing this command resembles the following 
	example:

	    PWTCP.EXE
                    2.00.00 FCS
                    2.00.00 Patch 4, Does not compare

	    Found 1 file(s) with different versions

	this means that the file PWTCP.EXE on your system is not the latest
	version available from Wollongong; the version on your system is 
	2.00.00 FCS and the version available from Wollongong is 2.00.00 
	Patch 4.  Each file in your PATHWAY directory that is not the latest 
	version available from Wollongong will be identified.

	If all files in your PATHWAY directory are up-to-date, the output from 
	the above command ("C:\PATHWAY> PWVER *.* /c PWVER.DAT") will resemble 
	the following:

	    Found 0 file(s) with different versions.

Downloading/Installing Patches
==============================
After you have determined which file(s) you need, locate which diskette(s) 
these files where originally distributed on.  For your reference, the following 
files (located in your PATHWAY directory) contain a listing of the contents of 
each media: README.RUN (Runtime), README.ACC (Access), and README.API (API).  
Based on the diskettes that you identify, you should download the appropriate 
self-extracting file(s) from our BBS, and install it/them on your system.

For your reference, following is a list of all the available self-extracting 
file names, with their corresponding diskette label:

	pchrun.exe      PathWay Runtime "SETUP"
        pchdrv.exe      PathWay Runtime "DRIVERS"
        pchaccd.exe     PathWay Access for "DOS"
        pchaccw1.exe    PathWay Access for "WINDOWS" (Diskette 1)
        pchaccw2.exe    PathWay Access for "WINDOWS" (Diskette 2)
        pchaccw3.exe    PathWay Access for "WINDOWS" (Diskette 3)
        pchapi.exe      PathWay API (all diskettes - Windows Sockets, Berkeley
                        Sockets (Microsoft C/C++), Berkeley Sockets (Borland
                        C++), MAPI/Telnet/FTP)  

Download and install the appropriate patch files as follows:

1.  Connect to Wollongong's BBS via modem or via ANONYMOUS FTP (as described
    previously).

2.  When successfully connected to the BBS, please perform one of the 
    following:

    If you are using ANONYMOUS FTP, issue these commands:

	a.  ftp> cd pub/dos
	b.  ftp> ls     

    (You will see the pwver.dat file, the text files (run-fixes.txt,
    acc-fixes.txt, and api-fixes.txt), and the self-extracting executables 
    (pchrun.exe, pchdrv.exe, pchaccd.exe, pchaccw1.exe, pchaccw2.exe,
    pchaccw3.exe, pchapi.exe.)

	c.  ftp> binary
	d.  ftp> get filename (For each self-extracting file that you wish to
	         obtain.)
	Skip to Step 3.

    If you are using a modem, issue these commands (from the specified
    locations):

	a.  From the MAIN: menu, select <F>ile
	b.  From the FILE: menu, select <3>

    Within this directory location, you will see the pwver.dat file, the text
    files (run-fixes.txt, acc-fixes.txt, api-fixes.txt), and the following 
    directories:

	run-fixes    <DIR>    dd-mmm-yy    Fixes area for Runtime 2.0
	acc-fixes    <DIR>    dd-mmm-yy    Fixes area for Access 3.0
	api-fixes    <DIR>    dd-mmm-yy    Fixes area for API 2.0

    The "run-fixes" directory contains the following files:
	pchrun.exe
	pchdrv.exe

    The "acc-fixes" directory contains the following files:
	pchaccd.exe
	pchaccw1.exe
	pchaccw2.exe
	pchaccw3.exe

    The "api-fixes" directory contains the following files:
	pchapi.exe

	c.  From the DOS/Windows FILE: menu, select <D>irectory
	d.  When prompted for, enter the name of the directory that you wish to
            change to.  (Please note that this directory name must be specified 
	    in lowercase.)
	e.  From the DOS/Windows(/directory) FILE: menu, select <P>rotocol
        f.  When prompted for Protocol, enter the protocol that you wish to
            use; it must be one of the following: X/Y/ZModem, or Kermit.
        g.  From the DOS/Windows FILE(/directory): menu, select <S>end
        h.  When prompted for the file to download, enter the appropriate name
	    of the required self-extracting file.  (Please note that this 
	    filename must be specified in lowercase.)
        g.  Finally, when prompted for, enter the specific local command to
	    tell your PC to accept this file.

3.  Once you have completed your download, log out/disconnect from the BBS.

4.  Copy the file(s) that you have downloaded to your PATHWAY directory, or the
    directory that contains your PathWay software.

5.  Change to your PATHWAY directory, or the directory that contains your 
    PathWay software.  

6.  Before installing the downloaded patch files, make sure that you are NOT 
    currently using any of the PathWay applications.
  
7.  If you have downloaded either pchrun.exe or pchdrv.exe, you must remove 
    your PathWay kernel (and network driver, if appropriate) BEFORE installing 
    the patch file.  Use the "PWTCPRM" command (and "-a" option if appropriate).
    For information on unloading your kernel and drivers, please refer to
    your PathWay Runtime User Guide.

8.  At this point, you should enter the following command against each 
    self-extracting module which was downloaded:

	PWPATCH.BAT name_of_file.EXE password_for_name_of_file
    
    THE PWPATCH.BAT PROGRAM WILL ONLY WORK CORRECTLY IF IT IS LOCATED AND RUN 
    FROM YOUR PATHWAY DIRECTORY, OR THE DIRECTORY THAT CONTAINS YOUR PATHWAY 
    SOFTWARE.
 
    PWPATCH.BAT will perform the following:

	a.  Create a temporary directory called TMP_PTCH in your current 
	    directory.
	b.  Create a directory called P_BACKUP in your current directory.
	c.  Change directory to the .\TMP_PTCH directory.
	d.  Copy ..\name_of_file.EXE to the TMP_PTCH (current) directory.
	e.  Explode name_of_file.EXE with password_for_name_of_file.EXE.
	f.  Copy your original files (that will be replaced by the files 
	    contained in name_of_file.EXE) to ..\P_BACKUP.
	g.  Copy the exploded files in the TMP_PTCH directory to the ".." 
	    directory.
	h.  Delete the contents of the TMP_PTCH directory.
	i.  Change directory to the ".." directory.
	j.  Delete the TMP_PTCH directory.
	k.  Execute the "PWVER *.* /c PWVER.DAT" command to verify that your 
	    current installation is now up-to-date.

9.  If you installed either PCHRUN.EXE or PCHDRV.EXE, you must now reload your
    PathWay kernel (and network driver, if appropriate), using the "PWTCP" 
    command.  Reloading your network driver will require you to run PWCONFIG,
    and, dependent on which driver you are using, various other commands.  Or,
    you may simply reboot your PC.  For information on reloading your kernel 
    and drivers, please refer to your PathWay Runtime User Guide.
      
If you require assistance at any time, please contact Wollongong's Product
Support Department via telephone at 415-962-7140, or fax at 415-969-5547, or
e-mail to support@twg.com.


Sincerely,

Product Support Department
The Wollongong Group, Inc.
