find path on process

[Faustvii]

hi i dont know if autoit is able to find a path to a running process lets say winlogon.exe then it should give you the path to the dir of the process does anybody know if autoit is able to do that? if yes can anyone give me an exsample ?

[Faustvii]

Anyone??

[Infinitex0]

Go to the helpfile and find macros probably one of them will do what you need (I just can't find it)

Edited February 14, 2006 by Infinitex0

[GaryFrost]

http://www.autoitscript.com/forum/index.ph...ndpost&p=113711

[Faustvii]

http://www.autoitscript.com/forum/index.ph...ndpost&p=113711

Tyvm for that link.. How do i do so it only looks in winlogon.exe and not all the others? Edited February 14, 2006 by Liope

[SmOke_N]

Here a stab at it, I only looked at larry's UDF... GetProcessName(ProcessExists(winlogon.exe))

[ChrisL]

Used Scriptomatic to generate most of this, see if it will work for you

Edit*

Forgot to say you need the beta

$Mypath = FindProcessPath ("WinLogOn")
MsgBox (0,"Required Path is", $MyPath)

Func FindProcessPath ($PIDName)
$wbemFlagReturnImmediately = 0x10
$wbemFlagForwardOnly = 0x20
$colItems = ""
$strComputer = "localhost"
$objWMIService = ObjGet("winmgmts:\\" & $strComputer & "\root\CIMV2")
$colItems = $objWMIService.ExecQuery("SELECT * FROM Win32_Process", "WQL", _
                                          $wbemFlagReturnImmediately + $wbemFlagForwardOnly)

If IsObj($colItems) then
   For $objItem In $colItems

      $path = "ExecutablePath: " & $objItem.ExecutablePath 
      $Name = "Name: " & $objItem.Name 
      $Pid =  "ProcessId: " & $objItem.ProcessId 
      if StringinStr ($Name ,$PidName,0,1) <> 0 then Return StringTrimLeft ($Path, 16)
   Next
Else
   Msgbox(0,"WMI Output","No WMI Objects Found for class: " & "Win32_Process" )
Endif
EndFunc

Edited February 15, 2006 by ChrisL

[Faustvii]

Tyvm for the help

[JerryD]

I had posted a WMI solution for this - How to get full file name from PID, but Larry subsequently posted the link to his solution - Get Process Name From PID which uses DLLCall.

I ran a quick test, and DLLCall is more than 10 times faster than using WMI, although when looping through all processes running. DLLCall did return a few errors, but it probably just needs a little tweaking, so if you're going to be using it a lot, I'd recommend using DLLCall rather than WMI.

Guess Larry is king!