J
Jbob
Noticed some issues using MSAS .614 on a new build of XP Pro. I just
loaded a
new hard drive with XP Pro/sp2. Fully patched. After I installed Office XP
and patched it I then installed all my AV/Anti-Spyware apps. Spybot S & D,
Ad-Aware, MSAS and got them fully updated. For now MSAS and NAV are my only
resident scanners. Not using Teatimer or Spybots immunize feature.
I then began installing many of my other apps. I never got any warnings from
MSAS of any installation changes to my system. After a few hours of
installing and tweaking I finally put in the MVPS Host file. Still nothing.
A few minutes later during a reboot all of a sudden MSAS popped a bunch of
warnings. Some of the warnings were for installations that had already
occured. I selected all the appropriate blocks to clear the warnings. Funny
I was able to fully add a new HOST file without a peep from MSAS.
I am able to duplicate this on another system but doesn't work that way on
all systems. Some I get an instant dialog alert some not.
After further checking I can safely say that MSAS should not be depended
upon for HOSTS file monitoring, at this level of development.
In tests on a machine that it is working, i.e. MSAS will alert me
immediately,
one single entry will generate a MSAS notification. If I enter more than 2
entries,
MSAS will only pop up one entry(the bottom/last one), which MSAS gives me
the option to allow or block, however it does not give the option for action
of
the other entries. After entering two new addtions to the HOSTS file, if I
tell
MSAS to block it it does, however the other entry is allowed.
I noticed this bahavior when adding a new HOSTS file to windows. If I use
either hpgugu's or the mvps version MSAS does notify of a HOSTS file change
but only the last entry is shown.
I suppose any notification is better than none though. One should always
check anytime MSAS notifies of a HOSTS file change.
Still doesn't answer WHY in my case on certain machines I get NO
notification. In this specific case it is more than a HOSTS file issue.
loaded a
new hard drive with XP Pro/sp2. Fully patched. After I installed Office XP
and patched it I then installed all my AV/Anti-Spyware apps. Spybot S & D,
Ad-Aware, MSAS and got them fully updated. For now MSAS and NAV are my only
resident scanners. Not using Teatimer or Spybots immunize feature.
I then began installing many of my other apps. I never got any warnings from
MSAS of any installation changes to my system. After a few hours of
installing and tweaking I finally put in the MVPS Host file. Still nothing.
A few minutes later during a reboot all of a sudden MSAS popped a bunch of
warnings. Some of the warnings were for installations that had already
occured. I selected all the appropriate blocks to clear the warnings. Funny
I was able to fully add a new HOST file without a peep from MSAS.
I am able to duplicate this on another system but doesn't work that way on
all systems. Some I get an instant dialog alert some not.
After further checking I can safely say that MSAS should not be depended
upon for HOSTS file monitoring, at this level of development.
In tests on a machine that it is working, i.e. MSAS will alert me
immediately,
one single entry will generate a MSAS notification. If I enter more than 2
entries,
MSAS will only pop up one entry(the bottom/last one), which MSAS gives me
the option to allow or block, however it does not give the option for action
of
the other entries. After entering two new addtions to the HOSTS file, if I
tell
MSAS to block it it does, however the other entry is allowed.
I noticed this bahavior when adding a new HOSTS file to windows. If I use
either hpgugu's or the mvps version MSAS does notify of a HOSTS file change
but only the last entry is shown.
I suppose any notification is better than none though. One should always
check anytime MSAS notifies of a HOSTS file change.
Still doesn't answer WHY in my case on certain machines I get NO
notification. In this specific case it is more than a HOSTS file issue.