Nothing to Say?

So, itʼs two months and a week since my last post. What else isnʼt new?

Well, jaw-droopingly enough, The Lovely One  has actually asked me to try posting regularly. (I know — tradition holds she hates any time I spend at the computer, even writing, and she has always thought my pathetic posts here on Wakdjunkagaʼs Blog were, uh, pathetic.) So at her behest more or less, letʼs  conclude the ten-week hiatus:

ClocksI have been doing nothing much with those 69 days. nearly nothing at all. (I did finish and revise a short story to submit for possible publication — the result still suspended in the atmosphere somewhere/somewhen. “Scholarsʼ Folly” takes Søren, sans Judah, from northeastern Iberia to Córdoba for a really bad day with supernatural intrusions, his subsequent ethical self-flagellations being reserved for what will become the following chapter in the final novel. However, that effort filled less than a week, really, the original composition having been part of my NaNoWriMo 2012 enterprises. The revised product was e-mailed for editorial consideration way back in mid-January.)

Today, having actually gotten a break from nearly daily snowfall (no lie — culminating in three days of flood-inducing rain), punctuated by regular weekly blizzards (both requiring me to shovel rather than head out to exercise first thing in the darkness before dawn), I did my time on the elliptical and came home feeling genuinely determined to do something (for once) today.* So here I am pecking away…

Unfortunately with nothing to say.

You see, that (lack of postable content) has been the major problem (other than lazily and worthlessly diddling all my time away each day) preventing the blog from acquiring updates. Nothing to say…

(And when I consider all that I found myself able to blather in 2010 when I did the post-a-day thing so glibly and logorrhea-cally, perhaps the current chastity of content seems less pitiful and more prudent. Perhaps.)

The same lackluster life (mine) has also prevented me from keeping my letter-writing particularly current (and I do need to write both to my long-suffering aunt and communication-deprived bother later today or no later than tomorrow). I havenʼt even added more than a few thousand words to my creative endeavors. Plenty of mental composition but nearly nary a word even smartpenned to paper for eventual upload into the (contemptibly frustrating) digital presumed-reality.**

However, even with this despicable deficiency of (for equally miserable want of better terminology) subject matter, I felt as though I must post something. So this drivel is it.


* Of course, my eff-viscerating, worthless computer has had other ideas: those first few sentences have taken some seventy minutes to get on the screen, as multitudes of pointlessly intrusive background processes have taken over the computerʼs processor cycles ahead of my considerably-less-than-feeble keyboard smashing (but regardless how fiercely I punch a key, for some reason Spotlight uselessly updating its database or the virus-protection programʼs mercilessly intrusive “Behavioral Injection” activities take precedence regardless). Yep, nothing has changed; and the computerʼs incompetence frustrates me and drives me away from the infernal screen/mouse/keyboard to do something that might seem potentially productive (or at least less emotionally traumatic) — like reading the Kindle instead (but more on that tomorrow). Appleʼs demonic apparatus and its meddlesome softwares even contrived to get me to delete somehow the original final sentences of the parenthetical conclusion of the paragraph above the one to which this footnote appends.

** And now, suddenly there is no ceaseless drive-grinding (blessed silence on that front for my tinnitus to fill with ethereal cacophony of unreal audio-effervesence instead), and the menu meter indicates merely four percent of the memory and processor active — thus my letters and words actually transfer from brain-and-fingers through the keyboard to the machine and thus the screen (and eventually, we hope, onto you). Astonishing.

Facebook Timewaste

Once again, I do have reports on reading (and recommendations thereby/fore), not to mention some travel and maybe even other items, for future posts — assuming as inevitably ever, the damned device permits.

©2013 John Randolph Burrow, Magickal Monkey Enterprises, Ltd, S.A.

Effing Mountain Lion

FML. My computer cannot keep up with my typing (and although I type relatively quickly, I do not type really, really fast, so anyone would believe that a modern — no, not contemporary, but still modern — computer could keep up with my only-human typing speed; that supposition would be wrong). So what is the problem?

