Getting Command line that started a ProcessID (win32/VBA(VBS?))

Given a process ID, I wanted to know the command line that launched it. Eventually I want to code this up in MFC/VC6, but for now I mocked it up in VBA (say yuck, but the WMI interface is quite simple compared to C/C++ and win32/MFC):

strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_Process WHERE ProcessID = 16132")
For Each objProcess in colItems
 Wscript.Echo "Process: " & objProcess.CommandLine & " Process ID: " & objProcess.ProcessID
Next

 Put your own PID in place of 16132. 

This file should be given an extension .vbs. Double click on it to get a dialog box, or run from the command line with cscript to get console output. Tested and working with Win10. 

This is the first VBA script I've ever written, but it seems like it's the right tool for the task. 

Obligatory Old New Thing Reference(s):


(this is a good reason to mock up the WMI query first, since you might not get what you want).


(not his actual title)

Raymond is a goldmine of info, and his (pretty old) book is hilarious to old Win32 programmers like myself. It's a literal crime that Microsoft migrated his blog to their new platform, breaking all the old links and deleting all the blog comments in the process. 

Comments

Post a Comment

Email me

Name

Email *

Message *

Popular posts from this blog

Panasonic TH-42PX75U Plasma TV review: input lag and upscaling tested using the piLagTesterPRO

Image
This 720p Plasma TV from 2008 is very unique and quite nice in many ways. It used to retail for around $1300. If you can find one it's a great choice for retro gaming.  Overview/Image quality This is a plasma TV, which generally means at least the following: nearly infinite viewing angles, and jaw dropping weight. That's true in this case as well. This 42" model weights 75lbs.  At native resolution (720p) this TV crops 20 pixels off the top/bottom and 30 off the sides. 480p/i crops 20 pixels off all sides. Both modes have aliasing, too, though it's not too bad. There's really no excuse for aliasing on a TV this big: you know the panel was designed specifically to be a tv. Why not hit 720p exactly? And as for 480p/i, they could have at least offered a zoomed out mode with black borders and 1:1 pixel mapping. But no such luck. There are zoom/stretch options to crop even more, but none that crop less. While the native resolution supposedly is 1366 x 768 it does accept...
Read more

piLagTester PRO order page

Image
The piLagTesterPRO measures your monitor's input lag and response time. It is a cheap, full featured add-on to the Raspberry Pi; I provide the sensor and required software, you provide the Pi (a $5 pi Zero is more than sufficient). Although it has a DIY aesthetic, it is quite functional and in fact offers quite a lot more features than the commercial alternatives (Leo Bodnar and the Time Sleuth), and has been tested with over 40 TVs, including 4k models .  Here's what it looks like in action: The pi draws a black background, and then roughly once a second displays a set of target rectangles (top/middle/bottom). You place the sensor over the desired target, and the piLagTester measures the monitor's response starting from the moment the frame of video data is sent over the Pi's HDMI port. This is plotted in the graph, which is sideways for space reasons. The lag tester measures two thresholds. In red it shows how long it takes for the monitor to start displaying t...
Read more

A $5 TV Input Lag tester using a Raspberry Pi Zero

Image
High speed monitors are all the rage now, with quoted response times  of 1-4ms. But does that mean that 1-4ms after you make an input (say, jump) you will see that on your screen? No. Often a much bigger issue is  Input lag. This is   the delay between your computer / game console sending a video frame to your display and your display starting to actually show it, and it ranges from 4ms to 80ms. The problem with measuring input lag is that you can't, at least with everyday hardware. The solution for hardware review sites is to purchase dedicated lag testers such as the leo bodnar tester,  timesleuth (both ~$100), or the pi lag tester pro ($40) or use homegrown methods utilizing an oscilloscope ("free" if you already own a $400+ oscilloscope and perhaps a $50k+ engineering degree). Here I introduce a $5 solution (or, "free" if you own the required equipment). What's required: A Raspberry Pi Zero ($5 + S&H from several sources). This single b...
Read more