Norton should be ashamed for releasing such under-baked software. I followed your instructions and now it's starting up as my dependable Mac has always done. symbol for no on startup, and using single-user mode (command+s during startup) said it couldn't find the 'root device.' I honestly thought my primary HD had s*&% the bed. Imagine stumbling across this 'hint,' which I would classify as a lifesaver. I got so desperate I wouldn't shut down and only put the computer to sleep during my off-hours. Someone else around to do those things - while I get to wait.THANK YOU kylegeek! This has been driving me nuts for two weeks now, and only by a fluke of random start-up key combos was I able to get my computer to boot. I also do not have the time to experiment with my Macs as before.Īnd I have things to do and people to see actually, I have to take I don't have the undivided time to expand my own horizons, to help. To user problems in online forums, ones I never experienced. That I'd have gone rather far into a crash-course to learn answers Unfortunately, I am probably not the one to do it! There was a time Issue/problem noted in their user forum, link in previous post? Was there a contact email, or reference to any kind of similar To no help in this part of the technical resolution. Than a passing awareness of some of its features, I am of little Of course, since I do not know the Terminal well or have more Way to attack this issue within the machine's Terminal. Going on inside the Mac OS X system, there must be another Single-user mode to attempt to disengage or change what is Path is certainly in Terminal or perhaps accessed via a booted Since the notations you cite from the system log indicate the Could it be the ClamXav was installed under a different methodĪs described in the web site & Uninstaller script can't go there?
0 kommentar(er)
