Running Milestones, Etc. on a Network
-------------------------------------

Licensing Requirements
----------------------
Workgroup Licenses and Site licenses are available.  You must have
either a Workgroup License, Site License, or enough individual copies
of Milestones, Etc. to accommodate the total number of simultaneous
users of Milestones, Etc. to legally run Milestones, Etc. on your
network.  If you make Milestones, Etc. available to your network, you must
be able to limit the number of simultaneous users to the size of your
workgroup license or to the total number of copies of Milestones, Etc.
that exist on your network.

Overview
--------
Milestones, Etc. is designed to run equally well on a single computer
or on a network server.  You may wish to install Milestones, Etc. on each
workstation and simply share files with other workstations or you may wish
to install Milestones, Etc. on a network server and have each each workstation
use the common copy of the software.

Milestones, Etc. Installed on Each Workstation with Shared Files
----------------------------------------------------------------
If you simply wish to share Milestones, Etc. schedules or custom symbols
across your network, but install individual copies of Milestones, Etc. on
each workstation then you should do the following:

1. Install Milestones, Etc. on each workstation.

2. Alter the following entries in each workstations MILES.INI file (located
   in the \WINDOWS directory on the workstation.

   [Milestones, Etc. 4.0]
       .
       .
   charts=C:\MILES\charts          (change to point to common location of
       .                            Milestones, Etc. schedules)
       .
   symbols=C:\MILES\symbols        (change to point to common location
       .                            of custom symbols)
       .
   templates=C:\MILES\template     (change to point to common location
       .                            of Milestones, Etc. template files)
       .
   graphics=C:\MILES               (change to point common location of
       .                            of graphic images included in Milestones,
       .                            Etc. schedules)
       .
   holidays=C:\MILES\holidays.txt  (change to point to common location of
                                    of holiday definition file)

   All or none of these entries may be altered.  The user must be able to
   read, write, create, and alter files in these directories as well as the
   MILES.INI file itself.  These changes may also be made via the Milestones, Etc.
   FILE PREFERENCES... menu.


Running Milestones, Etc. from a Server
--------------------------------------
To run Milestones, Etc. from a server, you should first install Milestones, Etc.
on the server.

For each user/workstation that will access Milestones, Etc. do the following from
the workstation:

1. Create a MILES.INI file in the workstation's local \WINDOWS directory by
   copying the MILES.INI file created when Milestones, Etc. was installed
   on the server.

2. Make the changes needed in the [Milestones, Etc. 4.0] section of the
   MILES.INI file to reflect the user's environment.

3. Ensure that the .DLL and .DIL files that support Milestones, Etc. graphics
   import feature are in the user's PATH.  If the .DLL files are not in the
   PATH Milestones, Etc. will not be able to start.

   If the .DIL files are not in the PATH, graphic imports will fail and graphics
   will not be displayed.

   These files are as follows:

      imageman.dll
      imgbmp.dll
      imgbmp.dil
      imgepsf.dil
      imggif.dil
      imgpcx.dil
      imgtga.dil
      imgtiff.dil
      imgwmf.dil

4. Ensure that the files that support OLE 2.0 are in the user's path and that
   the versions are the same or newer than those installed by the Milestones, Etc.
   installation program.  Without these files, Milestones, Etc. will not be
   able to start.  These files are as follows:

      compobj.dll
      mlsoleui.dll
      ole2.dll
      ole2.reg
      ole2conv.dll
      ole2disp.dll
      ole2nls.dll
      ole2prox.dll
      stdole.tlb
      storage.dll
      typelib.dll

5. Ensure that OLE 2.0 is registered by running the REGEDIT command on the
   OLE2.REG file:

       REGEDIT ole2.reg

   Note that you should prefix the .reg file with it's path so that REGEDIT
   can find it.

6. Ensure that the file CTL3DV2.DLL is in the user's \WINDOWS\SYSTEM directory.
   If CTL3DV2.DLL is loaded from any directory other than the \WINDOWS\SYSTEM
   directory the 3D dialog boxes will be disabled, a warning message will be
   displayed, and all dialog boxes will revert to the non-3D appearance.

   Note that the WINDOWS\SYSTEM directory may have a different name on your
   system, but it must exist.  It is the directory where printer drivers, video
   drivers, true-type fonts, .drv files, etc. are usually found.

7. Make a copy of the MILES.REG file created in the \MILES\SYSTEM directory
   when Milestones, Etc. was installed on the server.

   For each user, make the necessary path changes in the file to reflect the
   path to MILESV40.EXE that each user will be using.  There are several
   references to the MILESV40.EXE file in MILES.REG.  All must be changed
   in order for the OLE features of Milestones, Etc. to operate.

   For example, if from a workstation, the user will be running Milestones, Etc. from
   N:\MILES\SYSTEM, then all occurences of the default

   C:\MILES\SYSTEM\MILESV40.EXE

   should be changed to

   N:\MILES\SYSTEM\MILESV40.EXE

8. Run REGEDIT on the MILES.REG file that has been altered for each user.

   REGEDIT miles.reg

   Note that you should prefix the .reg file with it's path so that REGEDIT
   can find it.

9. Create a Program Manager icon for Milestones, Etc. using File New...
   from Program Manager.


Milestones, Etc. Provided File Access Protection
------------------------------------------------
Milestones, Etc. depends upon the functionality of SHARE in order to prevent
the same file from being open by more than one user at a time and to prevent
one user from filing over a schedule that is already open by another user.

If SHARE functionality is not detected Milestones, Etc. displays a warning
message when it starts.

Milestones, Etc. can run without SHARE functionality, but the above file access
protections may not operate and OLE functions should not be used. (OLE
functions can be disabled by the addition of the /noole command line
switch on the Milestones, Etc. icon properties.

Windows for Workgroups and Windows NT provide SHARE functionality.  Windows 3.1
under DOS can be provided SHARE functionalty via the DOS SHARE command.

Other network systems may also provide SHARE functionality.
