Linn Forums

Current time: 2017-12-14, 21:59 Hello There, Guest! (LoginRegister)

Linn Forums / Linn Music Systems & Hi-fi Separates / Network Music Players & Music Streamers v / [How to] Easily install Twonky 6.0.xx on a D-Link DNS 323 - a £55 NAS

Post Reply 
[How to] Easily install Twonky 6.0.xx on a D-Link DNS 323 - a £55 NAS
2011-02-16, 18:10 (This post was last modified: 2011-11-10 15:51 by Briain.)
Post: #1
[How to] Easily install Twonky 6.0.xx on a D-Link DNS 323 - a £55 NAS
Scope

D-Links are now available for about £55 and 1000 GB disks for about £40, so you can now build a single disk 1TB NAS for under £100 (inc delivery charges)!

Important Caveat

Please note that although I've successfully installed this on a friends D-Link and shared my installation scripts and processes here, I do not personally own a D-Link NAS and thus cannot offer any technical support service should you have a problem. I will try my very best to help folks who do have problems, but I am not able to offer anything like a support desk functionality as I have nothing to test any complex problems on (and since I neither work for Twonky nor D-Link, I have absolutely no financing and no thus no technical backup team; my resources are thus very limited, so should there be a barrage of questions, I'd likely have major problems answering them all).

Summary

I've spent a while experimenting with a friend's D-Link DNS 323 and trying to make it easy for anyone interested to install Twonky 5.1.x or 6.0.x on it. I've now got it running pretty sweet with the 6.0.34 version and I think I've now got it to successfully hibernate the disks (it's hard to be sure - it did once spun up - as there are a lot of things on my network and I've now had to hand the D-Link back to its owner; please let me know your own findings).

I've waited until now as the previous versions (including 6.0.30) had some issues with embedded art in some folks collections (on average, about 5% or more covers were missing compared to Twonky 5.1); this has now been fixed (in 6.0.31 and above) by the Twonky folks. Twonky 6 is faster at rebuilding the database and the rescan contents is now very quick; this makes it more suitable on slower NAS's than Twonky 5.1 was.

This D-Link is a very cheap NAS and I'd strongly recommend something like the Qnap TS-219P+ as being a far more appropriate solution for the vast majority of Linn DS users. That said, it is so remarkably cheap, that it could be a good place for folks to start out with their first ever Sneaky DS system (and on a tight budget). Things like the Qnap give far better speed, far better features and have more reliable 'hibernation' capabilities than the D-Link/Twonky combination; a lot more time (and money) has been spent in refining them into extremely advanced devices and in my opinion, they more than justify the additional price (the very fast TS-219P+ is about £310 and the slower TS-210 is about £160). In addition, many folks already have a D-Link DNS-323 and thus it also makes sense to provide instructions on how to install a more recent version of Twonky on their existing D-Link's

Relative Performance of DNS-323

