Any plans to release soon UltraVNC 1.0.3

[raindrop]

Like many other Vista users
I hope to hear the schedule date for the new release

I will appreciate any information, including info regards beta version

[mod=494,1214744117]moved from new to general help, this not a news ![/mod]

[hbruun]

The news note on the front page of the site says:

April 10 2007 v1.0.3 & Vista support soon

Vista patch is almost finished

Any chance that we could get a sneak peek at that new release?

[crisco]

The news note has been saying this for almost a month now, all they do is change the message from time to time.

Don't get me wrong, ULTRAVNC is hands down the best VNC product available and I really do appreciate the work that these folks do. Let's face it, without ULTRAVNC we would be paying the butt holes at REALVNC because they won't build VISTA compatability into the free version, but a little information would be real helpful.

[mattice06082]

Please understand that the developers have full-time jobs and do this in there free-time.

[crisco]

That is well understood and I have already stated my appreciation but your response seems to be the "standard" in this case, and if you read my previous comment I was not asking for a release just a little information. I like others who appreciate very much what these hard working developers do am only asking what ULTRAVNC's definition of Imminent, soon and almost is.

[DeathAndPain]

Yes, and while I also understand that the developers have only a limited amount of spare time, I wonder how long it takes to fix a few bugs. I mean, v1.02 has been out there for a year now, and as far as I understand, v1.03 is supposed to be a bugfix only (no new features aside from Vista compatibility). I mean, there are lots of well-documented and reproducable UltraVNC 1.02 bugs (some are even in the "to be fixed in v1.02" list that originates from v1.01 times, and fixing a reproducable, well-documented bug is typically but a matter of an hour or two. (Example: mouse cursor disappearing in UltraVNC viewer until it changes shape)

But even if the developers took one week to fix a single bug (all developers together against a single bug: that should not be much work for a week's time), then 52 bugs should have been fixed until now, which would well justify releasing a new version. But instead, nothing happens. NOTHING. A news entry every two months, that is pretty much everything. Without those entries, I would consider the whole project dead.

I mean, there are 3 official developers on this. In order to fix one bug per week for thw whole team, each of them would only have to fix one bug every third week. If they do not have enough time to do that, then they are not really involved in the project anymore, IMHO.

[UltraSam]

Well, you are wrong, this project is far from being dead.
That's not because few CVS updates are done that's there nothing happening on our machines...

We gonna release test v1.0.3 binaries on this forum to get feedback on Vista compatibilty
We are currently compiling the binaries and preparing the zip file.
(CVS was updated yesterday with some of the modifs for v1.0.3)

v1.0.3 is mainly a Vista compatibility update, and not a bugfix update (ok, it also include the v1.0.2 test2 patch that fix some connection stability bugs)

There are still a lot of modifs in the pipe but not compeletely working yet (Multithread DSM plugin support, new background FT code...)
We plan do do a bugfix campaign for v1.0.4 version, which should take less time than v1.0.3 to be released, if all goes well.

[DeathAndPain]

I know there is nothing to be demanded from a freeware project, so consider the following but my opinion, but I feel the need to state it anyway.

• That bugfix campaign is overdue since 1.01 (several years...). What is the point in adding new features (Multithread DSM plugin support...) when even the existing ones do not work properly? That is the approach of commercial software manufacturers that need something to advertise with but know that their customers will not discover the countless bugs before they have bought the product and paid the money. However, freeware projects should follow a more idealistic approach and focus more on perfection.
• Minor remark: Choosing a new version number two digits behind the decimal point is inappropiate for a new version that contains new features. You should name it 1.1.0 instead (the trailing zero indicating that this version still includes all the new bugs that came with the new features). A change two digits behind the decimal point indicate only a minor bugfix release.
• UltraVNC still suffers from the bug that the V-icon is not displayed in the taskbar when you install on Windows as a service and have not rebooted yet. Not a grave bug; rebooting once will help, but look: it used to be in the root code that all VNC variants are based upon, but was fixed in TightVNC 1.2.9, and how old is that archaic version? 5 years?
• I understand that tracking down bugs that only occur once in a while, with certain configurations (which are possibly not available to the developers) and only for certain users can be time-comsuming and frustrating, so I understand that dealing with such bugs is sometimes postponed. But hey, I am a programmer myself, and fixing a bug that fulfills both criteria "reproducable" and "well-documented" is but a laugh time-wise, and lots of known UltraVNC 1.02 bugs fulfill these requirements! You are free to leave the thorough testing of your bugfix to the community if you are low on time. They will kiss your feet to be allowed to do it for you!
• If something is happening on your machines, then why don't you share it with your fans for a full year!? If you have already fixed half of the bugs after a few months, then why not make it available as a minor bugfix release? If you are unsure concerning its stability, well, declare it a Release Candidate, and the community will be quick to find out and let you know. There is no need to do the stress-testing all by yourself.

Again, I am aware that you are not being paid for this (other than through donations), but nonetheless you should be honest: either you are willing to run this project properly, or you are not.

[UltraSam]

Thanks for giving us your opinion...
Things can always been improved, I agree.
I also agree that few bugfixing has been done and pushed on production the past 6 months. This is mainly of my fault. I just had no time for it.
But believe it or not, I'm still involved in the project.

FYI, Multithread DSM plugin support is not a new feature, it aims to fix a big bug. Same thing for the better FT background transfer.

We have always been open to bugfixes and new features integration into the UltraVNC source tree.
People that have helped the project (code, test, tech support) have generally been credited and thanked for their contribution.

As you seem to exactly know what is good and what is not, feel free to submit us some bugfixes or source code.
That's actually the best thing to do if you really want the project to improve.
If you help, I swear that we will carefully choose the version numbers to comply with your recommandations...
If you do, or if you decide to test our bugfixes/features, one condition though: do never try to kiss my feet

BTW, I've no problem with my honesty.

[Rudi De Vos]

Last 1 1/2 year about 80% of the request where for SC and PcHelpware,
more people seems to use the derivates then the full UltraVnc.

I devoted all my free time on that, so Sam was to only one working on
UltraVnc...

After we released 1.0, now a long time ago, we ask developpers to join the team and contribute, bug fix. All there fixes and contributions where added...so nothing at all.

Even having a day time job and running some commercial projects, we where still able to spend an average of 1-2 hours a day on UltraVnc, SC..

Reading such negative reactions i will ask Sam to postpone RC103 until
next month or chip it only to users who ask it nice.....just my 2 cent.

[Rudi De Vos]

You'r lucky... they are already online

[UltraSam]

So DeathAndPain can start testing right now and submit us some new bugs

[redge]

[topic=10763][/topic]

[redge]

uvnc 103 cancelled...
uvnc 104 stable coming soon, I hope.

[X3]

uvnc 103 cancelled...
uvnc 104 stable coming soon, I hope.

that has my vote I cant wait for Rudy & Ultrasam ro fix those pesky little bugs that cause viwer to disconnect on 104RC13 mean while rc12 it is...

/me goes back to corner and waits for 104 stable!

[redge]

still exist fews bugs to fix before release UltraVNC 1.0.5

major bug ---> dsmplugin under Vista (crash after fews hours)

minors bugs
[topic=12710][/topic] <-- fixed update 26 June 2008
[topic=12711][/topic] <-- fixed update 26 June 2008
[topic=12681][/topic] <--fixed update 16 June 2008
[topic=3870][/topic] <-- fixed update 26 June 2008
[topic=7038][/topic] <-- fixed update 26 June 2008

[X3]

theres quite a few more and the more they fix the more we find...

Thats gotta be a developers nightmare.

Plenty options on right click window frame on a connected viewer window do not show as selected...

Too many to mention or is it me?

Not just View only as reported in other topic.

Refresh screen is slow in some cases no individual scenario isolated.

thats within lan/wan.

[redge]

> Refresh screen is slow in some cases no individual scenario isolated.

known limitation of capture alpha-blending setting of winvnc admin properties
+
webpage with flash could increase slowdown the remote and heavy CPU usage

work around:
use ultravnc server mirror driver