Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

JS Association. Web Developer role, Windows.

Simple, Free, Open Source UltraVNC Wrapper Supporting Windows and Mac OSX
Post Reply
User avatar
kellygallen
Posts: 2
Joined: 2013-04-06 17:36
Location: Las Vegas, NV, USA
Contact:

JS Association. Web Developer role, Windows.

Post by kellygallen »

My computer is used for web development so JS files are set to open inside of an editor. When I run the complied InstantSupport file, 'unblock.js' opens in the editor vs executing. Perhaps this file is unnecessary, or there is a better way to invoke it. Otherwise great solution.
User avatar
supercoe
400
400
Posts: 1732
Joined: 2009-07-20 21:27
Location: Walker, MN
Contact:

Re: JS Association. Web Developer role, Windows.

Post by supercoe »

Sorry about that, it's a known bug.
Here is a solution: https://forum.ultravnc.net/viewtopic.php?f=50&t=29209
http://www.chunkvnc.com - ChunkVNC - Free PC Remote control with the Open Source UltraVNC wrapper InstantSupport!
User avatar
kellygallen
Posts: 2
Joined: 2013-04-06 17:36
Location: Las Vegas, NV, USA
Contact:

JS Association. Web Developer role, Windows. (New Solution)

Post by kellygallen »

Thanks to https://forum.ultravnc.net/viewtopic.php?f=50&t=29209 which had this problem before me. I solved it with two different edits that I tried on that thread.

Change Line 118 in the InstantSupport.au3
Did not work, because parameter needed to be in quotes to work with paths that have a space in them.

Code: Select all

ShellExecuteWait($WorkingPath & "\unblock.js", "", @ScriptDir, "")
Did not work because WScript didn't understand what engine to use.

Code: Select all

ShellExecuteWait("wscript.exe", $WorkingPath & "\unblock.js", @ScriptDir, "")
WScript: There is no script engine for file extension ".js"
Apparently my favorite Web Dev apps really messed up my JS file associations when I let them become associated. And there is a fix to reset the JS association.
http://www.winhelponline.com/articles/2 ... files.html
But this was not good enough.

It is simpler to edit the Line 118 in the InstantSupport.au3 to be:

Code: Select all

ShellExecuteWait("wscript.exe", '//E:jscript "' & $WorkingPath & '\unblock.js"', @ScriptDir, "")
What //E:jscript does is force it to use the js engine even if the registry pointing to that engine is messed up. It now works good.

Other Sources of information:
http://stackoverflow.com/questions/5700 ... e-argument
Post Reply