Antispyware won't start--licence expiry.

[John S.]

After downlodaing the beta version, I tried to run it--
but I got an error message to the effect that the licence
had expired on 1-Jul-05 and that I would need to get an
update. (This was done today 9-Jan-05).
Anyone else had this message? Any ideas how to get
around the problem?

John S.

 

[Jurren Bouman [MVP-Security]]

On what version of Windows is this installed and what are the "Regional
Settings?" Is the system clock set correctly?

 

[Guest]

Thanks Jurren.
I'm running XP/SP2.
My system clock is set to local time (Eastern Australian
Standard Time) and the date is currently showing as Sun-9-
Jan-05.

 

[anonymous]

Is your XP licence genuine?

 

[John S.]

Yes.

-----Original Message-----
Is your XP licence genuine?

.

 

[Bill Sanderson]

Can you try different locale and language settings. I know you folks speak
the same language as I do barring a few regional differences, but it is
possible that the app is balking at date differences between the locales.
It seems to be deeper than just English only.

 

[John S.]

Could it be related to the date format I have selected?
I have set this up as:
Short date format = DDD-DD-MMM-YY
Long date format = DDDD, DD MMMM YYYY
(Although I would have thought the application would
check the current system date using an internal system
format that remains independent of a local setting).

 

[Bill Sanderson]

I think something along these lines is likely.

Part of the process of integrating a third-party product as a
Microsoft-branded product is going to be lots of standards-oriented work
around issues just like this one.

I haven't looked into this at all--just reading these threads, but switching
back to whatever the default is for your locale, and/or switching the
locale, is likely to be the fix.

I'm sure this is an issue that they will fix in the course of the beta--and
this thread will help ensure that it is on the list!

 

[John Smyrk]

Thanks for that.

-----Original Message-----
I think something along these lines is likely.

Part of the process of integrating a third-party product as a
Microsoft-branded product is going to be lots of standards-oriented work
around issues just like this one.

I haven't looked into this at all--just reading these threads, but switching
back to whatever the default is for your locale, and/or switching the
locale, is likely to be the fix.

I'm sure this is an issue that they will fix in the course of the beta--and
this thread will help ensure that it is on the list!




.