• A computer running Windows XP Professional/MCE 2004/MCE 2005 (MCE 2005 required for full functionality).
• .NET Framework 2.0
• 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 is supported at the moment.
• Detection of buttons # and * needs improvement.

Run ControlRemote-setup.exe and follow the on screen instructions. If a previous version of ControlRemote has been run, settings can be upgraded. If you have downloaded a zipped release, simply unpack it where you like and run ControlRemote.exe. Shortcuts and startup options can be configured from the Settings UI.

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

1. 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. Desktop shortcut Places a shortcut to ControlRemote.exe on your desktop. 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). Show splash screen Shows a splash screen while loading. MouseLock icon When the mouselock is enabled, ControlRemote will use a different cursor to notify you. 2. Logging level Sets the level of logging of messages, exceptions and errors. Recommended “ERROR”. 3. ControlRemote web site link 4. PayPal donation web page link You may use ControlRemote free of charge for personal, non-commercial use. However, if you find it useful and would like to support my work and this kind of development, sending a PayPal donation by clicking the image will be highly appreciated. 5. Application version number

The buttons configuration is loaded from a XML file located in
<installation directory>\config\buttons.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 buttons-blank.xml as a template (just rename it to buttons.xml 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>