This Sunday

Sunday morning started with the usual Sunday morning white man with cat issues, which is replying to the demand, “Feed me, feed me, feed me, and get these other cats away from me,” in surround sound because I have three of them. They didn’t care that we’d fallen back an hour, clock-wise, here in ‘Merica. Their clocks weren’t affected.

Eventually, the beasts were fed, watered, and released back to the backyard wilds, freeing me to be me. I slid to the computer. That’s when the morning took an oomph turn. My mighty HP laptop wasn’t connecting to the net. Everything else in the household was connected; why was I selected for this cruel honor.

Something about the machine was off. Memories of being a younger person and working on my cars were awakened. I started car life with a 1965 Mercury Comet sedan. Forest green and automatic, a lively 289 V-8 was under the hood, as we said in those days. It was a stoutmobile. She’d run.

She was like my first girlfriend. I learned to do things, and did the standard stuff, from gapping and replacing plug and points (and all the wires) to brakes, muffler, and shocks, and all the fluids and fuses in between.

I think, because of that car, I’ve always since tried to fix things myself. Tried is a key verb in that sentence. (Is it a verb? I don’t know. I used to know these things.)

Details of what I did and the results will be avoided. No need to restore my stress levels by recalling those excoriating details. I worked on the computer for hours, returning it to connectivity. Doing so demanded a need to run recovery, a Microsoft Windows 10 process that’s not as nice as it sounds. Lots of personal files were removed (yeah, they said that wouldn’t happen, and they were wrong), along with apps and programs that I’d installed.

I had back ups of files, and MS does have some file recovery stuff. Eventually, though, I had almost everything. For some reason, I lacked the bible for the latest novel in progress. Don’t know what happened to that doc.

Reading old files slowed the process. Oh, there was The Soul Stone written years ago, never submitted nowhere. I read and enjoyed its first pages, along with Spider City, Everything Not Known, Everything in Black and White, and some stranger works, and the first draft of the self-published words, like the Lessons with Savanna series and Returnee. All still there, waiting for me to turn my attention back to them and do something more with them.

Not on this Sunday, though.

Frozen Apple

My wife owns an Apple. She owns several; only one currently functions. She loves her Macs, except for three things.

  1. The magnetic connection to the power supply. That thing is always falling out. She tapes it into place.
  2. The freaking battery. Can’t be replaced, you know. Once that dies, buy a new Mac.
  3. The computer freezes. When it does, only a hard reboot fixes it.

But she’s loyal to the brand. She always buys Apples.

Of course, she is a stockholder.

The Computer Painting Dream

It began like I was in one of my previous professions. At work, I received a phone call. A customer was having problems with his computer security. Well, those products ere being discontinued and his license keys had expired. Nonetheless, I cut new keys for him, directed him to a site to download them, and walked him through reinstallation. This is a process that would’ve taken some time but in dreamland, it was just a few minutes. Also, my dream office was much nicer and impressive than my real digs. It all seemed so sharp, it could’ve been real time.

The CEO came by. We chatted, and then drifted in opposite directions to new meetings. In my meeting, we were preparing to paint. Friends entered with the tablets. We stretched them out into large electronic canvases Then we painted on the screens. The tablets absorbed it, becoming a malleable medium. My painting was a large portrait of a blond woman in a yellow dress juggling tangerines.

Chinese food was brought in. We stopped to eat and talk about our work. A nearby young woman had been complaining about her finger. I told her to show me. She stuck out a blackened pinky.

“Your blood isn’t flowing,” I said. “Get me a needle and bowl.”

Holding onto her finger, I pricked her and squeezed her finger. Thick, black drops that behaved like mercury fell into the bowl. After doing that for about twenty seconds, her finger was normal.

End dream.

 

Crumbs

Crumbs populated his keyboard, slipping between the keys, forcing him to ponder, what did I eat and when did I eat it?

That made him hungry. He attempted to pick some crumbs up for closer examination, and perhaps to taste — just for investigative reasons, of course (that one looked like it may have come off a chocolate-chip cookie) (when did he eat a chocolate chip cookie?) -but the crumbs fled his efforts like kittens scattering at a noise, undermining his investigative process.

