Bug and Bugfix for "unblock.js"

[Netzvamp]

Hi,

i had a small issue with the "unblock.js"-file that is running if you start the instantsupport.exe.
In your Code you try to start that script, but you don't tell windows which programm should execute the script. So windows use the program that is associated with the filetype. Thats in 90% of all cases the right program (wscript.exe), but i associated *.js files with an texteditor
Every time i start the instantsupport.exe, this texteditor starts and shows me the unblock.js file

Fix:
Change Line 118 in the InstantSupport.au3

Code: Select all

ShellExecuteWait($WorkingPath & "\unblock.js", "", @ScriptDir, "")

with that line

Code: Select all

ShellExecuteWait("wscript.exe", $WorkingPath & "\unblock.js", @ScriptDir, "")

and it should execute the right executable with the right script.

Long text for such an easy task ... sorry

[supercoe]

Thanks for a solution, I know this was a problem for a few people.

[smgerber]

Thanks so much for this fix, Netzvamp. It was driving me bonkers, especially since Dreamweaver kept popping up and that isn't instantaneous.

[supercoe]

I haven't had time to test this but it looks like at least this user is still having a problem: viewtopic.php?f=27&t=29279

Looks like we need to have the path that gets sent to wscript.exe wrapped in quotes.

This should do the trick:

Code: Select all

ShellExecuteWait("wscript.exe", '"' & $WorkingPath & '\unblock.js"', @ScriptDir, "")

[smgerber]

I am the "this user" mentioned above by "supercoe".

I just tested this and it seems to work flawlessly now under WIN XP.

Thanks very much for a quick and what looks to be a total solution.

Regards ... Sam

[supercoe]

No problem man, glad it fixed the issue!