DIVE Installation

- Technical Memo -

Emmanuel Frécon - <emmanuel@sics.se>
Olof Hagsand - <olof@sics.se>

The Swedish Institute of Computer Science
Stockholm, June 1997

1. Introduction

This document describes how to install the Dive 3.2 binary distribution from SICS, June 1997.

2. Retreiving and unpacking.

Get the Dive 3.2 binary release from SICS, for example from http://www.sics.se/dive/.

You should at least get:

  1. the default dive binary (diva) for your platform and
  2. the data directory.

For example, if you have fetched the binary release for SGI MIPS IRIX 5.3, you should do the following:

  1. Place the distribution file(s) dive3.2.sgi.tar.gz in a suitable directory.
  2. Uncompress the file with gunzip (if the browser did not do it for you):
         gunzip dive3.2.sgi.tar.gz
  3. Untar the files, which will be placed in the dive3.1.0 sub-directory:
         tar xvf dive3.2.sgi.tar
  4. Set the DIVEPATH environment variable to data directory, for example:
         setenv DIVEPATH ~/dive3.2/dive/data
    DIVEPATH will indicate to the DIVE programs where to find data, such as materials, world and object files, VRML files, etc. DIVEPATH can be extended to a list.
  5. Change directory to the Dive applications directory:
         cd dive3.2/mips-sgi-irix5.3/appl
    In the case of another platform, than SGI, change to the appropriate directory.

3. Starting Dive

The following setup supposes that you have installed Dive according to the previous section. In short:

  • The environment variable DIVEPATH should contain the dive data directory (e.g. ~/dive3.2/dive/data) .
  • The diva binary should be in the binary app directory (e.g. ~/dive3.2/mips-sgi-irix5.3/appl).
  • For local multi-user use, the diveserver and proxyserver binaries should be in the binary app directory.
  • A soft link called vishnu should point to one of the diva executables: diva.gl, diva.opengl or diva.mesa. Change to Mesa Opengl, for example, by ln -s diva.mesa vishnu.

    • 3.1 Starting the Dive nameserver

    If you want to run multiple users within a site, start the Dive nameserver: 

    > ./diveserver
       ...
Own address: 193.10.66.13 : 3286
sid_netw_join: Joining 233.17.64.22:1167

    The diveserver can now either be contacted on multicast address 233.17.64.22 : 1167, or unicast address 193.10.66.13 : 3286. The multicast address will be tried by default. See configure file documentation to change the default nameserver address.

    3.2 Starting the Dive multicast proxy server

    If you have clients lacking IP multicast capabilities, you should also start the Dive multicast proxy server: 

    > ./proxyserver 
        ...
Own address: 193.10.66.13 : 3294
        ...
proxy_server: bind to 1177
proxy_server: bind to 1187

    An application that does not have multicast capabilities can connect to this proxyserver by setting proxy_host to 193.10.66.13 and proxy_port to 1177. See the configure file documentation for more information.

    If you want to run a proxyserver in order to be a member of the DiveBone, you will need to add the option -nameserver 233.17.64.20:1167, where 233.17.64.20 is an example of a common address for the nameserver controlling the DiveBone.

    3.3 Starting vishnu locally

    You should now be able to start the default Dive application called vishnu: 

    > ./vishnu
Reading configure file /home/emmanuel/dive/data/.dive_configure
Reading configure file /home/emmanuel/.dive_configure
Own address: 193.10.66.13 : 3290
Diveserver answering at 193.10.66.13:3286
Starting GUI... Completed.
sid_netw_join: Joining 226.94.92.241:1166

    By default, vishnu starts in the tutorial world which is a self-explaining with an accompaning web-page.

    3.4 Starting vishnu with proxyserver

    If you do not have multicast capabilities you can connect to the Dive multicast proxy server instead. In this example a connection is made to the proxyserver started above: started : 

    > ./vishnu -proxy_host 193.10.66.13 -proxy_port 1177
Reading configure file /home/emmanuel/dive/data/.dive_configure
Reading configure file /home/emmanuel/.dive_configure
Starting log in dive.log
Own address: 193.10.66.13 : 3302
Starting GUI... Completed.
Diveserver answering at 193.10.66.13:3286

    3.5 Starting vishnu to a remote server

    SICS will have Dive servers running constantly. If you use multicast you will have to adjust the TTL level (with the ttl option) to reach SICS. You can also run unicast by connecting to the SICS proxyserver. 

    ./vishnu -ttl 64
or
./vishnu -proxy_host 193.10.66.13 -proxy_port 1177
respectively

    193.10.66.13 is the current IP address of beowulf.sics.se - the primary Dive server - this may change.

    4. Misc Problems

    4.1 Diveserver not found

    If you get the message 'Diveserver not found on address: XXXX, continuing in singleuser mode' you are running in single-user mode. You will have to enter a correct divesever address, or start a new diveserver and try again. You can also change diveserver address at run-time by the Configure option in vishnu.

    4.2 Found another diveserver

    If you get the message 'Found another diveserver at XXXX,' when starting the diveserver, another diveserver runs serving the same multicast address. Either choose another multicast address, or use the already existing server.

    4.3 Wrong colors

    Netscape (or other program) uses up all of the colors in the colormap so the MesaGL colors are wrong. There are three ways to address this problem: