headers
Mike Smith | 1 Feb 2003 06:34

I fixed the bugs and sped up VNC 3.3.6 . . . what next?

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.

So, does anyone have any suggestions?

- Mike
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
http://www.realvnc.com/mailman/listinfo/vnc-list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jordan Share | 1 Feb 2003 07:47

Re: I fixed the bugs and sped up VNC 3.3.6 . . . what next?

I'd just compile it, put it on a website, and post the link.  Heck, if 
you'd like, I can host it for you (though I only have 110 kilobytes per 
second of upstream, but that's 3/4ths of a T1, so...not too bad).

There's no reason not to make it available, and no reason to feel that that 
would require anything more from you (as far as support, etc.)  You've done 
enough.

Ideally, the maintainers will incorporate your fixes.  If not, you have 
still given back to the community.

A desire to avoid responsibility (no negative connotations intended, 
whatsoever) should not preclude you from sharing your code.  Just call it 
"nonameVNC" and post the binaries (and source, naturally).

Jordan

At 09:34 PM 1/31/2003, Mike Smith wrote:
>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.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Geoff Harris | 1 Feb 2003 11:06

Re: I fixed the bugs and sped up VNC 3.3.6 . . . what next?

I agree with Jordan. VNC is a very useful tool. If you have
made something good, better, and you are willing to share
your hard work, but due to commitments can only make it
available on the terms that you have clearly laid out, I do
not think your colleagues will have a problem.

Take Jordan up on his offer, I will download it.

If you could at least, very briefly, sumarise changes so
that a sensible decision can be made as when to return to a
'standard' release.

Someone may even start a list! Your offer [without getting
too emotional] restores faith in human nature.

Geoff
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
http://www.realvnc.com/mailman/listinfo/vnc-list
Permalink | Reply | 0 comments |
headers
Carl | 1 Feb 2003 12:55

Re: I fixed the bugs and sped up VNC 3.3.6 . . . what next?

Mike,

You can just release it as AnotherVNC and specify, *AS IS - NO SUPPORT - USE
AT YOUR OWN RISK*.  Those that want it will try it those that don't won't.

You may want to send your code to RealVNC in case they want to look at it.

Carl

----- Original Message -----
From: "Mike Smith" <mike <at> coyoterd.com>
To: <vnc-list <at> realvnc.com>
Sent: Saturday, February 01, 2003 12:34 AM
Subject: I fixed the bugs and sped up VNC 3.3.6 . . . what next?

> 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.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alan Hourihane | 1 Feb 2003 13:41
Picon
Picon

Re: I fixed the bugs and sped up VNC 3.3.6 . . . what next?

Why not send the code here to the list and then those who want to add
it to their vnc offspin can.

Alan.

On Sat, Feb 01, 2003 at 06:55:41AM -0500, Carl wrote:
> Mike,
> 
> You can just release it as AnotherVNC and specify, *AS IS - NO SUPPORT - USE
> AT YOUR OWN RISK*.  Those that want it will try it those that don't won't.
> 
> You may want to send your code to RealVNC in case they want to look at it.
> 
> Carl
> 
> ----- Original Message -----
> From: "Mike Smith" <mike <at> coyoterd.com>
> To: <vnc-list <at> realvnc.com>
> Sent: Saturday, February 01, 2003 12:34 AM
> Subject: I fixed the bugs and sped up VNC 3.3.6 . . . what next?
> 
> 
> > 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
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Argence | 1 Feb 2003 15:41
Picon

unknown IP adress of the computer used to remote control another one

How can I do to :

Remotly control my office computer from my home computer if
when I leave the office, I don't know wich will be the IP adress of my home
connection ?

Thank you for your help

all instructions in english, not easy to me...
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
http://www.realvnc.com/mailman/listinfo/vnc-list
Permalink | Reply | 0 comments |
headers
Jerry McBride | 1 Feb 2003 21:10
Picon

Re: I fixed the bugs and sped up VNC 3.3.6 . . . what next?

On Fri, 31 Jan 2003 21:34:51 -0800 Mike Smith <mike <at> coyoterd.com> wrote:

> 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?
> 

Run diff across your source and submit your fixes to the RealVNC team for
inclusion in future releases.

--

-- 

******************************************************************************
                     Registered Linux User Number 185956
          http://groups.google.com/groups?hl=en&safe=off&group=linux
             Join me in chat at #linux-users on irc.freenode.net
     3:17pm  up 24 days, 20:51,  2 users,  load average: 0.07, 0.06, 0.00
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
Carl | 2 Feb 2003 05:27

Re: unknown IP adress of the computer used to remote control another one

Create an account with something like dyndns.org or the vnc dynamic ip
setup.   You run the IP update client on your PC and it will update the
dynamic dns service with your new IP whenever it changes.

Then your home PC will be something like:  yourdyndnsaccount.dyndns.org.

Carl

----- Original Message -----
From: "David Argence" <david.argence <at> wanadoo.fr>
To: <vnc-list <at> realvnc.com>
Sent: Saturday, February 01, 2003 9:41 AM
Subject: unknown IP adress of the computer used to remote control another
one

> How can I do to :
>
> Remotly control my office computer from my home computer if
> when I leave the office, I don't know wich will be the IP adress of my
home
> connection ?
>
> Thank you for your help
>
> all instructions in english, not easy to me...
> _______________________________________________
> VNC-List mailing list
> VNC-List <at> realvnc.com
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joseph J. Greenberg | 2 Feb 2003 07:19

real IP address in log

I have a router which I am using to foward requests on port 5800 to a specific
machine on my local network (with a local IP address). The log is telling me
that for all connections, the IP of the incoming machine is 192.168.x.x, which
is the IP of my router. Any way to get the real IP of incoming connectns?
_______________________________________________
VNC-List mailing list
VNC-List <at> realvnc.com
http://www.realvnc.com/mailman/listinfo/vnc-list
Permalink | Reply | 0 comments |
headers
Mike Smith | 2 Feb 2003 09:31

My WinVNC 3.3.6 patches now available!

Here is the bug-fixed, speed improved, patched WinVNC version 3.3.6
executables and source code.  In accordance with the GNU GPL:

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

DISCLAIMER:  Except for copyright notices, identifiers in the executables to
RealVNC, the company, have been removed so as to avoid confusion with their
official WinVNC version 3.3.6.  The programs released here have nothing to
do with RealVNC the company.  Please note that if you want to use or
distribute a RealVNC program, you MUST go to the RealVNC.com website and
download software from there.

There is NO support for these files, not by email, phone, or mailing list.
Any attempts to obtain support from me will be met with stony silence.  Use
these files at your own risk!  Downloading these files constitutes
acceptance of these terms.

Win32 Executables:  http://www.coyoterd.com/WinVNC-336-patched-exe.zip

Win32 Source:  http://www.coyoterd.com/WinVNC-336-patched-src.zip

To install the executables:  Unzip and copy the files somewhere, run
(Continue reading)

Permalink | Reply | 0 comments |

Gmane