SA Firefighter

General Discussion => SA Firefighter General => Topic started by: rescue5271 on February 29, 2008, 05:20:05 AM

Title: GRN time is wrong!
Post by: rescue5271 on February 29, 2008, 05:20:05 AM
I am sure today is the 29th/02/08 but the two pagers in this house say the 1st March 2008 bugger GRN does not know its a leap year.......
Title: GRN time is wrong!
Post by: Zippy on February 29, 2008, 05:50:57 AM
Rescue5271, yep...we've officially experienced time travel.  :mrgreen:
Title: GRN time is wrong!
Post by: Footy on February 29, 2008, 06:41:57 AM
Yep this pager i'm lookin at says march

hooray
i wonder when/if that issue will get fixed?

Its like when crews get responded daylight savings changeover days and arrive back at the station earlier than what they left...
Title: GRN time is wrong!
Post by: Zippy on February 29, 2008, 07:43:52 AM
hehehe

Paged:    0152
Mobile:   0156
OnScene:  0201
Complete: 0241
BackinStn:0150

:P

Those are the good early morning jobs...no loss of sleep ;)
Title: GRN time is wrong!
Post by: Darius on February 29, 2008, 08:02:41 AM
that's an interesting one.  The GRN people say the network date/time is 29 Feb and a response page I received this morning says 29 Feb (from BOMS).  However if you manually change the date on your pager it will revert to 1 Mar so some part of the network definitely thinks it's 1st of March.  The GRN/Link people are looking into it anyway.

Title: GRN time is wrong!
Post by: Footy on February 29, 2008, 02:08:44 PM
half way through the day my pager reverted automatically
in the morning it was march and by midday it was back to february

lol

just one of those things i think, not like any harm could have been done,
Title: Re: GRN time is wrong!
Post by: bajdas on February 29, 2008, 05:03:01 PM
Quote from: Footy on February 29, 2008, 02:08:44 PM
....just one of those things i think, not like any harm could have been done,

Unfortunately, from a computer database & logging prespective they would have had to fix the date problem quickly. Otherwise the database is incorrect into the future.