-- Hello, I've seen a few similar posts, so here's my $0.02.
I have two Compaq AP550 machines (2 CPUs each) running Windows 2000 SP3 with IE 5.5 and miscellaneous updates, and RealVNC 3.3.6 running as a service. As far as I know, device drivers are up-to-date. On both machines, winvnc.exe is frequently crashing with an access violation. The crash always occurs when I am trying to connect to the VNC service, usually just after I have entered a password. Crashes tend to occur after the VNC service has been running for a couple of hours. If I try to connect just after the service has restarted, I am generally OK. I have collected Dr Watson log files and WinVNC debug logs (debug level 12), which are available at the URL below. I also have Dr Watson's crash dump - I just can't post it publicly since it may contain passwords. http://www.mbrecknell.plus.com/vnc/ Some notes on the WinVNC log: 15:01 - I restart the VNC service after the previous crash. 15:12 - I connect successfully, log in, and disconnect about 30 seconds later. 17:10 - I attempt to connect, enter a password, and the VNC server crashes. As a work-around, I've set Win2K to automatically restart the VNC service whenever it exits, but I'd be interested to know if anyone has any other ideas, solutions, or similar experiences. Regards, Matt -- We've located a serious problem with the region-handling code in Win32, so we've switched to another method. If people are seeing the WinVNC server crash randomly or stop running without warning then I can send them a debug build to try, which uses the new region code. Cheers, -- Wez @ RealVNC Ltd. - http://www.realvnc.com Open Source VNC - Commercial Support & Development _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
