New Build 1.0.614

  • Thread starter Thread starter Model-Behavior
  • Start date Start date
WOW, well that changed the settings alright! Change to
English (US) changed the schedule clock to 12 hour and it
accepted a time of 1 p.m. Also gave warning that last
scan was Jan 7 2005 when it actually was 08:30 GMT today.

Hope this helps.

R.
 
Bill, I should also have said that changing back (to
English, UK) bought back the last scan date/time correct
(July 1 08:30) and again the schedule won't accept beyond
12:00 midday.

R.
 
Strange indeed. I'll see if I can test this sometime later this evening.

Thanks, glad that worked--what I want to try to do is figure out what the
least disturbing change is that is effective.

There may be two parts to the prescription--you can change the locale
temporarily--as you did--or change to a 12 hour clock setting--another user
posted how to do this. Folks might prefer one or the other of these for
various reasons.

--
 
Because of a synch issue between HTML (where you post) and NNTP (where I
read)--I didn't see this until today.

As I understand this issue now, you must change to a 12 hour time setting,
make the schedule setting, and then change back to 24 hour.

You can make that change either directly, via the time format, or
indirectly, by choosing, say, US English. Either way has the same effect.

I don't have any other workaround for this one--it's a bug.

--
 
Back
Top