Now it stays open and whatever error message the console gives will be visible. You could also try this: in XY AB simply type this
Code: Select all
!cscript
Code: Select all
!cscript
Aha. Thanks.highend wrote:just replace "cmd /c" with "cmd /k".
The window should stay open.
Content?
Code: Select all
Input Error: There is no script engine for file extension ".vbs".
Nope...does that mean that something else is missing?
There's a copy in \windows\system32, and three more copies (same filesize, not all the same date) in various complicated folders off \windows\winsxs. (My netbook isn't currently connected to the network as I'm at work and we don't do BYOD so if you want those foldernames too it'll take a bit more messing around...)Marco wrote: It likely means that I'm looking for it in the wrong place. Can you please search for it and tell me where it is located on your system?
That's so much easier than hitting the start button and typing cmd -- I have absolutely no idea why I hadn't picked that route at the command prompt up before!Marco wrote: You could also try this: in XY AB simply type thisWhat appears?Code: Select all
!cscript
Code: Select all
text %systemroot%;
C:\windowsMarco wrote:And what aboutin XY AB?Code: Select all
text %systemroot%;
Further to this, I modified the script to fully qualify the path to cscript.exe, just in case something was going on with environment variable expansion and it still fails in the same way.Marco wrote:And what aboutin XY AB?Code: Select all
text %systemroot%;
Thanks -- looked promising.Marco wrote:7 Starter, uh? Maybe this fix works? http://www.winhelponline.com/blog/error ... vbs-files/
Code: Select all
cmd /c $vbs_interpreter //nologo "$http_checker_path" "$download_url" "$last_modified" "$http_response_path"
Code: Select all
wscript "$http_checker_path" "$download_url" "$last_modified" "$http_response_path"
Can't say for sure, but I've done the replacement and run the script and it doesn't produce any errors. However, I'm not looking for beta versions so the only thing that happens is XY puts up its "already up to date" message.SammaySarkar wrote:Shooting in the dark: does it work with wscript.exe?
wscript is the "graphical" interpreter of vbs files, while cscript is the command line one. There should be no disadvantage, but I originally put cscript because I know its command line arguments better. I really can't explain why wscript works and cscript doesn't, nevertheless I would not worry and, most of all, I'd thank SammaySarkar once again for his helpSo what are the disadvantages of this approach? Or is it just an illustration of the "there's more than one way to do almost anything in Windows" adage? (Or -- more worryingly -- will it just fail later on, if there's an update to perform?)
I would certainly wish to do that very thing, and I'm sorry I omitted to do so!Marco wrote:most of all, I'd thank SammaySarkar once again for his help