ChunkVNC Upcoming Features and Requests

[supercoe]

I'll look into screen recording since you're not the first one to ask for such a thing. I do recall it being difficult with the repeater in the mix but we'll see.

On my recent test builds I've been able to remove unneeded resources from the winvnc.exe file greatly diminishing its size. My test InstantSupport.exe is 1.1mb.


Thanks for the compliment!

[guinness]

Do you have any recent builds you might be able to upload to GoogleCode?

[supercoe]

The code I have right now is a garbled mess as I was just testing a theory here and there. It's been a while since I've looked at it so I was thinking of just tossing it out the window and starting fresh again.

Now that summer is over I'm starting to get more time for my projects and ChunkVNC is getting close to being a priority again.

[guinness]

Excellent! In the mean time I have been learning a lot about AutoIt and the best practice in reducing the file size, also started to get into WM_NOTIFY and WM_COPYDATA!

[gottoon]

You might want to add the "-multi" switch on the winvnc command string. Just incase there remote system has a WinVNC already running.

Just another Dialog box to suppress for the end user.

[supercoe]

Thanks for the tip, I didn't realize this option even existed!
I'll do some testing and hopefully implement this because it would be a great feature to not have to close other VNC servers.

Thanks again.

[supercoe]

Maybe -multi doesn't work the way I want it to.

Here is what I did:

1) Run tightvnc server as local user and connected a viewer to it.
2) Modified InstantSupport to use the -multi switch for it's repeater connection.

The UltraVNC server being started with the -multi switch never makes the outgoing connection to the repeater.

It does seem to suppress any messages stating that another VNC server is running.

The UltraVNC server process that InstantSupport spawns stays open while the TightVNC server is running. It seems to react normally.

It doesn't seem to matter whether TightVNC has a viewer connected, just simply having it running prevents the UltraVNC server from making the outgoing connection.

I've tried this on Vista32 and XP.


I was hoping -multi would allow the UltraVNC server to make an outgoing connection to the repeater while another VNC server is running.


Correct me if I'm wrong, the reason I must have looked over this command is that I thought the VNC protocol only allowed one server per user session?


On a positive note, I did find out that the sending the -kill command closes both VNC servers.

[Pedja]

Is there a possibility to record ID's making them fixed for remote users. That would help a lot.

[supercoe]

Pedja,

I don't quite understand what you mean about "recording ID's", could you elaborate more on how you want it to work?

Installing InstantSupport as a service already allows you to choose an ID number.

[fedriani]

First of all, congratulations for the software, I've been using it a few months and truly is fantastic. One option could be added would be the end to make the application in remote and count the time that has been connected with our client. I mean, once we provide the connection code in the log to save time and sign-off once again add to this log to account for time used. Sorry for my English, I use a translator.

[supercoe]

Thanks for the suggestion, I'm not sure how I feel about time tracking support at the moment. I might add it in the future but for now you'll just have to look at the clock.

[guinness]

I found this >> http://www.autoitscript.com/forum/topic ... ollection/ which contains the DES Encryption Algorithm. Therefore you might be able to do away with the dependency of vnc_hash.exe and code in pure AutoIt.

Extra Details: http://www.vidarholen.net/contents/junk/vnc.html

[supercoe]

I was going to do away with the 8 char limited VNC password all together. Instead I will just automate the SecureVNC password creation. Much more secure this way and no need for all the extra dependencies.

[guinness]

That would of course be better!

[Cuatroporte]

periodically checking the SVN SourceCode trunk is definitely the best thing to do!

[B]

Pardon my bluntness, Cuatroporte, but you seem like a spammer. What SVN source code trunk are you talking about?

[supercoe]

Possible spammer but there is this: http://code.google.com/p/chunkvnc/

[B]

Ah, nuts! My apologies to Cuatroporte then. I did look for a repository link at chunkvnc.com but didn't find it. Thanks, supercoe.

[supercoe]

I've been considering retiring that repository so I removed the links, you've been the first to notice.

[B]

So you don't actually use that as your primary development vehicle? How up to date is it? Should forkers/contributors just be downloading your latest versions?

[supercoe]

Downloading the latest release is the best bet, there is really old code in google that was just me testing some ideas but I doubt it would be useful for anyone.

[MikaelDB]

Hi,

It took some time for me to understand how I was supposed to use this software, probably due to that English is my 2nd language...

But when I saw the 6 digits of code on my screen I knew that this is the software I'm going to use.

Some feature requests:

I would love to see ChunkVNC at github (:
Docs, or someway to contribute with them.

\\Mikael

[supercoe]

I'll look into github as an option, thanks for the info.