    ------------------------------------------------------------

            CMS Client for Windows, Version 1.2a README 

			November 1997

    ------------------------------------------------------------

    (c) Copyright Digital Equipment Corporation, 1995,1997.  

        All Rights Reserved.

    (c) Copyright Electronic Data Systems Limited, 1996,1997           





    This readme file provides information about the client

    product features as well as the hardware and software 

    requirements, installation, known problems and fixes, 

    documentation, restrictions, and how to report problems 

    when using the CMS Client for Windows.





    Requirements:

    ------------



    HARDWARE REQUIREMENTS



    CMS Client:



    o  A PC using an 80486 or higher microprocessor, IBM or 

       compatible OR an Alpha processor



    o  A minimum of 8 MB of RAM (for Windows 95) OR 16 MB of RAM (for

       Windows NT)



    o  CD-ROM drive 

    



    CMS Server:



    o  An OpenVMS system with a minimum of 100 (VAX) or 200 (Alpha) 

       disk blocks



    o  CD-ROM drive 





    SOFTWARE REQUIREMENTS



    CMS Client:



    o  Microsoft Windows 95 or Microsoft Windows NT Version 4.0



    o  For DECnet: 



    	-- DIGITAL PATHWORKS 32 Version 7.0



    o  For TCP/IP: TCP/IP support via Window Sockets Version 1.1:



    	-- Microsoft TCP/IP-32





    CMS Server Version 1.2a (Provided with the client):



    o  DIGITAL CMS Versions 3.8 - 3.9 or DECset Versions 12.1 - 12.2

       for OpenVMS Alpha or OpenVMS VAX 



       Note: The DEC C RTL is required when installing the server on 

       an OpenVMS V5.5-2 system.  To request the DEC C RTL contact 

       your Customer Support Center or local DIGITAL representative.



    o  For DECnet:



    	-- PATHWORKS for OpenVMS VAX Version 5.0 or higher  OR



    	-- PATHWORKS for OpenVMS Alpha Version 5.0 or higher



    o  For TCP/IP:



        -- DIGITAL TCP/IP services for OpenVMS (UCX) Version 3.3 or

           Version 4.1  OR



        -- PathWay [TM] for OpenVMS Version 2.5.1 (Attachmate 

           Corporation)  OR



        -- Cisco MultiNet [R] for OpenVMS Version 4.0 (Cisco 

           Systems [R], Inc.)  OR



        -- TCPware [R] for OpenVMS Version 5.1 (Process Software 

           Corporation)





    Installation Notes:

    ------------------



    CMS Client:



    The CMS Client is supplied on an AutoRun CD-ROM.  To install the 

    CMS Client:



       . Insert the CD-ROM into the CD-ROM drive on your system



       . Follow the instructions displayed until the installation 

         completes.

     

    If AutoRun is disabled, follow these steps:



       . From your desktop Start menu, click Run.



       . Enter d:\SetupClients



         Note: If your CD-ROM is not labeled d:, enter the 

         appropriate letter for the CD-ROM on your system.

         

    Once installed, you have access to the product readme file, help

    file and the product icons from the Start Programs menu.  





    CMS Server:



    The CMS Server is supplied in a VMSINSTAL installation kit.  You

    can install CMS Server from an OpenVMS SYSTEM account.



    To install the server, enter the following command at the OpenVMS 

    prompt:



       $ @SYS$UPDATE:VMSINSTAL kit-name device-name:[directory]



    In this example, kit-name represents the CMS Server kit 

    (CMSSRV012A for VAX and CMSSRV012A_AXP for Alpha) and

    device-name:[directory] represents the CMS Server directory

    name on the CD.



    Additional information regarding the CMS Server may be found in 

    the server release notes.



   



    TCP/IP Notes:

    ------------



    For TCP/IP connections to work properly, the remote execute 

    service must be enabled on OpenVMS.  This service is called 

    REXEC or EXEC for most TCP/IP networks (service port 512).  If 

    this service is not enabled, users will be unable to connect to 

    the CMS Server on OpenVMS.  Also, several TCP/IP networks allow 

    limits to be set on the number of REXEC services that can be 

    running at any given time.  This limit must be set high enough, 

    based on the user count, to allow successful connections (e.g. 

    if the limit is set to 5 and a 6th person tries to connect, that

    connection will fail).





    Troubleshooting:

    ---------------



    If in attempting to connect to a CMS library the error "Lost 

    connection to CMS server" occurs, the most likely causes of the 

    error are an invalid password, an invalid username, wrong 

    protection settings on the server files, and the server not being 

    installed.



    On Windows 95 systems, if in attempting to connect to a CMS 

    library via TCP/IP, the error "Host unknown" appears, check that 

    the node name or address being used is correct.  If it is, check 

    that the node name and address are specified in the local hosts 

    file:



        C:\WINDOWS\hosts

 

    Add an entry with the following form:



        <tcp/ip-dotted-address>     <alias-name>



    For example:



        102.54.94.97     OpenVMSMachine



    Please see the CMS Client User's Guide for more hints on 

    troubleshooting.



    One additional note not included in the User's Guide:



       An additional command line argument is available to capture

       the client's server messages.  If problems occur while 

       connecting to a CMS server or while files are being fetched 

       or reserved from a library add this argument to the command 

       line.



       Modify the properties of the CMS Client Shortcut, so the 

       command line contains the argument "-sde".



       For example, if you installed the CMS Client in 

       C:\Program Files\Digital\CMS Client

       then the command line should be edited to say:



          C:\Program Files\Digital\CMS Client\Cmscnt32.exe -sde



       The "-sde" option may also be set via the "Run..." command 

       under the "Start" button on the Windows 95 taskbar.



       The "-sde" switch will output additional handshaking messages 

       into a file called CMS$CLNT.TRA which is created in the local 

       directory as defined when the client is first invoked.



       To obtain a server trace file, on the OpenVMS system define

       the system logical name CMS$SERVER_TRACE with any non-null 

       equivalence name (e.g. "FOO").  This logical name must be 

       defined on the same node that the server is running on.  

       Define the logical name prior to running the client.



       The OpenVMS account that is used to establish the CMS 

       Client/Server connection will contain the file CMS$SERV.TRA 

       in the SYS$LOGIN directory.



       If you need assistance, this additional information can help

       DIGITAL diagnose the problem.





    New Features:

    ------------



    The following enhancements were added in Version 1.2a:



        o A new icon has been added to the toolbar to activate the 

          MMS Client for Windows.



    The following enhancements were added in Version 1.2:



	o Long filenames are supported by the client.  



    	o Added support for Alpha NT.



    	o Wish 19 - The user is now prompted for remark on drag and 

          drop reserve, replace, and unreserve.



    	o Wish 23 - The user is now warned during a reservation if

          the element is currently reserved, and prompted whether or

          not to proceed with the reservation.



    	o Wish 22 - The tooltips text for toolbar icons is additionally 

    	  displayed under the icon.



    	o Wish 3 - The user is informed if the cause of a login failure 

          is likely to be an invalid username or password.







    Problems Fixed:

    --------------



    The following bugs were fixed in Version 1.2a:

       

        o  During installation on Alpha Windows NT, the CMS Client 

           may be added to the Start Menu on the taskbar.



           The CMS Client installation now updates the Start Menu 

           Programs correctly.



        o  During installation on Alpha Windows NT V4.0, the CMS 

           Client Start Menu Programs File Folder may not be created.



           The CMS Client installation now updates the Start Menu 

           Programs correctly.



	o  Bug 11 - During the installation CMSSETUP.EXE file is left

           in the windows directory.



           CMSSETUP.EXE is no longer left on the system.





    The following bugs were fixed in Version 1.2:



        o Bug 15 - General protection fault when transferring multiple

    	  elements.  The client may fail with a general protection 

          fault during operations which cause numerous messages to be

          displayed.  The problem only occurs when the client needs 

          to create both a horizontal and vertical scroll bar for the

          Messages box while displaying multiple messages.  



    	o Bug 16 - Only latest generations can be inserted into 

          classes.  Regardless of which generation of an element was 

          specified during insertion into a class, the latest 

          generation was inserted into the class.  The specified 

          generation is now inserted into the class.



    	o Bug 17 - Protection fault if an alias is changed and the

          username is omitted.  If an attempt was made to change an 

          alias and the username was omitted, the client exited with 

          a general protection fault.  The alias is now saved 

          correctly without the username.







    Known Problems:

    --------------



    The following known problems exist in Versions 1.2 and 1.2a:

	

	o  Bug 7 - Error messages in UCX$REXECD_STARTUPLOG file.  The

 	   following messages appear at the end of the 

           UCX$REXECD_STARTUP.LOG file whenever the client is used 

           to connect to a library using TCP/IP:



		$ set noverify

		%RMS-F-WER, file write error

		-SYSTEM-F-BADPARAM, bad parameter value

		<process-name> job terminated at DD-MMM-YYYY, hh:mm:ss



	    The message occurs every time a connection is made, even 

            when no further CMS operations are performed.



	    The error messages may be ignored.



	o  Bug 8 - CMS Client Server:  Could not open TCP/IP network 

           link. Following a successful DECnet connection from the PC 

           to a CMS library, the NETSERVER.LOG file will contain the 

           following messages:



		SYS$QIOW returns 172

		CMS Client Server: Could not open TCP/IP network link



	   The error messages may be ignored.



    	o  If MultiNet is being used as the TCP/IP transport and a

           connection has already been made to a CMS library, an 

           attempt to disconnect from the current CMS library and

           connect to a new CMS library may fail with the error message

           "Lost connection to server".  If this occurs, attempt the 

           connection again.





    Documentation:

    -------------



    The following known problems exist in the client documentation:



        o  CMS Client Windows User's Guide, section 5 

           ("Troubleshooting"), sub-section 'Receiving "Server Timed

           Out" Message' incorrectly advises the user to run the 

           CMS$STARTUP.COM file if the message "Server Timed Out" is 

           received.



           Running the CMS startup file is unnecessary.



        o  Client Help contains the following:



	   "Why update your aliases?  Aliases point to objects which

            contain your server environments username and password."



           The password is not stored.



    	o  Title bar "CMS Client - (not connected)".  

  	   CMS Client for Windows User's Guide, Section 1 "Getting 

           Started", sub-section "Using the Main CMS Client Window" 

           shows the information displayed in the title bar prior to

           establishing a connection as: 



     			CMS Client - [not connected]



  	   However, the actual information uses parentheses:



     			CMS Client - (not connected)





    Restrictions:

    ------------



    The following restrictions apply to Versions 1.2 and 1.2a:



	o  The product is not Windows 95 logo-compliant.  For example, 

           it still has a Windows 3.1(1) look and feel to its 

           interface.





    Reporting Problems and Suggestions:

    ----------------------------------



    Depending on the nature of the request or problem and the type of

    support you have, you can call DIGITAL if your software contract

    or warranty agreement entitles you to telephone support.



    Review the SPD and Warranty Addendum for an explanation of the 

    warranty. If you encounter a problem during the warranty period, 

    report the problem preferably using electronic means such as 

    DSNlink. In the United States, customers can call the DIGITAL 

    Customer Support Center at 1-800-354-9000.



    In addition, DIGITAL now provides access to Web Information and 

    Support (WIS), a new electronic delivery application that allows 

    you to submit electronic service requests, access databases, 

    download patch kits, transfer files from DIGITAL, and connect to 

    global notes conferences via the World Wide Web.  If you are an 

    entitled service customer with access to the Web, you can now use 

    your favorite browser to connect to electronic services through 

    an easy-to-use, graphical interface.



    If you are already a DIA user, you can gain access to WIS by:



    1. Opening http://www.service.digital.com/wis.

    2. In the United States, clicking on the words "United States".

    3. Entering your DIA Access ID and password.  



    WIS and DIA use the same underlying account and directory on the 

    DIGITAL Customer Support Center host system.



    If you are not already registered for DIA, you can register for a 

    WIS account by contacting your Customer Support Center or local 

    DIGITAL representative.

        

    This method should also be used to make requests for additional 

    features or modifications to existing features.



    When submitting a report, please include the following 

    information:



    o  The version of CMS Client being used.



    o  The version of the CMS Server and the OpenVMS operating system 

       being used.



    o  The transport method and version being used.



    o  The PC operating system and version being used.



    o  The problem reduced to as small a size as possible trying not  

       to overlook any details.



    o  Any stack dumps that occurred, if applicable.



    o  All files should be submitted on machine-readable media 

       (magnetic tape, floppy diskette, or tape cassette).





----------------------------------------------------------------------

Trademarks:



  DECnet, DECset, DIGITAL, OpenVMS, PATHWORKS, VAX, OpenVMS and the 

  DIGITAL logo are trademarks of Digital Equipment Corporation.



  Microsoft, Windows, Windows 95 are registered trademarks of 

  Microsoft Corporation.



  Intel is a registered trademark of Intel Corporation.



  Cisco Systems and MultiNet are registered trademarks of Cisco 

  Systems, Inc.



  TCPware is a registered trademark of Process Software Corporation.



  [TM] PathWay is a trademark of Attachmate Corporation.



  [TM] Windows NT is a trademark of Microsoft Corporation.



