Now Windows' system files are the target of FP?

Sheesh…

Now atapi.sys can be infected?

As I said before, Avast!'s team really NEED to go back to the draft/design board and either rebuild the entire virus detection engine or build a new one altogether or take the time to perform EXTENSIVE tests of VPS updates prior to release…

Too many potentially “disastrous” FPs have been appearing as of late…
This is a major concern for an Antivirus product, mainly because most of its user base are not computer experts or do not have the knowledge of the inner workings of their OS and as such they “trust” what the product tells them… Even if it’s completely ludicrous or coudl led to them losing their system’s operability or data, like a quack doctor telling you 'tis alright to extirpate both your lungs. In a corporate environment this proves worse as they could lose money, data, deadlines, etc.

Please DO NOT let Symantec’s mass mailing rants about how “Free Antivirus solutions are untrustworthy” become TRUTH.

Yes, atapi.sys can be infected.Read the following article:
http://remove-malware.com/malware/malware-news/atapi-sys-rootkit-is-everywhere/

so avast warning is not FP?
is it the cause of my problem here:
http://forum.avast.com/index.php?topic=53320.0

Hello chachazero-tan…
There are other ways of telling whether your antivirus software has given you a reading that you may find questionable. Submit the file to avast, and have them check into it for you. You can have the file(s) in question submitted to an online virus checker. Their are free sources on the internet that are available to do this.

Also, you could have an online scanner check your system as well. There again are free sources as well to help you. Second opinions can be a valuable source of information when you’re trying to determine whether your system has an infection or not. In as far as Symantec is concerned…well…I’ll leave that for another time. ^.^