PATHWORKS V1.0A for Windows 95 Release Notes
14-Nov-1995

Contents
--------

    Required Hardware and Software
    Pre-Installation Steps
    Installation
    Post-Installation Steps
    PATHWORKS V1.0A Changes
    Additional Information
    Notes, Problems and Limitations
    Licensing and LAT Advanced Settings
    Programming Information

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

Required Hardware and Software
------------------------------

PATHWORKS V1.0A for Windows 95 requires the following minimum hardware and
software configuration:

    o 80386DX 25MHz PC with 8MB of memory and 10MB available disk space

    o Microsoft Windows 95 Final Release

    o Windows 95 Supported Ethernet, Token Ring or FDDI Adapter and Driver

    o A PATHWORKS V6.0 for DOS and Windows License
    
Ethernet and FDDI adapters must support a software-configurable network
address using the NetworkAddress keyword or you will be unable to use
DECnet.

Pre-Installation Steps
----------------------

*****************************************************************************
*                                                                           *
*   IMPORTANT: If you installed PATHWORKS for Windows 95 in an existing     *
*   PATHWORKS for DOS and Windows directory, SETUP will delete files that   *
*   do not work with Windows 95.  If you are running a multi-boot           *
*   configuration, you should install PATHWORKS for Windows 95 in a         *
*   different directory.                                                    *
*                                                                           *
*   IMPORTANT: If you installed a beta release of PATHWORKS for Windows     *
*   95 and you are already running SETUP, you must cancel SETUP and run     *
*   SETUP with the /FORCENEW option to perform a clean installation.        *
*                                                                           *
*****************************************************************************

If you are using DECnet, you should know your DECnet node name and
address before beginning installation.  To keep the DECnet databases from
previous PATHWORKS installations, copy the PW*.DAT files to your new
PATHWORKS directory after you run SETUP.

Installation
------------

Use the SETUP utility install the PATHWORKS for Windows 95 release.

    1.  Run SETUP from the root directory of the kit.  If you have not
        disabled the AutoRun capability, SETUP will be started
        automatically when you insert the CD-ROM.

    2.  Reboot after running SETUP.

Post-Installation Steps
-----------------------

PATHWORKS can only be used on a single network adapter.  If you are using
a configuration with multiple network adapters, you should verify the
adapter bindings:

    1.  Start the Network Control Panel:

        Start->Settings->Control Panel->Network

    2.  Verify the 'PATHWORKS NDIS Support' protocol is bound to the
        correct adapter.  If you have multiple adapters and need to
        change the bindings for PATHWORKS, see the section 'Changing the
        Adapter Binding' below.

PATHWORKS V1.0A Changes
-----------------------

The following list summarizes some of the differences between PATHWORKS
V1.0 for Windows 95 and PATHWORKS V1.0A for Windows 95.

    New support for native FDDI NDIS 3.1 drivers
    New support for upgrading from PATHWORKS V6.0 for DOS and Windows
    New support for PATHWORKS V6.0 client licenses
    New NFTW, FALW and VT320 equivalent to the PATHWORKS V6.0 versions
    Improved performance copying nodes with DECnet "Other Nodes" property page
    Fixed PATHWORKS licensing support with Microsoft TCP/IP
    Fixed occasional idle DECnet links with DECnet applications
    Fixed GPF with VT320 CTERM sessions and international characters
    Fixed problems reconnecting to LAT password-protected services
    Fixed maximum LAT sessions to be accurate (previously was one less)
    Fixed several compatibility problems with 32-bit programming libraries
    Fixed aging of LAT preferred services that may cause them to be removed

Additional Information
----------------------

The following information is in addition to the information included in
the online documentation and help.

o   DECnet Wide Area Name Resolution

    DECnet will automatically resolve names of file and print servers
    that are outside the local area network.  A PATHWORKS 4.x or 5.x
    server must be present in the LAN.  If the client cannot resolve the
    name on the LAN, PATHWORKS servers will resolve the address out of
    their DECnet node databases.  This eliminates the need to define
    nodes with the MS-NET flag in many cases.
    
    If you need to specify the MS-NET flag, you must use NCP DEFINE
    NODE.  The DECnet properties do not allow you to set this flag.

