Справочник Пользователя для Barco R9830350

Скачать
Страница из 44
R9830350 Octopus User Guide  (2001-08)
3-2
3.1 Octopus Software Installat ion
Before installing Octopus 2.1 Service Release,  please de-install all earlier versions
of Octopus!
Use the Add/Remove Software Option from the Windows Control Panel to uninstall
Octopus!
3.1.1 Hardware Prerequisites
  Pentium or Pentium II computer, 200MHz minimum recommended CPU
  CDROM reader
  32MB RAM minimum
  2MB free disk space per module
  Network card
3.1.2 Software Prerequisites
  Windows NT 4.0 (SP3 or higher) or Windows
  TCP/IP support
  Administrator privileges
Installation of the O
CTOPUS
 software generally requires some decisions to take place prior to actual
installation. Here is a synopsis of the decisions to be taken:
3.1.2.1 Central Installation vs. Indivi dual Installations
The binary software for each of the O
CTOPUS
 modules can be installed in a central location, on an
application server (this can be the wallboard processor), or installed on each client machine as needed.
We recommend installing the software in a central location to ease maintenance of the software as
upgrades and patches are made available. This will require that all computers that are going to use the
software have access to the directories that contain the installed software. In MS Windows operating
systems, this means that the installation directories must be shared with each user having sufficient
permission to read the directories.
If you plan to install the software on each computer individually (e.g.: in a small control room), then these
restrictions do not apply, although each machine must have it's own CDROM reader.
3.1.2.2 Administered Use vs. Non-a dministered Use
The O
CTOPUS
 software can operate in essentially two modes, one where all users have identical access
rights, and where each user has a defined priority level. When the software is installed, a default priority
is granted to all users which if left as it is will permit first-come-first-serve access to the wallboard. If this
is not a desired effect, then it is possible to assign each user, user and computer, or a global category a
priority level, which will determine access rights to the wallboard. On order to facilitate this process, it is
worthwhile to write down each of the users names, the machine names from which they will access the
wallboard, and the roles each will play in the operation of the wallboard system. The issues surrounding
this decision will be elaborated upon in a subsequent section of this manual.