Steps for use on d-link boxee box

23 views
Skip to first unread message

dmshimself

unread,
Mar 4, 2011, 6:22:29 PM3/4/11
to MythBoxee
Any chance of someone verifying the steps needed to install this app
on a dlink boxee? I'm not able to get past the autodiscovery and
enter the DB details.

I've added eriks repository, dialled it up and seen there are two
apps, selected the mythboxee app (it doesn't appear have a visible
version, but does comment that version 23.1 is needed) and install it
to the d-link. I get the invitation to to enter my setup pin as this
is the first time setup has been run.

No matter whether I enter the pin (which I do know!) or leave the
default, an attempting auto discovery message comes on and never comes
back. I've tried with the default protocol 23056 and 56 and I get the
same results.

If I do the same steps on my windows boxee, all is well.

Any suggestions?

dmshimself

unread,
Mar 5, 2011, 12:04:22 AM3/5/11
to MythBoxee
Sorry to comment on my own post, but I've found one other thing which
might give some clues. While the autodiscovery banner is up, the top
right part of the screen with mythtv DB settings is there but dimmed
out. I have found I can select and fill in the database area, but
pressing test and save doesn't appear to do anything. If I go out and
back in, the settings haven't been saved, but I'm guess that is
because the test and save hasn't completed.


Ryan Snyder

unread,
Mar 5, 2011, 8:11:08 AM3/5/11
to MythBoxee
I can help you get further but i haven't been able to get it work
myself.

You need to change the protocol version from 23056 to just 56. My
suggestion is to locate the MythStatic.py change it and restart your
computer to make sure that it is using it. Then you can go into the
mythboxee app and at least get it to connect.But you might end up like
where it just sits at the loading screen.

On Mar 4, 11:04 pm, dmshimself <david.medland-sla...@touchpaper.co.nz>
wrote:

dmshimself

unread,
Mar 5, 2011, 11:40:32 PM3/5/11
to MythBoxee
Thanks Ryan - I currently have the protocol set to 56 and I've tried
putting it back to 23056 just in case, reboots in between. It's
currently set to 56 but I get the same result

Cheers

Dave

Erik Kristensen

unread,
Mar 6, 2011, 10:34:59 AM3/6/11
to myth...@googlegroups.com
Hi Guys! Sorry I've been non-responsive, life has been extremely busy.

dms, are you trying to get this to work on the Boxee Box or on another
platform (windows, linux, etc)

Also no updated on 0.24 support, I've been working on converting the
necessary libraries but have't had much luck as of yet :(

-Erik

> --
> You received this message because you are subscribed to the Google
> Groups "MythBoxee" group.
> To post to this group, send email to myth...@googlegroups.com
> To unsubscribe from this group, send email to
> mythboxee+...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/mythboxee?hl=en
>

dmshimself

unread,
Mar 6, 2011, 1:18:39 PM3/6/11
to MythBoxee
Welcome back!

This in on a dlink boxee box. Latest firmware.

If I try the same sequence on a boxee windows platform I get much
further and in many cases can play files fine.

Ryan Snyder

unread,
Mar 7, 2011, 11:33:44 AM3/7/11
to MythBoxee
Erik,

Im running a Dlink Boxee Box and it just sits at the loading screen.
Running .23.1 Myth and Protocol Version 56. It sames that it connects
but it then just loads and loads.

Ryan

On Mar 6, 12:18 pm, dmshimself <david.medland-sla...@touchpaper.co.nz>
wrote:

Ryan Snyder

unread,
Mar 7, 2011, 11:33:22 AM3/7/11
to MythBoxee
Erik,

Im running a Dlink Boxee Box and it just sits at the loading screen.
Running .23.1 Myth and Protocol Version 56. It sames that it connects
but it then just loads and loads.

Ryan

On Mar 6, 12:18 pm, dmshimself <david.medland-sla...@touchpaper.co.nz>
wrote:

Erik Kristensen

unread,
Mar 7, 2011, 12:34:43 PM3/7/11
to myth...@googlegroups.com
Hi.

Well .23.1 uses 23056 as the protocol not 56. 0.23 was 56.

The version that is available for the box uses 23056 and supports only 0.23.1.

If you can grab the logs off the device that would help troubleshoot.
http://IP_OF_BB:8080 should allow you to download the logs. I normally
syslog my logs so I am not 100% positive that the logs I'll need are
located in that package but you can send it to me directly if you'd
like.

-Erik

Reply all
Reply to author
Forward
0 new messages