I've just had a search and found that can get a D-Link for about £60 (delivered) these days and whilst it's not the fastest NAS on the go, the price is astoundingly low (but please read the paragraph above this one; it's only £100 more for the basic Qnap). The D-Link 323 has a 500 MC/s ARM CPU so it is a bit slow, but once it's up and running, it's fast enough to deal with Twonky, custom trees and my 32,000 FLAC file collection. To give you an idea of the speed, below are some comparisons. The Duo ones are approximate guesses as I don't have a Duo to test them on; they're extrapolated from my experiments with Twonky 5.1 (a while back and with less tracks).

Full database rebuild (32,000 FLAC files)
ReadyNAS Duo : 80 minutes (est)
D-Link DNS323 : 60 minutes
Qnap TS-219P+ : 18 minutes

Restart and reboot refresh (32,000 FLAC files)

ReadyNAS Duo : 70 minutes (est)
D-Link DNS323 : 47 minutes
Qnap TS-219P+ : 6 minutes

These times are about 60% of the times Twonky 5.1.6 would take to do the same scans, so it's significantly faster at db build and NAS re-boots. The other advantage is that the rescan for new media only takes a few tens of seconds, so that's a great leap forwards.

In operation, the DNS takes about 8 seconds to load a new screen of 126 album covers into Kinsky Desktop (slightly slower than Twonky 5.1) whereas the Qnap's about 2 seconds. With the D-Link, certain bits of the inter-menu navigation are slow (using my custom menu trees) when using Kinsky Desktop, but it's not noticeable when using Chorus or Songbook on an iPad etc. Personally, I'd vastly prefer a faster, more fully featured and more fully 'developed' NAS, but this is an astoundingly cheap device and thus could be of interest to many folks.

Ease of Deployment

It's actually very easy to install Twonky 6 on the D-Link, but I'll write everything out 'in full' in case anyone is unsure of any of the steps. If you don't like it, Twonky 4 can be put back on the D-Link in the same way you installed it the first time (this will remove Twonky 6). Essentially, you only need change one file before first running Twonky, so below is the summarized version, and below that is the fuller description (for folks less familiar with the art of NAS tinkering).




Installation instructions (Brief)

For the experts, this small section will be enough

Basically, all you need do is note your old Twonky key, access the NAS, create a 'temp' directory on the NAS, drop 2 files into it, install the Twonky package (set it not to start the server immediately after installation), then using telnet, navigate to the temp directory, chmod a+x the 'go' file then run it (./go); that's it done.

The replacement starttwonky.sh file sets up the symbolic links to enable the NAS to reboot and start Twonky (without doing that, the NAS will not be accessible; you'd need to telnet in, delete the existing starttwonky.sh file and reboot it to fix things). The replacement starttwonky.sh can be downloaded from from here.

The replacement starttwonky.sh also sets permissions on the /twonky/resources/views XML files such that the trees can be changed by dropping replacements in using Windows (no need to telnet back in again).

Optionally, you can change the clients.db and default.ini (and even add new trees) to the unzipped installation files before running the installation; the only important bit is to replace the starttwonky.sh (using telnet) before Twonky is first run.

Once done, check to see what's running (ps aux) and if you see inotify_itunes it's worth disabling it via the D-Link web interface (it's the built in iTunes server)




Installation instructions (Detailed)

Instructions in a lot more detail:

Prerequisite requirements:

Assuming you already have a D-Link with Twonky 4.x.x on it, you will have had to install the fun_plug utilities in order to have installed Twonky 4 in the first place. This means you are ready to install the updated versions of Twonky. If not (if it doesn't already have a version of Twonky on it, or if it is a new D-Link, or you have just fitted new disk(s) into an old D-Link and set it up) then you'll have to first install the Fonz ffp_plug tools before you can proceed any further. There are instructions on installing below. If you are unsure whether it has been previously installed or not, see the third picture below (you can see the 'ffp' folder, which shows it has already been installed).

Preparation:

Access the D-Link configuration page and disable both the built in UPnP server and also the iTunes server. There's not enough room here, but I've shown a picture of the D-Link interface in the post below this one. Disable both iTunes and UPnP server in the same way.

Before doing anything else note your existing Twonky 4 license key. This can be found either by opening the Twonky ini file (in a text editor like Notepad) or by typing http://your.nas.ip.address:9000/rpc/get_all into your web browser. If you decide to stick with Twonky 6 (you get a 30 day free trial) the old key gets you discount on a new one. If you do loose the old one, it can be retrieved by contacting Twonky.

Update NAS firmware:

First backup your D-Link and then update it to the current firmware. I've updated the below to version 1.08 and it all went smoothly (I see there's also a 1.09 but the only difference is the addition of CTERA on-line backup). You can access the firmware page here.

--------

Fonz's Fun Plug

Now install Fonz fun_plug (if it's not already installed). If you already have Twonky, you'll have already installed it. If it's a new NAS, I expect it'll not be there (if you have a ffp directory visible, then it's installed). If not, it's simply a matter of downloading two files and rebooting the D-Link; see below.

Download the two latest files from fonz’ fun_plug repository. To save time, I've put links to the two files you need:

fun_plug (this is a text file, you will have to right-click the above link and save it to disk)

fun_plug.tgz (this is a 10 MByte “tarball” file, roughly the Linux counterpart of a Zip file) again, right click and save it to your computer's desktop)

Place a copy of both files in the topmost directory of Volume_1 of your NAS using Windows Explorer.

Reboot the D-Link (press and hold the power button for 5 seconds, then once it's fully off, press the button to start it again).

If you wish any more info about fun_plug, there is a tutorial here (navigate to the section about installing it), but to be honest, the bits above are all you need to know.

--------

Back to installing Twonky

Download and unpack the rest of the new files you will need. Again, right click on the links then save the files to your desktop.

First download the DNS-323 Twonky 6.0.34 package from here
(full page of other NAS versions here)

Next download PuTTY from here (full page of PuTTY versions here)
(The Mac has its own built-in Telnet client).

Now download the custom D-Link files pack from here (quite literally from 'here'; 'Oliverh' has very kindly stuck it on the Linn server for us)

Now unzip the Twonky 6.0.34 installation package onto your desktop. To save space, I've shown the options for using either Winzip or 7-Zip - a better and also free zip tool - on the one picture (you'll only need one of them).

[Image: attachment.php?aid=2357]


Now unzip the custom D-Link file pack and extract the four files (onto your desktop). Two of the files are optional extras (though recommended) and the other two ('go' and 'starttwonky.sh') are essential to the installation (they are both used in the 'Back to the necessary stuff' section, a little further down).

--------

Three Optional Changes (recommended)

Now open the unpacked Twonky 6.0.34 installation folder and you'll see the below set of files and folders

[Image: attachment.php?aid=2358]


You can now use the 2 of the 4 files from the custom D-Link pack to update the Twonky installation package before installing Twonky onto the D-Link (both optional, but both recommended):

File 1 (twonkymedia-server-default.ini)

From my custom D-Link files pack, drop the 'twonkymedia-server-default.ini' into the above folder (thus overwriting the original Twonky one).

File 2 (replacement clients.db,):

From my custom D-Link pack, drop the replacement 'clients.db' file into the 'Resources' folder (overwriting the original Twonky one). This is similar to the original Twonky one, but it now defaults to a new entry called 'Full Resolution Art to CP' and thus saves Kinsky Desktop users having to manually re-select the 'Linn DS CP' entry after performing a Twonky rebuild (it still sets itself automatically for all other things including Chorus and Songbook). Don't do this if installing Twonky 5.1 (it's a different file); for 5.1 you will need to instead have to overwrite the transcoding.db file with my 5.1 custom one (it's on the Qnap forum with my trees).

Trees (can be done now or later; I'd just go for it now):

Optional (but recommended for folks with more than a couple of hundred albums): At this point, you can (if desired) download one of my replacement menu (tree packs) from here (or use the following link to directly download the recommended albumartist pack here). They can be placed in the views folder (which is in the resources folder) for automated installation You don't have to change the trees now as I have included a line in the starttwonky.sh file which enables 'Windows Explorer' level of access, so you can easily change the trees at a future date.

--------

Back to the necessary stuff

Now access the NAS 'Volume_1' share (using Windows Explorer) either by typing your NAS hostname (\\hostname) or by opening your normal drive mapping (the usual way you deposit your albums on the D-Link) such that you can see the NAS's folders in Windows explorer. Right click on the white space and select to create a new folder (see picture below) and call the new folder 'temp'

[Image: attachment.php?aid=2369]



Open this new 'temp' folder and drop the remaining 2 files from my pack of 4 custom files; the ones called 'starttwonky.sh' and 'go' (as I have shown in the below picture):

[Image: attachment.php?aid=2371]


Now the package is ready to install automatically, but first open PuTTY to check that you can access the D-Link (we'll need to use this in a moment). Below shows the PuTTY opening screen you will get and the correct things to type in (ignore the bottom entries, simply enter your own NAS IP adddress and ensure the telnet connection type has been chosen); just populate the bits at the end of the red arrows.

[Image: attachment.php?aid=2366]


Now click open and log into your D-Link. On the D-Link I have, I've set a password and enabled a different form of access (as root user) so you will likely not have any user ID or password to enter (unless you specifically set that up after you first installed fun_plug). Where this NAS shows as root@WaveServ:~# your one will likely just have a symbol like ~#

Now type the below commands

cd /mnt/HD_a2/temp (then enter)
ls (then enter)

This will list the two new files you added to the new 'temp' folder a few moments ago. Please check that you see these two files (as below) as that will prove you are in the correct place and ready for the next stage.

[Image: attachment.php?aid=2370]


If you don't see these two files as shown above, do not proceed any further; re-read the above steps and correct the issue, then proceed as follows:

With everything left like that and the telnet session left running (the PuTTY Window left open), now go back into the unzipped Twonky 6.0.34 installation folder sitting on your desktop, and double click on the one called 'nassetup.exe' (see below red arrow); you will now get the below Window popping up:

[Image: attachment.php?aid=2372]


Click on 'Accept' then enter your NAS IP address (and user / password if required). Now untick the start server box as shown by the other big red arrorw and then you can click on the continue button.

I'm told Windows 7 pops up a warning to say Twonky did not install correctly; just ignore/cancel it (Windows XP doesn't do that).

Once it has finished, close the installation window (the one shown above) and return to your PuTTY screen; now type the below commands

chmod a+x go (then enter)
./go (then enter)

[Image: attachment.php?aid=2373]


After hitting the enter button (after ./go) in the above screen, the installation of my custom files will commence, the screen will update as shown below and the NAS will automatically reboot itself:

[Image: attachment.php?aid=2374]


Once the NAS has re-started, Twonky will start safely and you can set the media paths etc. It's defaulted to point nowhere, so go into Twonky config (http://your.nas.ip.address:9000) then click on the spanner icon, then from the left menu, select shares, then use the browse button to set the 'content locations' to point to your music; once selected, click on the 'save changes' button.

You can also set paths to videos and pictures folders if you wish (remember to change the types to videos and pictures respectively) and then save the changes.

You can now also delete the starttwonky.sh and go files you placed in that new temp folder (or delete the entire temp folder) but I'd recommend leaving them there for any future updates.


Attached File(s) Thumbnail(s)
                   

KDS/1 (music) + ADSM (AV) -> KK/1 -> 350A + miniDSP time & phase aligned 345 rear sub
KDS Renew -> Homebrew fixed attenuator -> 2250/D -> 212 and Sizmik front sub (bedroom)
MDSI -> 104C (awaiting installation in my kitchen)
MDSI -> Shahinian Arc (installed at my mum's house)
Find all posts by this user
Quote this message in a reply
2011-02-16, 18:24 (This post was last modified: 2011-02-25 16:12 by Briain.)
Post: #2
RE: [How to] install Twonky 5.1 or 6.0 on a D-Link DNS 323
Disable the built in iTunes and UPnP servers as shown below (I can't add any more pictures to the above post:


[Image: attachment.php?aid=2376]



Technical info only - no need to read this!

Don't read this unless you really want to!

For those that are curious about the technical stuff, the custom files are the clients'db, default ini and starttwonky.sh files. The clients.db is identical to the stock Twonky one, but I have added a new entry as below

>>
NA:Full Resolution Art to CP
HH:DLNADOC/1.50
XM:AASCALE#JPEGORG
TR:JPEGORG
DB:AUTO


and removed the HH:DLNADOC/1.50 line from the 'Generic Media Receiver' entry. This instead defaults it to the new one above (for clients that don't identify themselves in the user agent field) and thus generically sends full resolution art to any 'unrecognised' control points (eg Kinsky and Konductor). This works for Twonky installed on anything (not just a D-Link) and I use it on my own Qnaps.

The default ini now contains the below entries

contentbase=/mnt/HD_a2/
contentdir=+M|temp
friendlyname=Twonky DNS323
httpport=9000
enableweb=2
scantime=0
maxmem=15000
startupmb=0
norescale=1
platform=DNS323
suppressmenu=divAutoShare
cachemaxsize=300000


and the starttwonky.sh has been expanded to include symlinks and enhance the hibernation capability; it's detailed below. I've #'d out the multicast entry; multicast is enabled in FW 1.08 by default.

starttwonky.sh

Code:
#!/bin/sh

# Twonky 6.0.30 replacement start-up script for D-Link DNS-323 NAS 11 February 2011
# Creates directories and symlinks to move db and cache from /var and log from /tmp
# This protects NAS OS, prevents db rebuild at boot and loss of cache, settings etc

# If not already set in D-Link, remove # from below to set multicast to 224.0.0.0/4
# /sbin/route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0

# First run checks for and creates new databese folder and enables user tree changes
    if [ ! -f /mnt/HD_a2/twonky/sym_var ]; then
       /bin/mkdir /mnt/HD_a2/twonky/sym_var
       /bin/chmod -R u+rwx,g+rwx,o+rwx /mnt/HD_a2/twonky/resources/views
    fi

# First run checks/creates relocated log file exists
    if [ ! -f /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt ]; then
     /bin/touch /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt
    fi
    
# Removes old links (if Twonky is killed and then restarted at command line)
    /bin/rm /var/twonkymedia
    /bin/rm /tmp/TwonkyMediaServer-log.txt
    /bin/sleep 1
    
# Creates symbolic links for the cache and db then the log file
    /bin/ln -sf /mnt/HD_a2/twonky/sym_var /var/twonkymedia
    /bin/ln -sf /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt /tmp
    /bin/sleep 1

# Starts Twonky in mode that enables better hibernation characteristics
PIDFILE=/var/run/mediaserver.pid
TWONKYSRV="/mnt/HD_a2/twonky/twonkymedia"
$TWONKYSRV -powersavemode 1 &
/bin/sleep 2

    if [ -e $PIDFILE ]; then
        PID=`cat $PIDFILE`
        echo "TwonkyMedia server started"
    else
        echo "Looks like the daemon might have crashed, check ps aux"
    fi

The 'go' script removes the existing starttwonky.sh, then sets the new one as executable, then installs it above in /ffp/start/ and after checking that it's actually there, it finally reboots the NAS:

go

Code:
#!/bin/sh
#
# Installs Twonky start script into ffp/start then reboots NAS

if [ -f /mnt/HD_a2/starttwonky.sh ]; then
    /bin/rm /mnt/HD_a2/starttwonky.sh
fi
    /bin/cp starttwonky.sh /mnt/HD_a2/ffp/start/
    /bin/chmod u+rwx,g+rx,o+rx /mnt/HD_a2/ffp/start/starttwonky.sh
    /bin/sleep 1
    
if [ -f /mnt/HD_a2/ffp/start/starttwonky.sh ]; then
    echo ""
    echo ""
    echo "Update sucessful; the NAS will now reboot itself"
    echo ""
    echo "Please set the Twonky paths to your music once the NAS"
    echo "has rebooted itself (http://your.nas.ip.add:9000/config)"
    echo ""
    echo ""
    echo ""
    /bin/sleep 4
    /sbin/reboot
else
    echo ""
    echo ""
    echo "The update didn't work; please check that you"
    echo "have correctly installed Fonz fun_plug (ffp)"
    echo "Please read http://wiki.dns323.info/howto:ffp"
    echo ""
    echo ""
fi

I am certainly not anything remotely near to being a Linux expert (very far from it; a total newcomer in fact) and thus there are likely more elegant ways to do the above, but the D-Link is pretty basic and the above works pretty well. Smile

NB The below attachments are nothing to do with this post; they are for the post above this one (you can only upload 5 per post).


Attached File(s) Thumbnail(s)
                   

KDS/1 (music) + ADSM (AV) -> KK/1 -> 350A + miniDSP time & phase aligned 345 rear sub
KDS Renew -> Homebrew fixed attenuator -> 2250/D -> 212 and Sizmik front sub (bedroom)
MDSI -> 104C (awaiting installation in my kitchen)
MDSI -> Shahinian Arc (installed at my mum's house)
Find all posts by this user
Quote this message in a reply
2011-02-16, 18:37
Post: #3
RE: [How to] install Twonky 5.1 or 6.0 on a D-Link DNS 323
Hi Brian
Is there a link for Twonky 6.0.31 for a Netgear Duo?

regards
John
Find all posts by this user
Quote this message in a reply
2011-02-16, 18:40 (This post was last modified: 2011-02-17 10:48 by Briain.)
Post: #4
RE: [How to] install Twonky 5.1 or 6.0 on a D-Link DNS 323
Hi

The ReadyNAS Duo version is available on Super-poussin's Duo/NV add-ons page:

http://www.readynas.com/forum/viewtopic....47&t=41150

Bri

KDS/1 (music) + ADSM (AV) -> KK/1 -> 350A + miniDSP time & phase aligned 345 rear sub
KDS Renew -> Homebrew fixed attenuator -> 2250/D -> 212 and Sizmik front sub (bedroom)
MDSI -> 104C (awaiting installation in my kitchen)
MDSI -> Shahinian Arc (installed at my mum's house)
Find all posts by this user
Quote this message in a reply
2011-02-17, 22:57
Post: #5
RE: [How to] install Twonky 5.1 or 6.0 on a D-Link DNS 323
[quote='Briain' pid='110410' dateline='1297878042']
Hi

The ReadyNAS Duo version is available on Super-poussin's Duo/NV add-ons page:

http://www.readynas.com/forum/viewtopic....47&t=41150

Bri

Thanks Brian, for some reason 5.15 version just stopped working, causing nas to freeze. Installed version 6 and up and running OK

John
Find all posts by this user
Quote this message in a reply
2011-02-17, 23:50
Post: #6
RE: [How to] An easy way to install Twonky 6.0.xx on a D-Link DNS 323 NAS
Hi Bri,

Which version of Fonz fun_plug (ffp) are you using?

A week ago I decided to upgrade from 4.4.18 to 6.0.30 but I did upgrade ffp to version 0.5, which requires the '.sh' files to be in a different directory other than /mnt/HD_a2.

I'll be trying your .sh script as soon as possible to see how it works!

Vic
Ivor's "Tune-Dem Seminar" Alumni
Main: AK-0/ADS-0/2250/AV5125/AV5140s/Rythmik Audio F12SE Sub/Furman Elite 15i PF Linear Filter
Cave: LP12/Ittok LV-II/Arkiv/Lingo/Sonos ZP90/PS Audio DL III DAC/Wakonda/LK140/Katans
Spares: 2250/Cyrus One/Rega Kytes
Visit this user's website Find all posts by this user
Quote this message in a reply
2011-02-18, 00:23 (This post was last modified: 2011-02-18 01:45 by Briain.)
Post: #7
RE: [How to] An easy way to install Twonky 6.0.xx on a D-Link DNS 323 NAS
Hi Vic

Thanks for the heads up on that; I'll check it out tomorrow and amend the above. The FFP was the original the owner installed when the D-Link was purchased, so it's probably over a couple of years old (I hadn't considered they'd change something like that).

The Twonky installation script plonks the basic starttwonly.sh in HD_a2 by default, so that's the one I've suggested overwriting. If the new FFP looks for .sh files elsewhere, I'll need to add that info to the above post (it'll just mean copying my revised starttwonky.sh to the new location). The script will work no mater where it sits (it contains 'absolute' paths to everything within it) but if FFP doesn't look for it, the script won't run and Twonky simply won't start (it'll not be a problem for the D-Link; it just won't do anything).

Actually, if it has moved, it'll just make the installation process even more 'bomb-proof' for folks (even if folks copy the new one to the wrong place, it now means that there will be no risk of the existing default script still starting Twonky) so it's actually not such a bad change. I'll just amend the instructions to copy the starttwonky.sh to both locations and thus cover all eventualities; I'll only have to add one additional line to the telnet part of the instructions and that'll cover both versions. Smile

Did you happen to notice where the new FFP expects any 'start-up' scripts to be located? Knowing that would enable me to amend the above without dredging through the FFP site (I'm really very lazy). I wish they wouldn't change things that worked just fine as they were!

Bri

Maybe I need to add something like 'caveat emptor' as my default forum signature? Big Grin

KDS/1 (music) + ADSM (AV) -> KK/1 -> 350A + miniDSP time & phase aligned 345 rear sub
KDS Renew -> Homebrew fixed attenuator -> 2250/D -> 212 and Sizmik front sub (bedroom)
MDSI -> 104C (awaiting installation in my kitchen)
MDSI -> Shahinian Arc (installed at my mum's house)
Find all posts by this user
Quote this message in a reply
2011-02-18, 01:57 (This post was last modified: 2011-02-18 02:03 by Briain.)
Post: #8
RE: [How to] An easy way to install Twonky 6.0.xx on a D-Link DNS 323 NAS
I wonder if it now only looks for scripts in the FFP directory (where the ssh and telnet start-up scripts are located).

KDS/1 (music) + ADSM (AV) -> KK/1 -> 350A + miniDSP time & phase aligned 345 rear sub
KDS Renew -> Homebrew fixed attenuator -> 2250/D -> 212 and Sizmik front sub (bedroom)
MDSI -> 104C (awaiting installation in my kitchen)
MDSI -> Shahinian Arc (installed at my mum's house)
Find all posts by this user
Quote this message in a reply
2011-02-18, 02:02 (This post was last modified: 2011-02-18 02:04 by vicdiaz.)
Post: #9
RE: [How to] An easy way to install Twonky 6.0.xx on a D-Link DNS 323 NAS
(2011-02-18 00:23)Briain Wrote:  Did you happen to notice where the new FFP expects any 'start-up' scripts to be located?

Here:

[Image: attachment.php?aid=2367]


You must issue a 'chmod a+x starttwonky.sh' for the script to be executed at startup.


Attached File(s) Thumbnail(s)
   

Vic
Ivor's "Tune-Dem Seminar" Alumni
Main: AK-0/ADS-0/2250/AV5125/AV5140s/Rythmik Audio F12SE Sub/Furman Elite 15i PF Linear Filter
Cave: LP12/Ittok LV-II/Arkiv/Lingo/Sonos ZP90/PS Audio DL III DAC/Wakonda/LK140/Katans
Spares: 2250/Cyrus One/Rega Kytes
Visit this user's website Find all posts by this user
Quote this message in a reply
2011-02-18, 02:49 (This post was last modified: 2011-02-18 03:07 by Briain.)
Post: #10
RE: [How to] An easy way to install Twonky 6.0.xx on a D-Link DNS 323 NAS
Hi

Hmmmm; well I guess I'd better include the FFP update in my instructions and revise the location of the .sh (and add to make it exe); shame as it'll add more steps. Tempted to try now, but too many Laphroaig's would make that a bit unwise (mind you, it isn't my NAS). Smile

Does the Twonky installation (with the new FFP) now automatically put its default script into /ffp/start (or does it still stick it in HD_a2, meaning you physically had to move it yourself)? I'll test all this tomorrow anyway, but if you happen to read this first, it would be useful to know.

Bri

KDS/1 (music) + ADSM (AV) -> KK/1 -> 350A + miniDSP time & phase aligned 345 rear sub
KDS Renew -> Homebrew fixed attenuator -> 2250/D -> 212 and Sizmik front sub (bedroom)
MDSI -> 104C (awaiting installation in my kitchen)
MDSI -> Shahinian Arc (installed at my mum's house)
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)