o   Using an Alternate Port with TELNET

    TELNET support is provided via the Terminal Access Library and will
    work with a Windows Sockets-compliant TCP/IP implementation.  You may
    specify a port number to use when making a TELNET connection with
    VT320.  You do so by entering both the service name and the port
    number you wish to use in the Service Name edit box in the
    Communications Setup.  Separate the service and port number with a
    space.  For example, enter:
            
            MYNODE 23
    
    in the Service Name edit box to allow VT320 to connect to node MYNODE
    using port 23.  

o   NCP Does Not Support V4.1 Database Files

    The NCP utility and the DECnet property page do not support the
    PATHWORKS V4.x database files (DECNODE.DAT and DECALIAS.DAT).  Note
    that this may cause problems with DECnet applications designed to
    work with PATHWORKS V4.x, such as Digital eXcursion V1.1.
    
    A conversion utility, NM_5TO4, is available on the PATHWORKS
    Unsupported Kit.  See the enclosed flyer on PATHWORKS utilities for
    additional information.

o   DOS PATH Environment Variable

    The PATHWORKS directory is inserted at the front of the PATH.  If you
    want to change the location of the PATHWORKS directory in the PATH --
    for example, to make it the last entry in the PATH -- then update the
    PATH statement in AUTOEXEC.BAT.  When PATHWORKS starts, it will not
    replace or change an existing entry in the PATH.

o   NetWare Client Licensing

    This release includes support for NetWare client licensing that
    allows the Microsoft Client for NetWare Networks to access PATHWORKS
    NetWare servers.  To enable this, you must have selected the
    Licensing Agents with SETUP (if you used a custom installation) and
    should have added the Client for NetWare Networks with the Network
    Control Panel.  To enable NetWare licensing:

    1.  Invoke the Network Control Panel:

        Start->Settings->Control Panel->Network

    2.  Add the PATHWORKS licensing agent:

        Add->Service->Add->Digital Equipment->
            PATHWORKS Licensing Agent (NetWare)

    3.  Shut down and restart the system.

Notes, Problems and Limitations
-------------------------------

Diagnostic and debugging information is displayed in the PATHWORKS event
log.  If you have problems, first examine the event log using:

    Start->Programs->PATHWORKS->Event Log Viewer

Most of these error messages are documented in 'PATHWORKS for Windows 95
Client Messages' on the Information Shelf, which provides a more complete
description of the error as well as steps to take to correct it.

o   DNP0055: Cannot start DECnet: adapter's network address is not set
    to AA-00-04-00-xx-yy.

    This message is displayed if the address of the network adapter is
    not set to the correct value.  The value is set by SETUP using the
    NetworkAddress keyword in the registry and should be supported with
    NDIS 3.1 drivers that have a software-configurable station address.

    However, some drivers included with Windows 95 do not support this
    feature and may not work with PATHWORKS.  There are several possible
    workarounds to this limitation:
    
    o   Contact the vendor and request an updated driver that supports
        the NetworkAddress keyword or uses the NdisReadNetworkAddress
        function to determine the station address.

    o   If you have an NDIS V2.0 (16-bit) driver available, you can use
        the Network Address Driver from the PATHWORKS Unsupported Kit
        to configure the station address correctly using the NDIS V2.0
        driver.  
    
    o   If you have an ODI (16-bit) driver available that supports the
        NODE ADDRESS keyword, you can configure your system to use this
        driver using the Network Control Panel.
        
    Note that many NDIS V2.0 and ODI drivers are included on the PATHWORKS
    for DOS and Windows V5.x CD-ROM in the \NETWARE\DRIVERS and \LMDOS
    \DRIVERS directories.

