UltraVNC

Thinking about it, I'm going to implement it as a DLL, If anyone has security concerns, they can remove the DLL, and the caller should be able to handle it's absense.

I didn't #ifdef stuff. I just compiled, and fixes the compiler errors, the quickest way possible, just to get it to compile. I fixed some of the easier warnings about deprecated CRT stuff, the rest I left alone...

I will knock up a Firewall control EXE , should be easy enough, take either remove or ...

Looks interesting...

Special if we could add it as seperate app with the installer.
Firewall_control check registry vnc settings and open correct ports when you click.

Firewall control direct from vnc could trigger some spyware checkers.
If we add it direct in vnc, it need to be possible to ...

I have done some modifications to UltraVNC, so it can control the Windows XP SP2 firewall, create exceptions for itself (and remove them when it closes).

Is this usefull to anyone? It is for me, as I always forget to create firewall rules, then wonder why I cannot connect!!!

Anyway, I have ...

I should be able to modify the INF files to install the correct drivers for the correct platforom, so having I single zip file containing 1inf, with drivers for each.

Thanks I got the files, but they are IA64 binaries, not AMD64 (x64) binaries, and are incompatible.

If you get a chance to do AMD64 versions, that would be great (AMD64 x64 is the more common 64bit platform).

Thanks

Any chance of a 64bit driver for Windows XP x64? (32bit drivers are no good).

Dunno if this means a 64bit server is required... (unsure if 32bit apps can talk to 64bit devicedrivers).

Anything needing a test 64bit enviroment, I am happy to offer mine..

Unfortunatly, adding the debug option does bring up the window, but when it crashes, the debug window disappears before I can catch it...

Can we have a version where the debugging is output the standard debug streams, so sysinternals debugwin can see it? OutputDebugString(""); should be sufficent ...

Hmm, just tried recreating my sc exe using the 1.0 version posted, and it does the same, exits shortly after attempting to connect.

is the new version posted? (I do have the driver installed BTW).

Ahh, so the code that gets entered, determines which connection [HOST] is used? Is this it's purpose?

If i know the purpose, perhaps I may be able to explain it better...

I did read that, but it did not make much sense to me

Perhaps I am not quite understanding the point of the connection ID.

I was assuming that this could be unique to each user, so I knew who was requesting the incoming connection. By the looks of it, I need to "hard code" the ID into the helpdesk.txt. Surely this means it's nothing more than an ...

Hmm, can't get much sense out of this one.. It dies when you try to connect... Anyone else seeing this?

Also not sure where the enter.bmp is shown. Do you have a screenshot, or an example graphic?

had the option of RC20 or RC23, will there be a 1.0 version sometime?

Not really important, and can certainly wait until post 1.0, but in the file transfer dialog, it would be nice if the volume labels were shown. I have lots of drive letters, but identify them in Explorer mainly by the volume label.