Among the (many) complaints registered at the (ineffably slow) App Store against Appleʼs (unutterably poor, slipshod, pathetically inept) major dose of incompetence, MacOS 10.8.2 Mountain Lion, is the curse of the spinning beach ball — meaning that multicolored whirling circle which indicates that something is happening (but nothing relevant to what you just wanted to occur on your computer) although nothing ever does develop.
Wait, please wait… Wait… Keep on waiting… Wait, please… Wait.
Since yesterdayʼs attempt at calm reason (and closure) to my endless agonies with the recently installed system “upgrade,” that curse has been the essence of my longsuffering digitized existence, so much so that I actually shut down my iMac yesterday evening, screamingly frustrated beyond toleration and belief at hours of naught but “spinning beachball” nothingness, knowing full well that starting up this morning would be just another intolerably prolonged procedure, involving several stalls and resultant forced hard restarts —until I succeeded in causing a reboot in “safe mode,” which recently, at least, has actually worked and from which I can restart successfully (adding a mere hour to my morningʼs start-of-business).
I have also learned more than I really care to know about various processes on my Mac that can eat up all of the available active RAM — some being Appleʼs intrusions and some evidently resulting from my virus-protection package, Intego’s Virus Barrier X6 (version 10.6.18 for anyone counting), or so say the various Mac discussion sites discovered by my googling queries on such arcane processes as “launchd” (and many related programmed routines) “mdworker” (and its associated agents), “BehavioralInjector_32” and about a half dozen more — some of which it is safe to quit and some not, each of which can overflood the available memory and leave my computer just an electricity-sucking, luminescent lump of inactive digital dung.
A seventy-minute wait last night left the memory overfull and the cursor a movable spinning beachball. A marble of doom. So I finally, frustrated, shut down…
And felt much better almost immediately!
And then the new day dawned…
Right now, my memory meter (I having earlier quit several of the noisome processes already today) is not glowing all red with usage overplus, but nevertheless for every letter I attemp to tpe ere* in Scrivener, I only get a few, the calculated result being somewhat worse than uploading my hen-scratchings with the smartpen for interpretation (OCR?) and transformation into digital text. Maybe itʼs a sign that any work I accomplish today was meant to be handwritten?
And Lady Lovelace forfend that I should attempt to use the control-click over my own typos for a fast revision — oh, no, that just means two solid minutes of the dreadful beachball spinning.
Lus he disk is being ccsed nns I hbkgrn — Plus the disk is being accessed nonstop in the background.
Snarling sarcastic “thanks” for hindering all efforts, Apple… **
* That this is the kind of utter putrid crap my computer puts out when I am trying to type at a normal speed — I meant, “I attempt to type here” but as an example I left it as was (that passage at least being partially comprehensible, unlike some of the previous skips that deprived this text of whole words and phrases and ran letters ten words apart together into a nonsensical jumble).
** Babbage forbid that I might actually be able to use this computer for something other than its own care and feeding.
Now letʼs discover how many hours of pointless beachballing must be involved in transforming this file to HTML, copying said code, pasting into WordPress online, editing and proofreading and eventually posting…