Expiry Notice

[Tony Burke]

Microsoft AntiSpyware beta Version 1.0.0.509 -
When I try to activate the program a notice appears much
of the time saying this version HAS Expired as of July
31st!!!!
I sometimes have to try 4,5 or 6 times until the program
eventually opens!

 

[Andre Da Costa]

Please update to the latest build 614 to extend the expiration to Dec. 31,
2005.
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en
--
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

 

[Tony Burke]

Thanks for reply - I will download new version - but am
still puzzled by HAS EXPIRED notice!!

 

[Andre Da Costa]

Because it is a beta product.
--
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

 

[Guest]

Have downloaded and updated - it is now telling me
occasionally that it HAS!! EXPIRED 31/12/05 and I still
have to try a number of times before it opens!!

 

[Jupiter Jones [MVP]]

Go to Control Panel and open "Regional and Language options"
Click Customize button and then Date tab.
On the drop down menus, select the top item in each.

 

[Bill Sanderson]

If you check out the new download page:

http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

They are much more emphatic than before about the English only requirement.

There's a series of posts from Tom Emmelot, some of which are in
..announcements, where he states that if you are in a 24-hour clock locale,
and can't set a scan-time in the PM, you should switch your language to
English, make the setting (successfully!) and then switch the language back
to your native language, and the scan will continue to happen at the
appropriate time. This seems very strange, but he is very clear about it
and given the oddities of this program I'm inclined to believe this
solution.

This thread is the first I've ever seen where this type of date/timebomb
issue is not "solid"--though--I'm having real trouble understanding what
kind of bug allows the O.P to get past the timebomb in some tries, but not
others, with the same system and date and time!

However--I suspect your posted fix will do the job, but there are things
about the new build that I don't see enough experience with here yet to be
sure about.

 

[Bill Sanderson]

Re-reading this, I guess I can imagine a possible way for the time-bomb to
be variable, as cited in this thread. If the problem involves an overflow
of some sort, in mis-reading a date, it is possible that seconds or minutes,
in addition to the more obvious date elements, are involved--and perhaps
hitting the code at the right moment, in terms of seconds, is what is
getting him past the time-bomb. Ugly, of course, but at least a possible
objective reality.

 

[Guest]

Thanks for reply - the problem still persists in the
updated version - and also it sometimes shows my last scan
as December 30th.1899 at 00.00!!!! I am a novice at
Computers and still puzzled.

 

[Bill Sanderson]

Sorry--this message was not available to me to respond to until tonight.

I'm not a novice, although also not a great technical wizard, and this is
pretty puzzling to me, as well.

I believe this advice, posted by Jupiter Jones in this thread, is probably
key:

Go to Control Panel and open "Regional and Language options"
Click Customize button and then Date tab.
On the drop down menus, select the top item in each.


If you have done those steps, I would also recommend the following:

Start, control panel, add or remove programs, Microsoft Antispyware, Change,
Update....

This will perform a repair install, which I'm hoping will take away the
issue of variability, which I really don't understand.