11-03-2010 06:27 AM
Does the scan ever complete? If you leave it long enough does it continue, or do you end up seeing it as 'not responding' if you look at the Force Quit list?
The reason i ask is that if you have a very large DMG file for example this will take quite some time to scan. The main 'Scan Local Drives' scan is configured to check all 'archive' files which DMG is included as a type of.
It would be interesting to know if you create a custom scan of a folder with DMGs in it and scan it what your experience is. You could then edit this scan to change the scanning options to scan inside archive files, and see if your experience changes.
The other test of this would be to create a custom scan and add in all your hard drives / partitions (if you have more than one), but to not choose to scan inside archive files. This would replicate the 'Scan Local Drives' scan more or less but shouldn't unpack and scan inside DMG files. If this scan finishes and doesn't cause issues then you may have a DMG on your system that we are having trouble scanning, and we can then work to find this and figure out how to fix this issue.
11-03-2010 06:49 AM
I'm also having the same problem.
I did test it out yesterday on a 41gb folder containing 39 dmg's. It took over 2 hours to scan that folder and raised the temp of my Macbook Pro to 208*F during points during the scan.
I've also tried running a system scan on 3 occasions. All 3 attempts ended with me pushing and holding the power button to restart the laptop.
Two ran for about a half hour the 3rd I ran overnight with nothing else running. it ran for several hours and didnt progress beyond the initial 5-10 minutes that i saw it working before i went to bed.
I was able to get it to scan a 28mb, 10 picture folder without issue.
Macbook pro 3,1
500 gb hd with 55gb win 7 Bootcamp
Any ideas on why it wont scan the system?