others seeing the IPoint.exe file for the MS as a "threat"? being part of the MS software for their own optical mice
KAV when set to advanced mode has picked that up as well, i use one and co-incidentally was using the official driver package when i used KAV.
I had to remove it because the package forces mouse accelleration on, and that pisses me right off, but it was still detected.
KAV Also detects STEAM.exe as a trojan.
I think it's more important to mention; There is
no such thing as a false positive.
If an AV says something is a trojan, IT IS A TROJAN.
It's just not a HARMFUL trojan, many companies these days are implementing trojan-like code into their software to allow them to keep track of you.
STEAM is a perfect example where STEAM.exe and a few other files are picked up as a trojan - AND IT IS.
Yet the features which make it be detected as a trojan are simply part of STEAMS' anti-cheat system.
Doesn't change the fact that for all intensive purposes, steam is a trojan by definition. Not all trojans attack and not all trojans steal important info, so the most accurate defenition to stick by is my own;
"Software that has attractive qualities about it and the user installs the software wanting these attractive features. The software also has the ability to steal information and/or perform milicious attacks on the computer, which is hidden from the user"
STEAM.exe does exactly that, it reads memory, hdd folder tree and multiple other virus-like activities so it can find cheats on your system.
If you are found cheating it then bans you.
None of this is in STEAMs' End User Licencing Agreement however, so you're not giving STEAM consent for it to do this. That makes it fit every trojan definition to date; even
http://en.wikipedia.org/wiki/Trojan_horse_(computing) tends use a computer game as an example.... i'm wondering by now if they're actually referring to VALVe releasing steam with a trojan/backdoor
Nighthawk; FixMBR has been around since windows 2000, not sure if it was in 98, never needed it then. I needed it with 2000 however when installing a devian boot loader killed my MBR
Have a look in the bios setup on an older board sometime to see the option to enable or disable boot sector protection there.
That is rather useless. Boot Sector Protection only works on HDD0 Partition1 and your boot HDD may be HDD2 Partition 3. Sadly newer motherboards have allowed you to specify which hdd was your highest boot priority. I guess it was to remove the need for a multi-oS capable boot loader and allow you to boot into multiple OS's via picking the HDD it's on as the boot device.
Either way, especially with XP and 2k not requiring boot data to be within the 1018* odd cylinder boundry, boot protection is a false claim. It's much harder to protect your boot sector now than it ever was.
We're just lucky that 2k and newer has eliminated the rootkit problem which allowed the MBR to be attacked in the first place.