ETA on 4.0

[ich]

....I'm so happy

B
That particular thread shows that you've been having some serious problems and I've always had great results with UVNC, maybe you're just jinxed. I've been using it (in corporate environments as well) since version 1-RC4 without seeing as many problems as you are (BTW, Rudi kept adding functionality to the initial program and I think he hit RC18 before he ever released version 1)

Hang in there, this is a great product and, with the cool Chunk stuff SuperCoe has added, it's an awesome support tool.

[supercoe]

Thanks ich, it's nice to see others have good luck with ChunkVNC.

Yes, development underway again, not that it ever stopped I was just super busy with work.

[ich]

Not sure where else to put this so I'm taking a shot and sticking it here.

I'm getting more and more multi-monitor clients and I've had intermittent issues with not being able to click on stuff. Appears to be a <0 check or something as Rudi describes over here [post=69780][/post]
I'd really like to get the fix incorporated into the next Chunk, but it appears to be an unofficial/unversioned fix that Rudi tossed out and I don't know how you all feel about that.

Speaking of the next Chunk: I may be showing how old I am here, but there were some old Mervyn's Super Sale commercials where the lady is in front of the store at like 4 AM, nose pressed against the glass, chanting "Open, open, open!" Anyway, that's kinda how I feel about Chunk 4...

[Rat]

Geez Ich!

If you really can't wait then have a play with this...

"http://www.vuware.com/chunkvnc/ChunkVNC_3.1f.zip"

Don't forget to provide some quality feedback!

