By googling, I found a very simple way to do so without a CMD script, Command Prompt, and PowerShell.
ReplaceCode:Set l=CreateObject("Shell.Application"):If WScript.Arguments.length = 0 Then l.ShellExecute"wscript.exe",""""&WScript.ScriptFullName&""""&" ✱","","RunAs",1 Else MsgBox "Hello!" End IfMsgBox "Hello!"with your VBScript commands.
Googling has made up for my poor education.
Matthew,
What an excellent method.
Did you keep a note of the source?
[I like to note the sources in any code I've copied]
Denis
Source: How to Launch a Vbscript in Elevated Mode (Run as Administrator) >> Winhelponline
PS Thanks for the rep!
Matthew,
And thank you for the link. I have used a lot of Ramesh Srinivasan's suggestions over the years.
And yours. I've come round to your ideas about using Reg commands instead of .reg files to set up my Context menus.
- One of my intended Context menu entries is a Networking submenu containing a set of scripts to copy folders-files to the Desktops of my other computers [amongst other things]. I currently use shortcuts to them in my SendTo menu.
- I always like to write one script that I use without alteration on all three computers.
- The only way to avoid creating a redundant Networking entry [to copy to its own Desktop] is to have a test for ComputerName that skips certain commands
- .reg files cannot contain ComputerName tests so I will change to using a batch file instead.
Denis
Last edited by Try3; 07 Jul 2020 at 02:31.
You can mix ".cmd", ".vbs", ".ps2", and ".xml" into a batch file, but you cannot do the same into a .reg file, which I seldom use.
Matthew,
I've been using "0x00000020" rather than "0x00000040" but I've just tested both and they seem to have the same effect as each other anyway.
Denis
Quote
