Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 6 subscribers
  • Views 6389 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

problems scanning USB drive/large folders - Mac OS X 10.6.x with iWork, iLife, multiple partitions

grahamperrin1

Fuller subject:

Sophos Anti-Virus Home Edition stops responding, total system lock-up and other misbehaviour when scanning USB drive, or a folder, greater than 600 MB, on updated Mac OS X 10.6 or 10.6.3 with iWork, iLife and multiple partitions

busterb wrote:

…neither BootCamp nor Parallels Desktop / VMWare Fusion have never been anywhere near …

This is a brand new install of Mac OS 10.6, iWork and iLife only (yes, no third party anything installed) on a freshly formatted drive with two partitions. My system locks up, stop scanning, and otherwise misbehaves when I scan a large folder (by size) or entire external drive hooked up via USB. If I keep it to less than 600 MB, all is well. It seems if I go beyond that, the system locks up, and Sophos will not respond. …

busterb wrote:

… doesn't work on a brand-new install of OS X on a just-formatted drive with no third-party software installed …

… my experience has been the 'free' version is buggy … 

 busterb wrote:

… my personal experience on my Macs is one of total system lock-up when scanning anything over 600 MB. Mind you one of those Macs was a freshly formatted drive, new install of Mac OS 10.6.3 and updated, only Apple software on the drive, nothing third-party save for Sophos Home. …

:1000615


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

    … I have to reformat the iMac that is most problematic with Sophos. Shall I try just a 10.6.3 install and update to 10.6.5? 

    Going ahead with that test should be good if you have the opportunity and don't mind the time. Keep it very, very plain without iLife, iWork etc., minimal peripherals and a single partition. 

    The peripherals thing is probably way off mark in these rounds of tests, but very rarely in the distant past (off-topic from Sophos for a moment) I've seen a consumer Mac, or Apple server hardware, misbehave when the Apple keyboard attached is different in some way from the Apple keyboard that was bundled. Strange but true. Postscript: another strange but true example from the distant past was the sometimes pernickety/unpredictable behaviour of early Apple-installed FireWire in PowerPC towers. And so on, just rarely an issue is in the least expected place (we're so accustomed to Apple-provided hardware combinations just working in combination, the last thing on ours minds is that the combinations might not work 100%). 

    Back to SAV: go for the cleanest minimalist installation then try the command-line approach to (hopefully) catch a point at which things stop responding. 

    :1000701
Reply
  • 0
    busterb wrote:

    … I have to reformat the iMac that is most problematic with Sophos. Shall I try just a 10.6.3 install and update to 10.6.5? 

    Going ahead with that test should be good if you have the opportunity and don't mind the time. Keep it very, very plain without iLife, iWork etc., minimal peripherals and a single partition. 

    The peripherals thing is probably way off mark in these rounds of tests, but very rarely in the distant past (off-topic from Sophos for a moment) I've seen a consumer Mac, or Apple server hardware, misbehave when the Apple keyboard attached is different in some way from the Apple keyboard that was bundled. Strange but true. Postscript: another strange but true example from the distant past was the sometimes pernickety/unpredictable behaviour of early Apple-installed FireWire in PowerPC towers. And so on, just rarely an issue is in the least expected place (we're so accustomed to Apple-provided hardware combinations just working in combination, the last thing on ours minds is that the combinations might not work 100%). 

    Back to SAV: go for the cleanest minimalist installation then try the command-line approach to (hopefully) catch a point at which things stop responding. 

    :1000701
Children
No Data