(   PATHWORKS (Server) Support, Versions?   The Question is:    C I have a licenced copy of Pathworks32 V7.0 for an NT 4 Workstation.    # I have a Microvax running VMS V5.5.    B I need the NT Workstation to access file shares on the VAXstation.   I What is the minimum version of Pathworks server that I need to run on the F  VAXstation to allow fileshare access from the NT4 Workstation runningM  Pathworks32 V7.0 ? and what server based (and/or Client based) Pathworks are   required ?    J I would really like to avoid client based licencing if at all possible butH  please note that this VAXstation will serve at most 2 NT4 Workstations.    Thanks,     Jim      The Answer is :   I   Assuming the OpenVMS VAX system is running a TCP/IP stack, no PATHWORKS D   software is required on the Microsoft Windows NT 4 workstation; noC   licenses are required for this configuration beyond those for the F   OpenVMS software and for the Microsoft software; no PATHWORKS client/   software and no client licenses are required.    H   If the OpenVMS VAX system is not running a TCP/IP stack, then you willI   need to acquire and load PATHWORKS 32 client software on the Windows NT H   4 system to provide access to the DECnet protocol, or you will have toF   install a TCP/IP stack on the OpenVMS VAX system; on the VAXstation.   F   The OpenVMS VAX V5.5 system will require PATHWORKS V5.0F for OpenVMSK   (LanManager) to provide the file serving to the Windows NT 4 workstation.    C   You can use the server-based licensing model to avoid running any G   licensing software on the Windows NT 4 system.  With the server-based G   model, purchase enough licenses for the maximum number of anticipated /   simultaneous Windows workstation connections.    F   You will want to upgrade to a more recent (and supported) version ofD   OpenVMS VAX as the V5.5 release is a very old and long-unsupportedH   release.  As of this writing, V7.3 is the current OpenVMS VAX release.   /  Answer written or last revised on  6-MAY-2004  