XBMC will be renamed to Kodi for v14. Read here for more details

List of MCE remote controls, NFS

From Kodi
(Difference between pages)
Jump to: navigation, search
(Unbranded MCE remote)
 
(Network Filesystem Sharing (on Windows))
 
Line 1: Line 1:
This is a (probably futile) attempt to keep up with the vast range of MCE remotes out there, and give some indication of how well they work with XBMC.
+
==Introduction==
 +
:'''Network Filesystem''', (mostly called NFS), is a direct competitor to the [[SMB]] sharing. It benefits from low protocol overhead and unix like authentication via UIDs instead of usernam/password combinations. It is commonly found on all linux/unix distributions aswell as on Mac OS X and Solaris.
  
This article assumes you are using build 26407 or later of XBMC. Earlier builds don't have the support for MCE remotes built in.
+
:NFS sharing has many advantages over the other options, mainly:
 +
* It is already incorporated in UNIX like operating systems, eliminating the need for additional software and services to be installed on your PC
 +
* It allows for authentication by UID, removing the need of saving username and password in XBMC source xml files (but also makeing it weak for attacks - so NFS should be only used inside the own LAN)
 +
* Once properly configured, it will allow your network shares to be seen and accessed by not only XBMC, but also any other machine on your network.<br /><br />
  
If you are adding a review please try to be as detailed as possible about the remote. For example:
+
==Network Filesystem Sharing (on Windows)==
<ul>
+
:For ''serving'' and sharing files with NFS from Windows there seem to be three choices:
  <li>What operating systems and versions of XBMC have you tested on</li>
+
*Windows Server 2003 R2 and Windows Server 2008 have built-in NFS Server and Client through Subsystem for UNIX-based Applications (SUA).  With 64-bit support, this solution supports files up to 4TB in size
  <li>Does the remote send keystrokes or is it MS compatible?</li>
