Time bug

[PeterF]

Set the regional options Time to H:mm:ss like most
Europeans have it set.

Now click on Tools->Spyware scan->Manage Spyware Scan
Schedule. Try to set the Start time to anything after
11:59:59. You will notice that "Current scheduled spyware
scan runs at:" displays an AM time in stead of PM.

Good luck,
Peter
Beta ID 462863

 

[Andre Da Costa]

List of changes in the beta 1 Refresh Update, if its not on this list, its
not in there:



1) Software expiration will be extended to December 31, 2005.

2) Alerts Moving Quickly Across the Screen : Messages which move
quickly off the screen when the start bar is not docked horizontally are
also fixed. Users who dock their start bar on the sides of their screen will
now be able to read messages generated from Microsoft Windows AntiSpyware
(beta).

This issue is what we dubbed the "Flying Toast Issue" and one which I was
passionate about getting fixed in this refresh build.

3) Support for Long Descriptions: Users of older builds only have
access to the short descriptions which ship as part of the signatures. These
short descriptions only provide limited information about potentially
unwanted software. Long descriptions in build 613 will help users by giving
them more information about the potentially unwanted software detected on
their PCs.

4) Improved Winsock LSP removal mechanism: In some cases, removing
spyware LSPs, or can disrupt network functionality. Through enhancements
made in this beta refresh, we've lessened the chance that this problem will
occur.

 

[PeterF]

Hi Andre

Well, I thought it was so obvious that I didn't submit it
until now I find out it's still int there

Peter

 

[Bill Sanderson]

Peter - this bug doesn't just affect users using European conventions--it
affects all the Americans as well.

I've seen one report that this is fixed in build 613. If you'd like to test
that yourself and post back to this thread, that'd be great. It isn't on
the list of what's fixed, but one user reported that he was able to scan
both at noon and reliably on a particular chosen by name day of the week.

--

 

[Tom Emmelot]

Bill Sanderson schreef:

Peter - this bug doesn't just affect users using European conventions--it
affects all the Americans as well.

I've seen one report that this is fixed in build 613. If you'd like to test
that yourself and post back to this thread, that'd be great. It isn't on
the list of what's fixed, but one user reported that he was able to scan
both at noon and reliably on a particular chosen by name day of the week.

Hello Bill,

I am Dutch, the first beta i could change my scan schedule to 21.00 hour
but now i must change the Langue to US english, than change to 21.00
hour and go back to Dutch than the scan time stay's that way.
Else the 21.00 hour go's back to 9.00 AM.

With regards >*< TOM >*<

 

[Andre Da Costa]

Which would obviously mean then, its not fixed.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

 

[Bill Sanderson]

Hello Bill,

I am Dutch, the first beta i could change my scan schedule to 21.00 hour
but now i must change the Langue to US english, than change to 21.00 hour
and go back to Dutch than the scan time stay's that way.
Else the 21.00 hour go's back to 9.00 AM.

With regards >*< TOM >*<

Thanks, Tom.

If I am reading you correctly, and I think I've seen this in another
post--not sure from whom--this looks like a new bug to me, in the new build.

I don't even have a machine running 614 yet--so it'll be awhile before I
can test this better--thanks for the clear post.

 

[Andre Da Costa]

Its the same thing in build 614 Bill.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

 

[Tom Emmelot]

Bill Sanderson schreef:

Thanks, Tom.

If I am reading you correctly, and I think I've seen this in another
post--not sure from whom--this looks like a new bug to me, in the new build.

I don't even have a machine running 614 yet--so it'll be awhile before I
can test this better--thanks for the clear post.

Hello Bill,

614 is the same, about what fix 614 see my mail in announcements!

Regards >*< TOM >*<

 

[Bill Sanderson]

My sense of the workaround for this issue, judging by what I've read here so
far, is using a 12-hour clock setting, rather than a 24-hour one--but I
haven't tested yet. I do now have a couple of machines on .614 but haven't
done the testing yet.

--