Beta in general

[Antioch]

I have only recently discovered community and discussion
groups for solving problems. And I have great enjoyment
reading the post in this discussion group.
Up until the end of may I had little or no dealings with
the internet but have since become an avid 'silver surfer'
and I built a quite high performance machine mainly for
simulators.
In addition I did heavy research into security and of
course downloaded MS Antispyware beta, plus Adaware and
McAfee.
Now being long in tooth and having a rather jaundiced view
of most things, I have come to the conclusion that if I
want MS stuff then I have to accept that it seems their
philosophy in marketing is 'build this in two weeks - get
it on the shelves - sell it - then get the community and
discussion groups to solve the problems we cant be
bothered/havnt got the time to solve. This is the case
with sims.
My first beta was due to run out July 31 - then without
any permissions I sudenly noticed that it was due to run
out Dec 31. I do not like anything to download without my
permission so disconnected autoupdate. I have for a week
now been asked repeatedly to update this prog.
Having read pages and pages of these posts in this group
and in other security sections I am loathed to do so.
I have a mind to uninstal current version and then load
the most recent or just plod along with what I have -
although it has found nothing for the last four weeks or
so.
My thanks in particular go to Robin Walker(in partic. the
bit about setting PM schedules - it worked), other 'Most
Valued Players, and Bill Sanderson. Your clarity of
explanations are exceptional.
Until I came to this group I thought Beta was American
for 'Better' but it aint always the case????
So, do I uninstall and download or just update?
Sorry for the length of this post.
Many thanks
Antioch
'You cant educate pork'

 

[Andre Da Costa]

"Having read pages and pages of these posts in this group
and in other security sections I am loathed to do so."

Thats a typical thing to do and happen during a beta, new builds all the
time. Microsoft has not been rushing it either, its been in beta since
January and no definite release date specified.
--
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

 

[Alan]

The original program was produced by Giant Company, whom
Microsoft bought out to acquire Giant AntiSpyware, now
called Microsoft Windows AntiSpyware.

Giant's version wasn't without it's problems. Most of
the files that the MS versions use were created by Giant,
hence the gc in almost every file associated with MSAS.
Also, the program went into beta only 21 days after MS
acquired it from Giant Company.

As for the upadating loop, my guess is that you are using
build 614, the last version of MSAS. Go to
http://www.microsoft.com/downloads/details.aspx?
FamilyId=321CD7A2-6A57-4C57-A8BD-
DBF62EDA9671&displaylang=en and download the installer
for build 615. This installer will fix the update
issue. Build 614's installer didn't update a critical
file, gcUncompress.dll, used for uncompressing the
downloaded definition files, and 615 installer does
update this file.

Alan

 

[Robin Walker [MVP]]

Until I came to this group I thought Beta was American
for 'Better' but it aint always the case????

No, "Beta" means a stage of pilot testing before proper release.

Because the product is only in pre-release testing we have to live with many
quirks.

If you wish to continue testing Microsoft AntiSpyware, then I do recommend
that you update the software itself to the latest version, available by
following the download links from http://www.microsoft.com/spyware/

You should also allow the definitions to update themselves automatically.

 

[Bill Sanderson]

My first beta was due to run out July 31 - then without
any permissions I sudenly noticed that it was due to run
out Dec 31. I do not like anything to download without my
permission so disconnected autoupdate. I have for a week
now been asked repeatedly to update this prog.

Thanks for the kind words!

The process of upgrading from one version to another (as was necessary to
move between the two expiration dates)--doesn't happen without a number of
clear prompts. There's been no automatic upgrade of code on your machine.

Do you share the use of the machine with anyone else?

 

[ANTIOCH]

Hello B.S.
I am sure I did not give any sanction to the move bet.
expiration dates. But then thats the beauty of memory at
my age - you meet new people every day!!!!
Howsomever, do I uninstal my 1.0.614 with Def. Version
5727 and go for a new clean instal on the latest or shall
I hit the update button when prompted?
Your input would be appreciated
Antioch
'You cant educate pork'

 

[Bill Sanderson]

The update button is just fine.

There have been 3 builds released with the new expiration date--.613 (very
short-lived), .614 (which has a versioning issue with a .dll related to
updating definitions), and .615.

None of them were installed automatically as far as I am aware--each
required the same set of prompts and responses.

--

 

[Guest]

Many thanks-I will hit the button when next prompted
Antioch