Hello: This may be somewhat off topic, but if someone has an answer, I would much appreciate it.
I've been using RealVNC to help administer my Dad's computer (Windows XP) for about eight months now and it has been working nearly flawlessly. During the entire time, I've had the screensaver (on the server machine) disabled. Recently, I set the screensaver to 'Blank'... which is not properly a screen saver, I guess, but rather puts the screen into sort of a sleep mode. (I'm pretty sure Dad's monitor is still a CRT.) There is a setting in the RealVNC Server Properties (under the 'Inputs' tab) to 'Allow input events to affect the screensaver'. This has always been checked. After setting the 'Blank' screensaver, it appears as though connection via VNC is blocked when the screen is dark (or asleep ?). I'm now getting "Connection closed unexpectedly" errors immediately after (otherwise) successfully connecting to the server. Is this the expected behavior from this particular screensaver mode and/or would the same thing happen if I had the option (in XP's Power Options) set to 'Turn off monitor' after x minutes? Thanks. Peter B. ----- _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
