View source for TipsTricks

= WDLXTV Troubleshooting, Tips & Tricks =

This is a collection of useful tips and tricks regarding common problems with WDLXTV.<br>

== Reboot ==
When we say '''reboot''' we mean '''reboot''', that's either pulling the plug or typing '''reboot''' in telnet/ssh or klicking '''reboot''' in webend.<br>Powering the unit down with remote POWER button is only standby and it's not sufficent when you need to '''reboot'''.


== WDTV acting weired ==
If your WDLXTV starts acting weired and it seems only <u>YOU</u> are affected (others can't reproduce the problem),<br>here's what to do first (best in this order and check after each step with full '''reboot'''):
*Reset to factory settings in OSD (Settings->System Setting->Reset to factory defaults)
*Delete any '''.wd_tv''' folder you find on any drives (and shares if r/w) connected to WDTV
*Complete Config Reset (WEC->Config->Reset Everything)<br>To do this from shh/telnet use these commands:<br><code>rm -rf /conf/* && config_tool -s && config_tool -s && reboot</code>


== Change View (List/Thumb/Preview) ==
To switch between List and Thumb display when you browse your media files on WDTV, on remote press '''OPTION''', select new view mode with '''LEFT/RIGHT''' then press '''OK'''.


== SSH/FTP not working ==
You need to set a telnet password first! SSH and FTP will <u>NOT</u> work without a root password set.
[[Set_SSH_password]]


== Editing WDLXTV files on windows ==
Use Notepad++, PSPad, etc... any Editor that knows about *nix linebreaks and doesn't change file names (or extensions) on it's own ;)
So hardly any editor '''BUT NOT''' MS Notpad....


== Custom UMSP plugins ==
Besides putting '''umsp-plugins.tgz''' in '''/conf''' (which is a bad idea because it has very limited space!)<br>you can put a file called '''umsp-plugins.zip''' in the root of a usb drive (just like an '''app.bin'''). This way you can circumvent the space limitations of '''/conf'''.


== Boot WDLXTV from USB ==
You don't need to flash the firmware every time you want to try/test/use a different version, just boot it from USB.<br>
[[Difference_between_FW_formats#EXT3-Boot_.5Bnon-flash.5D]]<br>
[[USB_Boot]]


== EarlyMounts ==
Sometimes it's required to access a connected usb drive quite early during boot (eg. for use with rtorrent).<br>
In this case you can tell WDLXTV to mount this drive early under /tmp/mnt/<UUID-of-USB-drive> by simply creating an empty file named '''.mnt''' in the root of that drive.<br>This can also be done by simply ticking the drive under WEC->Main->EarlyMounts and save.<br />
A nice side effect of this is that the drive will '''ALWAYS''' be mounted on the same dir (because it includes the UUID of that drive), and it doesn't depend on which drive gets scanned and mounted first on boot.


== Scripts/Configs don't work ==
There are numerous reason why a script can fail to run, I'll try to list the most common ones here:
* Script has no executable flag<br>In order to be able to execute any script on linux you need to set the executable rights on the file.  Have a look here for more information: [http://www.tuxfiles.org/linuxhelp/filepermissions.html Linux file permissions]<br>eg. to allow everybody to execute the file you need to enter something like this:
 chmod a+x yourscript.ext


* Script has DOS/Windows or MAC linebreaks<br>This is a quite common problem and sometimes not obvious at first glance. To avoid this simly run your script through '''dos2unix''' to make sure it has propper linux linebreaks:
 dos2unix yourscript.ext


* Missing or wrong shebang<br>[http://en.wikipedia.org/wiki/Shebang_%28Unix%29 Shebang] is the very first line in a *nix script which tells the OS how to open/execute the script file. Beginners often remove that line because they think it's a comment, which also start with a #.<br>
Also there must be no whitespace (space, tab) before the shebang, the first two characters in the file should be '''#!'''.<br>
Example: This shebang will tell the system to use the perl interpreter to run the script:
 #!/usr/bin/perl


* Leading spaces in script
This seems to be mostly happening when you klick 'SELECT ALL' on a code box on the forum and copy/paste in an editor.
To avoid this simply manually select the code in the codebox with the mouse and copy it.<br>


* Read, read, read... ;)<br>Here are some random links, if you google for linux and scripting you will find so much more...<br>[http://www.freeos.com/guides/lsst/ch02sec01.html How to write shell script]<br>[http://www.tldp.org/LDP/abs/html/ Advanced Bash-Scripting Guide]<br>[http://linux.about.com/library/bl/open/newbie/blnewbie7.2perl.htm Simple Programming under Linux]<br>[http://www.tizag.com/perlT/ Perl Tutorial]


to be continued...
--[[User:Recliq|Recliq]] 11:37, 7 April 2012 (UTC)