Response of Intego/VirusBarrier to it new update crashing SuperDuper

[dnanian]

To repeat what I posted to your previous posting of this information:

Unfortunately, they're incorrect. Adding /Library/Intego to the trusted zone doesn't work, according to the users I've forwarded that to.

It's regrettable that they're pointing fingers at us, when the problem certainly seems to be in their court. It's one thing to deny access to an infected file: the user is then alerted that the file is infected, and can take action to remedy the situation.

It's another thing entirely to install files onto a drive that can't be copied due to the action of their kernel extension, and not even allow the files (which have rather bogus names with single byte ASCII characters that are typically 'invisible' to the user) to have their date/time information retrieved, even from a process that's running with root privileges.

Intego needs to have a bit more respect for their users than they're showing, I think. Scanning for (nonexistent, I might add) viruses should not prevent users from copying their completely uninfected drives.