> -----Original Message----- > From: Jordan Share [mailto:[EMAIL PROTECTED] > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > Behalf Of Andy Harter > > Sent: Wednesday, March 05, 2003 10:26 AM > > To: [EMAIL PROTECTED] > > Subject: VNC 3.3.7 released > > > > > > RealVNC is pleased to announce the release of version 3.3.7 of VNC. > > > > Binaries and source can be downloaded from the RealVNC website at > > http://www.realvnc.com/download.html > > > > This release is completely compatible with previous versions. It is > > primarily a bug-fix release, providing greater reliability and > > stability on > > Windows platforms. > > > > For full details see http://www.realvnc.com/3.3.7-release-notes.html > > Does anyone know if: > "Improved reliability of Windows VNC server on > multi-processor systems." > > means that the performance doesn't suck on multi-processor > systems anymore? > I'd not had problems with the service crashing on me (which > "reliability" > connotes, to me anyway), but it is /dog/ slow. > > I've installed it on our system, but, alas, it requires a > reboot to start it > up again, and it's a production machine, so I can't take it down.
I think if you don't use vnc, you can savely stop and shutdown the vnc services. Then update vnc and restart the services. That is, on Wnt based systems. DETAIL: I don't know if the installer does an automatic reboot. Correct me if I'm wrong but the only reason it can do so is to activate the file associations and start the services. The first one is already done with the previous install, the second can be done manually. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
