Transponder time lost and minor mishaps

[ginacman]

I've installed the 107.3_rd_v20040127.1153.img

Everything's fine, except a small detail:

When I disconnect the AC mains plug, the DB looses a set of information:

A) The correct transponder time
B) The correct emu association with services (although having issued REMEMBER on each of them the emu tab come back to show the CI setting)
C) the Unix date (minor mishap).

While the timer programming is somehow retained across power cycles, the most boring thing happens in a way that such time programming becomes completely useless after the DB looses the transponder time and the emu associations, namely while you are out.

Is any way to save this set of data somewhere else in memory, so that they can be remembered?

PS: I agree power cycles should be avoided on a DB, but indeed it can happen, and it always does!

[ginacman]

One possible reason the correct transponder time gets "lost" across power cycles is that, when the DB is powered back on, it gets tuned on an eastern eropean service that stays on a different time zone. In according to that, the DB adjusts internally the time but then screwing the previous right setting.

I formulate a new question then:
How the inital TV service can be tuned when the DB is first powered on?
Thanks for any hints.

[ginacman]

To whomever it may concern, I've resolved my own question.

In order to get the DB tuned in a given service, when freshly started up, just tune once in that service and then do a graceful shutdown via the main menu. That's the beauty of simplicity.

The above simple action ensures that same service will be tuned every time the power be restored after a a power failure.
Rgds
--