Twitter
Facebook
NMT Wiki
Search
Member List
HelpFirmware: 
A-400 [13 May 2013] | C-300 [30 Nov. 2012] | A-300 [30 Nov. 2012] | C-200 [21 Jan. 2013] | A-200/A-210 [10 Aug. 2012]
Networked Media Tank
/
Community Jukebox, Themes, & UserApps Section
/
200/300/400 Series - Development and User Apps
/
100 Series - Development and User Apps 
/
llink-1.5
/
llink-1.5
User(s) browsing this thread: 1 Guest(s)
|
llink-1.5
|
|
12-17-2007, 04:58 PM
 Post: #106 |
|||
|
|||
|
Nice... The trailers directory appears empty though, anything else I have to do? The PH has direct internet access on my LAN.
This may be a silly question, but is there currently a way to get to the next page using the Aquarius skin? I can't enter '11' like you can when using myiHome, the PageDown button causes an infinite loop, and I can't figure out a way to access the up/down controls at the top right... |
|||
|
![[+]](images/collapse_collapsed.gif)
|
12-18-2007, 01:27 AM
Post: #107 |
|||
|
|||
|
Ok, I broke ROOT code in 1.9, maybe don't go upgrade just yet. It seems to include root in subdirs, although hilarious, rather useless.
Hubert: for trailers, llink needs to be able to access the internet, as well as NMT. Run it with -v 32 for "root" debug output. Can "11" really also change to next dir? I should look at that, for now I think we have to add a "Next" link you push on, unless Syabas comes up with an idea as to why one button push sticks on forever. |
|||
|
|
12-18-2007, 01:47 AM
Post: #108 |
|||
|
|||
|
Ok, new 1.9 is up. Make sure you refresh your cache if needed.
Fixed the ROOT problem, added new NextPage to aquarius, try both "Page Down" and "Blue" buttons, as they are defined differently. |
|||
|
|
|
12-18-2007, 03:15 AM
Post: #109 |
|||
|
|||
|
On myiHome, if you enter a number for a directory that's not currently shown on screen, it will jump to the screen showing that directory. I just meant pressing 11 as in getting to the screen after the one showing items 1-10.
|
|||
|
|
|
12-18-2007, 03:24 AM
Post: #110 |
|||
|
|||
|
Interesting... I wonder how they managed to do that.
This would be a lot easier with the documentation for the protocol 
|
|||
|
|
|
12-18-2007, 12:27 PM
Post: #111 |
|||
|
|||
|
ok, 1.9 was riddled with bugs, but after spending the whole afternoon in Devstudios debugger, I believe I have nailed the big ones.
http://lundman.net/wiki/index.php/Llink Both 1.9 sources and Windows binary is out. |
|||
|
|
|
12-19-2007, 06:34 PM
Post: #112 |
|||
|
|||
|
please help compile llink 1.9 for asus wl500gp with oleg
please help compile llink 1.9 for asus wl500gp with oleg
|
|||
|
|
|
12-19-2007, 11:50 PM
Post: #113 |
|||
|
|||
|
Sure, what goes wrong?
it "should" be ./configure make cd src ./llink -d |
|||
|
|
|
12-20-2007, 08:09 AM
Post: #114 |
|||
|
|||
please help compile llink 1.9 for asus wl500gp with oleg
lundman Wrote:Sure, what goes wrong? Hi Lundman I mean, help doing the *.ipkg packet. I dont have any compiler, and dont understand linux. Please |
|||
|
|
|
12-20-2007, 08:30 AM
Post: #115 |
|||
|
|||
|
I do not know what an ipkg is, but it should be easy to cross compile if one knew the right things to compile for. But it would be a hell of a lot easier to do with hardware access.
What is it anyway, PowerPC? People already done toolchain? |
|||
|
|
|
12-20-2007, 09:46 AM
Post: #116 |
|||
|
|||
lundman Wrote:I do not know what an ipkg is, but it should be easy to cross compile if one knew the right things to compile for. But it would be a hell of a lot easier to do with hardware access. I dont know, Get all my packet's here http://www.nslu2-linux.org/wiki/Optware/...g.Packages |
|||
|
|
|
12-20-2007, 12:05 PM
Post: #117 |
|||
|
|||
|
ah the unslung stuff...
http://members.home.nl/lhspiljard/guide/...chain.html looks straight forwards, I dont have windows but it might just work under unix. |
|||
|
|
|
12-20-2007, 12:22 PM
Post: #118 |
|||
|
|||
|
Oh anyone remember where the moon/sky picture I am using came from? I would like to credit them for it.
|
|||
|
|
|
« Next Oldest | Next Newest »
|
