Search forums

Reply to thread

Message: [QUOTE="AcWxRadar, post: 2732269, member: 44249"] Ice, Since it obviously escapes from this "booting" sequence, either on its own with time or sometimes with a little nudging and coaxing, then it is not a total or hard failure as you also indicated. If I may assume that this problem has been in existence from the start (I remember the conversations regarding the ethernet port being bad right off when you got the unit), then I have a suspicion or a hunch that it may be due to the defective ethernet port. I am thinking that possibly during the reboot process, that the logic is scanning the ethernet port and since there is a problem there, it is getting hung up. That is just my first SWAG at this problem. I cannot explain why it would apparently make a difference when rebooting by the menus and that leaves me rather uncertain and confused. However, this is the first and most obvious system error or discrepancy that I could site as possibly being the cause. I don't know how you would prove it, other than having the ethernet port failure repaired. The problem with doing that is obvious to you already. It would likely be expensive and still may not resolve this specific problem. I have personally not read of anyone else having the identical symptoms as what you have here. All of what I have read have been AZBoxes stuck in the "booting" sequence permanently. I experienced a totally locked up AZBox and I actually went through the whole process of the recovery procedure for such failures at my own expense for time, labor and materials. At a certain point in that recovery process, the instructions stated that if I achieved a specific response at a certain point, that I was basically screwed and could not utilize the procedure to repair my unit. I was required to send it to Portugal for a factory warranty repair. It turned out for that one unit that it was actually a component failure that I could not have repaired myself. That whole story has so many twists and turns that no human could make a pretzel to compare with it! Unless your unit is new enough to still be under warranty, I would not bother. If out of warranty, the only way I would do it again is if someone I knew was traveling to Portugal and would take it with them and deliver it directly to the Opensat repair center and wait for it and bring it back with them. That whole affair for me drew out to nearly a whole year if not more. Your unit is obviously not under warranty any longer (it has been over two years I am sure). So, unless you can figure out how to repair the ethernet port yourself, I don't know if you will have much luck at fixing this "pain in the BOOT". The recovery process I mentioned earlier requires you to utilize the ethernet port and it addresses a totally blocked or locked up unit anyway, so that won't assist you. Wrong problem and the back door required (the ethernet port) is known to be toast already. The only suggestion beyond repairing the ethernet port is to try other firmware image files and se if they help. Unfortunately, you are already up to some of the highest revisions already. That doesn't offer much hope. I guess I could suggest trying image 5308 and 5309 and crossing your fingers, but I think you have a pretty good idea of the results to expect. The only other suggestion I have at this point is to go online to the AZBox BUG reporting forum and post the problem and see if anyone else responds with more positive information. [url=http://forum.azbox.com/?sid=f093a0b1164b72cf18dec6d25572f1c4]Login[/url] Good luck to you Ice! Gordy [/QUOTE]

Verification

Top