SambaBitTorrentWeb

NOTE!!! There seems to be an issue where the O!Play will run out of memory and crash the DvdPlayer application when using this modification. This is probably the reason that the O!Play doesn't support Samba/BitTorrent while other similar devices do. While other devices have internal harddrives which support a swap partition (effectively increasing available memory), it seems that the physical memory limitation can cause problems.

For now, it is recommended to use the ipkg_install.sh (temporary) method to get temporary Samba access to the O!Play. When you have finished transferring files, reset the system and you can operate it normally.

Here is another easy method to add Samba, BitTorrent and a Web interface to the Asus O!Play.

The O!Play is based on the same CPU and Firmware as several other Media Players, such as the A.C. Ryan PlayON HD. These other players have the ability to use Samba and BitTorrent, as well as having a Web Interface to control these functions. It is fairly easy to get these utilities running on the O!Play as well.

I have put together a small tarball which contains all the necessary files extracted from the AC Ryan Firmware. Download the file oplay_ipkg.tar and copy the .tar file onto a USB memory stick or USB Hard Drive.

Once you have them on the USB storage device, connect it to your O!Play and telnet to the O!Play from your host machine and log on as root.

On the O!Play, change to the directory containing the .tar file. Normally it is /tmp/usbmounts/sda1, but it might be sdb1 depending on the number of devices and partitions. Extract the file using 'tar xf oplay_ipkg.tar'.

You will have two directories named packages and scripts, as well as the ipgk-cl executable and two installation scripts: ipkg_install.sh and ipkg_nand_install.sh. The two installation scripts are used in slightly different ways depending on what you want to accomplish

The first installation script, ipkg_install.sh, is designed to do a temporary installation. When run, it will install the packages into memory, create samba shares and start the Samba daemon, BitTorrent daemon and the Web interface. The downside to this installation method is that when the system restarts, you will need to telnet to the system again and re-run the script.

The second installation script, ipkg_nand_install.sh, is designed to do a persistent installation. This script will copy all the required files to the /usr/local/etc directory and modify the /usr/local/etc/rcS script. Since the /usr/local/etc/rcS script is executed every time the system starts, Samba, BitTorrent and the Web Interface will be available automatically. This installation method also modifies the USB Hotplug methods so that when you remove/attach a USB device, the Samba shares will be modified appropriately.

All the mounted USB devices will be available as a Samba share with the Machine Name "Venus" in the workgroup "workgroup".

You need to use your web browser to add/delete torrents, so put the address http://venus into your browser and you should connect automatically. All BitTorrent downloads are stored in /tmp/usbmounts/sda1.

Notes: I renamed the package and scripts and added a more permanent installation method. Hotplug devices are better supported with Samba shares modified as required. Any firmware update will remove these installed files, so you will need to reinstall after the update.

Also, for the NAND installation, the BitTorrents are directed to /tmp/usbmounts/sda1. This might not be the device you want, so you can change it to your desired device/partition by using "ln -s /tmp/usbmounts/[device] /tmp/btdownload". I am looking at changing the BT configuration web page so that it can be changed that way.