Bug in a version 1.0.614

[Maury]

Hello, I have as soon as unloaded version 1,0,614 and
must say of to have found a bug in the formulation of the
hour of beginning automatic scansion. I wanted setting
to the 17pm, but when I press key UPDATE SCHEDULE, the
hour is transformed in 5äm and not there e' towards
making to work it. Hello and thanks for the
attention... Maury

 

[JohnF.]

17PM is 5AM


Hello, I have as soon as unloaded version 1,0,614 and
must say of to have found a bug in the formulation of the
hour of beginning automatic scansion. I wanted setting
to the 17pm, but when I press key UPDATE SCHEDULE, the
hour is transformed in 5äm and not there e' towards
making to work it. Hello and thanks for the
attention... Maury

 

[Engel]

0500 = 5AM
1300 = 1PM
1700 = 5PM

 

[Bill Sanderson]

yes,. but 17 "PM"?

--


0500 = 5AM
1300 = 1PM
1700 = 5PM

 

[Niklas E]

17PM is 5AM, but there is no such thing as 17PM. Either
you use 24h 00-24 without AM or PM or you use 12h 0-12 and
include the AM or PM.

The latest release is so buggy. What have they been doing?

/Niklas

 

[Steve Dodson [MSFT]]

Fixing flying toast, scan schedules, LSP, and a lot more

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
17PM is 5AM, but there is no such thing as 17PM. Either
you use 24h 00-24 without AM or PM or you use 12h 0-12 and
include the AM or PM.

The latest release is so buggy. What have they been doing?

/Niklas

 

[Bill Sanderson]

Steve - Scan schedules are better for some, but in a new way worse for
others.

I don't have clear evidence of the parameters of the problem, but users in
European locales with 24 hour time zones apparently cannot set PM scan times
at all.

Not sure whether the issue is 12 vs 24, European locale vs US, or particular
time zone settings---but something is differently wrong with the new build.

--

Fixing flying toast, scan schedules, LSP, and a lot more

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
17PM is 5AM, but there is no such thing as 17PM. Either
you use 24h 00-24 without AM or PM or you use 12h 0-12 and
include the AM or PM.

The latest release is so buggy. What have they been doing?

/Niklas

-----Original Message-----
I want the schedule set to 20 o'clock (8 in the
evening!), but it keeps setting it to 05AM (5 in the
morning). When I set it to 10 AM after pressing update
schedule is says 112:00 AM (???????????) What time is
that?


.

 

[Bill Sanderson]

correction--this issue may be related to US English versus another
language--still haven't tested, though--but both Italian and Dutch users
report success by switching to US English, setting the scan times, and then
reverting to their usual language settings.

--

Steve - Scan schedules are better for some, but in a new way worse for
others.

I don't have clear evidence of the parameters of the problem, but users in
European locales with 24 hour time zones apparently cannot set PM scan
times at all.

Not sure whether the issue is 12 vs 24, European locale vs US, or
particular time zone settings---but something is differently wrong with
the new build.

--

Fixing flying toast, scan schedules, LSP, and a lot more

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
17PM is 5AM, but there is no such thing as 17PM. Either
you use 24h 00-24 without AM or PM or you use 12h 0-12 and
include the AM or PM.

The latest release is so buggy. What have they been doing?

/Niklas

-----Original Message-----
I want the schedule set to 20 o'clock (8 in the
evening!), but it keeps setting it to 05AM (5 in the
morning). When I set it to 10 AM after pressing update
schedule is says 112:00 AM (???????????) What time is
that?


-----Original Message-----
yes,. but 17 "PM"?

--

message

0500 = 5AM
1300 = 1PM
1700 = 5PM
-----Original Message-----
17PM is 5AM


message
Hello, I have as soon as unloaded version 1,0,614 and
must say of to have found a bug in the formulation of
the
hour of beginning automatic scansion. I wanted setting
to the 17pm, but when I press key UPDATE SCHEDULE, the
hour is transformed in 5äm and not there e' towards
making to work it. Hello and thanks for the
attention... Maury


.



.

.