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

Unable to complete login after reboot

mdoorkeeper

Hi,

I installed Sophos Anti-virus for Mac Home Edition yesterday.  Install went as expected.  I ran a custom scan on a small micro SD to try it out and it went well, so I ran a full system scan.  That went faster than expected - MUCH faster than ClamXav, so I thought, "I like this".  BUT!!!! When I went to restart my computer today, I was unable to login to my admin account.  The whole computer would hang and become completely unresponsive to any interface just after launching Finder.  I had to force shutdown using the manual button in the top right corner.  I then ran "Applejack", (which cleaned a HUGE cache file), and rebooted.  Same result, ie; hang after Finder launch.  Sooo, I forced shutdown again, rebooted in Safe mode, and uninstalled Sophos AV.  

It has been suggested on another forum that the problem is that my computer was not connected to the internet at the time I restarted.  My computer is a Macbook and I usually use it in a mobile environment, so I'm almost never connected to the internet when I reboot.

I like the product.  I've not had the slowdown issues I see posted here, in fact I was impressed by how fast it worked and how little CPU it used while running in the background, but until I can restart without problems, I'm afraid it will stay uninstalled.

FYI:  My computer is an '08 Macbook 13" aluminum with 4gb RAM, running OS X 10.6.4

:1000262


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

    In the system.log extract for that 2010-11-12 00:43 incident, I'm not overly focused on the 

    INSERT-HANG-DETECTED

    in the closing line. Google finds many matches for that expression and I don't recall this particular search/match for any previous incidents. 

    Incidentally Spotlight was busier than usual, at login time of the second incident, only because the first incident evidently corrupted Spotlight index files — that's something I forgot to mention in the previous post. 

    (The current estimate in the Spotlight menu is about 28 hours remaining but maybe the progress bar will leap ahead at some point.)

    :1000711
Reply
  • 0

    In the system.log extract for that 2010-11-12 00:43 incident, I'm not overly focused on the 

    INSERT-HANG-DETECTED

    in the closing line. Google finds many matches for that expression and I don't recall this particular search/match for any previous incidents. 

    Incidentally Spotlight was busier than usual, at login time of the second incident, only because the first incident evidently corrupted Spotlight index files — that's something I forgot to mention in the previous post. 

    (The current estimate in the Spotlight menu is about 28 hours remaining but maybe the progress bar will leap ahead at some point.)

    :1000711
Children
No Data
Cookie Information Banner