Time zone/setting time

If RISC OS starts up with the RTC set to 01-Jan-2100 and DST automatic (note the RTC always stores date and time in GMT/UTC format) and OS_Word 15,5 is then used to set the GMT date to (say) 5th April 2017 at 10:00 [it does this correctly] and then OS_Word 14,3 followed by OS_ConvertStandardDateAndTime is used to read it back, it reads it as 10:00 rather than the correct local time of 11:00. On next CTRL-Break OS_Word 14,3 followed by OS_ConvertStandardDateAndTime reads it back correctly as 11:00 local time (proving that OS_Word 15,5 had worked correctly).

If RISC OS starts up with the RTC set to a Summer time date and you do the same date/time setting, again to a Summer time, then it all works correctly.

Can RISC OS handle a change of daylight time status whilst it is switched on?

Can RISC OS handle a change of daylight time status whilst it is switched on?

I baked support for CET and CHEST into my ROM, including altering the Messages so the rule should affect any timezones in UK… And it still didn’t change (machine always on). Go figure.

Using

SYS "Territory_SetTime",tmm%+1

SYS "OS_Word",15,tmm%

?tmm%=5
tmm%?1=0
tmm%!2=&553AD900+151*33750
REM Set UTC time to 31-May-2016 01:00 BST/00:00 UTC/GMT
SYS "OS_Word",15,tmm%

Presume OS_Word,15,5 should be deprecated (it is not in the PRMs so few will know about it).

What call does BASIC use when the TIME$=“<time/date>” statement is used?

Using SYS “Territory_SetTime”,tmm%+1 in place of SYS “OS_Word”,15,tmm% seems to overcome this

When Rick was doing his investigation a couple of years ago I found that the Territory SWIs were much more reliable. I would agree that they should be used when practical (although I’m still grateful to Rick for fixing CLib!)

I baked support for CET and CHEST into my ROM, including altering the Messages so the rule should affect any timezones in UK… And it still didn’t change (machine always on). Go figure.

I tried looking at adding New Zealand DST rules at one point, which ended up looking like more trouble than it was worth. Also, for some bizarre reason there’s a territory number for Maori-speaking NZ but nothing for English-speaking!

Don’t get me started on how utterly broken the Territory system is…

I tried looking at adding New Zealand DST rules at one point, which ended up looking like more trouble than it was worth. Also, for some bizarre reason there’s a territory number for Maori-speaking NZ but nothing for English-speaking!

Probably over a decade ago I realised I was wasting time with the apps, and now just use

*configure timezone +12/+13

Shouldn’t language be treated separately also? eg English person in a different timezone which might have an un-useable language?

Rick just said not to get him started! :P