stuart wrote:
> Hi...
>
> I haven't figured this one out yet. And maybe it's just the new MClient
> code I am working with. But, have any of you with more then 1
> slimserver client, MClient or otherwise, had problems with the list of
> tracks being played? I thought this problem was restr
Hi...
I haven't figured this one out yet. And maybe it's just the new MClient
code I am working with. But, have any of you with more then 1
slimserver client, MClient or otherwise, had problems with the list of
tracks being played? I thought this problem was restricted to the album
cover (w
Hans Halvorson wrote:
> Here is my /etc/default/atftp:
> USE_INETD=true
> OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5
> --mcast-port 1758 --mcast-addr 192.168.1.0-255 --mcast-ttl 1 --maxthread 100
> --verbose=5 /tftpboot"
The only thing relevant in this file is "USE_IN
Eric,
Thanks for your quick reply. Here is my /etc/default/atftp:
USE_INETD=true
OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5
--mcast-port 1758 --mcast-addr 192.168.1.0-255 --mcast-ttl 1 --maxthread 100
--verbose=5 /tftpboot"
I also tried it with port 16869.
-Hans
> Jul 28 07:30:08 dell dhcpd: DHCPDISCOVER from YYY via eth0
> Jul 28 07:30:08 dell dhcpd: DHCPOFFER on 192.168.1.4 to YYY via eth0
> Jul 28 07:30:08 dell dhcpd: DHCPREQUEST for 192.168.1.4 from YYY via eth0
> Jul 28 07:30:08 dell dhcpd: DHCPACK on YYY via eth0
It looks like you DHCP configuration
I am a new mvpmc user, and I have failed yet to boot, despite many tries.
My setup: a linux server at 192.168.1.3, a router at 192.168.1.1, and the
mediaMVP (non-flash version, Rev D3A) which will -- if everything goes well --
get address 192.168.1.4. (There is another computer at 192.168.1.2,