Hi all,
maybe you was watching my HookApplication project - just to remind you, HookApplication allows you to hook your specific actions to any process.
Some blog posts I wrote are here:
http://msmvps.com/blogs/martinzugec/archive/2007/03/01/hookapplication-some-real-life-examples.aspx
http://msmvps.com/blogs/martinzugec/archive/2007/02/16/hookapplication-introduction-hope-so-you-will-like-it.aspx
Problem was that after creation of concept itself, I didnt have enough time to work on it :(
I would like to give you access to technology preview - small utility that is providing you with access to all features I mentioned before, however you will need to create your own configuration and it is not really user friendly.
So, how to use it?
1.) Create folder with name of your process inside Configuration folder (msnmsgr.exe for example).
2.) Inside this folder, create file Configuration.ini
3.) Inside this file, specify configuration for particular process
Currently only (very) limited number of options are available:
Run - run specified command
RunWait - run specified command and wait until it finishes
RunHidden - run specified command hidden
RunWaitHidden - run specified command hidden and wait until it finishes
RunMainProgram - run process that is hooked (in this case msnmsgr.exe)
RunWaitMainProgram - run process that is hooked and wait until it finishes
RunMainProgramHidden - run process that is hooked
RunWaitMainProgramHidden - run process that is hooked hidden and wait until it finishes
For example if I would create small script that is killing messenger (taskkill /f /im msnmsgr.exe - reason is that if you run messenger twice, it will get corrupted and you wont see GUI, only multiple processes), my configuration appears as follows:
C:\HA\Configuration\msnmsgr.exe\Configuration.ini:
RunWaitHidden=KillMessenger.cmd
RunMainProgram
Another example - I would like to disable Solitaire.exe. I am using MsgBox.exe utility:
C:\HA\Configuration\Solitaire.exe\Configuration.ini:
Run=MsgBox.exe "Solitaire is not allowed"
We only created configuration so far, but now we must enable these entries - to do it, use script called ActivateHooks with /Add parameter...
/Add supports *, so when you are finished, just use ActivateHooks.cmd /Add * and it should work.
I am sure you will come with more examples... As I said, it is not really usefriendly (as is usual with technology previews), however if you want to test it, you can (and I would really really love to get any feedback ;))