I have detected a Problem with Microsoft AntiSpyware. In
trying to set the time for an automatic scan, I set the
scheduled scan time to 12:10:00 pm. When I clicked on the
update schedule button to change the schedule, the
program changed the 'pm' to 'am'. The schedule change
seems to work fine if I set the hour to any hour except 12

I sent the above message to 'Online Customer Service '
and got the answer that since 'Microsoft AntiSpyware' is
a beta release, it doesn't have any technical support. I
was directed to wait until the final release was
available to get help with 'my' problem.

This isn't my problem; it is a problem that probably has
been in the code since 'Giant' owned it. My
communication was to point out a minor problem that I
thought Microsoft would like to correct before the final
release was made.

If possible, please send this text to the 'Microsoft
AntiSpyware' development team to check out. I have found
that this occurs on both Windows XP Pro sp2 and Microsoft
Server 2003.

Thanks in advance for your time and assistance in this
matter.
Pete Sheridan

Pete Sheridan presented the following explanation :
> I have detected a Problem with Microsoft AntiSpyware. In
> trying to set the time for an automatic scan, I set the
> scheduled scan time to 12:10:00 pm. When I clicked on the
> update schedule button to change the schedule, the
> program changed the 'pm' to 'am'. The schedule change
> seems to work fine if I set the hour to any hour except 12

Well, this is a really wellknown bug and will be fixed in Beta 2

--
plun

--
This is an automatic signature of MesNews.
Site : http://www.mesnews.net

try 11.59 or 23.59

Pete Sheridan wrote in news:0d9b01c5518b$f1750810$(E-Mail Removed)
>I have detected a Problem with Microsoft AntiSpyware. In
> trying to set the time for an automatic scan, I set the
> scheduled scan time to 12:10:00 pm. When I clicked on the
> update schedule button to change the schedule, the
> program changed the 'pm' to 'am'. The schedule change
> seems to work fine if I set the hour to any hour except 12
>
> I sent the above message to 'Online Customer Service '
> and got the answer that since 'Microsoft AntiSpyware' is
> a beta release, it doesn't have any technical support. I
> was directed to wait until the final release was
> available to get help with 'my' problem.
>
> This isn't my problem; it is a problem that probably has
> been in the code since 'Giant' owned it. My
> communication was to point out a minor problem that I
> thought Microsoft would like to correct before the final
> release was made.
>
> If possible, please send this text to the 'Microsoft
> AntiSpyware' development team to check out. I have found
> that this occurs on both Windows XP Pro sp2 and Microsoft
> Server 2003.
>
> Thanks in advance for your time and assistance in this
> matter.
> Pete Sheridan
>
>

Schedules
This appears to be "correct" behavior for the code currently distributed,
believe it or not!
Two days ahead of the scheduled day is "normal" as is the appearance when
you select 10 am.

Times between 12:00 and 12:59 PM are not selectable.
--

Andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"Pete Sheridan" <(E-Mail Removed)> wrote in message
news:0d9b01c5518b$f1750810$(E-Mail Removed)...
>I have detected a Problem with Microsoft AntiSpyware. In
> trying to set the time for an automatic scan, I set the
> scheduled scan time to 12:10:00 pm. When I clicked on the
> update schedule button to change the schedule, the
> program changed the 'pm' to 'am'. The schedule change
> seems to work fine if I set the hour to any hour except 12
>
> I sent the above message to 'Online Customer Service '
> and got the answer that since 'Microsoft AntiSpyware' is
> a beta release, it doesn't have any technical support. I
> was directed to wait until the final release was
> available to get help with 'my' problem.
>
> This isn't my problem; it is a problem that probably has
> been in the code since 'Giant' owned it. My
> communication was to point out a minor problem that I
> thought Microsoft would like to correct before the final
> release was made.
>
> If possible, please send this text to the 'Microsoft
> AntiSpyware' development team to check out. I have found
> that this occurs on both Windows XP Pro sp2 and Microsoft
> Server 2003.
>
> Thanks in advance for your time and assistance in this
> matter.
> Pete Sheridan
>
>