ChunkVNC: InstantSupport throws error when launched

[smgerber]

I applied a fix to InstantSuport.au3 to avoid Dreamweaver coming up to edit unblock.js. The fix I applied (supplied in the ChunkVNC forum) is:

; Unblock InstantSupport.exe to prevent "Windows Security" messages.
ShellExecuteWait("wscript.exe", $WorkingPath & "\unblock.js", @ScriptDir, "")

Notice that I explicitly entered the name of the script handling program, wscript.exe.
It works great in terms of avoiding bringing up the javascript file in an editor, but unfortunately throws the following error whenever it's launched in WinXP Sp3. It still works but I'd like to avoid the error.


Can anyone help? The compile was done in XP SP3. The problem does NOT occur when Instant Support is launched on Windows 7, only when launched in XP.

Thanks very much ... Sam

[supercoe]

See my response here: https://forum.ultravnc.net/viewtopic.ph ... 761#p91761

Next time post in the ChunkVNC sub forum, it was an accident that I even came across this post!

Let us know if the new code does the trick.

[smgerber]

I've reviewed this problem and from what I can tell there's no way that ChunkVNC's Instant Support can work properly under Windows XP.

It seems to me that Directory names with embedded blanks are messing with the AutoIt scripting. One of the directories handled by the script is "Documents and Settings" which throws one error after another during execution of the InstantSupport.exe file.

The script does not appear to be written to allow for such directories. I tried to modify the line below to:

; Unblock InstantSupport.exe to prevent "Windows Security" messages.
ShellExecuteWait("wscript.exe", ""$WorkingPath"" & "\unblock.js", @ScriptDir, "")

based on some tips from Google but that only led to further and different errors down the road. Notice the quotes around $WorkingPath.

Windows 7 apparently can handle directory names with embedded blanks and that's why it doesn't throw any errors.

Hasn't anyone had execution problems with InstantSupport.exe on a WINXP system that has a program like Dreamweaver installed which handles .JS files?

I'm stuck until the author visits this page. Can any of you who have his ear encourage him to look at this thread? I do not believe this is a wild goose chase but rather a serious scripting issue which needs repair.

Thanks ... Sam

[supercoe]

I've reviewed this problem and from what I can tell there's no way that ChunkVNC's Instant Support can work properly under Windows XP.

ChunkVNC does work with XP, it would be silly to not support it.
Slow down and realize that the issue you are experiencing is because you modified InstantSupport.

The bug you were trying to fix (unblock.js opening in an editor such as Dreamweaver) only happens on machines that have changed the default open command for the .js file extension.
InstantSupport still functions even if it is run on a computer with Dreamweaver installed although not as intended.

Indeed the fix that was posted by the other user was flawed because it didn't account for the spaces in the command line which XP can't handle. (thus causing your original issue here)

Since seeing this thread I went back to review the other users fix and realized that it would cause the problem you are explaining.
I went ahead and corrected the code which you will find if you follow the link in my previous post.


It seems to me that Directory names with embedded blanks are messing with the AutoIt scripting. One of the directories handled by the script is "Documents and Settings" which throws one error after another during execution of the InstantSupport.exe file.

Correct, it is the space in the path that causes the issue after your previously mentioned modification was preformed.


The script does not appear to be written to allow for such directories. I tried to modify the line below to:

; Unblock InstantSupport.exe to prevent "Windows Security" messages.
ShellExecuteWait("wscript.exe", ""$WorkingPath"" & "\unblock.js", @ScriptDir, "")

There is no way that code would function as it is flawed.
You need the quotes around $WorkingPath and \unblock.js so you get:
"c:\path with spaces\unblock.js"
What you have there would produce:
"c:\path with spaces"\unblock.js

See my previous post for a link to the thread where I explain the correct code to try.

[smgerber]

Here I am again to close this out. The author "supercoe" provided a solution in another thread which he references above. His posting somewhat crossed in the mail with my earlier lament, posted above his solution.

I'm happy to say that his solution appears to have worked and there should no longer be an issue for people executing InstantSupport.exe on an XP machine with a javascript handler installed.

Thanks very much "supercoe". My hat's off to you.

Best ... Sam

[supercoe]

lol yea, looks like we "picked up the phone" at the same time.
Be sure to post in the ChunkVNC forum next time as I don't get notification on this sub forum when there is a new topic.

[smgerber]

Thanks once more for all your assistance getting this working, supercoe.

I never tried to imply your code didn't work under XP. I believe I said "work properly". After the error is thrown it does go on to work. I just couldn't subject novice users to this type of error; it'd scare them to death.

When I tried to fix the coding error to the fix suggested by the other user, I made a rookie error with the placement of the quotes. I tried to follow suggestions I found on Google since I never coded AutoIt before. Thank you for explaining where I screwed up the fix to the fix.

I have a friend who's a networking consultant who has used VNC for support for many years. He was resistant to moving to Chunk until I explain how the entire UltraVNC INI file was available to customize the server. He's also a big fan of your repeater function. He'd be your biggest fan ever if you had a viewer that works on his iPhone. He'd pay $$ to buy something if it were available now.

Finally, sorry I've been posting to the wrong forum. I'm still green with these forums and missed the concept of subforums. I saw VNC Related products in large font and just jumped in. Won't do that again for ChunkVNC.

'Nuff said I guess. Am quite glad to have all this working. It's really terrific!!

My best to you ... Sam

[supercoe]