 
                       Mobile File Sync Beta README
 
 This README file contains the latest information about Mobile File Sync.
 (MFS).  After you install MFS and reboot your system you can get more
 information about MFS in MFS.DOC which is located in the Mobile File Sync
 folder.
 
 If the editor you are using to view this file is currently using proportional
 font, you may notice some irregularities with the spacing and alignment of
 the text.  For the best viewing results, please display this README file in a
 monospace font.
 
 
 CONTENTS
 --------
 
 This README file includes the following information:
 
  1.0  General Introduction
  2.0  Installing MFS from Diskettes
  3.0  Known Problems and Limitations
  4.0  Trademarks
 
 
  1.0  General Introduction
       --------------------
 
       MFS is a file system that supports mobility of OS/2 Warp clients.  OS/2
       Warp clients can be either File and Print clients, OS/2 Peer clients,
       or OS/2 Netware clients. 
 
       MFS enables OS/2 Warp client users to physically disconnect from the
       server and still have access to their server files.  While the users 
       are disconnected, they can read or modify existing files, create new
       files and directories, or delete files and directories.  When the users
       reconnect MFS automatically updates the server with any new files or
       directories that werer added or deleted, and updates files with changes
       that were performed at the client.  MFS provides extensive conflict
       detection and resolution of any files changed on either the server or
       the client.  MFS runs from the client only, and does not require
       changes to the server.
 
       With MFS, intermittent network failures are transparent to File and
       Print clients, OS/2 Peer clients, or Netware clients.  This is 
       especially valuable for unreliable or low-speed connections.  For
       example, wireless devices such as InfraRed (IR) and Radio Frequency 
       (RF) can have their client/server connection temporarily interrupted if
       the client moves out of the device range.  If InfraRed Direct Access
       (IRDA) devices are used for a client/server connection, that connection
       can be temporarily interrupted when someone simply walks in the direct
       path between the transmitter and the receiver.  MFS protects against
       this type of temporary disconnections by caching the files from the
       server to the client when a connection is available, and by accessing
       the cached version of the files when the user is disconnected from the
       server.
 
 
  2.0  Installing Mobile File SYNC From Diskettes
       ------------------------------------------
 
       To install MFS from diskettes, do the following:
 
         1.  Insert diskette 1 into drive A.
         2.  At the OS/2 prompt, type:
 
              a:install
 
             The Instructions window displays.
         3.  From the Instructions window, click on Continue.  The Install
             window displays.
         4.  From the Install window, click on OK.  The Install - Directories
             window displays.
         5.  From the Install - Directories window, click on Select all.
         6.  The pathname at the bottom of the Install - Directories window
             displays the location where MFS is going to be installed.  If
             the drive letter displayed in the pathname is the correct
             location where you want to install MFS, skip to Step 10.
             Otherwise, continue with Step 7.
         7.  From the Install - Directories window, click on Disk space.
             The Disk Space window displays.
         8.  From the Disk Space window, do the following:
               a. Select the drive where you want to install MFS
               b. Select the Change directories to selected drive check box
               c. Click on OK
             The Install - directories window displays.
        10.  From the Install - Directories window, click on Install.
        11.  When prompted, insert diskette 2 into drive A.
        12.  Click on Continue.
        13.  When prompted, insert diskette 3 into drive A.
        14.  From the Installation and Maintenance window, click on OK.
        15.  From the Installation window, click on Exit.
        16.  Reboot your machine.
 
 
  3.0  Known Problems and Limitations
       ------------------------------
 
       This section contains known problems and limitations.
 
       o  If you start MFS from Persistent Storage, the MFS automatic
          Server/Alias GUI may display.  If it does, DO NOT enter the
          servername and alias again.  Instead click on Cancel, to close the
          MFS GUI.  The Status icon will be  MFS Status :CONN. .  Then MFS
          is ready for use.
 
       o  You must install MFS on a single drive.
 
       o  When you start MFS, do not use drive Z.
 
       o  When you issue a DIR command on a directory that contains an
          exceptional number of entries the response may be slow due to 
          the required initial caching.
 
       o  File locking is not supported.
 
       o  When you are transferring data from the server, DO USE the Stop
          MFS icon, it can result in an incomplete file.
 
       o  Some word processors, (for example, AmiPro) create temporary
          files and then delete the files on the final save of the file.
          If you use one of these word processors on the MFS drive while 
          you are disconnected, Temporary Files Create and Delete will be 
          propagated to the server during reintegration.
 
       o  If you are using AmiPro and you repeatedly open and close an
          existing file, the data in the file may not display.  To correct
          this problem, close AmiPro and restart it.
 
       o  After you start MFS, to see the files on the MFS drive use the
          normal file finder within your application or use the DIR command.
          The OS/2 drives folder object for MFS, will be empty.  The GUI
          representation of the MFS drive does not represent its contents.
 
       o  When interacting with MFS, the system editor E.EXE does not
          close completely.  To close it, use the option from the window.
          The window is located in the Minimized Window Viewer by default.
 
       o  You can attach MFS to a server drive using File and Print client or
          other supported client software packages.  In doing so, there is a
          two-step mapping process:  server drive to local LAN, and local
          LAN drive to a local MFS drive.  For example, if the LAN drive is
          L:, and the MFS drive is M:
 
             Type     Name    FSDName    FSAData
             Remote   L:      LAN        \\S1\D1
             Remote   M:      MFS        L
 
          After attaching to the drive, MFS will always remember the drive
          letter L: as the D1 drive on server S1.
 
          DO NOT use the L: drive for any other purpose.  If you want to
          use L: for another purpose, or want to use MFS to cache data from
          another drive, then do the following:
 
            1.  Connect to the S1 server
            2.  Reintegrate your changes to S1
            3.  Disconnect
            4.  Stop MFS
            5.  Clear persistence
            6.  Start using the new server
 
 
  4.0  Trademarks
       ----------
 
       The following terms are trademarks of the IBM Corporation in the United
       States or other countries or both:
 
           IBM
 
       This file is provided "as is" without warranty of any kind.  IBM
       disclaims all warranties, whether expressed or implied, including
       without limitation, the implied warranties of fitness for a particular
       purpose and merchantability with respect to the information in this
       file.  By furnishing this file, IBM grants no licenses to any patents
       or copyrights.
 
       This file could include technical inaccuracies or typographical errors.
       Changes are periodically made to the information herein; these changes
       will be incorporated in new editions of this file.  IBM may make
       improvements and/or changes in the product(s) and/or the program(s)
       described in this file at any time.
 
       (C) Copyright IBM Corporation 1996.  All rights reserved.
 
