MS$ translations are always fun - especially when it comes to the cmd
Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
Windows Command Line
Re: Windows Command Line
Yes, replace was just the first thing that came to my mind (I don't think there is a codepage with a dot in the name)
MS$ translations are always fun - especially when it comes to the cmd
MS$ translations are always fun - especially when it comes to the cmd
Re: Windows Command Line
Am I doing something wrong? In sem;colon's example above, several events are generated. When I try a basic command, there are no events generated. However, the result of the command is found in eg.result. Windows 8.1, 64-bit.
Also, Pako, would you consider making an elevated command (i.e. administrator) version of this? I have a need to use the Devcon command and currently have to use some workarounds to make it work. Thanks.
Also, Pako, would you consider making an elevated command (i.e. administrator) version of this? I have a need to use the Devcon command and currently have to use some workarounds to make it work. Thanks.
Re: Windows Command Line
Do you mean the process.created.* events? those are from the "Process Watcher" plugin.kkl wrote:Am I doing something wrong? In sem;colon's example above, several events are generated.
jonib
Re: Windows Command Line
Yes, that's what I was looking at. Thanks for the help Jonib.
Re: Windows Command Line
You can do that by:kkl wrote:would you consider making an elevated command (i.e. administrator) version of this? I have a need to use the Devcon command and currently have to use some workarounds to make it work. Thanks.
-Running EG as admin
-Using PSexec and store your admin credentials somewhere
-Using the windows task scheduler
Re: Windows Command Line
Sem;colon, thanks for the feedback. I am aware of these options from this thread. I've used the last two successfully. The first one doesn't work, at least not for the Devcon command.Sem;colon wrote: You can do that by:
-Running EG as admin
-Using PSexec and store your admin credentials somewhere
-Using the windows task scheduler
I am happy that a workaround exists, but I'm still hoping that that it might be simple to create an admin privileges option for this plug-in. Pako never ceases to amaze me.
- Pako
- Plugin Developer
- Posts: 2294
- Joined: Sat Nov 11, 2006 1:31 pm
- Location: Czech Republic
- Contact:
Re: Windows Command Line
I spent working on it for several hours, but I finally decided that I will not do it.kkl wrote:Also, Pako, would you consider making an elevated command (i.e. administrator) version of this?
I found that it would have too many flaws and limitations.
That would actually be just such a better workaround.
Pako
Re: Windows Command Line
Me too.Pako never ceases to amaze me.
eventghost.net
Be there or be square.
Be there or be square.
Re: Windows Command Line
Thanks very much for taking the time to consider it.Pako wrote:I spent working on it for several hours, but I finally decided that I will not do it.
Re: Windows Command Line
Hi Pako,
I just wanted to give you one more feedback.
It works great now with EG v0.4.1r1687, thank you!
I just wanted to give you one more feedback.
It works great now with EG v0.4.1r1687, thank you!

