Since the current release is only a beefed-up version of the single-user app
that Giant Company produced, then these types of issues are bound to come up
when trying to use this app on multiple account systems.
Not only might they be coding Beta 2 to be multi-user, but they might also
be changing the source code from VB6 to C++ (likely .NET) or C# .NET. MS
released the first Beta 1 build on Jan. 6, which was only 21 days after
acquiring it from Giant Company. Because of the large amount of time that
the program has been beta and MS has't released any information of when Beta
2 is coming out other than "later this year," it's very poosible they are
doing a huge overhaul of the app. Let's hope the changes include running the
program as a service, like almost every AV app out there. Doing so should
make it possible to update the definition files by using WindowsUpdate.
Some of this information can be found at
http://www.microsoft.com/downloads/d...displaylang=en.
Alan
"Dave M" wrote:
> Hi Alan;
> So let me be sure I understand your warning in it's entirity. Are you saying
> that if any user (Admin or not) other than the installer of MSAS gets an event
> message from MSAS he should always allow such events, provided they have the
> installer's account name referenced in the message? And if such messages have
> his own name then he should use his own judgement as to the propriety of
> allowing or blocking them? And how about the case of an event warning to a
> non-installing user with the name of another non-installing user on the same
> system, if that would even happen (I'm not sure?) I'm beginning to regret
> having set up my XP multi-user install. Hoping Bill is right about Beta2 w/
> multi-user support coming soon, or I'm going to be doing some disabling, pronto.
> --
> TIA, Regards, Dave
>
>
> Alan wrote:
> > Is this account a limited user account?
> >
> > If so, you likely caused the problem by blocking a change that MSAS
> > "detected" when you logged into the account the first time the account was
> > used after installing the app on your administrator account. When you
> > blocked this event, you told MSAS to link two accounts together and this is
> > likely causing the problem since MSAS DOES NOT install ANYTHING on your
> > system other than the files that are associated with the app. If you get any
> > dialog box warnings from MSAS in the future, read them CAREFULLY as the user
> > name is included and not paying attention to this information WILL result in
> > you having to hack the registry to fix these types of mistakes. NOTE: This
> > also applies if using a different administrator account than the one that
> > installed the app.
> >
> > One more question, did you download the app from Microsoft.com or somewhere
> > else? If you downloaded it from elsewhere, there's a chance that what you
> > downloaded included spyware, which is what's causing your problems. NEVER
> > download anything from any source other than the producer's web site,
> > otherwise you can get burned if you don't do so.
> >
> > Alan
> >
> > "Candyman" wrote:
> >
> >> And before i knew it microsoft had placed some "shell" operation on my
> >> desktop....ok so i found the log antispyware but have since deleted it and
> >> can't seem to get rid of the stupid thing. I can not save anything to my
> >> desktop it autoatically sends it to my documents and then into the desktop
> >> folder. If i do want to place anything on the desktop i now have to use the
> >> "user" file and place objects in it's "desktop" folder.......does anyone know
> >> how to get rid of this grip microsoft has put on my desktop?
>
>
>
Similar Threads