It did promote a greater appetite (if he trusted the messages that his stomach was issuing). Nothing healthy was offered for sale here, and he didn’t want to leave to eat somewhere else. Therefore, his logic forced him into a less healthy choice, which turned out to be a raspberry scone.

It was just a one-time deal, he told himself, so it would do no lasting harm.

He blamed it on the crumbs.

Floofware

Floofware (floofinition) – Major items of equipment or components intended for use by animals.

In use: “Although laptops and keyboards are not floofware, many pets like to believe otherwise.”

Spoiled

I know it’s another Princess and the Pea complaint, but don’t you hate it when the ‘net is so slow that you can click a link, go make a cuppa coffee, drink half of it, select new music, peruse the newspaper, and then return to the computer in time to see the page load?

These things always trigger corollary suspicions: is it just my provider, or this location, a flawed router or modem, a computer issue, DDoS attack or virus, the web site, the browser…?

Bah. Too damned spoiled, aren’t I?

A Bit in the System

I was reflecting on my Air Force command and control past today. 

We’d begun moving into the small computer age back in the early 1980s. The Air Force — and the Defense Department — were being cautious. Locally, we realized that much of the repetitive, manual entries we did on logs, messages, and grease boards, along with the phone calls used to relay information, could be done via computers. We began visualizing and flow-charting the entire process. Military Airlift Command (MAC), which had operational control over us, said, no. Don’t. Stop.

At my next assignment, with Tactical Air Command (TAC), a young major had begun computerizing the mission flows. He was manually doing it himself. Watching him, I began asking questions about why he wasn’t doing this and that, which led to me taking over what he was doing. He and I had a lot of fun working on that. Five years and two assignments later, I was in Europe with a small flying unit. They had begun using computers to do some of the stuff I’d wanted to do. As soon as I saw it, I maneuvered to get involved.

They were happy as hell to let me. Controlled by the J-4 and J-5 Directorates of JCS, with input and oversight from the National Reconnaissance Organization (NRO) and NSA, USAFE didn’t care what I did. Locally, several officers were being advised that small computers were the future and were starting to take computer programming classes, but most weren’t familiar with them, so the commander and DO told me, “Go for it.”

So I did. By the time that I left four years later, other offices in my unit had enlisted my help, as did other units on base, asking me to share all the stuff I’d done with my small computers to automate and correlate information. My trend to incorporate computers continued with my next assignments with Space Command.

This all came to mind via “60 Minutes” and Crucible last night. “60 Minutes” featured a segment on Artificial Intelligent (AI). Crucible, a James Rollins thriller that I’m reading, features Artificial General Intelligence (AGI) as part of the plot. I ended up thinking back to the MAC days and how and what robots could do. With scenes from WarGames flashing through my head, I visualized all those messages, reports, and phone calls associated with mission profiles, aircraft configurations and repairs, and mission execution, and how computers and robots could augment or replace humans.

It’s intriguing to think about. After a twenty years-plus career, I’ve been out of the military for over twenty years. They may have come to grips with many of the ideas I considered and the inherent obstacles.

Somehow, I doubt it. The military has always lagged behind for much of that, preferring to spend their annual funds to modernize weapon systems, if possible. You never know, though; those in charge have now grown up with computers as part of the digital age. My thinking would probably amuse them because they’ve gone so far past that. Oh, to be a bit in the system and overhear what’s going on.

Well, actually, I guess that’s what I was: a bit in the system.

The Micro-Code Dream

This is a recurring dream. I had it twice, maybe three times in the past few weeks. It’s also a sequel to another dream. The first dream was dreamed at least twice. Both dreams evolved in its depths and complexity, or my ability to remember them. As always,  I wonder how much I remember and how much I manage to fill in gaps through my imagination without being aware that I’m doing so.

In both, the backdrop is that I’m with IBM. The first dream has me being given a project. Not uncommon. I have a print out of several pages. Most of the back pages are lines of micro-code. The first page is an explanation that this list of hospitals need to be notified of these micro-code changes by a specific date. It’s a Friday afternoon. The date is the following Monday.  So, YIKES. The next four pages are lists of hospitals where this code needs to be applied, with identifying fields.

