> Ok folks, after seeing so many complaints about bugs, crashes, features
> not working in the Windows version of VNC 3.3.6, I just have to speak
up.
> I took some time last year going through the various flavors of VNC
> trying to settle on one Windows version to work on. I finally decided
on
> RealVNC mainly because it's been ported to the most platforms. So, I
> spent several months fixing bugs (including the server crash bug) and
> making speed improvements. I've finally gotten it to a point where I'm
> happy with using it in a production enviroment and where I feel it
> competes performance-wise with Remote Administrator. It even
> out-performs UltraVNC on a LAN in my informal testing.
> My question is: Now what?
> I don't want to release it as RealVNC 3.3.7 or 3.3.6a or 3.3.6whatever
> since that's not my perogative and I have nothing to do with RealVNC, I
> DON"T want to release it as MyCompanyName VNC ver.1.0 because I don't
> want to support it or answer emails about it, but I still want everybody
> to benefit from the improvements and fixes I made. I got a note back
> from RealVNC saying they would take a look at it for possibly including
> it in a future release, but that could be months from now.
Mike,
I'm afraid I can't be more specific about a timescale for
including patches to the codebase until I know what those patches are, as
I'm sure you can appreciate.
If you're keen to release a patched version as soon as possible,
then I'd recommend taking up one of the offers of web hosting for it that
I've seen posted in reply to your message. If you also post us the
changes then as I said, I'll be happy to look them over for inclusion in
an upcoming release, so that they become part of the standard codebase.
Cheers,
Wez @ RealVNC
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
