Killing a process when starting a program

[Madderikk]

Hey there,

I have a rather specific problem and I hope I'm not violating any rules or agreements by using the exact program names and such.

The thing is: I'm trying to set up my Logitech Rumblepad 2 as an alternative to my mouse so that I can browse the web or start/pause a movie while sitting comfortably on the couch/lying in my bed. The configuration works perfectly fine in the Logitech Gaming Software Profiler (v.5.10.127). Therefore I had to made a new profile with 'explorer.exe' being the executable and make it a globally active profile which leads to my problem...

When it comes to gaming that profile is making almost everything unplayable since most games doesn't even need the software to support the gamepad and I now have a forced mouse set-up with some random buttons that aren't even related to the supposed function in the game. That's why I thought that I could let EventGhost detect when I start a game or steam (since it has controller support in big picture-mode) and kill the process of the Logitech Profiler via a cmd command. I guessed that would have been the solution but somehow the gamepad's explorer-profile is still active (due to its global setting I'd say) and I'm no step ahead. This info may help: If I close the profiler manually (right-clicking the tray-icon -> Exit) and confirm the warning that the periphery may not work correctly, the profile is off meaning the controller is back to normal and perfectly usable in any game.
I also thought of restarting the 'explorer.exe' which doesn't seem to have an effect on the profile/driver although the profiler is already shut down.

I'm just asking here to see whether someone has a tip or knows an alternative solution. Meanwhile I'm still trying to get it to work. Thanks in advance.

Btw. I'm using the latest version of EventGhost (v.0.4.1.r1640) on Windows 7 Ultimate x64.

[themaster1]

So basically you want to kill the Logitech Gaming Software Profiler which i suppose is an executable right ?

If you know how to create task/switch events it's a piece of cake, you have to load the task create/switch event to begin with.

In the switch folder you create a macro called "Steam" and you add the event Task.Activated.Steam and Task.Created.Steam although i'm not sure of the syntax, double check in the log part (left side) when you start steam what it says exactly (uncheck "log only assigned events indeeed) .Then you add the action "enable exclusive folder" (which will point to a sub folder you'll create in the programs folder).
Create an action to kill the logitech software (probably with some python code) i have no idea how at the moment

Finally In the Programs folder you create a sub folder with macros for your mouse

[blaher]

Create an action to kill the logitech software (probably with some python code) i have no idea how at the moment

You could run a batch file with this in it:
C:\Windows\Syswow64\TaskKill /F /IM logitech.exe

where logitech.exe is the file you want to stop. Bring up task manager with ctrl + shift + esc to find the correct name of the logitech process you want to end.

[Madderikk]

At first, thanks for your replies and sorry for my late response, I was busy all week.

I get the feeling that I may have explained the situation a little too confusing...
I already killed the logitech process or rather the profiler (called 'LWEMon.exe') by using a batch file but it just doesn't have the effect it should have. Somehow, the configurations for the pad are still running. Only if I close the profiler manually, the settings stop working which is my aim, btw.. Besides, according to the Task Manager, there is no other Logitech-related process running. Is there a possibility to create a macro that closes the profiler manually (with automated key hits or mouse movements or something like that) or can I simply configure a mouse setup in EG and deactivate it when steam is started?

To clarify things, this is what I got so far:

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="1640">
    <Folder Name="Gamepad" Expanded="True">
        <Macro Name="Steam on?" Expanded="True">
            <Event Name="Task.Activated.Steam" />
            <Action>
                Window.FindWindow(u'LWEMon.exe', None, None, None, None, None, False, 0.0, 0)
            </Action>
            <Action>
                EventGhost.NewJumpIf(XmlIdLink(35), 0, False)
            </Action>
        </Macro>
        <Macro Name="Close Logitech Profiler" id="35" Expanded="True">
            <Action>
                System.Execute(u'E:\\Programme, Software\\Gamepad\\Close LWE.cmd', u'', 0, False, 2, u'', False, False)
            </Action>
        </Macro>
    </Folder>
</EventGhost>

[blaher]

Is there a possibility to create a macro that closes the profiler manually (with automated key hits or mouse movements or something like that)

Sure, just use the 'find window' which you've already discovered, then use a mouse click on the exit button, or send an (alt+f4). It could be a service rather than an .exe that needs ending too, in which case use the pic below as a guide and substitute AleternateMceIrService with the logitech service name.

[Madderikk]

Thanks for your answer

The problem with the Logitech Profiler is that there is no possibilty to exit it from it's window because there is no such option and using {Alt+F4} or clicking the 'X' will just let it end up in the hidden tray. Since I'm not always running the same programs at a time, I discovered, it's practically impossible to close it with automated mouse movements because the position of its tray icon could always be different.
Other than that I can't find the adressed Logitech service name or it just doesn't work (I used LWEMon and Logitech instead of 'AlternateMceIrService" in the command line).

[blaher]

You need to find the correct service name to have a chance. Type services.msc into the Windows search, sort by status, and look for any Logitech/Game/Profile sounding stuff that is 'Started'.

viewtopic.php?f=2&t=3987#p22917 might help if it doesn't work after you find the service name.