If you do loose the old one, it can be retrieved by contacting Twonky.įirst backup your D-Link and then update it to the current firmware. 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.
This can be found either by opening the Twonky ini file (in a text editor like Notepad) or by typing into your web browser. Disable both iTunes and UPnP server in the same way.īefore doing anything else note your existing Twonky 4 license key. There's not enough room here, but I've shown a picture of the D-Link interface in the post below this one. 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).Īccess the D-Link configuration page and disable both the built in UPnP server and also the iTunes server. There are instructions on installing below.
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. This means you are ready to install the updated versions of Twonky. 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)Īssuming 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. 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. 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). The replacement starttwonky.sh can be downloaded from from here.
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). For the experts, this small section will be enoughīasically, 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.