Hi.

Can some one show me how to install VNC on "i386 Solaris" platform? I
couldn't find the manual on line, it took me a day; but no thing done :(.
Thank you.

Phu


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, March 13, 2001 9:03 PM
To: [EMAIL PROTECTED]
Subject: RE: Screen Artifacts on W2K vncviewer

I've had the same thing happen on 1 of 2 Windows 2000 computers.  One is
perfectly fine and doesn't do that when I VNC into it.  The other always
leaves artifacts.  Like the screen lock.  after I input my password to
unlock the computer, the desktop comes up with the icons and taskbar, but
the image of the password input screen still remains  I haven't quite
figured out why that is either.  I am running 3.3.3r2 on both.

The only thing I can figure is maybe it has something to do with my new
video driver (it didn't use to do it on the one machine, but I recently had
to reinstall the whole computer and in the process I updated to a newer
video driver).

John

-----Original Message-----
From: Waltner, Steve [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 14, 2001 10:51 AM
To: '[EMAIL PROTECTED]'
Subject: Screen Artifacts on W2K vncviewer


        I've been using VNC to access our Solaris servers with good success.
We have also used it to connect to Windows servers with slightly less
success. The problems are slower screen updates and screen artifacts left on
all clients (Solaris, Windows, MacOS). The artifacts are from the client not
getting the full screen update. This hasn't been a real problem since we
only have a few Windows systems that we are serving with VNC.

        Today, one of our users started experiencing the same problem when
attached to our Solaris servers. The only real difference between this
person and all of our other users is that he is running on Windows 2000. The
screen artifacts are usually left when a window is unhidden and moved in a
single step. Selecting the "request screen update" fixes the problem, but
this happens often enough to make that workaround annoying. Any idea on what
to try. We see the same problem with both the AT&T 3.3.3r7 and TridiaVNC 1.4
releases of the viewer. We are running the AT&T 3.3.3r2 server on the
Solaris system.

--
Steve Waltner
LSI Logic
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

----------------------------------
Download ICQ at http://www.icq.com
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to