                  Supplemental information for
               OpenMind Windows Client Version 2.0 


This file contains last minute information for users of the OpenMind Client 
Version 2.0. Where applicable, the information contained in this file
supercedes any information contained in the Users Guide.


A. What's New
   1. World Wide Web and Hypertext Features
      a. Web Browser
         OpenMind Version 2.0 contains a completely integrated Web browser.
         The browser is accessible through the Section menu item "Goto URL".

      b. Internet Sections
         Through the Section.Manage menu, you can now link an OpenMind section
         to an Internet resource by simply specifying its Uniform Resource
         Locator (URL). When you navigate into that section, it invokes the Web
         browser on the URL, bringing up a hypertext display in the client's
         window.

      c. Hypertext Sections
         Also through the Section.Manage menu, you can associate an HTML
         hypertext document with an OpenMind section, so that the hypertext
         document is displayed in the client window.  You use the document
         management (folder) facilities of OpenMind to store the HTML source
         documents, as well as any embedded images.

      d. OpenMind URL's
         Hypertext documents within OpenMind can contain OpenMind URL's, which
         can be used to specify the addresses of sections within the Mind
         itself. By combining this feature with the hypertext section feature,
         you can create hypertext "navigation" pages, permitting the creation
         of custom access views of the Mind.  OpenMind automatically generates
         the necessary URL for you through the "Copy URL" command available on
         the right mouse button menu for a section.

      e. Internet Protocol Tunneling
         With this version of OpenMind, you can use the OpenMind server as a
         gateway onto the Internet.  By a simple preference change, you can
         route all Internet protocol requests via the OpenMind server,
         regardless of the transport you use to connect to the server.  Thus,
         you do not need Internet connectivity on your desktop, or even TCP/IP.
         Your OpenMind server administrator must enable this functionality.


   2. E-mail Support
      a. E-mail Integration Features 
         Version 2.0 features support for two new gateways that enable e-mail
         users to participate in OpenMind discussions. Version 2.0 supports a
         gateway for both MAPI compatible systems (such as Microsoft Mail), as
         well as VIM-compatible e-mail systems (such as cc:Mail). These may be
         installed when the OpenMind Server is installed.

      b. E-mail Participation 
         E-mail users can participate in OpenMind discussions via special
         commands embedded in e-mail messages that are sent to one of the
         gateways.  E-mail users can start new subjects, reply to messages, or
         participate in personal discussions (pd's) with OpenMind users.

      c. Tracked Information Forwarding
         You can now forward your tracked information (new activity on marked
         items and FYI's) to your e-mail inbox. You can use this feature to
         enable your e-mail inbox as a universal inbox. To configure OpenMind to
         forward your tracked information to your e-mail inbox, select
         File.UserInfo, and click the Email button.

      d. Directory Synchronization
         The e-mail gateways provide facilities for syncrhonizing the user
         directories of each mail system with the OpenMind user directory.
         This permits system administrators to manage a single user directory,
         rather than one for e-mail and one for OpenMind.

   3. Enhanced OLE Support
         The OLE automation interface has been significantly enhanced to
         support more objects and methods. See the Administrator's Guide for
         more details.
         
   
B. Addendums
   1. User Name Entry
      When adding or modifying user names, one can enter in either FIRST MIDDLE
      LAST or LAST, FIRST M. If a user has more than one name for either FIRST,
      LAST or  MIDDLE one must enter the name in the format LAST, FIRST, MIDDLE
      (note the  comma usage).  This lets the Client know where the double name
      entry belongs.
      
   2. Proxy Server
      The Internet access components of Version 2.0 can use a proxy server
      (if necessary) to permit access to Internet resources across a firewall.
      You can have a separate proxy server and proxy port for each of the  
      three protocols supported by the OpenMind browser:  HTTP, FTP, and Gopher.
      You must specify proxy designations in the OPENMIND.INI file.
      For example, to specify the host "my.http.proxy" to listen on port 80
      as a proxy for all OpenMind Internet requests, insert the following in
      the OPENMIND.INI file:

      [Internet]

      httpProxy=my.proxy
      httpProxyPort=80

      ftpProxy=my.proxy
      ftpProxyPort=80

      gopherProxy=my.proxy
      gopherProxyPort=80


   3. Timeouts while connecting over async (dial-up)
      You may occasionally experience timeout errors while attempting to
      connect to an OpenMind server using the async transport, particularly
      when dialing long distance using credit card dialing.  The timeout error
      is normally caused by the client taking longer than 50 seconds (the 
      default for most modems) to dial and connect with the server's modem.  
      You can configure the async transport to wait a longer time before 
      timing out by adding information to your OPENMIND.INI file.  For example,
      to configure OpenMind and your modem to wait up to two minutes for a 
      connection, add the following lines to your OPENMIND.INI file:

      [Async]
      ; Time to wait in milliseconds
      CallTimemout=120000
      ; "Extra" modem initialization
      ; S7 sets the modem's carrier detect timeout (in seconds)
      ; The vertical bar at the end of the string inserts a carriage return
      ModemInitStr=ATS7=120|

      Note:  You must give the modem specific commands in the ModemInitStr 
             so you can program your modem to wait for the desired period of time.
             Consult your modem user's guide for more information.

C. Known Problems and Limitations
   1. 1.0 Client <-> 2.0 Server
      Due to a limitation in both the 1.0 client and 1.0 server, you may not be 
      able to use a 1.0 client with a 2.0 server. Both the client and server 
      have a heartbeat mechanism that allows a server to tell when a client is 
      inactive for a set time.  This heartbeat mechanism did not work on the 
      1.0 client and server. Therefore, if you do not have a 2.0 client, when 
      the server sends a heartbeat message to the client, the client will not respond 
      to the heartbeat message and will time out.

      You can disable the heartbeat mechanism at the server, which would allow 
      1.0 clients to operate properly with a 2.0 server. Doing so, however 
      causes problems with TCP/IP sessions. Apparently IP sessions, when 
      improperly terminated, (machine reboots, hang-ups, etc) leave remnants, 
      which is what the heartbeat mechanism corrects. 

      The bottom line is if you are not using TCP/IP you can mix 1.0 clients 
      with a 2.0 server by turning off the hearbeat mechanism. If you use IP, 
      however, you should upgrade all clients to version 2.0.


   2. Connections
      All of your configured connection types are stored in the openmind.ini
      file. The Openmind.ini file for the 1.0 Client is structured a little
      differently than the Openmind.ini file for the 2.0 Client.  The new
      OPENMIND.INI file will not work with the version 1.0 Client.  The
      OPENMIND.INI file is copied to your windows subdirectory. Setup will not
      overwrite this file, only add some new entries to it. However, the
      client, upon first invocation, will alter these connection type strings
      to match the new 2.0 format. 
      
      If you wish to maintain your 1.0 client, you will need to copy the
      OPENMIND.INI file to a safe place so that you can bring it back
      when you run the 1.0 client.
      
   3. Setup Progress Bar
      Windows NT users may notice that when the progress bar is first displayed
      and a number of system files are being copied, no file names appear
      above the bar. This is due to a problem in the Microsoft setup toolkit,
      which was used to create the OpenMind Setup program.  At time of this 
      release of OpenMind, Microsoft had not corrected this problem.
      This problem is purely a cosmetic flaw and in no way affects the files 
      being copied.
      
   4. CTL3D vs CTL3DV2
      The OpenMind client no longer relies on the system file CTL3D.DLL. It now
      uses a newer version labelled CTL3DV2.DLL. Therefore it is important that
      all users, especially network attached users, run Setup to ensure
      that this new file is properly installed. If you do not run setup, an 
      operating system message appears, indicating that CTL3DV2.DLL was
      not installed properly.
      
   5. Modem Database
      We have added many new modems to our modem database. In doing so, the
      modem you may have selected to use with version 1.0 may be invalid. 
      We recommend that async users check their connection type and make 
      sure it is still valid.  If your modem type has been renamed/refined 
      it may show up as the default Hayes modem setting. Simply reselect 
      the proper modem from the list.

   6. FTP TCP/IP stacks
      If you are using the TCP/IP stack from FTP,  make sure that you are using 
      the Windows based VxD drivers rather than the DOS based TSRs. Also, you
      should use a copy of FTP's WINSOCK.DLL version 1.15.1 or later.  If you 
      use either an old WINSOCK.DLL or the TSR drivers, OpenMind may have 
      unpredictable results when shutting down.
      
   7. Other TCP/IP stacks
      Some TCP/IP stacks do not require the WINSOCK.DLL file to be installed.  
      OpenMind requires the WINSOCK.DLL file in the PATH to connect to the
      OpenMind server using the TCP/IP Connection type.  If the WINSOCK.DLL 
      file is not available, the client returns the error "Can’t Initialize
      TCP/IP transports."
 

   8. Print Setup
      Due to a bug in some beta versions of Windows NT 3.51, the Print Setup
      menu item may not be operational when using this version of NT. This
      problem does not exist in the released version of Windows NT 3.51. We 
      recommend that you use the released version of Windows NT when possible. 
      If you are using a beta version of Windows NT, you can access the Print
      Setup dialog box from the Print dialog box.  The production version of
      Windows NT 3.51 resolves this issue.

   9. Viewer and improper DOS filenames
      The OpenMind viewer in the Windows client version of the product cannot
      read files that have invalid Windows/DOS filenames. Please be sure when 
      posting files from other operating systems (e.g. Macintosh) that the files 
      are valid Windows/DOS filenames if they are to be read by a Windows client.

   10.Multiple transports and Windows NT 3.5
      Due to a problem in Windows NT 3.5 and 3.51, using an IPX connection to
      the OpenMind server while also using a local TCP/IP stack may cause FTP
      file transfer failures within NT. This can be avoided in one of two
      ways:
          -Use TCP/IP, or any other non IPX protocol, to connect to the 
           OpenMind server.
          -Use TCP/IP tunneling instead of a local stack.