I am having a problem with the second Openbox S9 I installed for a client on Thursday (luckily, a very nearby).

Basically, everything works ok, but once in a while, the box will not boot from standby after powering off via the remote control. When it gets to this status, the rear power switch must be flicked off then on for it to work again (even unplugging the power cable does not work - must using the hardware power switch).

The annoying thing is that his does not happen all the time - but at least once a day.

I will be exchanging the box for them of course, but as I actually purchased the units direct from overseas, I am in a hard position (shipping it back to China >$30).

Meanwhile, I have not had any such issue on my first one (test box at home).

The thing is, I am pretty sure it is not a physical disconnection of electricity, and this is why I think this:

The Openbox S9 power indicator light has 3 states: red (standby), off (booting) and green (on). When the above problem occurs, it is always stuck in the off (booting) state, though the the display never gets to the "boot" stage - it never displays anything.

The box is connected to a Moteck VBox II and using DiSEqC control with a C-band 2.3m dish and OCS LNB through a 2 way splitter tracking 5 sats.

Any opinions whether this is a firmware or hardware (i.e. RMA worthy) problem?

This 2nd one, and my other test box, both run the 10-11-08 firmware. This faulty one is not running any clines (LAN not connected at all) while the test box (working fine) has two active clines but is not controlling a DiSEqC postioner/motor (only using a 0/22Khz + voltage multiswitch to choose between two sats).

Oh dear! That is terrible!

When you say it "goes away for awhile" after reflashing an old (how old?) then new image - how long does it actually remain stable for?

Do you think it might be due to a bad image or usb drive?

Anyone else has this problem?

I updated two STBs in two consecutive days. The first box does not experience this problem - it has been rock solid and has been manually turned on/standby at least 20 times since update to 101108.
Second one (unfortunately at a customer's premises - guess how happy that makes them!) malfunctions each day.

If it is due to a bad flash - it should be fixed just by updating firmware using a different usb stick and image? Trouble is I am not sure if it is safe to restore the TP_PROG.abs afterwards - really do not want to have to set up the positioner and channel lists again. Does the TP_PROG.abs dump include the satellite settings (switch/lnb LO freq/DiSEqC positions)?

You would think they have a checksum in the image that gets checked before the image gets burned into flash - would you know if this is the case?

I really like this box - its cheap, runs really cool, supports NTFS, simple cline config, acceptable picture, and fairly simple to use. Hopefully we can solve this problem, because it is a showstopper