The infamous chiclet-keyboard (with the inimitable Gwen Hernandezʼs incredibly useful Scrivener for Dummies right there, close to hand when needed.

The infamous chiclet-keyboard (with the inimitable Gwen Hernandezʼs incredibly useful Scrivener for Dummies right there, where it always resides, close to hand when needed).

Well, up front I should admit that I donʼt lways hit every key precisely (particularly on this damnable chiclet Bluetooth keyboard*). For example, that missing “a” in the previous sentenceʼs “always” is probably not the fault of the computer but of this user (of course, the spelling-correction feature is underlining the defective “lways” — both above and in this parenthetical insertion, but I intend to post this initial message for 2013 just as my computer — and I — create[s] it, more or less**; likewise, if I adntʼ mad Typinator change m regular mistyped “setnence” to sentence, that ould have remained wrong as well). I also, as suggested already, have a horrible tendency toward typos — dyslexic fingering that creates jumbled words with letters misordered, some of which I have programmed to get corrected*** (as noted above), some not. Both kinds, however, stir up Mountain Lionʼs intrusive correction suggester (putting up a blue suggestion of what I presumably was supposed to mean to type below the active word onscreen), which although helpful once in a blue moon, usually serves merely to slow down the computerʼs response to the continuation of my typing (which I guess could be resolved, at least somewhat, if I watched the screen and not my fingers/keyboard — as if that will happen at this very late stage in my typing life). Thus, third, I should acknowledge that I myself have created many intrusions into the ordinary typing process, some (if nch) my help to slow down th computerʼs acceptance and display of my maladroit dgitsʼ dance across the excruciatingly tiny keys.****

So some of my curet problems must be ascribed simply to me. (That boldfaced bit of idiocy is an automatic correction, believe it or not, for current!)

I missed BehavioralInjector_64 using 83.3 percent of the RAM by less than a second before the screencapture camera clicked. Drat.

I missed BehavioralInjector_64 using 83.3 percent of the RAM by less than a second before the screencapture camera clicked. Drat.

On the other hand, and that other mitt is the thrust of todayʼs post, none of this was a problem before I “upgraded,” witlessly, moronically, to Appleʼs system 10.8.2, the savagely unready-to-be-released Mountain Lion. (I know I have moaned about this Windoze-like***** set of programming incompetence already, but… ) I have begun to discover that the problem seems to reside with the vast number of processes that think whatever unimportant background activity (like updating Spotlight or too-frequently backing up to Time Machine or whatever mds and mdworker, among too many other gnomically-named bits of coded nuisance, keep attempting to do behind my back, without my permission) is more important than the actual task at which I am genuinely at work (meaning that my typing or program-opening or whatever comes a distant third to whatever other disk-grinding busy-nesses are happening about which I do not care). And I am not the only one.

Some of the worst offenders are processes from programs I have installed (namely Syncoveryʼs totalitarian backup agent and Intego VirusBarrierʼs horrible BehavioralInjector — whether underscore32 or _64, the former being the more dictatorial and domineering). However, using Activity Monitor, I can quit those processes (usually — sometimes it takes ten or fifty quits to get BehavioralInjector to stay absent/inactive). Appleʼs own intrusions are not so user-friendly. Furthermore, that aforementioned spinning beachball has really gotten irritatingly omnipresent!

And that, my friends, is why I keep not getting much done. (Amusingly — and I intend that word literally, etymologophiles — these processes donʼt interfere with getting online. Much — see beachball reference above.)

Maybe now, with as few issues in the most recent paragraphs as there were, I can get back to work on important fiction (really).

* Really, Apple? You couldntʼ make a real keyboard that connects wirelessly? Really…

** The less being that whatever I noticed was wrong when I finished, I boldfaced. (And I wonʼt comment on what I may know were my own issues and what the fornication-worthless software/hardware permitted to be wrong.)

*** Another standard correction, which the computer currently finds nearly impossible to handle adequately is the transformation of straight apostrophes to curly typographerʼs apostrophes (and since I cannot get PopChar to function today — more computer trauma, I guess — I canʼt show a straight one). What happens is: all too often the apostrophe gets inserted after the final s in a possessive (I am coming to think because of the ridiculously slow and intrusive correction-suggester); several examples have occurred in todayʼs post.

**** That would translate as: “some (if not each) may help to slow down the computerʼs…” (Hmmm… you can tell that these footnotish interjections were created down here as I wrote because with these, too, the number of errors decreases with time. Interesting?)

***** Shall we enumerate every Microsoft Windows nonimprovement since XP (and most before)?

Did anyone get the punning initial acronym? Apple… ? (Itʼs not my life that I was addressing.)

©2013 John Randolph Burrow, Magickal Monkey Enterprises, Ltd, S.A.

Oh, Yeah, Sadly, Itʼs “Tech Frustration (5)”

…evidently also known as the “marble of doom”

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…

©2012 John Randolph Burrow, Magickal Monkey Enterprises, Ltd, S.A.

Tech Frustrations (3) — Apple Edition, part one

Having resurrected Janetʼs laptop (at least to an almost acceptable point, admittedly lacking virus protection), I proceeded almost immediately to screw everything up to an almost unbelievable degree by upgrading my iMac from Snow Leopard (MacOS 10.6.8) to the current Mountain Lion edition (MacOS 10.8.2 — with another improving update already available and suggested).

Big mistake. Huge, as a matter of fact.

My computer couldnʼt even restart the first time after the Apple App Store application had installed the new system. (And I had hesitated over the many complaints in the reviews section, wondering why Apple didnʼt think anyone needed an installation CD from which to restore the system when necessary, and it has been necessary — five times up to now, and thatʼs not shutting down daily as I had formerly done). And the installation took four hours (maybe a little more)!

I made my twenty-dollar mistake on Thursday evening, September 27, and I was frustrated and computer-deprived for the next three days, reinstalling the system all over again twice (and learning all about what the new installation had done, not to mention getting almost instantly sick of that tan cordillera/sierra felineʼs glare). The biggest flaw (for me at least) with Mountain Lion is that the software cannot restart from a hard shutdown/restart (meaning pushing the little  power/startup button on the rear left of the computer when everything suspends activity unalterably — freezes or hangs) or in my experience from an ordinary restart sequence (even the one Apple imposes with the installation — and upgrade — packages).

As I reported in my own review of the product once I had successfully gotten my iMac operational again (the following Sunday, then Monday):

Got really tired of seeing this visage on this screen in the past three-and-a-half weeks (five times, friends and comrades — so far)

Installed Mountain Lion (MacOS 10.8.2), foolhardily, Thursday afternoon (four days ago, as I write) — net result: couldnʼt get my iMac to fully restart afterwards… Constant, invariable hangs/freezes once the lovely new constellation desktop picture loaded.

Reinstalled said system, using the hidden Recovery partition this installation creates (and, buyers, do make sure you already know your Apple ID and Password [and LAN/Wi-Fi access code/password!!] without software assistance when installing this premature ejaculation of a product) on Friday evening after a whole night and day of forced restarts after start-up hangs, but no go on fully loading on restart, even after the four-hour download and installation. 

However, Saturday morning, inexplicably and without any changed approach on my part, when I tried another start-up, the system loaded and worked… until some programs wouldnʼt open and I decided to restart the computer… Naturally: hang city all over again…

No luck all day Sunday, either (even leaving the stalled start-up alone for hours and hours). The “consult the Apple Support Forums” option presented by the recovery partition merely takes you to standard info, no real help. Except perhaps for restoring from Time Machine and runnning Disk Utility (no problems of that kind in my case), none of the options works without internet connection (thus the need to have your LAN password ready before trying anything from the recovery partition).

Reinstalled for the third time this morning, Monday, and even before the promised three hours and 41 minutes (download and installation) had elapsed, we were up and running. Wowza.

Iʼm planning to leave my poor, abused machine continuously on for a long time today (tomorrow… into next year?) to let Spotlight index (if it actually is — estimate is back up to 20 hours, after ten hours on). And get three or twenty good Time Machine backups complete. Surviving so far without troubling Apple support by phone, although they were VERY helpful once in the distant past.

Anyone think I can afford to shut down (ever) without needing to reinstall yet again?

Hardware Overview:

  •   Model Name: iMac
  •   Model Identifier: iMac9,1
  •   Processor Name: Intel Core 2 Duo
  •   Processor Speed: 2.66 GHz
  •   Number of Processors: 1
  •   Total Number of Cores: 2
  •   L2 Cache: 6 MB
  •   Memory: 4 GB
  •   Bus Speed: 1.07 GHz
  •   Boot ROM Version: IM91.008D.B08
  •   SMC Version (system): 1.45f0

Not really recommended, based on my experience. I should have heeded all those earlier reviewers with problems!

Too harsh, thinkest thou, O Gentil Reader? Itʼs only gotten worse…

©2012 John Randolph Burrow, Magickal Monkey Enterprises, Ltd, S.A.