Also if you know how to run a Perl Script on your server, (or even your web host's server if they allow Perl) then have a look at this too...

"http://www.vuware.com/chunkvnc/ultravnc_repeater.zip"

This is a slightly modified version of Karl Runge's brilliant ultravnc repeater perl script which will accept command-line arguments making it simpler to run on shared hosting servers. It also appears to be bug-free and supports multiple concurrent sessions even ones sharing the same ChunkVNC ID code.


Cheers,
Rat.

This Zip file includes all of my source code and also a Windows installer, "ChunkVNCRemoteSupport_Install_3.1f.exe". I suggest you run the installer in a virtual Windows machine and see the new entries it creates in the Start menu. The Installer includes some 0 byte length placeholder files which must be re-created post-installation by running a compiler-compiler executable that you are prompted to run at the end of the installation.

The InnoSetup script for this installer is also included: "ChunkVNCRemoteSupport_Install_3.1e.iss". This script provides a lot of clues as to how the whole thing works.

This is a fairly major departure from the original v3.1 base code.

It supports a considerable amount of customisation which I use when creating re-branded Remote Support utilities for myself and my clients. You can view some examples at the following links:

www.vuware.com/remote.html
www.vushield.com/remote.html
www.xbase.com.au

This high level of customisation is responsible for some of the (unusual) naming conventions I employ. e.g. In the file "ChunkVNCSupportDefs.au3" I have the following lines:
$InstallerIcon = 'InstallerIcon.chunkvnc'
$ServerIcon = 'ServerIcon.chunkvnc'
$ViewerIcon = 'ViewerIcon.chunkvnc'

In this instance the "chunkvnc" suffix would be replaced with a different moniker depending on the target. And of course the file "ChunkVNCSupportDefs.au3" would also be renamed to "<TargetName>SupportDefs.au3" and so on.

[ich]

Damnit Rat, I just lost an hour when I should have been doing other things.

QUIT GIVING ME COOL STUFF TO PLAY WITH!!

Wait, never mind, I retract that.

Very cool stuff in the works!

[supercoe]

I've been having the same problem with Rat, DAMN YOU!

[lupick]

any news?? Is the development stopped?

L.

[Rat]

No its definitely not stopped, In fact its accelerating. We just aren't releasing anything at the moment. I have recently, (in the past week) added the following functionality to an upgrade to my current v3.1g version which is to be merged with Chunk's v4.0:

1. "Minimise/Maximise to system tray.
2. Configurable Connection Timeout.
3. Optional Hide on Connect.
4. An auto-connect option, (in v3.1g this is the only available mode), to support a manual "Connect" Button.
5. An optional user defined list of technicians and associated ports.
6. An option to "de-chrome" the window so that no title bar or border is shown.
7. Background monitoring of connection status.

I spent most of today attempting to use the Perl PAR Packer to convert (a slightly modified version of), Karl Runge's VNC repeater script into a standalone Windows executable. I almost got there... but the "setpgrp" function is not implemented in Strawberry Perl, so I have appealed to Karl for help. My goal is to provide this as an alternative executable to the UltraVNC repeater used in ChunkVNC which is a bit flakey, (I personally just run it as a Perl script on my web host see here: [topic=18106][/topic]).

So please be patient... its coming and in the meantime download v3.1g, (see here: [topic=17342][/topic])

Cheers,
Rat.
^//>o

[guinness]

What do you think of the V2alpha that was released this week?

[sf2]

Also if you know how to run a Perl Script on your server, (or even your web host's server if they allow Perl) then have a look at this too...

"http://www.vuware.com/chunkvnc/ultravnc_repeater.zip"

[/quote]

Rat,

I have a shared hosting account that doesn't have shell access and have been looking for something like this for my low use needs.

I didn't need to modify the script because Perl is located in the path that is specified.

I uploaded the script, changed the permissions to 755 and am running it as a CRON job.

/usr/local/bin/perl /home/myaccount/public_html/cgi-bin/ultravnc_repeater.pl -L BG -c 5909 -s 5505 -l /home/myaccount/public_html/log/repeater.log

Initially the log had entries that the standard ports were in use so I changed the script to use other ports.

I recompiled entering the new ports. I have the client and server on two different networks. A netstat -ano shows each is connecting to my website IP on the proper port. The viewer eventually times out with "failed to connect to server".

Any ideas on how to troubleshoot this?

Thanks

[B]

Most likely it's the 1.0.8.2 repeater issue. The 1.0.8.2 version of UltraVNC server, bundled in most ChunkVNC packages, does NOT work properly. After an hour or two it stops working. You can, however, drop a working 1.0.8.0 in its place. Described at [post=70930][/post] and elsewhere.

[bunger]

Does anyone know when 4.0 will be released? We have been running v3.1 in a testing environment, waiting to go production when v4 is released... but it has been a little while...

[B]

Only supercoe knows. He did just say that he's going to release a "maintenance 3.2" release first though.

[post=71226][/post]

[Zyxyx]

Quick questions :

Any news for the next version of ChunkVNC or "ChunkVNC Fork" or, hopefully, a combination of these great tools ?

Is there any specific reason why the Google Code initiative didn't work so well after all for a better centralization of the efforts of the ones involved ?

Do you plan to release this ChunkVNC 3.2 [post=71226]maintenance release[/post] to fix a few known bugs and remove the need for closed source files... and maybe integrate the new UltraVNC 1.9.0 ?

Zyxyx

[supercoe]

Any news for the next version of ChunkVNC or "ChunkVNC Fork" or, hopefully, a combination of these great tools ?

Good news, even Duke Nukem Forever is coming out!


Is there any specific reason why the Google Code initiative didn't work so well after all for a better centralization of the efforts of the ones involved ?

It came down to time with me, business is a priority.

Some developers were added to the project because of their experience in adding new features to customize for their specific needs. Since my vision is to remain simple and elegant most of those features couldn't be added.

I was really hoping for someone to step up and take over the project while I could just oversee it. Many offered, none came through. It had nothing to do with lack of ideas or motivation, it's always about the limited hours in a day.

Maybe I expected to much, the original idea was for people to be able to customize ChunkVNC themselves as they saw fit. Then again even batch files scare some techs.

I've always made sure to take time out of my day to come here and answer questions so until that stops consider ChunkVNC work in progress.



Do you plan to release this ChunkVNC 3.2 maintenance release to fix a few known bugs and remove the need for closed source files... and maybe integrate the new UltraVNC 1.9.0 ?

I don't make plans anymore as they just seem to lead to broken promises but I'm checking out 1.9 today as I didn't even realize it had been released.