mdian - 9 hours ago »
Any news from Humax Barry, assuming you are in regular contact with them? Must say I'm really disappointed in them, letting customers down simply by not even making mention of this on their news feeds so customers can be reassured.
Always In regular contact with Humax Towers, they are still trying to identify the cause.
Whilst not disputing some of you are having issues, again yesterday 3 units on all day and no 'lockouts'
Hi all, just to update, my box booted up ok again this morning.
So either switching off the options as previous post, or the possible data overload as others have posted about, or possibly the problem has been dealt with by others! time will tell.
Hi guys, just received this from Humax support team, haven't tried it yet.Thank you for contacting Humax Support.
I am sorry to hear you are having trouble. The issue was caused by a recent issue on the Freesat server and if you are still encountering issues you will need to follow the below steps:
Please find the instructions below to reset your box.
Following these instructions will reset some system settings including your Recording Schedule (Please replace when complete to ensure you still record favourite programmes)
Any previous recorded programmes will be saved.
1. Press Settings or Home on your remote.
2. Move to Settings > System Settings and press OK.
3. Move to Factory Default and press OK.
4. Reset System will be highlighted, press OK.
5. It will ask you if you are sure, highlight Yes and press OK.
6. It will then ask for your password, default is 0000
7. The box will then reset itself. You will then need to go through the initial setup again.
Once reset, you will need to leave the unit on BBC 1 HD for roughly 30 minutes.
Apologies for any inconvenience this may have caused you.
Will give it a go later.
The above is slightly misleading, as it doesn't work for all.
mdian - 2 minutes ago »
The above is slightly misleading, as it doesn't work for all.
Try it again. On Demand went AWOL for a while this morning, and has now returned. Possibly Freesat have been fixing the "issue".
Really wish they'd explain exactly what caused the problem, if it's now been diagnosed.
It always seemed likely the trigger was something on the Freesat server/EPG but that doesn't let Humax off the hook for this. A problem on the Freesat server should not cause a lock up in this fashion, hopefully Humax have identified the reason why the box locked up and this will be dealt with in a future firmware issue to ensure that a similar server fault will not cause this problem again.
My box has been fine today but the system reset did not fix it yesterday other than temporarily.
Do we know that the problem was something Humax should have anticipated and prepared for? I don't think we do, especially as it didn't affect most boxes. There must be another factor, to do with usage or set-up.
If Freesat would spill a few beans about what was happening at their end, it might help users avoid similar trouble in the future.
Humax seem to me to have responded quite promptly. (If indeed the problem's now been fixed)
JamesB - 6 hours ago »
Do we know that the problem was something Humax should have anticipated and prepared for? I don't think we do, especially as it didn't affect most boxes. There must be another factor, to do with usage or set-up.
They probably couldn't have anticipated it as such but their software is not very robust if it can get stuck in an infinite loop* (or whatever) because of an error in its input. Defensive programming should be very much at the front of anyone's mind who is writing software dealing with data from an external source.
Humax seem to me to have responded quite promptly. (If indeed the problem's now been fixed)
Yes it was a quick response if they did anything as it didn't have the look of something easy to find. Of course last time it disappeared and then reappeared again now, we won't know unless it happens again as the negative could just be Freesat fixing things in the server.
*The fault stinks of an infinite loop with some functionality still working (that with a higher thread priority and/or using interrupts) and some stopping completely - that will be the coding error, the trigger and original fault will be at the Freesat end. That is just my best guess of course.
We'll have to agree to disagree, I guess. Mind your options. 
You must log in to post.
