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.