If It Isn't Broken...

It is sad when the *second* worst thing that happened last night was Ruby getting skunked again.

I had plans to do a lot of recording this weekend. Now, whenever I need to do some recording, I usually wander down to the studio and discover that it is time to install a whole bunch of updates. It was pushing 9 PM, so I figured I could quickly run down to the studio, install the updates, and hit the ground running today.

I already knew that there was a Cubase point release that I should go ahead and install, so I did that. Then I noticed that there were three Intel updates waiting to be installed. Ok, I could take care of that too. No problem. A couple of reboots, but no problem.

The Intel update screen lists (among other things) my motherboard type and the current BIOS version. I looked at that and said to myself, "That BIOS is pretty old. I wonder if there is a newer one that I should install." This was my first mistake.

On the ASUS website, there was a brand-new BIOS for my motherboard, less than a month old. Looked good, so I figured I'd install it. This requires putting it on a memory stick, booting into the BIOS, and then loading it from there. I've done this sort of operation before, so I didn't have too much trouble with it. There was also a newer version of the Intel ME utility, so I installed that too. All good.

Having installed a new version of Cubase, I figured I'd fire it up so that it could inspect all of the plugins, because that sometimes can slow things down on the first restart. Still no problem.

Well, there was no problem until Cubase told me that I needed to pick an ASIO driver. It should just default to the Universal Audio Thunderbolt driver. Except I picked that and Cubase said "What Thunderbolt device?"

Oh, that is bad. Let me start up the UA application and see if it sees the Apollo unit. It does not. And the Thunderbolt cable is plugged in. Ack!

I start searching the Internet. Apparently, this is a problem with older versions of the ASUS Thunderbolt add-in card when the BIOS for this type of motherboard (and its various relations) gets updated. I check the Device Manager and it tells me that there is a problem with the Thunderbolt port. Yes, I had figured that out. Removing the device and putting it back does not help.

Maybe there is a newer driver or firmware for the Thunderbolt card. There's no new driver, but there is new firmware. I set up to flash the card with the new firmware and discover that it won't take it.

Apparently, there are *two* slightly different versions of this card. I have the older one, which will not take this update. There does not appear to be an update for the older card.

Maybe I can get a newer version of the Thunderbolt card. Micro Center does not carry this card. Amazon does. They can get it to me around July 1st, which is not compatible with recording this weekend. Or next weekend.

Ok. How can I get up and running? I *do* have a laptop with Cubase installed *and* a Thunderbolt port, but that is the same port that it uses for charging. About now, I realize that I could probably bodge things together with a Thunderbolt dock, but it was approaching midnight last night and I was running out of brain cells.

The latest generation of PC motherboards has a number of boards that support Thunderbolt directly on the back panel ports. My new office PC is one of those. I am not going to move my freshly-configured office PC to the basement for this. Really not.

I could *buy* a new motherboard. Which will require buying a new processor and new RAM. And a new heatsink. That is going to be annoyingly expensive and a whole lot of work, but is an available backup plan.

Let's try reverting to an older version of the motherboard BIOS. What version had I started with? Eventually, I realized that I still had it on the computer in installable format, so I copied it to the memory stick, rebooted, and installed the older BIOS. So far, so good. Let's boot up the computer.

The computer does not boot up. It beeps eight times. My phone tells me that this is a sign of a problem with the CMOS memory on the computer.

I am old. I know what to do about this. I shut off the power to the computer, pull the plug, and pull the CMOS battery. If I wait until morning, the computer will forget all of the BIOS settings and I should be able to get back into the machine. (Later, I check the manual and find the location of the two pins that I need to short to clear the CMOS. They are inconveniently buried behind the Thunderbolt card. I try fishing at them in the morning with a screwdriver, because why not? I'm not sure if I ever got to them...)

It is now nearing midnight and time to head up to bed.

At some point during this fiasco, Julie comes downstairs to tell me that Ruby has encountered a skunk, so if I smell something when I go upstairs, don't panic. It is apparently less bad than some of the previous skunkings. Gretchen has rubbed the dog down with some odor killer called "Pooph" and the report is that it has improved the situation. Gretchen, meanwhile, has gone off to the bedroom, having had enough of all of this for the night.

When I get upstairs, things are not *too* stinky, so I turn off the kitchen exhaust fan and head upstairs to join Gretchen. It is a *long* time before I can manage to get to sleep (which includes watching another episode of "Leverage" so that we can both wind down).

This morning, I get up, get cleaned up, and head down to the basement. I fish around for the clear CMOS pins, decide that I am not going to remove the Thunderbolt card to try to get at them right now, and put the battery back in. Then I fire up the computer.

Happily, after a mild round of complaints, it boots into the BIOS. I turn the Thunderbolt support back on and reboot. Windows fires up, I start the UA application and it informs me that there is no Apollo unit attached.

Then I plug the Thunderbolt cable back in. And now I have a connection! And there is much rejoicing.

And then I fire up Cubase and it tells me that there is no device connected. So I fire up the UA Console app, see the message "Connecting to Apollo", and now Cubase can see the device and lets me select the Thunderbolt ASIO driver. I open up a song, hit play, and there is sound from the speakers.

My mood is *greatly* improved.

So, kids, this is why you just shouldn't mess with a system that is working. Just ask old Uncle Bill.

In other news, the house still smells mildly of skunk downstairs and we are trying to air it out. Ruby does not seem to be very skunky, for which I am thankful.

At least I didn't have to run out and buy peroxide last night.