o   Changing the Adapter Binding

    If you have multiple network adapters, SETUP will bind PATHWORKS
    protocols to the first Ethernet, Token Ring or FDDI adapter on the
    system.  If this is not the adapter you want to use PATHWORKS
    protocols on, you must change the adapter bindings as follows:

    1.  Start the Network Control Panel:

        Start->Settings->Control Panel->Network

    2.  Select the adapter where the 'PATHWORKS NDIS Support' is
        currently bound.
        
    3.  Remove 'PATHWORKS NDIS Support' from the bindings:

        Properties->Bindings, uncheck 'PATHWORKS NDIS Support'

    4.  Select the adapter where you want PATHWORKS protocols used.
    
    5.  Add 'PATHWORKS NDIS Support' to the bindings:

        Properties->Bindings, check 'PATHWORKS NDIS Support'
        
    6.  Choose OK and reboot the system when requested.

o   ODI Configurations

    The first time you install an ODI driver using the Network Control
    Panel, the NET.CFG file does not have the proper NODE ADDRESS
    setting.  Complete the installation of the driver and reboot to have
    the changes take effect.  Then run SETUP to update the NET.CFG.

o   SETUP Does Not Automatically Remove Licensing Agent (LAN Manager)

    This procedure is only necessary if you choose to stop using the
    licensing agent after installing it.

    The PATHWORKS Licensing Agent (LAN Manager) will not be removed from
    the Network Control Panel by SETUP even if the user deselects it in a
    custom mode install.  Use the following method to remove the
    licensing agent software from the Network Control Panel:

    1.  Start the Network Control Panel:

        Start->Settings->Control Panel->Network

    2.  Select PATHWORKS Licensing Agent (LAN Manager).

    3.  Choose Remove.

    4.  Choose OK.

    5.  Shut down and restart Windows 95.

o   NetWare Client Licensing

    Unlike the LAN Manager license agent, the NetWare license agent does
    not report errors to the PATHWORKS event log.  If you suspect a
    problem with the NetWare licensing components, you must edit
    WINSTART.BAT and add a PAUSE command after the PWLICNW.EXE command.

o   DECnet Performance Problems Between Fast and Slow Systems

    If you perform file transfers between two PATHWORKS for Windows 95
    clients that are mismatched in performance (a Pentium client and
    an 80386 client, for example), you may experience some performance
    problems.  This is particularly evident if the slower client is
    on a Token Ring network and the faster system is on Ethernet.

    To improve performance on these systems, reduce the receive pipe
    quota to 3 or less with the NCP DEFINE EXEC RECEIVE PIPE QUOTA
    command.

    Similarly, if you use NFT on a slow machine and FAL on a fast
    machine, NFT may leave an idle network link when it exits.  These
    idle links can be displayed with the NCP SHOW KNOWN LINKS command
    and deleted with the NCP SET LINK 'n' STATE OFF command.

o   VT320, NFTW and FALW Do Not Support Long File Names

    VT320 and the DECnet file transfer utilities NFTW and FALW do not
    support Windows 95 long file names.  With NFTW, long file names must
    be manually shortened to 8.3 format during copy operations.  With
    FALW, long file names are automatically shortened.

o   VT320 and NFTW and Tutorial References

    Both VT320 and NFTW make reference to the PATHWORKS Tutorial in the
    help and menus.  This tutorial is not included on the PATHWORKS for
    Windows 95 release, but is available on PATHWORKS for DOS and
    Windows.  For information on using these utilities, consult the
    online help or the online documentation in the PATHWORKS Information
    Shelf.

o   Documentation References to PATHWORKS for DOS and Windows Components

    There are some references in the DECnet Management Guide to PATHWORKS
    for DOS and Windows components -- such as SPAWNER and NFT -- that are
    not included on the PATHWORKS for Windows 95 product.  Only the
    information on components supplied with the PATHWORKS for Windows 95
    product applies to Windows 95 configurations.