+
*[http://en.wikipedia.org/wiki/Microsoft_Windows_Services_for_UNIX Microsoft Windows Services for UNIX (SFU)] available [http://www.microsoft.com/download/en/details.aspx?id=274 here]for Windows 2000, Windows XP Professional (NOT Home edition, without a [http://www.networkedmediatank.com/showthread.php?tid=1434 hexedit hack]), Windows 2003 Server, and Windows Home Server (based on 2003 Server).  SFU is 32-bit only, which ''may'' mean it only supports files up to 2GB in size, [http://www.suacommunity.com/SUA_Tools_Env_Start.htm#_Toc203389873 according to some sources] (this is unconfirmed).  A good installation guide can be found [http://www.networkedmediatank.com/showthread.php?tid=1434 here].  Windows SFU will not install on Windows Vista or Windows 7, so there is no way to ''serve'' NFS from Windows Vista or Windows 7 with the possible exception of the haneWIN solution below, but it is unconfirmed if that works with Windows Vista/7.
  <li>If it's MS compatible have you tested reconfiguring it using the registry and did this work?</li>
+
*[http://www.hanewin.net/nfs-e.htm haneWIN NFS Server for Windows] - a shareware program that costs 19EUR for non-commercial use.  Claims to work for "Windows 2000 and above"
</ul>
+
  
  
 +
:For ''Accessing'' files on an NFS server from a Windows client
 +
*Accessing an NFS share natively from within XBMC for Windows is not possible right now. The porting of the needed library (libnfs) is a work in progress with low priority at the moment, since it is very complex.
 +
*NFS shares can be mounted at the OS-level in Windows with the built-in SUA NFS client available only in Windows Vista/7 Ultimate and Enterprise editions.  An NFS client is available for Windows 2000, XP Pro, 2003 Server, and WHS (Windows Home Server) through Windows Services for UNIX (SFU) mentioned above.
  
== Microsoft Media Center Remote Control ==
+
==Network Filesystem Sharing (on Mac OS X)==
 +
<big>Introduction</big>
 +
:'''NFS Sharing''', is build into Mac OSX (OS 10.5 and later). For basic setup guidelines please take a look at the following links:
  
Original and best! I don't know if Microsoft still sell them, but there are usually lots available on eBay. They tend to be a bit expensive but they are well made and highly configurable.  
+
* [http://www.macuser.de/forum/f113/10-5-1-a-327813/ for 10.5 (leopard)]
 +
* [http://seanmcgrath.wordpress.com/2010/07/05/setup-nfs-on-mac-os-x-10-6/ for 10.6 (snow leopard]
  
[[Image:microsoftlearningremote.jpg]]
+
:'''Note!''' This article assumes some basic knowledge of the UNIX/BSD operating-system interface and environment.
 +
<big>Configuring NFS Sharing for using with XBMC (leopard and snow leopard)</big>
  
There are 3 versions of this remote:
+
For allowing non root users to connect to the NFS server the file "/System/Library/LaunchDaemons/com.apple.nfsd.plist" has to be edited. Add the option "-N" to the startup parameters. Otherwise XBMC can only access the NFS server when run as root.
  
- Microsoft (Microsoft Logo at bottom of remote and on receiver)
+
  <array>
 +
    <string>/sbin/nfsd</string>
 +
    '''<string>-N</string>'''
 +
  </array>
  
[[Image:mcelearningsmalla.jpg]] (Microsoft)
 
  
- Microsoft with Teletext (Microsoft Logo at bottom of remote and on receiver) plus Red,Green,Yellow,Blue and a 'teletext' button.
+
The configuration of the NFS server takes place in the config file "/etc/exports". As already mentioned the authentication to the NFS server is done through UIDs. So for XBMC this means that the UID which the XBMC process is running under is given to the NFS server. For knowing the UID just type "id" into a console:
  
[[Image:mceteletextsmall.jpg]] (Microsoft with Teletext)
+
  penix:~ memphis$ id
 +
  uid=501(memphis)
  
- Dell (No Logos on remote or receiver and no TV standby or volume learning ability)
+
So my UID is 501. For iOS keep in mind that the user XBMC is running as is the user "mobile" which should have UID 501 also.
  
[[Image:remote-microsoft.jpg]] (Dell - No Learning)
+
A basic configuration for exporting one PATH with NFS is looking like this:
  
All these variants of the MS remote will work out of the box with XBMC Live, though with a standard Linux install you'll need to install and configure Lirc. To get it to work on Windows you need to configure it to simulate key-presses. See [[Using a Microsoft remote control in Windows]] for details.
+
  /nfs/export -mapall=nobody -alldirs <ip>
  
{| border="1"
 
|-
 
! remote
 
! wake on USB?
 
! multi-device control?
 
! volume learning?
 
! universal-remote code available?
 
! IR transmit?
 
! linux/osx/windows?
 
|-
 
| Microsoft
 
| ?
 
| N*
 
| Y
 
| ?
 
| ?
 
| all
 
|-
 
| MS w/ Teletext
 
| ?
 
| N*
 
| Y
 
| ?
 
| ?
 
| all
 
|-
 
| Dell
 
| ?
 
| N
 
| N
 
| ?
 
| ?
 
| all
 
|}
 
  
== Hauppauge Media Center Remote Control Kit ==
+
By changing some of the options of that line we can realise 3 different approaches see the linux section for this and try to adapt according to the given examples for Mac OSX.
  
[[Image:remote-hauppauge.jpg]]
+
<big>Examples for exported pathes</big>
  
Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Hauppauge.
+
  /nfs/allread                -ro -mapall=nobody -alldirs
 +
  /nfs/allwrite              -mapall=nobody -alldirs -network 192.168.1.0 -mask 255.255.255.0
 +
  /nfs/writeAsMemphis        -mapall=501 -alldirs 192.168.1.5
 +
  /nfs/xbmcuser
  
Note that this is not the same as the Hauppauge 45 button remote that plugs into the Hauppauge PCI card. The Hauppauge 45 button remote has caused some hair tearing and wouldn't be the first choice for an XBMC remote.
+
The path "'''/nfs/allread'''" can be accessed from all computers ('''no ip given'''), readonly ("'''-ro'''") and access rights for user nobody are used ("'''-mapall=nobody'''").
  
== Mediagate GP-IR02BK ==
+
The path "'''/nfs/allwrite'''" can be accessed from all computers on the subnet 192.168.1.0/255.255.255.0, readwrite (no "'''-ro'''") and access rights for user nobody are used ("'''-mapall=nobody'''").
  
[[Image:Remote-IR02BK.jpg]]
+
The path "'''/nfs/writeAsMemphis'''" can be accessed from the computer with the IP 192.168.1.5, readwrite (no "'''-ro'''"), and access rights for user with UID 501 (e.x. memphis in my case) are used ('''-mapall=501''').
  
Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Mediagate. The remote is currently available on Amazon UK and US.
+
The path "'''/nfs/xbmcuser'''" can be accessed from all computers ('''no ip given'''), readwrite (no "'''-ro'''") and the access rights for the UID which is connecting to the NFS server are used ("'''-mapall'''" removed).
  
There are some additional buttons not on the official MS remote. These can be configured using the following in the .reg file:
+
The UIDs which are used to connect to the NFS server or which are specified with "-mapall" have to exist on the NFS server. Otherwise the filesystem permission can't be set.
  
<pre>  27,00,00,00,04,03,04,\ ; Zoom    - sends ctrl-shift-A
+
Remember - access rights are these you give in the filesystem. So for makeing the "'''/nfs/allwrite'''" export path writeable to everyone the filesystem access rights have to be set for user nobody:
  47,00,00,00,04,01,10,\ ; Music    - sends ctrl-M
+
  49,00,00,00,04,01,0C,\ ; Pictures - sends ctrl-I
+
  4A,00,00,00,04,01,08,\ ; Movies  - sends ctrl-E
+
  50,00,00,00,04,01,04,\ ; Radio    - sends ctrl-A
+
  5a,00,00,00,04,03,09  ; Teletext - sends ctrl-shift-F</pre>
+
  
== DEC-200B ==
+
  chown -r nobody /nfs/allwrite
  
[[Image:Remote-200B.jpg]]
+
The server can be started by doing:
  
Compatible  with the MS remote. Works out of the box with XBMCLive. Not tested (so far) with the Windows and OSX versions. Don't know if it's configurable with the registry.
+
  $ sudo nfsd start
  
== AVS Gear HA-IR01SV ==
+
==Network Filesystem Sharing (on Linux)==
  
[[Image:Remote-HAIR01SV.jpg]]
+
<big>Introduction</big>
 +
:'''NFS Sharing''', is build into linux kernel since long time ago. For basic setup guidelines please take a look at the following link:
  
Compatible with the MS remote. Works out of the box with XBMCLive. Not tested (so far) with the Windows and OSX versions. Don't know if it's configurable with the registry. Currently available from Amazon UK (search for HA-IR01SV). Googling suggests it is widely available.
+
* [http://wiki.ubuntuusers.de/NFS for Ubuntu]
  
== Speedlink SL-6399 ==
+
:'''Note!''' This article assumes some basic knowledge of the Linux/UNIX/BSD operating-system interface and environment.
  
[[Image:remote-SL6399.jpg]]
 
  
Cheap and cheerful remote. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX.
 
  
Apparently there are different usb receivers that come with the remote.
+
<big>Configuring NFS Sharing for using with XBMC</big>
<pre>
+
ID 1241:1503 Belkin Keyboard      // all keys seem to work
+
ID 1241:e000 Belkin                // keys Start, RTV, Videos, Music, Pictures, MyTV don't work
+
</pre>
+
  
There are several extra buttons not on the standard MS remote. If you want to add mappings for
+
The configuration of the NFS server takes place in the config file "/etc/exports". As already mentioned the authentication to the NFS server is done through UIDs. So for XBMC this means that the UID which the XBMC process is running under is given to the NFS server. For knowing the UID just type "id" into a console:
these keys here are the entries you need in keyboard.xml.
+
  
<pre>&lt;t mod="ctrl"&gt;Notification(Key, TV power, 3)&lt;/t&gt;          &lt;!-- TV power --&gt;
+
   penix:~ memphis$ id
&lt;menu&gt;Notification(Key, More, 3)&lt;/menu&gt;                  &lt;!-- More --&gt;
+
   uid=501(memphis)
&lt;z mod="ctrl,shift"&gt;Notification(Key, Aspect, 3)&lt;/z&gt;      &lt;!-- Aspect --&gt;
+
&lt;e mod="ctrl"&gt;Notification(Key, Red/Videos, 3)&lt;/e&gt;        &lt;!-- Red/Videos --&gt;
+
&lt;m mod="ctrl"&gt;Notification(Key, Green/Music, 3)&lt;/m&gt;      &lt;!-- Green/Music --&gt;
+
&lt;i mod="ctrl"&gt;Notification(Key, Yellow/Pictures, 3)&lt;/i&gt;   &lt;!-- Yellow/Pictures --&gt;
+
&lt;t mod="ctrl,shift"&gt;Notification(Key, Blue/MyTV, 3)&lt;/t&gt;   &lt;!-- Blue/MyTV --&gt;
+
&lt;g mod="ctrl"&gt;Notification(Key, Guide, 3)&lt;/g&gt;            &lt;!-- Guide --&gt;
+
&lt;o mod="ctrl"&gt;Notification(Key, RTV, 3)&lt;/o&gt;              &lt;!-- RTV --&gt;
+
&lt;f1&gt;Notification(Key, Help, 3)&lt;/f1&gt;                      &lt;!-- Help --&gt;
+
&lt;return mod="alt"&gt;Notification(Key, Maximise, 3)&lt;/return&gt; &lt;!-- Maximise/restore --&gt;
+
&lt;a mod="ctrl"&gt;Notification(Key, Radio, 3)&lt;/a&gt;            &lt;!-- Radio --&gt;
+
&lt;m mod="ctrl,shift"&gt;Notification(Key, DVD, 3)&lt;/m&gt;        &lt;!-- DVD --&gt;
+
&lt;a mod="ctrl,shift"&gt;Notification(Key, Audio, 3)&lt;/a&gt;      &lt;!-- Audio --&gt;
+
&lt;u mod="ctrl"&gt;Notification(Key, Title, 3)&lt;/u&gt;            &lt;!-- Title --&gt;</pre>
+
  
== Unbranded MCE remote ==
+
So my UID is 501. For iOS keep in mind that the user XBMC is running as is the user "mobile" which should have UID 501 also.
  
[[Image:remote-unbranded.jpg]]
+
A basic configuration for exporting one PATH with NFS is looking like this:
  
There is no manufacturer's name on this remote or the manual, though it may be a [http://www.chinavasion.com/product_info.php/pName/pc-remote-control-media-function-remote/ Chinavasion CVSB-983] or [http://www.acowin.com.hk/product456.html Acowin AURC-001]. It can be used with Logitech Harmony Remote Software by picking Computer>>Media Center PC>>Chinavasion>>CVSB-983.
+
  /nfs/export <ip or iprange which is allowed to connect>(rw,all_squash,insecure)
  
They are available on Ebay for as little as $2 ($10ish after S&H). It's cheap and feels a bit flimsy, but it works well enough. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse, although it's no match for a proper mouse or trackpad.
+
The important options here for usage with XBMC are the "ip or iprange" and the "insecure" option. The "insecure" option is needed because we want to be able to run XBMC without root privileges. When using secure only the root user (uid 0) may have access to the nfs share. The "ip or iprange" specifys from wich hosts in the network the access to the NFS export is allowed.  
  
It isn't very configurable and certain buttons don't work as they should. For example, the fast forward and rewind buttons skip forward or backwards instead of moving gradually.
+
By changing some of the options of that line we can realise 3 different approaches for getting the access rights configured as we want:
  
If you want to add mappings for the four coloured keys here are the entries you need in keyboard.xml. The other keys can't be trapped.
+
1. The option all_squash (most insecure) - all UIDs connected to the NFS server are mapped to UID 65534 (user nobody)
 +
* In this case all files which shall be accessed on the NFS exported path should have the correct rights for the user "nobody".
 +
2. Using the option "all_squash" in conjunction with the option "anonuid" and "anongid"
 +
* By adding the options "anonuid=501" and "anongid=501" all accesses would be mapped to the user with UID 501 (user "mobile" on iOS or user "memphis" in my example above)
 +
3. Removing the "all_squash" option the accesses will be done with the UID given from the user which is running XBMC
 +
* So if XBMC is started with username foobar (which has UID 1000) all accesses to the NFS export path will be made with UID 1000.
  
<pre>&lt;f1 mod="ctrl,alt"&gt;Notification(Key, Green, 3)&lt;/f1&gt;  &lt;!-- Green --&gt;
 
&lt;f2 mod="ctrl,alt"&gt;Notification(Key, Orange, 3)&lt;/f2&gt; &lt;!-- Orange --&gt;
 
&lt;f3 mod="ctrl,alt"&gt;Notification(Key, Blue, 3)&lt;/f3&gt;  &lt;!-- Blue --&gt;
 
&lt;f4 mod="ctrl,alt"&gt;Notification(Key, Yellow, 3)&lt;/f4&gt; &lt;!-- Yellow --&gt;</pre>
 
  
Update 16th Jan: the rewind button sends three keypresses, left, then ctrl-left, then ctrl-shift-B. The left press causes the video to jump back 30 seconds. With the later releases of XBMC the ctrl-shift-B then starts the rewind (release v9.11 ignores ctrl-keypresses).
 
  
== GoTView PC Remote ==
+
<big>Examples for exported pathes</big>
The GoTView PC Remote control looks exactly like the "unbranded remote" above. It is also detected as MCE remote by lircd, but has slightly different keycodes, which are incompatiable with xbmc defaults.
+
To make things work correctly, add something like the following before the &lt;/keyboard&gt; &lt;/global&gt; lines in your /usr/local/share/xbmc/system/keymaps/keyboard.xml file
+
<pre>
+
      <one mod="ctrl,alt,shift">ContextMenu</one>
+
      <two mod="ctrl,alt,shift">ActivateWindow(PlayerControls)</two>
+
      <three mod="ctrl,alt,shift">ActivateWindow(music)</three>
+
      <four mod="ctrl,alt,shift">ActivateWindow(pictures)</four>
+
      <five mod="ctrl,alt,shift">ActivateWindow(video)</five>
+
      <home mod="ctrl,alt,shift">ActivateWindow(MusicPlaylist)</home>
+
      <r mod="ctrl">Queue</r>
+
      <h mod="ctrl,alt,shift">Info</h>
+
      <b mod="ctrl,alt,shift">ActivateWindow(MusicOSD)</b>
+
      <f mod="ctrl,alt,shift">ActivateWindow(VisualisationPresetList)</f>
+
     
+
</pre>
+
  
== VRC-1100 ==
+
  /nfs/allread                *(r,all_squash,insecure)
 +
  /nfs/allwrite              192.168.1.0/24(rw,all_squash,insecure)
 +
  /nfs/writeAsMemphis        192.168.1.5(rw,all_squash,insecure,anonuid=501,anongid=501)
 +
  /nfs/xbmcuser              *(rw,insecure)
  
[[Image:remote-VRC1100.jpg]]
+
The path "'''/nfs/allread'''" can be accessed from all computers ("'''*'''"), readonly ("'''r'''") and access rights for user nobody are used ("'''all_squash'''").
  
There is no manufacturer's name on this remote or the manual, but they appear to be from Ortek (http://www.ortek.com/product.asp?pid=103&cname=Mobility). They are widely available on eBay. Maplin UK also sell an own-brand remote control (product code N18HC) that seems to be identical. The remote simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse, although it's no match for a proper mouse or trackpad.
+
The path "'''/nfs/allwrite'''" can be accessed from all computers on the subnet 192.168.1.0/255.255.255.0, readwrite ("'''rw'''") and access rights for user nobody are used ("'''all_squash'''"). Remeber that "'''rw'''" doesn't mean automatically that you can write. The user "nobody" has to have write access to the exported path too for finally allow writing.
  
Note that the the i button sends a right mouse click, which isn't much use in XBMC as the right click can't be mapped to an action. There is no way round this without using some helper app like Eventghost, but the Info action could be mapped to one of the other buttons.
+
The path "'''/nfs/writeAsMemphis'''" can be accessed from the computer with the IP 192.168.1.5, readwrite ("'''rw'''"), and access rights for user with UID 501 (e.x. memphis in my case) are used ("'''all_squash,anonuid=501,anongid=501'''").
  
If you want to add mappings for the four coloured keys and the four keys below them here are the entries you need in keyboard.xml. The top left (Internet Explorer) key can't be trapped.
+
The path "'''/nfs/xbmcuser'''" can be accessed from all computers ("'''*'''"), readwrite ("'''rw'''") and the access rights for the UID which is connecting to the NFS server are used ("'''all_squash'''" removed).
  
<pre>&lt;t mod="ctrl,shift"&gt;Notification(Key, Yellow, 3)&lt;/t&gt; &lt;!-- Yellow button --&gt;
+
The UIDs which are used to connect to the NFS server or which are specified with "anonuid" and "anongid" have to exist on the NFS server. Otherwise the filesystem permission can't be set.
&lt;m mod="ctrl"&gt;Notification(Key, Blue, 3)&lt;/m&gt;        &lt;!-- Blue button --&gt;
+
&lt;i mod="ctrl"&gt;Notification(Key, Green, 3)&lt;/i&gt;        &lt;!-- Green button --&gt;
+
&lt;e mod="ctrl"&gt;Notification(Key, Red, 3)&lt;/e&gt;          &lt;!-- Red button --&gt;
+
&lt;o mod="ctrl"&gt;Notification(Key, u/Yellow, 3)&lt;/o&gt;    &lt;!-- Button under Yellow --&gt;
+
&lt;g mod="ctrl"&gt;Notification(Key, u/Blue, 3)&lt;/g&gt;      &lt;!-- Button under Blue --&gt;
+
&lt;t mod="ctrl"&gt;Notification(Key, u/Green, 3)&lt;/t&gt;      &lt;!-- Button under Green --&gt;
+
&lt;m mod="ctrl,shift"&gt;Notification(Key, u/Red, 3)&lt;/m&gt;  &lt;!-- Button under Red --&gt;</pre>
+
  
 +
Remember - access rights are these you give in the filesystem. So for makeing the "'''/nfs/allwrite'''" export path writeable to everyone the filesystem access rights have to be set for user nobody:
  
For full linux support see http://trac.xbmc.org/ticket/8827
+
  chown -r nobody /nfs/allwrite
  
== XBox DVD Remote ==
+
[[category:File Sharing]]
 
+
[[category:Linux]]
[[Image:Remote-xbox1.jpg]]
+
[[category:Mac OS X]]
 
+
The original DVD remote for XBox 1. This is a simple well working remote, almost out of the box experience and it has a good support in xbmc.<br/ >
+
See [http://wiki.xbmc.org/?title=HOW-TO_wire_your_XBOX_DVD-Remote_for_USB wiring] and [http://wiki.xbmc.org/?title=Lirc_Config_for_Xbox_DVD_Remote lirc config]
+
 
+
This remote won't work "out of the box" with Windows as it doesn't send keystrokes and can't be configured to do so. It can be made to work with a helper app like Eventghost or IR Server Suite.
+
See http://forum.xbmc.org/showthread.php?t=45337 for the details.
+
 
+
== Philips 5100 4in1 Vista MCE Remote ==
+
 
+
[[Image:philips5100-4in1 landscape.jpg]]
+
 
+
Philips have produced a family of remotes in this range designed for different sales regions each with different features.  This one has the ability to control 4 devices (PC, TV, Sat, Amp) and can be programmed using the manufacturer codes database supplied.  It also has the ability to learn functions from other remotes to replace any of its buttons, making it very versatile once customised to your home cinema setup.  However, the keys are not backlit and the supplied infra-red usb reciever only works with Vista or Windows 7.
+
 
+
Note: Also works with the Official Microsoft MCE reciever as it sends the same signals (RC-6), meaning it can be used on Windows XP via this reciever.
+
 
+
Discontinued - (Can be found on ebay UK)
+
 
+
== HP MCE Remote ==
+
 
+
[[Image:hpremote.jpg]] (Older)
+
 
+
[[Image:HPRemotenewer.jpg‎]] (Newer)
+
 
+
Both versions are compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the HP remote.
+
 
+
On Windows XP Pro SP3 the receiver was recognised and installed automatically. There are reports that Windows XP may not automatically detect the receiver unless you edit irbus.inf as described in http://it.megocollector.com/?p=8. It is not clear when this hack is needed.
+
 
+
With the Remote-XBMC.reg config all the buttons work in XBMC except for the "T" and "Print" buttons. To configure these buttons add the following to the .reg file:
+
 
+
<pre>  4E,00,00,00,04,01,22,\ ; Print button on HP remote - sends ctrl-5
+
  5A,00,00,00,04,01,23,\ ; T button on HP remote    - sends ctrl-6</pre>
+
 
+
== Asrock Remote ==
+
 
+
NB this is preliminary information based on a discussion in the forum.
+
 
+
[[File:AsrockRemote.jpg]]
+
 
+
The Asrock ION PCs come with a remote control. This is compatible with the Microsoft remote, and in Windows 7 (and possibly Vista) the .reg files used to reconfigure the MS remote will also work with the Asrock remote. The .reg files will not work in Windows XP because Windows XP does not detect the remote as an eHome device and install the eHome driver. It is possible the eHome drive could be installed with suitable modifications to irbus.inf (see the review of the HP remote above) but so far this has not been explored.
+
 
+
With the Remote-XBMC.reg config all the buttons work in XBMC except for the four buttons in the row above the coloured buttons. To configure these buttons to send the standard Media center keyboard shortcuts add the following to the .reg file:
+
 
+
<pre>  47,00,00,00,04,01,10,\ ; Asrock remote: Music    - sends ctrl-M
+
  49,00,00,00,04,01,0C,\ ; Asrock remote: Pictures - sends ctrl-I
+
  4A,00,00,00,04,01,08,\ ; Asrock remote: Movies  - sends ctrl-E
+
  50,00,00,00,04,01,04,\ ; Asrock remote: Radio    - sends ctrl-A</pre>
+
 
+
== Microsoft MCE Keyboard Remote ==
+
 
+
[[Image:Microsoftmcekeyboard.jpg‎]]
+
 
+
Similar to the buttons to the Microsoft MCE remote, but with a full keyboard and a 'nipple' for moving the mouse.  Range is limited and it requires a direct line of sight to the receiver.  Can be operated on the users lap. The keyboard has a very nice feel, though the mouse nipple is hard to use.
+
 
+
Works with the Official Microsoft MCE receiver and with compatible RC6 receivers like the HP receiver.
+
 
+
== AURC-002 ==
+
 
+
[[Image:AURC002.jpg‎]]
+
 
+
Manufactured by Acowin Industrial Limited; see http://www.acowin.com.hk/product535.html.  Microsoft MCE clone with a cloned HP receiver.  Compatible with the .reg files used to reconfigure the official Microsoft remote and receiver.
+
 
+
== Xbox 360 Wireless Controller for Windows ==
+
 
+
[[File:XBox360WirelessController.jpg]]
+
 
+
The [http://www.microsoft.com/hardware/gaming/ProductDetails.aspx?pid=090 Xbox 360 Wireless Controller for Windows], which is sold my Mircosoft with a separate receiver, works with XBMC 9.11 on Windows XP with Standard Microsoft Drivers.
+
 
+
The File '''Xbox360EventClient.exe''' from this [http://forum.xbmc.org/showpost.php?p=426397&postcount=11 Forum-Post] [[http://ul.to/4p5n3t Mirror]] (MD5: 4B69791B1DC2DA4400B5912CFF9EFED0) need to run in the Background. The default Keymapping is optimal.
+
 
+
 
+
 
+
[[Category:Remote]]
+

Revision as of 11:30, 24 June 2011

Contents

1 Introduction

Network Filesystem, (mostly called NFS), is a direct competitor to the SMB sharing. It benefits from low protocol overhead and unix like authentication via UIDs instead of usernam/password combinations. It is commonly found on all linux/unix distributions aswell as on Mac OS X and Solaris.
NFS sharing has many advantages over the other options, mainly:
  • It is already incorporated in UNIX like operating systems, eliminating the need for additional software and services to be installed on your PC
  • It allows for authentication by UID, removing the need of saving username and password in XBMC source xml files (but also makeing it weak for attacks - so NFS should be only used inside the own LAN)
  • Once properly configured, it will allow your network shares to be seen and accessed by not only XBMC, but also any other machine on your network.

2 Network Filesystem Sharing (on Windows)

For serving and sharing files with NFS from Windows there seem to be three choices:
  • Windows Server 2003 R2 and Windows Server 2008 have built-in NFS Server and Client through Subsystem for UNIX-based Applications (SUA). With 64-bit support, this solution supports files up to 4TB in size
  • Microsoft Windows Services for UNIX (SFU) available herefor Windows 2000, Windows XP Professional (NOT Home edition, without a hexedit hack), Windows 2003 Server, and Windows Home Server (based on 2003 Server). SFU is 32-bit only, which may mean it only supports files up to 2GB in size, according to some sources (this is unconfirmed). A good installation guide can be found here. Windows SFU will not install on Windows Vista or Windows 7, so there is no way to serve NFS from Windows Vista or Windows 7 with the possible exception of the haneWIN solution below, but it is unconfirmed if that works with Windows Vista/7.
  • haneWIN NFS Server for Windows - a shareware program that costs 19EUR for non-commercial use. Claims to work for "Windows 2000 and above"


For Accessing files on an NFS server from a Windows client
  • Accessing an NFS share natively from within XBMC for Windows is not possible right now. The porting of the needed library (libnfs) is a work in progress with low priority at the moment, since it is very complex.
  • NFS shares can be mounted at the OS-level in Windows with the built-in SUA NFS client available only in Windows Vista/7 Ultimate and Enterprise editions. An NFS client is available for Windows 2000, XP Pro, 2003 Server, and WHS (Windows Home Server) through Windows Services for UNIX (SFU) mentioned above.

3 Network Filesystem Sharing (on Mac OS X)

Introduction

NFS Sharing, is build into Mac OSX (OS 10.5 and later). For basic setup guidelines please take a look at the following links:
Note! This article assumes some basic knowledge of the UNIX/BSD operating-system interface and environment.

Configuring NFS Sharing for using with XBMC (leopard and snow leopard)

For allowing non root users to connect to the NFS server the file "/System/Library/LaunchDaemons/com.apple.nfsd.plist" has to be edited. Add the option "-N" to the startup parameters. Otherwise XBMC can only access the NFS server when run as root.

 <array>
   <string>/sbin/nfsd</string>
   <string>-N</string>
 </array>


The configuration of the NFS server takes place in the config file "/etc/exports". As already mentioned the authentication to the NFS server is done through UIDs. So for XBMC this means that the UID which the XBMC process is running under is given to the NFS server. For knowing the UID just type "id" into a console:

 penix:~ memphis$ id
 uid=501(memphis)

So my UID is 501. For iOS keep in mind that the user XBMC is running as is the user "mobile" which should have UID 501 also.

A basic configuration for exporting one PATH with NFS is looking like this:

 /nfs/export -mapall=nobody -alldirs <ip>


By changing some of the options of that line we can realise 3 different approaches see the linux section for this and try to adapt according to the given examples for Mac OSX.

Examples for exported pathes

 /nfs/allread                -ro -mapall=nobody -alldirs
 /nfs/allwrite               -mapall=nobody -alldirs -network 192.168.1.0 -mask 255.255.255.0
 /nfs/writeAsMemphis         -mapall=501 -alldirs 192.168.1.5
 /nfs/xbmcuser

The path "/nfs/allread" can be accessed from all computers (no ip given), readonly ("-ro") and access rights for user nobody are used ("-mapall=nobody").

The path "/nfs/allwrite" can be accessed from all computers on the subnet 192.168.1.0/255.255.255.0, readwrite (no "-ro") and access rights for user nobody are used ("-mapall=nobody").

The path "/nfs/writeAsMemphis" can be accessed from the computer with the IP 192.168.1.5, readwrite (no "-ro"), and access rights for user with UID 501 (e.x. memphis in my case) are used (-mapall=501).

The path "/nfs/xbmcuser" can be accessed from all computers (no ip given), readwrite (no "-ro") and the access rights for the UID which is connecting to the NFS server are used ("-mapall" removed).

The UIDs which are used to connect to the NFS server or which are specified with "-mapall" have to exist on the NFS server. Otherwise the filesystem permission can't be set.

Remember - access rights are these you give in the filesystem. So for makeing the "/nfs/allwrite" export path writeable to everyone the filesystem access rights have to be set for user nobody:

 chown -r nobody /nfs/allwrite

The server can be started by doing:

 $ sudo nfsd start

4 Network Filesystem Sharing (on Linux)

Introduction

NFS Sharing, is build into linux kernel since long time ago. For basic setup guidelines please take a look at the following link:
Note! This article assumes some basic knowledge of the Linux/UNIX/BSD operating-system interface and environment.


Configuring NFS Sharing for using with XBMC

The configuration of the NFS server takes place in the config file "/etc/exports". As already mentioned the authentication to the NFS server is done through UIDs. So for XBMC this means that the UID which the XBMC process is running under is given to the NFS server. For knowing the UID just type "id" into a console:

 penix:~ memphis$ id
 uid=501(memphis)

So my UID is 501. For iOS keep in mind that the user XBMC is running as is the user "mobile" which should have UID 501 also.

A basic configuration for exporting one PATH with NFS is looking like this:

 /nfs/export <ip or iprange which is allowed to connect>(rw,all_squash,insecure)

The important options here for usage with XBMC are the "ip or iprange" and the "insecure" option. The "insecure" option is needed because we want to be able to run XBMC without root privileges. When using secure only the root user (uid 0) may have access to the nfs share. The "ip or iprange" specifys from wich hosts in the network the access to the NFS export is allowed.

By changing some of the options of that line we can realise 3 different approaches for getting the access rights configured as we want:

1. The option all_squash (most insecure) - all UIDs connected to the NFS server are mapped to UID 65534 (user nobody)

  • In this case all files which shall be accessed on the NFS exported path should have the correct rights for the user "nobody".

2. Using the option "all_squash" in conjunction with the option "anonuid" and "anongid"

  • By adding the options "anonuid=501" and "anongid=501" all accesses would be mapped to the user with UID 501 (user "mobile" on iOS or user "memphis" in my example above)

3. Removing the "all_squash" option the accesses will be done with the UID given from the user which is running XBMC

  • So if XBMC is started with username foobar (which has UID 1000) all accesses to the NFS export path will be made with UID 1000.


Examples for exported pathes

 /nfs/allread                *(r,all_squash,insecure)
 /nfs/allwrite               192.168.1.0/24(rw,all_squash,insecure)
 /nfs/writeAsMemphis         192.168.1.5(rw,all_squash,insecure,anonuid=501,anongid=501)
 /nfs/xbmcuser               *(rw,insecure)

The path "/nfs/allread" can be accessed from all computers ("*"), readonly ("r") and access rights for user nobody are used ("all_squash").

The path "/nfs/allwrite" can be accessed from all computers on the subnet 192.168.1.0/255.255.255.0, readwrite ("rw") and access rights for user nobody are used ("all_squash"). Remeber that "rw" doesn't mean automatically that you can write. The user "nobody" has to have write access to the exported path too for finally allow writing.

The path "/nfs/writeAsMemphis" can be accessed from the computer with the IP 192.168.1.5, readwrite ("rw"), and access rights for user with UID 501 (e.x. memphis in my case) are used ("all_squash,anonuid=501,anongid=501").

The path "/nfs/xbmcuser" can be accessed from all computers ("*"), readwrite ("rw") and the access rights for the UID which is connecting to the NFS server are used ("all_squash" removed).

The UIDs which are used to connect to the NFS server or which are specified with "anonuid" and "anongid" have to exist on the NFS server. Otherwise the filesystem permission can't be set.

Remember - access rights are these you give in the filesystem. So for makeing the "/nfs/allwrite" export path writeable to everyone the filesystem access rights have to be set for user nobody:

 chown -r nobody /nfs/allwrite
Personal tools
Namespaces

Variants
Actions
Navigation
Wiki help
Toolbox