The first thing I do is get a yellow highlighter and a list of hospitals that are our customers. Then I go through the list, highlighting the hospitals that are our customers. I also make notes in black pen.

Follow-up is to create the letter to send these customers. I do this on a computer, merging the letter with the data fields from the hospital lists, import the letters into email, and send them out. Done and done. My boss checks on me. I confirm with her that it’s done. She’s surprised that it was done so quickly, and I show her what I did and how. Done and done.

The second dream has me at some team party. I work in a one-deep position, from home, so I know few people, but I’m on this campus with my team, who are usually just voices on the phone or names in emails. I’m wandering the party and encounter some product engineers. They heard that I took care of the hospital micro-code notification. They have questions. Essentially, they want reassured that it went okay.

First, I sit with a senior guy with the micro-code in a room full of computers on desks and in frames, with people working on things all around us. It’s very noisy with the sounds of fans, hard-drives, and conversations. He shows me the micro-code and begins to ask who and what questions.

Excusing myself, I go to my computer bag in the other room and get my working company, along with a print out of the letter that I sent, and another print out that shows who it went to and when. I give these to him and tell them what they are. He’s surprised and asks me why I gave them to him. I tell him, that’s what I would’ve wanted to know if I was following up.

Everything is quickly answered with these papers. Other of his team members come by to ask and see, and he tells them what I gave them, and they’re all relieved that it’s been done. Time to party.

But first, another team comes up to check on the project, too. The first team gives the second team my papers, tells them what I did, and everyone is satisfied.

As this ends, another engineer is talking loudly at a table. She’s talking about a modem’s identification and wondering who was dumb enough to use last names as part of a modem’s identification. As I turn, I hear another person say my full name, because that’s the name used as a modem identification.

I go over and tell them it was me and answer questions. Yes, it was ignorant, but I was ignorant about the process, working alone, and learning on the job. She said she can change it for me. I shrug that off, because we’re not using it anywhere except the lap now. It’s older and we use new stuff for production and operations, but the old stuff is helpful for trouble-shooting customer issues who are using old stuff.

That ends. Everyone is going off to the party in the next room. I begin a drift that way. Others find me and congratulate me for the work on the project. That amuses me because it seems like it was such a quick and easy project.

The main party is in a huge ballroom at the end of a hall. Music is blaring and people are dancing in there. That’s also where the restrooms are. I need to use one but can’t get to them because of the dancing crowd. I make a long detour around the crowd until I find a place where I can cut through, go in, use the bathroom, and come back out.

When I do, I’ve decided to look up some people while I’m there. I find several and huddle with them. Speaking loudly over the music, in a huddle with our arms intertwined over one another’s back, I tell them that I’ll be leaving soon, but I wanted to thank them and tell them how much I enjoyed working with them.

The dream ended.

A Little Interruption

I received an email from my wife that her computer had been hacked. It made her a little nervous.

She’d sent the email two hours before. (As an aside, she sent it on one of our other computers. How many do we have? Yes, too many.) I’d been busy writing and didn’t have my email open, so I didn’t see the email. When I saw it, I wrote, “Okay, I’m coming home.” I was almost done with writing like crazy for the day, although I’d wanted to walk to think more about the concept and plot.

Her computer is an Apple Mac. She hadn’t been hacked but was being scammed by a Mad Defender variant, a little surprising. It’s pretend ransom-ware. The Mac Defender scam is about blocking the user from changing tabs and pages in Safari while a warning that spyware has been detected is shown. It then tells you to call a number for Apple support.

From there, several things can happen. One, they can urge the gullible to share computer access. Two, they can be conned into buying a security program that’s not a security program but gives them access to your computer and its files and information. Or, most enticing for them, they get your credit card info and go to town.

It took me about seventy minutes to research her particulars and find and delete the malware app, along with the offending processes. As Mac Defender and the other names it goes by has been around since 2011, they’d changed details to make it more difficult to find and remove. I was surprised that they were using the MS Azurewebsites for this, as MS has been burned by this in the past. That was a big, immediate clue when I opened her computer and saw the message.

Anyone, it was a disruption to writing and posting blog thingies, along with walking and a few other things, but all’s well, and that’s the bottom line in all of this.

Back to our normal programming.

Blog at WordPress.com.

Up ↑