F
Filthy McNasty
Is there some setting within WinXP Pro SP2 which protects the HOSTS file
from alteration? Following recent hardware problems, I took the
opportunity to re-install Windows using a slip-streamed SP2 CD. Under
SP1 I had never been able to run a successful upgrade to SP2 - Too many
unidentified problems. Anyway, soon into the reinstallation - security
updates and security-related programs first - I decided to overwrite my
HOSTS with the MVPS HOSTS file. No dice. Eventually I tried Safe Mode
and succeeded. This was BEFORE installing SpyBot S&D, SpywareBlaster or
WinPatrol. ZoneAlarm free had NOT been configured to protect HOSTS.
Barring ZA, only Ewido and AVG Free were running. Both give me a clean
bill of health, so Trojans and Viruses (ii?) are not suspected
The only other notion I had, is that XP Pro has some default service
running which locks the HOSTS as in use before log-in. The problem with
that idea is that, as an experiment, in Safe Mode I renamed HOSTS so
that there was nothing to be locked. Nevertheless, on reboot, attempts
to copy MVPS HOSTS to the correct location, or to rename the previously
disabled HOSTS, failed, even though the renamed file should not have
been in use
I have NOT tinkered with my default Services, other than to disable
Messenger and UP&P. Nor have I installed those parts of XP - IIS and the
like - which are not part of the default installation. ALL essential
security patches have been installed, plus the latest DotNet RunTimes
Thanks for any ideas. It's only an irritation, soluble in Safe Mode, but
I like to know why things do not behave as they should
from alteration? Following recent hardware problems, I took the
opportunity to re-install Windows using a slip-streamed SP2 CD. Under
SP1 I had never been able to run a successful upgrade to SP2 - Too many
unidentified problems. Anyway, soon into the reinstallation - security
updates and security-related programs first - I decided to overwrite my
HOSTS with the MVPS HOSTS file. No dice. Eventually I tried Safe Mode
and succeeded. This was BEFORE installing SpyBot S&D, SpywareBlaster or
WinPatrol. ZoneAlarm free had NOT been configured to protect HOSTS.
Barring ZA, only Ewido and AVG Free were running. Both give me a clean
bill of health, so Trojans and Viruses (ii?) are not suspected
The only other notion I had, is that XP Pro has some default service
running which locks the HOSTS as in use before log-in. The problem with
that idea is that, as an experiment, in Safe Mode I renamed HOSTS so
that there was nothing to be locked. Nevertheless, on reboot, attempts
to copy MVPS HOSTS to the correct location, or to rename the previously
disabled HOSTS, failed, even though the renamed file should not have
been in use
I have NOT tinkered with my default Services, other than to disable
Messenger and UP&P. Nor have I installed those parts of XP - IIS and the
like - which are not part of the default installation. ALL essential
security patches have been installed, plus the latest DotNet RunTimes
Thanks for any ideas. It's only an irritation, soluble in Safe Mode, but
I like to know why things do not behave as they should