Guest User!

You are not Sophos Staff.

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 stops working when my mac starts up

Hope someone can point me in the right direction.

I'm using a mac (10.6.8) and have the latest sophos 8.04C - every time I close down my mac and restart it the next morning Sophos stops working and wont allow me to change anything at all via preferences. If I just put my mac to sleep there's no problem at all when it wakes up and sophos continues to work.

If I download the sophos software again everything works smoothly until the next time I shut down my mac ..........!

Maybe I'm missing something - perhaps I've got one of the settings wrong, perhaps my OS wont work with the latest sophos - I just don't know!

Anyone got any ideas?

Thanks in advance

:1007673


This thread was automatically locked due to age.
Parents
  • In a way, it's good to know that you're experiencing the same problem (frustrating for you though) -- as this means that the issue is likely due to your specific setup and can be corrected on your end given enough time and patience, assuming you're willing to put in that level of work.

    In the meantime, I'd recommend keeping on-access scanning disabled (which it appears to do for you anyway) and creating some scheduled scans -- weekly for your entire computer, and daily for your download folder, desktop, and anywhere else you regularly store files.

    You can get to the list of kernel extensions by opening up About This Mac... from the apple menu, clicking on "More Info..." and clicking the Extensions listing.  You'll likely have to wait a minute or so, and then an entire list of loaded extensions will show up.  With this, I should be able to see if there's something loading at startup that may be interfering with Intercheck's ability to communicate with other processes.  I'll also probably be getting you to check for processes that start at login, which may involve a bit of typing in terminal.app.  If it comes to that, I'll give you specific instructions on how to do it.

    :1008101
Reply
  • In a way, it's good to know that you're experiencing the same problem (frustrating for you though) -- as this means that the issue is likely due to your specific setup and can be corrected on your end given enough time and patience, assuming you're willing to put in that level of work.

    In the meantime, I'd recommend keeping on-access scanning disabled (which it appears to do for you anyway) and creating some scheduled scans -- weekly for your entire computer, and daily for your download folder, desktop, and anywhere else you regularly store files.

    You can get to the list of kernel extensions by opening up About This Mac... from the apple menu, clicking on "More Info..." and clicking the Extensions listing.  You'll likely have to wait a minute or so, and then an entire list of loaded extensions will show up.  With this, I should be able to see if there's something loading at startup that may be interfering with Intercheck's ability to communicate with other processes.  I'll also probably be getting you to check for processes that start at login, which may involve a bit of typing in terminal.app.  If it comes to that, I'll give you specific instructions on how to do it.

    :1008101
Children
No Data