• A computer running Windows XP Professional/MCE 2004/MCE 2005 (MCE 2005 required for full functionality), Windows Vista or Windows 7 (x86/x64).
• .NET Framework 2.0/3.5
• Version II MCE Remote and receiver.

• The blocking of buttons does only work for buttons that maps keyboard strokes, like the numerical and directional buttons.
• Remapping a button to a different button actually sends the equivalent keyboard shortcut for that particular MCE functionality.
• Setup does not check for system requirements.
• Only one buttonset per file is supported, however multiple config files are suported.
• Detection of buttons # and * needs improvement.

Unpack the downloaded package where you seem fit and run ControlRemote.exe.
Shortcuts and startup options can be configured from the Settings UI.
If a previous version of ControlRemote has been run, settings can be upgraded.

The settings can be accessed by double clicking the Tray icon next to the clock, or by rightclick the icon and select Settings.

Settings Autoload at log on Places a shortcut to ControlRemote.exe in your Start-up folder. Enabled at startup ControlRemote will be enabled when it starts, listening for remote commands. Show splash screen Shows a splash screen while loading. Desktop shortcut Places a shortcut to ControlRemote.exe on your desktop. MouseLock icon When the mouselock is enabled, ControlRemote will use a different cursor to notify you. Smooth mouse When the mouselock is enabled, moving of the mouse pointer via ControlRemote is accelerated. Ignore key "Unknown" By design the MCE Remote sends series of codes for a single press, where only some are “real” button codes. Checking this option lets ControlRemote discard any code not matching to a button. (Recommended). MCE Standby fix Some users had issues resuming from STR/hibernation on MCE 2005. This fix should solve this issue. Alert on logged error Besides logging, also show a popup message of the error. Display notify popup for caught event Shows a taskbar notification popup (like Messenger) with information of the caught button event. Update pre v1.8 config files when loaded A minor change was made to the XML schema for version 1.8.0. This option will update any "old" config file and re-save it to use the new format. Display debug options in menu Display the debug menu to allow some troubleshooting options. Logging Level Sets the level of logging of messages, exceptions and errors. Recommended “ERROR”. Type Type of log; EVENT, FILE or NONE.

The buttons configuration is by default loaded from a XML file located in
<installation directory>\config\default.xml.
View sample file.
Creating your configuration is not hard, but you should be familiar with editing XML documents. The file buttons-example.xml should give you some hints, and you can use a copy of this file as a template (just rename it to buttons.xml or whatever you prefer when you’re done).

The root element contains the
nodes.


Settings
<setting id="" value="" />

<setting id="sleep" value="350" />
The “sleep” setting determines the time in milliseconds
ControlRemote sleeps before handling another button event.
Default value is 350. You can try different values if you experience
multiple actions for a single press.

<setting id="mousespeed" value="8" />
The “mousespeed” setting determines the distance in pixels
ControlRemote moves the mouse pointer when mouselock is activated.
Default value is 8. Higher value means higher speed but less precision.


Mouse
<mouseButtons><mouseButton id="" value="" /></mouseButtons>

The mouseButton node contains the mouseButton configuration for the mouselock feature.
Valid id’s are “leftclick”, “rightclick” and “clicklock”. The directional keys are
predefined for controlling the pointer. A custom cursor will be used to notify you when
the “remote mouse” functionality is enabled (optional).

Left-and rightclick maps to left and right mousebutton. The clicklock button is a toggle
state button allowing you to perform dragn’drop, move windows etc.
When enabled, the left- and rightclick buttons will stay in a “mouse down state” until
you click left/right again. Pressing the clicklock button again puts the buttons back to
normal mouse button functionality. The clicklock
functionality is only available when the mouselock macro has been executed.

Example:
<mouseButtons>
  <mouseButton id="leftclick" value="Enter" />
  <mouseButton id="rightclick" value="Back" />
  <mouseButton id="clicklock" value="TeletextYellow" />
</mouseButtons>