Sunday, February 19, 2012
The post I wanted to write was going to be flowery verses about triumph and perserverance. It was going to show the several poor souls who visit here regularly-ish that the future is now, that flying cars are just around the corner. It was was going announce that the GameCube Portable was really, really, real and ready to amaze. There was going to be pictures and video.
But this is a different post. This one is about stumbling at the finish line, dropping the ball in the end-zone, kicking the puck into the net, forgetting to save your game - just name your cliched about disappointment.
We were so close, we were. A few days ago we had fitted all of the remaining GameCube components into the case. It was a tight fit to get the motherboard, batteries, and cooling fan into their best positions. We even had to do a bit of last-minute tinkering just to shorten up some wires before fastening them into their places.
Everything worked - the screen, speakers, disc drive, headphone jack, triggers, power management. Everything worked. The final step was to join the 2 halves of the case and screw them together. With each turn of each screw, we tested and tested again to make sure everything still worked. And with half the screws in place, something happened.
The Z-button started acting strange. There's a little-known Gamecube 'easter egg' that involves pressing the Z-button while the console is powering on. When you do this, the Gamecube will play audio that sounds like a squeaking monkey followed by the sounds of a rattle and a laughing baby. Unfortunately, we were getting ths easter egg without holding the Z-button. Furthermore, the Z-button failed to work when we tested gameplay.
Since everything had been working properly before assembling the case, we could only deduce that something had been broken in the process of squeezing the the components together. And so we retreated back to familiar terrain - testing, removing, and replacing bits-and-pieces of the Gamecube while trying to pin-point the problem.
We've checked the Z-button, itself, and found no issues. We've replaced the controller daughterboard with a spare and this has not fixed the issue, eiether. We're now in the process of replacing some wiring and, while it doesn't seem likely this is the culprit, anything is possible. The good news (I suppose) is that we are isolating the problem and we will get it fixed. And all of the fussy work we've done with triggers, the screen setup, and overall case construction will be unaffected. As well, the latest setback has shown up a few more safeguards we'll need to consider when we get back to assembling the case halves. The bad news, of course, is that we're, again, a few more hours away from 'done'.
Pray for us.
Tuesday, February 07, 2012
Now the only possible obstacle on my weekend runway was a minor physical ailment. I spent all day Friday with mild stomach pains - really, just sore muscles - that I attributed to an overzealous visit to the gym the night before. By dinnertime the pains had localized and (slightly) intensified in my lower right abdomen, but I was still under the impression that Age + Exercise = Soreness.
Remember this for it is a key point in the story.
Pains aside, my wife, my son, and I made a trip to local cineplex that evening to take in a showing of Tintin. The movie was quite a lot better than I expected and the theater was completely free of anyone chatting or texting during the movie. This good fortune was tempered by those stomach pains - now growing intense enough that concentrating on Tintin took some doing.
By the time we arrived back home that evening, I was pretty convinced that I was dealing with something more than sore stomach muscles. It was painful to simply walk and breathe. Finding a comfortable sitting position was proving elusive. My happy weekend was becoming compromised so, being a good geek, it was time to consult the Internet.
I'm pretty good at Internet research. When I need answers, I try to find as many different sources as I can, suss out the zeitgeist and, behold, there are my answers. So let me net this out: when the Internet considered my lower right abdominal pain along with a few secondary (imagined?) symptoms, it became all pretty clear that I had appendicitis. And when I say 'pretty clear' I actually mean 'fairly certain'. And, of course, I made sure I understood all of the surgical techniques and recovery details that I would need for the inevitable trip to the hospital.
I did not immediately share the Internet's diagnosis with my wife, offering her only the assurance that I had cramps and they would go away with a Tylenol-3 and a good night's sleep. While the pill took some of the edge off, I still laid sleepless in bed the entire night trying to find a comfortable position while mulling over the idea that someone would have to cut into my guts to remove the pain.
With that much time and worry to consider, the mind fixates. I began to imagine what the coming days had in store. I wondered how many needles I'd get (I hate needles). I wondered who would get to shave the incision area (likely the oldest, scariest nurse they could find). I wondered how many weeks I'd get to miss work while recuperating (2 to 3, says the Internet).
Saturday morning came. I was no better off and a lot more fatigued. The day was one long out-of-focus camp-out in front of the TV - alternating between restless catnaps and reality programming. I ate nothing and drank only water. My wife offered time and time again to take me to a clinic while I resisted (time and time again). I checked and re-checked my medical research. All signs continued to point to the appendix. The Internet was only too happy to determine how long I could stall before the risk of peritonitus was too high (42 to 78 hours from on-set, give or take).
As Saturday morning became afternoon and then evening, I sat in my chair and gave in to the notion that I would need to be cut open - and soon. There was no hiding from it. But the wimp in me decided it would wait until Sunday. I would get up and have my wife drive me somewhere - maybe straight to the hospital. I drifted off into another uneasy catnap while, outside, the skies debated how many grey clouds it needed to match my mood.
By dinnertime Saturday, things changed. A few hours of actual sleep had done something wonderful. I was rested and, miracle of miracles, my lower right abdomen was somewhat less painful! It wasn't the imaginings of a man avoiding the chance to be sliced apart by science. It was actual recovery! As evening turned into nighttime, my stomach ailments all but disappeared. I didn't wish to jinx my luck by saying the Internet had been wrong, but the thought, incomprehensibly, was there in the back of my mind.
Sunday morning brought almost a full recovery, albeit a tender one. I could only think of myself doing some kind of Ebenezer Scrooge panto: flinging open the window and shouting my miracles to first unlucky soul who came along. Since I'm not typically given to such displays, I could only give my wife reassurances and resolve that I would live each day as though it were my last. Starting with Sunday, it would be Me 2.0.
The Internet wasn't done with me yet. Me 2.0 had planned to spend quality time with my PC to do a bit of video editing. My PC, having other plans, decided to chew up a hard drive and swallow all of my in-progress video bits. Back to the Internet, I spent hours chasing rumours and lies about how I could rescue my videos and maybe triage my hard drive. Like phantom appendicitis, all I ended up with was too many lost hours and vague memories of happier times. And suddenly, the weekend, my happy weekend, was dead and gone - buried in scores of URLs and questionable advice from total strangers.
So the Internet is not my Doctor, nor is it yours. But we both know that next time we feel a twinge in our joints, the next time we need to know if a certain hotel is vermin free, the next time we need advice about the important decisions in our lives, the Internet will there waiting for us. And we'll be there, too.
Posted by Crazylegs at 3:24 PM