o   Removing PATHWORKS V1.0A for Windows 95

    PATHWORKS V1.0A for Windows 95 does not provide an automatic removal
    procedure under the Add/Remove Programs Properties.  To remove
    PATHWORKS V1.0A for Windows 95 from your system follow the
    steps below.

    1.  Start the Network Control Panel:

        Start->Settings->Control Panel->Network

    2.  Select PATHWORKS Licensing Agent (LAN Manager).

    3.  Choose Remove.

    4.  Select PATHWORKS NDIS Support.
    
    5.  Chose Remove.
    
    6.  Choose Ok.

    7.  Shut down and restart Windows 95.

    8.  Delete the PATHWORKS directory.

    9.  Delete the PATHWORKS Start Menu Folder.
    
        Start->Settings->Taskbar->Start Menu Programs->Remove->PATHWORKS

    10. Delete the PATHWORKS Event Viewer from the Startup Folder

        Start->Settings->Taskbar->Start Menu Programs->Remove->
            Startup->PATHWORKS Event Viewer

    Several PATHWORKS files get copied to the Windows System and INF
    directories and may be deleted as well.  The files that are present
    are based on the options selected when PATHWORKS was installed.
    
    Files located in the Windows System directory:
   
        DECCORE.VXD DECDNP.VXD  DECIOCB.VXD  DECLAT.INI  DECLAT.VXD
        DECLICL.VXD DECLMAP.VXD DECND31.VXD  DECNDIC.DLL DECSHOW.VXD
        DNPIC.DLL   DNPIC.HLP   PWEL.DLL     PWEL32.DLL  PWIOCB32.DLL
        PWNDI.DLL

    Files located in the Windows INF directory:

        DECDNP.INF  DECLAT.INF  DECLICL.INF  DECLICN.INF DECNDIS.INF

o   Setting Properties for Network Components

    There is a known Windows 95 problem in handling of registry
    information for some component property pages.  Selecting the "Not
    Present" radio button does not clear a pre-existing value or reset
    the value to the default.  This problem has been reported to
    Microsoft.
    
    The workaround is to manually set the default value and not use the
    "Not Present" option once a value has been changed.  This problem
    affects the Licensing and LAT property pages.

Licensing Advanced Settings
---------------------------

PATHWORKS Licensing Agent (LAN Manager)

You can specify the following parameters in the 'PATHWORKS Licensing Agent 
(LAN Manager)' properties in the Network Control Panel.

Property            Value Description
--------            -----------------
License Server      License server name required for Wide Area Networks
                    such as Async DECnet, Async TCP/IP, or where the 
                    license server is on a LAN outside the local LAN.
                    The named server will be the first server asked
                    for new licenses.

License Group       The license group name of the client.  If no group
                    is specified, new licenses will be assigned from
                    the group "default".

License PAK 1       PAK names of licenses to request, for example:
License PAK 2       DECPWLMDOSCC05.01 or DECPWNWXXXFP05.00
License PAK 3           Note: The first three characters of the
License PAK 4           license value is the "Producer" code and
License PAK 5           the remainder is the "Product" code.
                    Overrides "License Type" and normal defaults.

License Type        This value is used to select a type of PATHWORKS
                    client license if License PAK 1 through 
                    License PAK 5 are not specified. It overrides
                    the normal default.

Timeout (sec.)      Maximum time (in seconds) to allow for connecting
                    to each license server and getting a response for
                    each license server request. Default is 5 seconds.
                    A message will be displayed if any operations
                    fail due to a timeout.


License Management Agent (NetWare)

NetWare Client Licensing utilities (PWLICNW.EXE and PWLICNWT.EXE) are
added to the file WINSTART.BAT in your Windows directory when you install
'PATHWORKS Licensing Agent (NetWare)' with the Network Control Panel.

