VNCviewer issues with Solaris 8

[CATHERINE BROLLE]

Hi,

I'm evaluating RealVNC for a work project, and I've run into a number of problems.

I am using the latest version, Enterprise Edition 4.1.9, on a trial license.  I have the Solaris version installed on a Solaris 8 SPARC machine, and the Windows version on a Windows 2000 machine.  The Windows machine is acting as the server.

During pkg installation on the Solaris machine, I got the following warnings:
Warning: /usr/openwin/bin/xauth is not in your path
Something regarding /dev/urandom and installing OS path 112438.  I tried installing this patch, and reinstalling VNC - same warning.
chmod: can't access /tmp/vnc.pam

I launch the viewer from /usr/local/bin/vncviewer.

If I attempt to connect to a PC that is not powered on, the application hangs (on the IP address screen) and I have to kill it with a Ctrl-C in the terminal window.

Once I connect successfully, if I try to resize the viewer window to a size larger than it was originally, it adds grey border to the new area (rather than actually resizing) pauses a moment, and then aborts.  The message in the terminal window is:
TXScrollbar.cxx:32: failed assertion 'limit_ > 0 && len_ >= 0 && len_ >= limit_'
Abort - core dumped

I can reproduce this core dump every time.

I installed the pkg as the root user, but logged in as sysadmin.  If I try to run the vncviewer from a terminal window as root, no problem.  As sysadmin?  Failed to save the key file, and failed to open identities files.  I checked the .vnc directory in the sysadmin folder, and it was owned by root, with the 2 files in the directory owned by root.  Was this because I installed the pkg as root, or because I first ran it as root?  I'm going with the latter.

If anyone has some tips on how to make this product more stable on Solaris, I'd greatly appreciate.  Not a single problem so far on the Windows server end.

Thanks!
Kate Brolle