There is an environment variable on Linux called F_UFMTENDIAN that can put the Intel processors in big-endian mode. If this variable is set to big, unset it or set it to little.

When the local machine is used for the batch processing, that is, the ‘Use Local Machine’ option is selected in the ‘Machine Setup’ window, the batch process is sometimes stopped during the initialization (right after ‘Execute’ is pushed). There is a red popup message which says ‘Remote connection failed‘.

Work-around: Switch off the ‘Initial Access Check’ in the Wavefront Tracer Batch window.

If the machine access check in the NORSAR-3D Common Shot Wavefront Tracer - Batch fails, check the following:

1. The access check needs rexec enabled on the remote machine:
   
   cd /etc/xinetd.d 
   
   Ensure that it says disable = no in rexec
   
   /etc/rc.d/init.d/xinetd reload
    
2. TCP port 514 must be open.
    
3. The user must have the same home directory on both machines, or the same .rhosts file.

The NORSAR-3D Common Shot Wavefront Tracer- Batch uses r-services to communicate with remote machines.

1. Check that rsh server is installed
   
   rpm -qa | grep -i rsh
   
   If not installed, install it. (It is not installed with the default installation of Suse.)
    
2. Enable xinetd
   
   /sbin/chkconfig --list xinetd
   
   Check that it says on for 3 to 5. If not:
   
   /sbin/chkconfig --level 345 xinetd on
    
3. Configure xinetd services
   
   cd /etc/xinetd.d
   
   Set disabled = no in rexec, rlogin, rsh
   
   These are server processes that are listening on TCP port 512, 513 and 514.
   
   Default: Suse off, RedHat on.
    
4. Start xinetd
   
   Reboot the computer or start using the script /etc/rc.d/rc5.d/S*xinetd

On Suse most of this can be done in yast2 inetd. On RedHat some of this can be done in redhat-config-services.

Visit the web site of your graphics card manufacturer to see if there are any updated drivers for your graphics card available. On Linux, use the command:

lspci | grep VGA 

to find which graphics card you have installed.

Due to an issue in Motif, files larger than 2 GB may not show up in some file dialogs. Please type in the file name manually.

Login using rlogin instead of su.

OpenGL is not supported by the regular version of Exceed. You need Exceed 3D to run NORSAR-3D.

When installing VNC, a configuration file is created:

/etc/vnc/config

In this file there is a line specifying a font registry:

-fp "catalogue:/etc/X11/fontpath.d,builtins"

This is based on the font settings at VNC install time.

These settings can be overridden in a file:

/etc/vnc/config.custom

If you create such a file and add the line:

-fp "catalogue:/nonexisting/path.d,builtins"

and start a new VNC server, you will only have a few fonts (the builtin ones.)

You no have one VNC session with a large set of fonts, and another with a much smaller set of fonts available. This means that even though the basic installation has all the fonts installed it is possible that the VNC session does not.

Possible solutions:

1. A local solution which will enable fonts on the local VNC session currently running:

xset +fp /usr/share/X11/fonts/misc

xset +fp /usr/share/X11/fonts/75dpi

xset fp rehash

   or...

xset +fp catalogue:/etc/X11/fontpath.d

xset fp rehash

2. A persistent solution:

Create the file: /etc/vnc/config.custom

Add the following line (if /etc/X11/fontpath.d is a directory containing symbolic links to existing font directories):

-fp "catalogue:/etc/X11/fontpath.d,builtins"

Then, restart the VNC server(s).

Check that fonts are loaded in the VNC session by running xlsfonts.

If (2) does not work correctly, you can add a comma-separated list of paths to directories containing fonts.dir files.

Note that the xset commands do not necessarily have to be performed as root user. By doing it as an ordinary user, the font settings will be valid for the user.