Not running?

[orlyjamie]

Not running?

[orlyjamie]

Hello dlimanov,

I've tested now on Win8.1 x64 and have not noticed any issue.

Does it just hang after the ASCII art? If that is the case it may still be searching in memory (The more browser tabs you have open, the longer it will take to complete the script) - Note: I've had it take up to 4-5 minutes with a lot of tabs open in Chrome.

In order to do more controlled testing you may want to limit the process scope by only targeting a single process in line 532

$matchesFound=[mimikittenz.MemProcInspector]::InspectManyProcs("chrome")

[dlimanov]

Hi Putterpanda,
Thank you for replying! That's the thing, even the ASCII graphics don't load; it's like nothing happens whatsoever, as if PowerShell doesn't know what to do with the script. I'll check Event Viewer to see if there are any relevant events that hopefully will shed some light on this issue.

On Jul 19, 2016, at 8:55 PM, putterpanda [email protected] wrote:

Hello dlimanov,

I've tested now on Win8.1 x64 and have not noticed any issue.

Does it just hang after the ASCII art? If that is the case it may still be searching in memory (The more browser tabs you have open, the longer it will take to complete the script) - Note: I've had it take up to 4-5 minutes with a lot of tabs open in Chrome.

In order to do more controlled testing you may want to limit the process scope by only targeting a single process in line 532

$matchesFound=[mimikittenz.MemProcInspector]::InspectManyProcs("chrome")

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[dlimanov]

This is super weird, I just tried on both Win7 and 8.1 and while Event Viewer registers script execution (Event ID 4104, Source: PowerShell), still nothing is being displayed in the PowerShell command window (or ISE for that matter, I tried that as well); not ASCII, no errors, nothing.
You don't happen to have a video of the script executing on your system, do you?

[Dangles91]

Hey dilmanov,

The ps1 file contains just the function itself and doesn't call it directly, you'll need to modify the ps1 to also call the function, or dot source into a module file.

Alternatively, you can remove the function header and closing curly brace and call the script file directly.

[orlyjamie]

@ dlimanov Ah hehe, did not even realize that you were not calling the function Invoke-mimikittenz (My bad)

The reason I wrote the script like this is because I plan to add additional functions to the script.

If you want it to run the way your trying you can follow Dangles91 recommendations or you can simply add Invoke-mimikittenz; at the bottom of the script on it's own line.

[scopolamin]

==> #2 How to run it

---

PS C:> Set-ExecutionPolicy RemoteSigned
http://www.howtogeek.com/106273/how-to-allow-the-execution-of-powershell-scripts-on-windows-7/

---

3 options:

1. Call the function from the file (=> last line)

function Invoke-mimikittenz
{
  /* code */
  write-output $asciiart
  $matches=[mimikittenz.MemProcInspector]::InspectManyProcs("iexplore","chrome","firefox")

  write-output $matches
}

Invoke-mimikittenz

2. Invoke the functions from the file

PS C:> powershell -command "& { . C:\foo\bar\Invoke-mimikittenz.ps1; Invoke-mimikittenz }"

3. Load the file and call the function

PS C:\foo\bar> .\Invoke-mimikittenz.ps1
PS C:\foo\bar> Invoke-mimikittenz

[dlimanov]

Gosh do I feel stupid! Sorry to waste the time guys..

[Dangles91]

Haha all good mate, I might know powershell, but the reason I know what was wrong, is because I did the exact same thing XD

[orlyjamie]

No problem dlimanov, thanks for the feedback any way.

[E3V3A]

Please add this info to the README file. I wasted too much time to find this in a closed issue.

Also, please provide the output of Get-ExecutionPolicy -List when it is working.