important feature thats missing on this beta 1

A

Aaron

Multiple user account/limited Account support. plus a
basic and easy user account management so that
administrator can prevent user from changing settings.
 
A

Alan

Missing for ONE VERY IMPORTANT reason. In order to scan
multiple accounts, the file permissions and system files
must not be altered in ANY way. Since a user might be
running the application under a limited-user account and
be scanning the entire system, including all
administrator accounts, then a lot of care must be taken
to ensure that no changes are made to any system files,
nor the file permissions of any user. This involves a
major amount of coding and testing before even
considering releasing it to the public. The alst thing
we need is for MS to push an update out the door before
it has been thuroughly alpha (pre-beta) tested. Just
imagine the nightmare you could experience if this isn't
done properly and you have to do a reinstall of Windows.
They are taking their time to make certain that there's
no major bugs with the updated application before making
it available to the public for beta testing.

In the past, many computer companies WOULD NOT take these
precautionary steps before making this type of update
available for beta testing. The way that MS is
approaching this type of update is very smart, and allows
them to do more testing of the application than they were
able to do before making Beta 1 public. They bought the
original source code from Giant Company and the
application went public only 21 days later, with mainly
cosmetic changes to the application's source code. The
most changes made were changing the references of Giant
Company to Microsoft.

Alan
 
G

Guest

Thanks for making it all clear.

-----Original Message-----
Missing for ONE VERY IMPORTANT reason. In order to scan
multiple accounts, the file permissions and system files
must not be altered in ANY way. Since a user might be
running the application under a limited-user account and
be scanning the entire system, including all
administrator accounts, then a lot of care must be taken
to ensure that no changes are made to any system files,
nor the file permissions of any user. This involves a
major amount of coding and testing before even
considering releasing it to the public. The alst thing
we need is for MS to push an update out the door before
it has been thuroughly alpha (pre-beta) tested. Just
imagine the nightmare you could experience if this isn't
done properly and you have to do a reinstall of Windows.
They are taking their time to make certain that there's
no major bugs with the updated application before making
it available to the public for beta testing.

In the past, many computer companies WOULD NOT take these
precautionary steps before making this type of update
available for beta testing. The way that MS is
approaching this type of update is very smart, and allows
them to do more testing of the application than they were
able to do before making Beta 1 public. They bought the
original source code from Giant Company and the
application went public only 21 days later, with mainly
cosmetic changes to the application's source code. The
most changes made were changing the references of Giant
Company to Microsoft.

Alan

.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top