"Classic VNC" and TightVNC are fully compatible among themselves. You may upgrade each VNC when you want, and in whatever order you wish. All you be able to do is use the Tight Compression unless both ends ( Client and Server ) have TightVNC on them.
Gustavo Wagner ----- Original Message ----- From: "Ronald W. Heiby" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 09, 2002 7:05 PM Subject: Upgrade -- VNC to TightVNC > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello vnc-list, > > I have installed VNC "Classic" (3.3.3r2) onto several machines. I have > a few Linux servers. I have a few Windows (98, ME, and 2000) servers. > I have also installed the corresponding clients, though I believe that > only the Windows version clients are in any sort of active use. > > Now, I've found out about TightVNC. Looks cool. Looks like it > addresses some of the things that have been annoying us. > > My question is this. Do I need to have a "flag day" where I replace > *all* of the VNC "Classic" servers and clients with TightVNC servers > and clients. Or, can I replace them in any order I want at any time I > want. Or, must I replace all of the servers first, then all of the > clients. Or, must I replace all of the clients first, then all of the > servers. Or, ???? > > Thanks! > > Ron. > > -----BEGIN PGP SIGNATURE----- > Version: PGP Personal Privacy 6.5.8 > Comment: The last PGP with full source disclosure. > > iQA/AwUBPVQ8am8pw+2/9pUJEQJh5gCg+HgA9Hf2CmMRUiLbrjDqtTBEzJ8AnRtd > CdIZ4eKScerhpouiPXAKlh6s > =ad+9 > -----END PGP SIGNATURE----- > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
