Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Titanite]

Hello,
I've gone through the Fun plug install and everything worked. I tried the 4.4.18 NAS setup.exe, and it gives me the "cant find network interface" error.

So I created a twonky folder in the /ffp folder, and followed these directions....(from the http://wiki.dns323.info/howto:twonkyupnpserver site).

"Other Operating Systems
If you need to install via some other operating system, you will need to FTP the files, and modify the autostart file, fun_plug to start twonkymedia.
Create the directory /mnt/HD_a2/twonky. Copy the following files and directories to /mnt/HD_a2/twonky: twonkymedia twonkymedia-default.ini cgi-bin plugins resources twonkymediaserver
Start server by running twonkymedia."

I started twonkymedia by typing ./twonkymedia

I now have Twonky showing up as a media server on PS3, however, how do I link it to the video and music files that were previously loaded on DNS-323, as there is nothing showing up with twonky.

Thank you in advance!!

[HSishi]

You have to call the Twonky setup UI from within your browser:

http://your-NAS-IP:9000

There you can setup the folders with your music etc.

//HSishi

[47th_ronin]

installing twonky manually is not quite that simple thing to do. i followed the described process and these things then happened:

1. twonky trial period did not expire
2. twonky reverted to default settings after each restart
3. after a while of playing music i got purple drive lights and 323 reported both drives failure by email (fixed by restart)
4. rootfs got filled up to 100% (fixed by restart)

i believe the problem was twonky writing temporary files to incorrect location, thus messing up the system. during twonky shutdown (either manually or with 323-s restart/shutdown) changes were not written anywhere. still, media database was always up to date.
i'm not skilled enough in linux to 'take apart' the twonky installation script to figure out how to modify twonky files and so fix the situation. well, getting 'free' twonky kind of added to my lazyness in that.

oh, and playing movies was faultless. no problems with rootfs and drive leds.

[007james]

well here is a fix for that:

Symlinks could be used to fix the problem instead, described here: http://forum.dsmg600.info/viewtopic.php?id=5288

## First create a directory for working files:
# mkdir /mnt/HD_a2/twonky/appdata
# or create it using Windows File explorer in \\yourNas\Volume_1\twonky
## And a file for log data like this
# touch /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt

Then add these lines near the beggining of starttwonky.sh:
ln -s /mnt/HD_a2/twonky/appdata /var/twonkymedia
ln -s /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt /tmp

installing twonky manually is not quite that simple thing to do. i followed the described process and these things then happened:

1. twonky trial period did not expire
2. twonky reverted to default settings after each restart
3. after a while of playing music i got purple drive lights and 323 reported both drives failure by email (fixed by restart)
4. rootfs got filled up to 100% (fixed by restart)

i believe the problem was twonky writing temporary files to incorrect location, thus messing up the system. during twonky shutdown (either manually or with 323-s restart/shutdown) changes were not written anywhere. still, media database was always up to date.
i'm not skilled enough in linux to 'take apart' the twonky installation script to figure out how to modify twonky files and so fix the situation. well, getting 'free' twonky kind of added to my lazyness in that.

oh, and playing movies was faultless. no problems with rootfs and drive leds.