Services Utility: Ati HotKey Poller Service
|Display Name (?):|| Ati HotKey Poller|
|Short Name (?):|| Ati HotKey Poller|
|Executable (?):|| ati2evxx.exe|
|Library (?):|| None.|
|Depends On (?):|| None.|
|Supports (?):|| None.|
|Description (?):|| None.|
|OS (?):|| Third party or non-default|
The ATI HotKey Poller is installed with any current ATI driver set. It is used in intercepting any key combinations that you define to perform specific tasks that involve multiple monitors. Simply put this means that this service listens to your keystrokes and when you press keys that match hotkeys that you define (macros) then it will perform the assigned task to that hotkey. If you disable this service then you will not have this functionality. I suggest most people should disable this service unless they use multiple monitors or odd output devices such as TVs.
Most current video cards support dual monitor display, and a few others support more (like the Matrox Parahelia that supports tri monitor display). This allows you to expand your computer's desktop across multiple monitors to give you more real estate. People that use their computers in more advanced ways, such as graphics design or those that just use a lot of programs at once, find this ability quite useful.
The ATI display driver is equipped to support the functionality of multi display. And this is where the Hotkey Poller comes in. Within the display property (right click desktop, properties) and under settings and then under the advanced button, ten under the Displays tab you have the ability to select which monitors or TVs to output your display signals onto. You can also configure hotkeys that perform tasks such as switching between multiple monitors.
If you wish to disable this service you should set it to disabled and reboot your computer as it will not let you stop the service. If you cannot reboot (or you don't want to) then you can kill the executable ati2evxx.exe. You can freely terminate (kill) these through task manager as they are not protected services. There will most likely be two of these processes running under the same name, but they're both the same thing. One is most likely a driver intercepter and the other a frontend client of sorts. If there are two then you will need to kill both to properly close them.