DP Tool Club 17/CD_ASCQ_17_101194.iso/vrac/epi_info.zip/README.LAN

Text File | 1994-09-01 | 7KB | 145 lines

README.LAN                                        August 19, 1994
                INFORMATION FOR LAN ADMINISTRATORS

The main programs in Epi Info are LAN compatible.  ENTER allows
multiple users to enter data in the same file, using record-
locking techniques that work through DOS and are not LAN
specific.  ANALYSIS in Version 6.01 allows several users to read
the same file and give appropriate messages when trying to write
files if this is not permitted.

Epi Info may be installed on Local Area Networks (LAN's) in
several different configurations, depending upon the intended
use:
   1.  The compressed installable system, containing INSTALL.EXE
       and FILES1.EXE, FILES2.EXE, etc. may be placed in a LAN
       directory to allow users to install the system on their
       hard disks (using the (I)nstall option in INSTALL) or
       copy it to floppy disks (using the (C)opy option) for
       distribution to others or installation on a laptop
       computer.

   2.  The executable version of Epi Info may be installed
       in a LAN directory in a directory for which most users
       do not have write privileges.  It is important to use
       the INSTALL.BAT program to install the system.  The
       main programs and examples will be installed in a
       directory called \EPI6, which may be made read-only to
       most users.  Users should then run the system from
       another directory in which they DO have write privileges,
       either another LAN directory or their local hard
       disk drive.  If the sample surveillance system is
       chosen during installation, a directory called \NETSS
       is also created. This directory MUST BE WRITABLE for
       users, or provision must be made to copy its contents
       to another directory for individual use.

   3.  To install Epi Info in subdirectories that are not
       directly subordinate to the root directory (e.g., in
       N:\APPS\EPI6 and N:\APPS\NETSS), use the batch file
       INSTALL.BAT for instructions, or merely log into the
       parent directory (N:\APPS) and proceed with installation
       using INSTALL6.EXE.  The desired directories will be
       created subordinate to the currently logged directory
       on the DESTINATION drive.  To allow Epi Info to run
       properly with directories not directly off the root,
       a DOS ENVIRONMENT VARIABLE called EIDIR must be set
       to tell Epi Info where to find its directories.  In
       this case SET EIDIR=N:\APPS will do the job.  See
       the SAMPLE below.

   4.  It is possible for a user to install and run
       Epi Info in a writable directory on the LAN without help
       from the LAN administrator, although others having access
       to the same directory can then alter the files.

                            LAN NOTES

Some tutorials and examples require write privileges. Epi Info
programs need to write configuration files or save data files,
and this cannot be done in a directory for which the user does
not have read/write privileges. Although the system may reside in
a directory for which the user does not have write privileges,
the user must run it from a writable directory, either on the LAN
(if users are to share a single data file, for example), or on
the user's local hard disk.

If tutorials or examples are run from the main menu while DOS is
logged to an inappropriate directory a message now suggests using
the SETUP function in the TUTORIAL or EXAMPLE menu. Depending
upon circumstances, this either changes the logged directory to
\EPI6 or offers to copy needed files from a read-only directory
on the LAN so that Tutorials and Examples will run easily.

The PATH statement in AUTOEXEC.BAT must contain the location of
the Epi6 directory on the LAN.  This allows Epi Info to be run
from the LAN without being on the user's hard disk, although the
latter is also a reasonable option if there is disk space
available.

The programs should run faster if the system is copied to the
user's own hard disk and run from there (perhaps accessing a
common data file on the LAN).  Programs residing only on the LAN
must be loaded into RAM on the user's computer via the LAN, and
this can slow things down in some cases.


                SAMPLE (Novell) LAN INSTALLATION

In a Novell LAN, a batch file is placed in a directory called
M:\BATCH that is accessed when a user types EI6; the batch file
contains the following commands:

@echo off
cls
set eidir=n:\apps                 (Set an environment variable
                                   to tell Epi Info the parent
                                   directory for \EPI6 and \NETSS)
map ins s6:=sys:/apps/epi6        (Set up mappings)
map ins s7:=sys:/apps/netss
call m:home.bat                   (Be sure that the user is running
                                   system from a directory with
                                   write privileges)
call n:\apps\epi6\epi6.exe        (Run Epi Info)
map del s7:                       (Remove the mappings)
map del s6:
call m:home.bat                   (Go back to home)
set eidir=                        (Erase the environment variable)
echo on

Although other LAN's may have different configurations or
commands, perhaps this example will be helpful in setting up a
smooth system for accessing Epi Info.

To run the sample surveillance system contained in the NETSS
directory the user must be logged into the NETSS directory, and
must have write privileges.  There are several choices in setting
up NETSS on a LAN.  Here is one solution:

In the menu configuration file EPI6.MNU, in the DONETSS block,
delete 'REM' from the front of lines 5, 6, and 8, making
appropriate changes as needed; then add 'REM' to the front of
lines 3, 4, and 9. The commands are the same as for DOS batch
files.  Line numbers are for this discussion only and are not in
the file.

1  DoNETSS
2  BEGIN
3    cd %EIDIR%\NETSS
4    IF NOT EXIST NETSS.MNU GOTO NONETSS
5  REM   n:
6  REM  cd \apps\netss
7    NETSS
8  REM  call home
9    cd %EIDIR%\EPI6
10    GOTO END
11    :NONETSS
12     ECHO Could not locate %EIDIR%\NETSS\NETSS.MNU menu file for NETSS.
13     ECHO Was it installed?
14     ECHO If you are running on a LAN see README.EI6
15     ECHO NETSS must be run from NETSS directory
16     PAUSE
17    :END
18 End