Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Programmer needed for VNC project - fame and fortune
Programmer needed for VNC project - fame and fortune
Hi all - I'm looking to have a silent install package built around UltraVNC. No splitting the atom, just an elegant wrapper around existing technologies.
I've posted a request on rentacoder.com, but figured there might be some folks here that might be interested in the project as well. Here's a link to the bid: http://www.rentacoder.com/RentACoder/mi ... tId=191436. High level description follows. Please PM me here (or email joe at presto dot org) or register on their site if you're interested.. thanks!
----------------
These customers are mostly individuals, behind routers, so the connection must be initiated from their end.
Here’s an outline of the process.
Customer calls for help. I provide either a link to a download or email them a small executable. (500k or less)
Executable unpacks, runs, and pops up a terms and conditions page that they must agree to.
Customer enters a ticket number and zip code. Executable queries a web service, which returns with either a "FQDN:port" which it dials out to, or a "fail" response which blocks any further action and triggers an uninstall.
It will connect to my VNC client, which I’ll have listening.
When complete, I’ll click on an icon in the system tray (which is on the customer/server side) to trigger a close of the session and a complete deinstall of the product. This icon can be triggered by customer as well if I lose connectivity.
Other notes:
- Encryption is required (available by plugin to VNC). Any dependencies on OS encryption packs should be stated
- Code ownership will be transferred to me
- Not particular about language, other than it being small and not have any dependencies.
- This should support Windows 98 and up
- Rebooting during the process should be possible (once rebooted, the server/customer side should automatically try and reconnect)
- UltraVNC preferred, but other flavors fine
- Incoming connections to the server/client should be disabled
I've posted a request on rentacoder.com, but figured there might be some folks here that might be interested in the project as well. Here's a link to the bid: http://www.rentacoder.com/RentACoder/mi ... tId=191436. High level description follows. Please PM me here (or email joe at presto dot org) or register on their site if you're interested.. thanks!
----------------
These customers are mostly individuals, behind routers, so the connection must be initiated from their end.
Here’s an outline of the process.
Customer calls for help. I provide either a link to a download or email them a small executable. (500k or less)
Executable unpacks, runs, and pops up a terms and conditions page that they must agree to.
Customer enters a ticket number and zip code. Executable queries a web service, which returns with either a "FQDN:port" which it dials out to, or a "fail" response which blocks any further action and triggers an uninstall.
It will connect to my VNC client, which I’ll have listening.
When complete, I’ll click on an icon in the system tray (which is on the customer/server side) to trigger a close of the session and a complete deinstall of the product. This icon can be triggered by customer as well if I lose connectivity.
Other notes:
- Encryption is required (available by plugin to VNC). Any dependencies on OS encryption packs should be stated
- Code ownership will be transferred to me
- Not particular about language, other than it being small and not have any dependencies.
- This should support Windows 98 and up
- Rebooting during the process should be possible (once rebooted, the server/customer side should automatically try and reconnect)
- UltraVNC preferred, but other flavors fine
- Incoming connections to the server/client should be disabled
that should be easy for more than several in here, but something i doubt are whether the term
- Code ownership will be transferred to me
will satisfy the GNU Public Lisence in case you aren't planning to open the source code, and whether you can include the video driver in your package if you want it as how you chose Ultr@VNC.
- Code ownership will be transferred to me
will satisfy the GNU Public Lisence in case you aren't planning to open the source code, and whether you can include the video driver in your package if you want it as how you chose Ultr@VNC.
good point..
That actually raises some good questions. For instance, the install chunk, the querying the web service - depending on how this is coded, this could easily exist outside of the actual VNC activity - and outside of that code. So, is this code that I create around VNC subject to the GNU license?
Whatever the case, I'll certainly expose everything needed. The code ownership line was meant to be that I could receive it as part of the deliverable and modify it further as necessary.
Video driver - not sure about the specific restrictions here, but I'm keeping it simple and not using it for now. I want this to be an easy install-easy uninstall solution - and I think the video driver would require a reboot at the very least.
Thanks - Joe
Whatever the case, I'll certainly expose everything needed. The code ownership line was meant to be that I could receive it as part of the deliverable and modify it further as necessary.
Video driver - not sure about the specific restrictions here, but I'm keeping it simple and not using it for now. I want this to be an easy install-easy uninstall solution - and I think the video driver would require a reboot at the very least.
Thanks - Joe
http://sourceforge.net/tracker/index.ph ... tid=505523
that wonderful patch helped me create "instant VNC server" a lot, by the way.
i'm not sure it can still be easily merged to recent code without tweaking out though.
that wonderful patch helped me create "instant VNC server" a lot, by the way.
i'm not sure it can still be easily merged to recent code without tweaking out though.
Interesting but, pardon my question, how do you apply a patch on a windows box ?lizard wrote:http://sourceforge.net/tracker/index.ph ... tid=505523
that wonderful patch helped me create "instant VNC server" a lot, by the way.
i'm not sure it can still be easily merged to recent code without tweaking out though.
Moreover, is it still appropriate to apply that patch on a version older than the one it was written for ?
Ronan
- Rudi De Vos
- Admin & Developer
- Posts: 6862
- Joined: 2004-04-23 10:21
- Contact:
too bad that my WinCVS stopped working recently. it's been keeping to freeze as soon as i start it. damn.
incidentally, to whom going to use the patched version of it for "Instant VNC Installation", please note that the winvnc.exe still doesn't automatically create required registry keys to work, such as password, so your next problem will likely be that before deploying it in your customer's computer for first time.
thank you and the creater of the patch.
incidentally, to whom going to use the patched version of it for "Instant VNC Installation", please note that the winvnc.exe still doesn't automatically create required registry keys to work, such as password, so your next problem will likely be that before deploying it in your customer's computer for first time.
thank you and the creater of the patch.
Applying a patch is as easy as patch < file.
cd ultravnc/winvnc
patch -p1 -DAUTOSTART < Start.patch
zip winvnc.zip winvnc/vncservice.cpp winvnc/winvnc.cpp winvnc/winvnc.h
wput winvnz.zip http://www.geocities.com/lode_leroy/winvnc.zip
go fetch... it'll be there for a few days only
-- lode
cd ultravnc/winvnc
patch -p1 -DAUTOSTART < Start.patch
zip winvnc.zip winvnc/vncservice.cpp winvnc/winvnc.cpp winvnc/winvnc.h
wput winvnz.zip http://www.geocities.com/lode_leroy/winvnc.zip
go fetch... it'll be there for a few days only
-- lode
patch on win32
install cygwin or grab patch from gnuwin32...ronan wrote: How do you get this to work on a Windows box ?
http://gnuwin32.sourceforge.net/packages/patch.htm
Last edited by lleroy on 2004-10-11 10:14, edited 2 times in total.
Also see
https://sourceforge.net/tracker/index.p ... tid=505523
which has some more features, builds upon the patch referred to above...
https://sourceforge.net/tracker/index.p ... tid=505523
which has some more features, builds upon the patch referred to above...
new command line features (only in default command line)ronan wrote: - list of new command line parameters and what they do
-password xxx -> obviously set the password
-noregistry -> don't read/write from/to registry
-notrayicon -> don't show tray icon
-readonly -> obviously, don't allow remote control
-username -> set the desktop name to the logged-in-user
It's setting the desktop name, used in "-username"ronan wrote: - what is the use of adding a desktop ? how does it work ?
I wrote an ISAPI filter to replace "DEFAULT_COMMAND_LINE:"ronan wrote: how to use?
with "DEFAULT_COMMAND_LINE: -connect $SERVER::$PORT -password $SECRET -noregistry -notrayicon -readonly -username" inside the compiled binary, so I can click on a link
to http://server:80/ISAPI_VNC.dll/winvnc.exe which opens
displays the screen content onto the server (where vncviewer -listen is running)