Strange one this, I have two HDs, both same configuration, on one the EPG works on the other EPG does not work! Both have all the same packages installed and latest webif 0.6.4-1. Tried reinstalling webif but gives same result, strangely however if I click on more options then a genre it displays the list of matching programmes with channel logos but won't display the regular EPG. I don't use this feature normally so am not that bothered, however if you have any bright ideas on how to fix I am happy to test.
Unfortunately mine fixed itself before I could investigate further. It could have been that the EPG database was being updated, or that something about the current programme on BBC1 was unparsable for some reason.. will have to keep an eye on it.
S.Lurker has installed 1.11 already! I don't think that will have changed the disc-based stuff though will it. For what it's worth, here's what happens when he tries an EPG search:
Runtime Error: /mod/var/mongoose/lib/epg.class:136: near "/": syntax error in procedure '.00000000000000000001>' called at file "epg_search.jim", line 97 in procedure 'epg get_channel_info' called at file "/mod/lib/jim/oo.tcl", line 46 at file "/mod/lib/jim/oo.tcl", line 62 at file "/mod/var/mongoose/lib/epg.class", line 136
I have been delivered a screen grab of the next runtime error (with 0.6.6-1):
Runtime Error: /mod/var/mongoose/lib/epg.class:80: expected number but got "" in procedure '.00000000000000000001>' called at file "epg_search.jim", line 99 in procedure 'epg ended' called at file "/mod/lib/jim/oo.tcl", line 46 at file "/mod/lib/jim/oo.tcl", line 62 at file "/mod/var/mongoose/lib/epg.class", line 80
Far be it for me to criticise, but one of the first lessons I got when "apprenticed" in hardware design (well, mentored really) was when my supervisor hit my circuit with unexpected input and broke it. But I know it's hard work trapping all error input.
Super Lurker is now reporting EPG success with WebIF 0.6.5. However, he says the pie chart keeps dropping back to the USB stick even though his hard drive is the top of the list.
New info: he seems to have different versions of WebIF installed on the HDD and the USB stick, and gets different results according to whether he's got one or both plugged in! More of a standardised test environment required...
Configuration: Buffalo Ministation HDD + USB pen drive (UPD) via Trust USB port multiplier. /mod folder exists on both HDD and UPD. Starting with only the HDD...
Super Lurker said:
The HDD by itself shows the correct Pie chart as you would expect, and is Drive 1.
Hot plug in UPD and it shows up as Drive 2. When highlighted the Pie chart still shows that of the HDD.
Everything is normal on the TV-Media view. Pie chart switches between the two.
However, rebooting with both drives plugged in crashes the WebIF interface. Rebooting with both drives plugged in (but having removed the /mod folder from the UPD)...
Super Lurker said:
Went through the same procedure as before, except when I rebooted I got the basic Webif screen with the invitation to- 'Download and Install the Full Web Interface' (I think they are the words - it's the screen you get after installing the modded firmware and restarting). Didn't do it.
I pulled out the UPD but when I re-accessed the Webif I still had the basic screen.
Required a reboot to get the full Webif back.
Obviously the UPD must not be left in. It is strange that the Humax detects the UPD first.
It seems that the Pie chart shows whichever drive is first in the lineup and stays stuck on that.
Commentary: I'm not sure about the "when highlighted" part - is the pie chart supposed to follow the highlighted drive?
Super Lurker said:
I have had a thought about why the UPD is detected first. Nothing to do with the position in the USB extender.
The UPD is alive, so to speak, as soon as it receives power but the HDD takes a little longer to spin up. Enough of a lag for the HDD to come second.
Does any of that make any sense?
Ok, that makes sense. On the HD model, the mod software has to be installed on an external disk and it is always going to boot from the first one that the Humax detects. It should be possible to change this behaviour in a future version however.