VNC Service stops
Sun Nov 30 17:26:01 2003
> Greg - it's a known bug in WinVNC 3.3.7 and derived code. That's why
> you should upgrade to VNC 4b4, which is the latest release and doesn't
> have that bug.
How is it a known bug? Where are the bugs listed? What does it take
to recreate it? I been using 3.3.7 for a while and have not seen it
happen to me.
About going 4b4, it is a beta not a release. Installing unfinished
code in a production enviroment is just "bad form". Besides your
website pushes 3.3.7 as of 2 hours ago, so how is 4b4 better? Why is
3.3.7 being pushed and not warning the user of this issue failing
What will it take to prove the 3.3.7 bug does not exist in 4? How
long before the 4b4 is a release?