How Do I Run a Virus Scan? Attempting to Resolve Gmail Access Issue.
Hello. I'm not technically savey and am in need to assistance in resolving an issue. I suddenly am no longer able to access my GMail account. The system will not accept long-used password. I'm working back through GMail assistance forum and was told "to run a virus scan on the computer," i.e., "scan your machine for viruses and malware. Get rid of any programs found during the scan." The message refers me to a Google Pack, which comes with free anti-virus software. When I check the website I don't see anything that looks like it is appropriate for running a virus scan on the computer.
How do I "run a virus scan"? Thank you in advance for your assistance.
Download ClamXAV - <a "http://download.cnet.com/mac/3151-20_4-0.html">VersionTracker or
MacUpdate. It's free. However, it's quite unlikely you have a virus.
How to you access GMail? Do you use a browser or an email program? If the latter which one do you use? Are you able to access your account using a different method or program than you are now using?
Hello Kappy, Thank you for your response. I reviewed a portion of the "Missing Manual" by David Pogue and figured out how to go into utilities and repair permissions. The following are the responses I got when I ran "repair permissions":
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "sbin/umount" has been modified and will not be repaired.
Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
Warning: SUID file "usr/sbin/pppd" has been modified and will not be repaired.
Warning: SUID file "usr/sbin/vpnd" has been modified and will not be repaired.
ACL found but not expected on "Applications/Utilities".
So what do I do with this information? I'm not sure what it means and how it impacts the computer. However, after I ran this, I was able to complete the goggle form for a new password (my computer no longer recognized my years-old password) and obtain a new one and then access my email account again. (I opened a bogus email yesterday that I have since learned contained a virus so I am assuming this may have caused my angst.) So I'm now back to my gmail account but not sure how the above information related to the "repairs permission" should be addressed if at all.
Thank you again for your assistance. I am truly not computer savey and what is intuitive for some folks just goes over my head so I truly appreciate your help.
Not a thing. All that is normal. Furthermore, permissions have nothing to do with viruses and repairing them won't affect anything within your Home folder. But if there were serious problems with system files' permissions, then repairing them may resolve system related problems that arise from bad permissions.
