The writing day continued with little issue but the planned writing evening became disrupted by computer issues.
Chrome was suddenly sluggish. Shockwave plugins crashed. The usual culprits were investigated and found innocent.
Chrome worsened. The plugin crashes put Chrome into stasis. Firefox was called into action for comparision purposes; it turned out to be worse. Yet, memory and CPU was still available. The security side showed protection was up, yet the security side was very, very business. Logs showed nothing.
I shut everything down and re-booted. Same situation. Again....
Seventeen Windows updates, including office. Seriously? How many were optional? None.
Bah. This was a treadmill I thought I'd put behind me, but no. Computers have their own tides, and that returns us to their treadmills. I was surprised that so many updates were being downloaded until I realized, oh, super Tuesday.
Of course, how stupid of me. Super Tuesday is when Microsoft does it major update release. The release often causes issues with others. Many other softwares work with Microsoft to plan their updates around the super Tuesday releases. It's as certain as the wind about how effectively this works. Some companies don't have the resources to fully test the new releases, identify and fix problems. Sometimes Microsoft's releases don't seem to go as planned, with unexpected problems caused in different operating systems, security programs, and browsers. Getting Java updates synced seems to be a notorious problem. Some websites fail to load and run properly unless you go to a previous Java version.
Two hours later, though, the transparent and seamless background updates were downloaded and installed. Chrome was again functional, although it didn't seem happy. It's bug prone in the first place, and as a resource hog, it doesn't like playing nice with other apps.
Meanwhile, I noticed an intruder on my system. I've noted them before. Today I decided to take action and lock down my network.
It knocked she who uses an Apple off our network. I'd just gotten her back on it!
The question, then: why does locking down the network knock her off when she's been properly added and vetted? (Ah, there's that why that writers love. The same why haunts computers....)
But no problem, right? You'd think you could just unlock the network and allow her back in.
But no; computer life isn't that simple and straightforward. The same symptoms that manifested itself the last time I had problems with her MacBook Pro joining our secure Linksys network manifested itself. Once again I hit the labyrinth of forums, seeking solutions. I checked keys, keychains, permissions, time out settings, updates, ran verify disk on her MBP, ran verify permissions and repair permissions, rebooted the network several times, added and deleted the network from her Apple, and so on...for two hours.
Null value returned.
I called it a day at midnight. I tried putting her back onto our network this morning. No go. I returned her to a hardwired state and turned off her Airport.
As I say, the writing evening went awry, enticed by why when the computer started acting contrary to expectations. I thought all of that would entail a few minutes, thirty minutes at most, but in the end, five hours were gone.
Yet, I'd done writing earlier. I was riding waves from it, from looking at this Ashland and envisioning it some several hundred years in the future, after cars are no longer employed. What does the valley look like? What happens to the roads? How much actions does humanity take to remove roads? Well, doing that costs money...but eventually nature takes over. By the time my mission has returned to Earth, the first humans back, most of the old structures are buried. Of course, there were questions to ask and answer, mostly why, as Mary Wilkinson shared with us.
Asking it as a fiction writer is far more fun than asking it as a computer repair tech.
Causes Michael Seidel Supports
Kiva, Women's International League for Peace and Freedom, Propublica.org, Doctors Without Borders, GreaterGood.com