Everyone send me options on what you would like to see on an automated 
setup, and I will take a guestimate on how much time it would take me.  If 
it doesn't take much time I will set something up and make available at my 
demo web site. (Just setting up demos now).
At 11:17 AM 8/6/01 -0400, you wrote:
>This is a problem for me, too.  A number of our machines I control through
>VNC (Linux, Solaris, Win*).  For Windows, I still have some running ORL VNC
>3.3.3r9, some running TightVNC release and some TightVNC Preview.  I would
>like to upgrade them all to TightVNC preview or 1.2 when it comes out, but
>short of using VNC to install another controller package, then using that to
>upgrade VNC, then uninstalling it and switching back to VNC.
>
>Anybody out there have any ideas on how to do an automatic update or even
>manual like some other packages do?
>
>Ryan
>----- Original Message -----
>From: "David Brodbeck" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, August 06, 2001 10:36 AM
>Subject: RE: TightVNC vs regular VNC
>
>
> > My biggest problem is that the machine that it'd be most useful on is one
> > that we've shipped off to a site 1200 miles away, and something tells me
> > that I can't upgrade to a newer VNC while operating the machine via VNC.
>;)
> >
> > -----Original Message-----
> > From: Edric Bulalacao [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, August 06, 2001 10:14 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: TightVNC vs regular VNC
> >
> >
> > My findings were based on the latest preview source code of Tight
> > VNC...downloaded from www.tightvnc.com.  Indeed, if bandwidth is your main
> > concern, then go with Tight VNC and play around with the Custom and JPEG
> > compression levels and the mouse cursor thingie.  But in addition, you'll
> > need to consider the additional server resources that these options
> > consume...more CPU utilization and additional memory requirements per
>user.
> > ---------------------------------------------------------------------
> > 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
>---------------------------------------------------------------------
---------------------------------------------------------------------
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