Stance and Balance

This is the time of year, imbedded in Whistler, to do major maintenance of my computing environment.  And with my holiday gift to Tobae…four hours of computing support free of raised voice and any other bad behavior on my part…her computing environment as well.  As so here I sit with my MacBook Pro next to her slightly newer MacBook Pro.

Mine was bought in March, but it didn’t become my “production” computer until September.  Burned once by Migration Assistant, I pretty much build from scratch and it takes awhile.  Then a few weeks of carrying both with me.  Finally convinced that I didn’t have to go back and forth anymore, found a good home for the old computer after extracting its hard drive and putting a new one in for its next user.

And so it has gone for Tobae.  She has a very old MBP.  In November I visited brother Ken who works at the Apple Store in Bellevue Square and acquired a new one for her.  And it has been mostly sitting ever since, waiting for time to get all the things working that need to be working.

The day started poorly.  I’m not quite sure what happened when trying to apply one of those multiple operating system updates from the App Store, but was quite evident the computer was not planning to boot again unless I re-installed.  A ‘Command-R’ boot and two hours later (most of this was time downloading) and  was back to the out-of-the box state.  (This “Internet Recovery” feature is quite sweet!)  Smoothly sailing thereafter:  additional browsers (Firefox and Chrome), 1Password, iStat Menus, Quicksilver, Dropbox, configuring Mail.  A few tasks left…Microsoft Office, Google Earth, MacGPS Pro.  Not to forget to moving all existing data, but that is best left for last…one of the trickiest parts of a slow transition. Pretty linear.

And then there is VMware Fusion.  Easy to install the program itself…the harder work setting up virtual machines, and for Tobae this is Windows.  Windows is critical for Tobae in two ways.  She runs her practice on QuickBooks and (just like for Quicken) the Windows version is so very much better than the OS X one.  And the Providence Hospital electronic medical records system is Windows-based.  However there is nothing more challenging than Windows licensing as one changes hardware, for the ability to run the operating system requires an activation step intimately linking the product key (effectively the license) to the hardware.  Windows 7 seems the right place to be for at least another year or two.  I’ve been running it for about a year now.  With XP support going away in 2014, time to get Tobae off of XP.

One can spend considerable time trying to make sense of Windows licensing, especially in a virtual environment.  Bullet proof is buying the ~$270 retail version.  $270?  An alternative, and Microsoft doesn’t give very clear guidance, is the OEM version meant for new computers spanning computer manufacturers to DIYers.  Or what isn’t clear, building virtual ones.  At ~$140 pretty compelling.  But there is one (near) truth.  The OEM version anchors to one and only one motherboard forever.   So workable, but with risk.   I was concerned that we had only OEM licenses in our personal world at this point but finally established that the license Tobae holds is a retail version, so the upgrade version of Windows 7 (~$130) will work.   It is ordered.

Pretty easy to contrast this Microsoft licensing nonsense with the lack of nonsense from Apple for OS X.  Yes Apple hardware is more expensive.  Going from 10.X to 10.X+1 costs a little, nothing like ~$130.  Most impressive though is the model of trust.  Certainly there is a license from Apple to which one agrees.  But there are no certificates of authenticity, holograms, license keys, activation, branding chaos (e.g., Home, Pro, Ultimate).   Thank you Apple for knowing that “I am not a crook.”

Tobae fired up Excel today and Microsoft AutoUpdate told her of the recent service pack for Office for Mac 2011.  She asked whether she should download it and given our poor bandwidth and its size (110 MB), I said to do it at her office tomorrow.  So she clicked not now and then Excel crashed and Microsoft Error Reporter launched.  Yes send the report and re-open Excel and her file.  Excel crashed again and Microsoft Error Reported launched again.  And so on.

Had the data file been corrupted?  Attached her “Time Machine” disk and restored the most recent backup.  Excel crashed…  But in doing so it had changed the date modified on the file.  I didn’t want to start possibly corrupting every spreadsheet on her computer.  I’d make my own spreadsheet.  File -> New Workbook.  Excel crashed…

Time for some work with Google.  Search came up with many entries having to do with the Outlook killing version of SP2 known as 14.2.0.  But she was still 14.1.4.  Tightened up the search and was led to this article in the Microsoft Support Knowledge Base:  Microsoft Excel Has Encountered A Problem…  There are many similar articles in the knowledge base.   The titles never entertain the possibility that the problem not only was encountered but also created by Microsoft.  And they always involve doing lots of things that you don’t want to do.  An amusing part of the particular one is that it begins with Step 1, then Step 2, then Step 5, then Step 4, then Step 5.

The alternative was to download the now repaired service pack 14.2.1 and be optimistic.  The download took 90 minutes on our rural connection.   It consumed 2% of our monthly quota and will likely have us throttled for awhile.  It seemed to overwrite some of Tobae’s preferences, but the file opened and she was back in business.

My other bit of work on her computer this weekend was to update VMware Fusion to 4.1.2.  Just like when I had updated my own computer a couple of weeks ago, I got the message “The operation can’t be completed because you don’t have permission to modify VMware Fusion.   On my own machine, I have a true root account enabled.  I switched to it and got the update installed.  But I didn’t want to go that path on Tobae’s computer.  Should have used Google before for the solution presented on the VMware Knowledge Base was simple, though not quite intuitive:

We get many fewer unsolicited calls in Canada, but they are so much more interesting.  My recent favorites are from Thomas who called last week and then again today.

Thomas purports to be from the “International Security Department of Windows”.  He asserts that my “Windows computer” has been compromised by hackers and I am generating spam and that he will help me solve the problem.  Quite insistently.

English is not Thomas’s first language, so I was much too direct.  I said I did not have a Windows computer.  He said I did.  I said I didn’t and hung up.

Imagine my surprise at being called back today.  (Why continue to robo-dial people that listen briefly then just hang up?  I suppose that I didn’t hang up with enough vigor.)  Tonight I engaged more thoroughly, though it was brief.  Same initial pitch.  So I ask “Thomas, who do you work for?”  “Windows”  “Thomas, Windows isn’t a company.”  “I work for Windows.”  “Thomas, who makes Windows?” [silence]  “Thomas, what is my IP number?”  [silence]  Damn, Thomas hung up on me!

Beware of Thomas.  I think he is FoS.

Last night I heard a loud pop and was hit in the chest by the outer casing of a AA Duracell battery.  No bruise.  This a a first for me, but a quick Google search reveals it is reasonably common, at least for batteries installed in devices.  Mine was not, it was in a Ziploc bag sitting on the granite ledge that separates our dining area from the kitchen.  This picture sets the scene: the bag was sitting just to the left of the basket with fruit and avocados.

The battery was sitting in a Ziploc bag just to the left of the basket of fruit.

The remains:  The top of the bag is detached and covered with battery innards.  The outer casing hit me, just where the picture was taken from.  The base piece with the short wire and the inner packing were found in the hallway just under the pictures in the distance.  The plastic bag was still on the granite ledge.

The strength of the Ziploc seal compared to the bag itself is impressive

The debris field covers about a 4 ft x 4 ft area on the wall, with splatter on three of the picture frames and the wall itself.

Typical of the debris field. The largest spot is about 3/8 inch across.

I’m not sure what lesson this is suppose to teach me.  Hadn’t seen such in my 60 years, so probably won’t again.  I guess I am simply thankful that the battery was pointed such that I wasn’t the target of the debris.