Find a system process by it's name (and check whether or not it is running)

[promalley2]

Greetings!<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
<o> </o>
I’m creating a number of routines and functions that work in conjunction with my CAD software’s VB API. In order for the VB API to function properly, it requires two environment variables with specific names and one system process to be running (which is started when a new asynchronous connection and session is established between an application and the CAD software). I’ve been able to successfully check whether the two environment variables exist by calling them by their specific names, but I’m having trouble figuring out how to identify if the unique system process is running. For this discussion, let’s call the name of the unique process “namespc.”<o></o>
<o> </o>
In my research prior to posting, I haven’t been able to locate a way to look at the list of system processes running outside of the windows API—which is not something I’m familiar with at all, but I’m open to learn if someone can point me to the right resources. But I’m looking for suggestions as to what ways there are to examine the list of system processes and which one might be considered “the best.”<o></o>
<o> </o>
Again, all I’m looking to do here is look at the list of system processes by name and see if “namespc” is there. And if “namespc” is contained in the list of system processes, I’d like to check to see if it’s running (or is it the case where if the process is in the list, then it is considered to be running?).<o></o>
<o> </o>
Thanks in advance for taking the time!<o></o>
<o> </o>
<o> </o>
--PRO<o></o>

 

[Norie]

Glad you found something.

You might also want to look at Windows Powershell.

I only just found that when I fired up an old machine that I'd forgotten about.

Checked on my current machine and it was there too.

Perhaps not much use for what you want to do, I can seem to find much about integrating with other apps or using VBA.

Mind you it did find something about scripting WMI using Powershell.