中国DOS联盟

set WshShell=Wscript.CreateObject("Wscript.Shell")
WshShell.Run("C:\Program Files\WinRAR\WinRAR.exe")
Says the specified file cannot be found???
This file exists!
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "%windir%\notepad "
Calling the program in the system directory has no error prompt!!!

1. Do not use parentheses
2. VBS does not use variables like %windir% (unless generating VBS in batch processing). As long as it is a file stored in the system default variable directory (viewed with set in CMD), just write the file name directly.

WshShell.Run("C:\Program Files\WinRAR\WinRAR.exe")
VBS: For function calls, it doesn't matter whether there are parentheses or not. Don't use parentheses for the sake of being standard. It's convenient to sometimes turn into JS. These two Windows scripting languages are basically similar. However, to develop a good writing style, it is still recommended to add parentheses when calling functions. This is also required by the standards of many languages like Java.
Also, this problem has been solved. The main reason is that the path has spaces and causes problems. You can use WshShell.Exec, but this function is mainly for 32-bit programs. Of course, it can also be solved like this: WshShell.Run("C:\Progra~1\WinRAR\WinRAR.exe"). This function is very strange, it seems to return to the DOS state and has space problems. VBS was also studied yesterday. If there are any mistakes, please correct them by everyone. In fact, JS and VBS are basically the same, and they can both achieve the same functions. However, since JS has problems with local permission calls, it is the same to expand it to *.hta! I forgot its interpreter name early in the morning :) But many antivirus tools are very easy to misdetect such files :( Note that such JS is JScript, which is exclusive to the Microsoft system, just like VBscript, not JavaScript

set WshShell=Wscript.CreateObject("Wscript.Shell")
WshShell.Run createobject("scripting.filesystemobject").getfile("C:\Program Files\WinRAR\WinRAR.exe").ShortName

Just add quotes to him, no need to use short filenames.
set WshShell=Wscript.CreateObject("Wscript.Shell")
WshShell.Run("""C:\Program Files\WinRAR\WinRAR.exe""")

The method on floor 5 is really wonderful!!

WshShell.Run is equivalent to you pasting the following string into the Run dialog box in the Windows Start menu.

So variables like %windir% can be supported.

Therefore, the problem of paths with spaces exists. So adding quotes to the called string can solve it.

C:\Program Files\UltraISO\UltraISO.exe G:\viursINx\ISO\3SwordPE.iso
How is such a problem determined?

Proceeding with the previous problem, here's the continuation:

——————————————
Two examples are given:
"D:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode
"D:\Program Files\360\360safe\SoftMgr\SoftManager.exe" /page=3 /start=menuunist

After splitting by spaces, the program parameters are still used as they are.

***************************So, it should be:
set WshShell=Wscript.CreateObject("Wscript.Shell")
WshShell.Run("""C:\Program Files\UltraISO\UltraISO.exe""" G:\viursINx\ISO\3SwordPE.iso)

Originally posted by ywjco at 2010-5-16 21:54:
An old question, continued now:
——————————————
Give two examples:
"D:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode
"D:\Program Files\360\3 ...

You are wrong like this.