[!Organizer] No rule for given timezone (55207)

Hello

I am using !Organizer, but I get the following error message when trying to access the diary: “No rule for given timezone (55207)”.
I set the timezone Central Europe (01:00).
If I set it to UK GMT (00:00), the error does not occur.

Thanks for your help.

François

If you write to the Organizer Technical Support address with details of your version of RISC OS you will get some help.

Hello Martin

I sent an email to technical support.
In fact, I realized that the issue occurs also with timezone UK/GMT, when the “DST active” is not checked. If i check this flag, !Organizer works nice with timezone Uk GMT.

Unfortunatelly, this flag is “lost” at every boot, so currently I manually set it after every boot.

Until this bug is fixed, I am wondering how to write a script to set the “DST Active” flag during the boot process?

Thank you for your help.

Regards

Unfortunatelly, this flag is “lost” at every boot, so currently I manually set it after every boot.

What version of the time setup plugin do you have? If it’s less than 0.04 it’ll always get the DST flag wrong cos it didn’t work. Alternatively, what does

*STATUS DST

Hello

After a reboot, *STATUS DST returns NoDST.

I wrote a obey script with the single line:
Configure DST
and put it in the boot process.
Now, after every boot, the “DST Active” flag is set.

But weird enough, this actually does not solve the problem with !Organizer. I definitely have to manually set the flag if i want !Organizer to run smoothly…

There seems sth is definitly wrong with Time and Date management under RiscOS 5.19 :(

Cheers

François

No email has been received by Organizer Technical Support! Are you sure you used the correct address … it includes avisoft not blueyonder!

Hi Martin

I sent the email yesterday to the adress from which I received a copy of !Organizer after buying it (and it includes blueyonder, indeed)…

Email sent to the right recipient….

Thanks for pointing this.

Regards

The same problems I have if the timezone is not UTC+00:00.

Many thanks to Martin. The fix is working fine.