To change settings, you must edit WINSTART.BAT and modify the PWLICNW.EXE
command line:

    Usage: PWLICNW.EXE [server] [switches]

    Where:

    server              License server hint. The named server will be the
                        first server asked for new licenses.

    /GROUP:<group>      Specifies the system's license group, if any.  If
                        not specified any new licenses will be acquired from
                        the default license group "default".

    /CURRENT:<dirpath>  Directory containing PWLICNW.DAT.  This file
                        is used to store the assigned licenses for the
                        next time the network is started.  Same as /I:.

    /NEEDED:<filepath>  File containing list of required licenses, LICENSE00
			through LICENSE09. Same as /FILE:.

			Example file contents:

                        	LICENSE00=DECPWLMDOSCC05.01
                        	LICENSE01=DECPWNWXXXFP05.00

                                Note: The first three characters in the
                                license value is the "Producer" code and
                                the remainder is the "Product" code.

    /VERBOSE            Provide more messages.  Lists current license,
                        licenses needed and licenses released.

    /NOCONNECTION       Loads any previously assigned licenses but does
                        not attempt to validate them or acquire new licenses.
                        For use with sometimes-connected (mobile) clients.
                        The Client License Requester must be run again when
                        the network has been connected to validate the
                        licenses and acquire new licenses.

    /SHOW               Display all licenses currently assigned to this
                        client.

    /SERVERS            Display all available license servers.

    /TIMEOUT:<sec>      Maximum time (in seconds) to allow for connecting
                        to each license server and getting a response for
                        each license server request. Default is 3 seconds.
                        A message will be displayed if any operations
                        fail due to a timeout.

    /PWACCESS           ERRORLEVEL 0 if CCS or FPA license is present.
                        Used in a .BAT file to test for successful
                        assignment of a license to access PATHWORKS
                        servers.  Example:
                                PWLICLM /GROUP:LGROUP1
                                PWLICLM /PWACCESS
                                IF ERRORLEVEL 0 GOTO SUCCESS

    /? or /HELP         Display this list.

    /NOLOGO             Suppress the copyright banner.

    /FILE:<filepath>    Same as /NEEDED (for backward compatibility)

    /I:<dirpath>        Same as /CURRENT (for backward compatibility)

LAT Advanced Settings
---------------------

Preferred services are stored in DECLAT.INI in the Windows system
directory by default.  Please see the template DECLAT.INI provided for
information on configuring preferred services.  The name and location of
this file can be changed on the Advanced page of the LAT properties in
the Network Control Panel.  

Programming Information
-----------------------

Copies of PATHWORKS programming libraries for Windows 95 are included on
the distribution kit in the SDK directory tree.  There is no installation
process; you must copy the files as desired.   

Additional programming information can be found in the Information Shelf
(Start->Programs->PATHWORKS->PATHWORKS Information Shelf).

o   Windows Sockets (Winsock) Support

    WARNING: Do not replace the existing WINSOCK.DLL if you are using
    Microsoft or another TCP/IP stack.  If you do, your TCP/IP
    applications may stop working.

    The PATHWORKS WINSOCK.DLL only supports DECnet.  If another vendor's
    TCP/IP stack is installed, the TCP/IP WINSOCK.DLL will have to be
    installed first in the DLL search path, or these applications will
    not work.
    
    Each Winsock V1.1 provider supplies a WINSOCK.DLL for use with its
    network transport.  If there are two transport providers, each with
    its own Winsock, only one WINSOCK.DLL will be accessible at a time
    for implicit linking.  Simultaneous use of multiple Winsock providers
    is being addressed by the Winsock V2.0 specification.  
      
    The PATHWORKS WINSOCK.DLL V5.2.050 and later contains an alternate
    way to enable DECnet support.  This method corrects a situation where
    a 32-bit Winsock application uses a thunk to access the PATHWORKS
    16-bit WINSOCK.DLL.

        // Enable DECnet support WSAStartup() 
        // Passing version 1.50 should succeed for V5.2.050 or later
    
        wVersionRequested = 0x3201;    
        err = WSAStartup(wVersionRequested, &wsaData);

o   Microsoft Visual C++ V2.0

    The include files now use PW_APIENTRY (FAR PASCAL) instead of
    APIENTRY, which is defined by the MSVC++ V2.0 compiler.

o   Win32 and IOCB Limitation

    The following applies to a Win32 application using the PATHWORKS IOCB
    interface to communicate with DECnet or LAT.  DOS and Win16
    applications are not affected by the limitation described.
    
    Do not use the MSG_CALLBACK IOCB flag for those functions that
    execute and return immediately.  The IOCB functions that execute
    immediately and those that take time to complete are listed in the
    IOCB Interface chapter of the 'PATHWORKS Network Programming
    Reference'.  If you do set the MSG_CALLBACK flag for these functions,
    the callback will not work correctly and behavior is unpredictable.
