Shulou(Shulou.com)06/03 Report--

This article mainly introduces how to start two applications in vbs, which is very detailed and has a certain reference value. Friends who are interested must read it!

Q:

I want to start two executables with one script. After the first application closes, I want this script to close the second application and then exit. How to accomplish the above tasks?

A:

You know, this is the kind of problem we like. Why? Because it sounds really complicated and tricky. If someone wants us to do something, we can say, "you know, I'm trying to write a script that starts two applications, waits for the first to close, and then automatically closes the second." And then they would say, "Oh, I'm sorry. Obviously, you're busy," and then they stopped looking for us.

Of course, they don't know, it just sounds difficult. In fact, it is as difficult as the following script:

The copy code is as follows:

StrComputer = "."

Set objWMIService = GetObject ("winmgmts:\\" & strComputer & "\ root\ cimv2:Win32_Process")

ErrResult = objWMIService.Create ("calc.exe", null, null, intCalcID)

ErrResult = objWMIService.Create ("notepad.exe", null, null, intNotepadID)

Set objWMIService = GetObject ("winmgmts:\\" & strComputer & "\ root\ cimv2")

Set colProcesses = objWMIService.ExecNotificationQuery _

("Select * From _ _ InstanceDeletionEvent" _

& "Within 1 Where TargetInstance ISA 'Win32_Process'")

Do Until i = 999

Set objProcess = colProcesses.NextEvent

If objProcess.TargetInstance.ProcessID = intCalcID Then

Exit Do

End If

Loop

Set colProcesses = objWMIService.ExecQuery _

("Select * from Win32_Process Where ProcessID =" & intNotepadID)

For Each objProcess in colProcesses

ObjProcess.Terminate ()

Next

Really, trust us: it's actually pretty easy when you understand what the script does. We first connect to the WMI service on the computer, specifically, to the Win32_Process class. That's what we're going to do now:

Set objWMIService = GetObject ("winmgmts:\\" & strComputer & "\ root\ cimv2:Win32_Process")

Then, we use the Create method to create two new processes: Calc.exe and Notepad.exe. For each new process, we use code similar to this line of code:

ErrResult = objWMIService.Create ("calc.exe", null, null, intCalcID)

All we have to do is call the Create method with the following:

The name of the executable file (you may need to specify the full path name of the application, depending on your computer's settings).

A pair of Null parameters. Using these two parameters, we can specify different working folders for the application and configure some other startup options. In this sample code, we don't need to think about these things, so we just set the parameter value to Null.

A variable (named intCalcID) that acts as an output parameter. After these processes are created, the ProcessID number assigned to the process is also assigned to these output parameter variables.

The end result is that we start Calculator, and the variable intCalcID contains the process ID assigned to the Calculator instance. Then, we start notepad, and the variable intNotepadID contains the ProcessID assigned to the notepad instance. This is how to start two applications and track them.

The next thing we need to do is, well, it's pretty much nothing: we want the script to pause until Calculator is turned off. To complete this task, we reconnect to the WMI service and then use ExecNotificationQuery to monitor any deleted processes. We need to reconnect to the WMI service because at the beginning of the script we are only connecting to the Win32_Process class; therefore, the object reference (objWMIService) is just a reference to this class. We need to connect to the "generic" WMI service, so we just reuse the object reference objWMIService and make a new connection:

Set colProcesses = objWMIService.ExecNotificationQuery _

("Select * From _ _ InstanceDeletionEvent" _

& "Within 1 Where TargetInstance ISA 'Win32_Process'")

What is the reason for doing this? Each time a process is deleted, an instance of the _ _ InstanceDeletionEvent class is generated. We will examine each instance to see if the process ID of these instances is the target ID, that is, the ID assigned to the intCalcID. If the deleted process has a different ID, it is not a Calculator instance; in this case, the script resumes monitoring. If the deleted process has the same ID as intCalcID, it must be a Calculator instance (because the process ID must be unique). In this case, we should stop monitoring and then close the notepad.

Here is the code that actually performs the monitoring:

Do Until i = 999

Set objProcess = colProcesses.NextEvent

If objProcess.TargetInstance.ProcessID = intCalcID Then

Exit Do

End If

Loop

What we do here is set up a loop that runs until the variable I equals 999. Now, the fact is that the variable I will never be equal to 999; it's just a trick to make sure the loop runs until the Calculator is turned off. How do we know that the variable I will never be equal to 999? Well, we don't assign a value to I; therefore, it takes the default value of 0. Because we have never made any changes to this value, I is always 0, so it will never be equal to 999. )

In the loop, we use this line of code to wait for the next deleted process:

Set objProcess = colProcesses.NextEvent

Each time we delete a process, we check that the ProcessID matches the process ID assigned to the Calculator. If it matches, we use the Exit Do command to break the loop and continue the script. If we don't have the same ID, we just need to continue the loop and wait for the next deleted process. (as we said above, I will never be equal to 999, but it doesn't matter: you can get out of the loop by using the Exit Do command. )

Be careful. We found that we somewhat skimmed the whole train of thought of incident surveillance. If you are a little confused about things like _ _ InstanceDeletionEvent and colProcesses.NextEvent, see script expert Webcast Preventive: introduction to WMI events.

For now, we just need to terminate the notepad instance we started. To accomplish this task, we use this WMI query to retrieve a collection of all processes with the process ID assigned to notepad:

Set colProcesses = objWMIService.ExecQuery _

("Select * from Win32_Process Where ProcessID =" & intNotepadID)

After we get this collection, we use this code block to cycle through the entire process set (there is only one process), and then use the Terminate method to close the application:

For Each objProcess in colProcesses

ObjProcess.Terminate ()

Next

By the way, this method works for both remote and local computers; you just need to change the value of the variable strComputer to the name of the remote computer. Keep in mind, however, that in Windows XP and Windows Server 2003, processes started on remote computers run in invisible windows; they are not visible on the screen. This means that when dealing with remote computers, this method is useful for applications that do not require any user interaction, while for applications that do require user intervention, it is far less useful (in fact, completely useless).

These are all the contents of the article "how to start two applications in vbs". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.