Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 28 replies
  • Subscribers 6 subscribers
  • Views 34948 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Anti-Virus for Mac V7.3.1 is compatible with Mac OS X Lion

spiderman

Apple just launched their latest operating system OS X 10.7 (Lion) today and we wanted to let you know that your version of Sophos Anti-Virus for Mac already supports it.


In anticipation of the Lion launch, we released an update at the end of June that automatically upgraded SAV for Mac to v7.3.1. This version is compatible with OS X Lion so whenever you upgrade to Lion, you’’’’ll be fully protected.


If you are a home user and don’’’’t have Sophos Anti-Virus for Mac already installed, or have not been upgraded to v7.3.1, you can download the latest version for free here: http://www.sophos.com/freemacav

:1003485


This thread was automatically locked due to age.
Parents
  • 0
    lemon wrote:

    So far so good...

    I tested it for a while and the result is that I will keep it working like this. Which means:

    I disabled all the external discs from scanning. I only allowed one external partition to be scanned but NOT time Machine.

    My mac seems to stay stable and it seems no more maxing out of CPU, is happening. I will come back to report if it stays this way or if it goes crazy again.

    Excellent news!  So you're saying that you are and were not using network shares, but were scanning all locally attached media, and that excluding your Time Machine drive fixed the CPU error?

    :1003615
Reply
  • 0
    lemon wrote:

    So far so good...

    I tested it for a while and the result is that I will keep it working like this. Which means:

    I disabled all the external discs from scanning. I only allowed one external partition to be scanned but NOT time Machine.

    My mac seems to stay stable and it seems no more maxing out of CPU, is happening. I will come back to report if it stays this way or if it goes crazy again.

    Excellent news!  So you're saying that you are and were not using network shares, but were scanning all locally attached media, and that excluding your Time Machine drive fixed the CPU error?

    :1003615
Children
No Data
Cookie Information Banner