The Trouble with Troubleshooting

I troubleshoot a Photoshop CS3/Mac OS X 10.6.3 problem.

Yesterday, after composing a blog post on my MacBook Pro, I went into my office with an SD card full of photos with every intention of choosing one or two to include in the post. I copied the photos to my hard disk along with my GPS track log and geotagged the ones I could tag. Then, after using QuickLook to make a preliminary selection, I opened five images with Photoshop CS3.

Or at least I tried to.

The problem was that Photoshop wouldn’t launch. It kept “unexpectedly quitting.”

And so began more than 2 hours of troubleshooting that culminated with my making an appointment today to visit the Arrowhead Apple Store down in Peoria, 50 miles from my home.

If you’re having this problem and are looking for a solution, read this post that I wrote this morning for Maria’s Guides.

This post is mostly about what a pain in the butt troubleshooting can be.

My troubleshooting process began with a Google search for Photoshop CS3 with Mac OS 10.6.3. I suspected the problem had to do with my update to 10.6.3 the previous week and I turned out to be right. There were discussions going on in the Apple forums about the problem. The most promising was titled “Installed 10.6.3 and now Photoshop CS3 won’t open.” The thread originator posted a quick description of the same problem I was having and got (so far) 167 responses.

Sadly, the responses were distributed over 12 individual pages, so I’d scan a page, click Next, and wait for the next page of responses to load before I could continue scanning. I don’t have a fast Internet connection in Wickenburg, so it was time consuming and tedious.

But it’s the content of the responses that I have a problem with. Only about 1/3 of them were of any use. The rest fell into one or more of the following categories, listed here with my comments.

  • Did you restart your computer? A person who can find and post a request for help in an Apple forum is likely smart enough to try restarting the computer before looking for outside help.
  • I’m using Photoshop CS3 with Mac OS 10.6.3 and I’m having that problem, too. Okay, what else can you tell us to help us troubleshoot?
  • I’m using Photoshop CS3 with Mac OS 10.6.3 and I’m not having that problem. So the rest of us are imagining it? Why not provide some info so we can learn how our systems differ from yours?
  • Did you try doing ABC? This comment might be helpful the first time ABC is suggested, but when it’s suggested a half dozen times and people have already reported that it doesn’t resolve the problem, it is a waste of time. Please read all the suggestions and the responses before adding your own.
  • It’s Apple’s fault. They don’t test updates. Don’t waste my time with this bull.
  • It’s Adobe’s fault. Their software sucks. Don’t waste my time with this bull, either.
  • It’s because you’re using a Mac. This problem doesn’t happen on Windows. What the hell are you doing on an Apple forum? Go play with Bing.
  • XYZ Program is better for photo editing than Photoshop. You expect me to toss a costly program I’ve been using for 15 years just because of a [likely minor] incompatibility issue? Get real.

It would be great if Apple’s forums had a way to vote down unhelpful comments so only the helpful ones appeared. I think we could have weeded out at least 100 of the comments that hid the solution. Or, better yet, offer some way to flag the comment that actually contains the “answer.” After all, the discussion thread was marked “answered,” so someone must have recognized one of the posts as a solution.

Adobe’s Web site had a TechNote that offered three possible solutions. One, which suggested turning off Rosetta, did not help me, since Rosetta was not enabled for Photoshop. I’m pretty certain the problem is related to an incorrectly entered serial number after having my logic board replaced two years ago. That’s what’s taking me and my 40 pound, 24″ iMac down to Peoria in two hours. Evidently, there’s no way for an end user to fix a serial number issue.

The net result of all this is that I lost two hours of my life to a troubleshooting exercise and will lose another three hours making a trip down to the Phoenix area to get a problem fixed on my Mac that was introduced by Apple.

Side benefit/drawback: I will get my hands on an iPad so I can give it a test drive. If they’re in stock, I’ll likely walk out of the store $500 poorer.

On Stiff Mixture Control Arms

The saga comes to an end…I hope.

If you follow the helicopter-related posts in this blog, you may know that I’ve been having a problem with my helicopter’s mixture control. My usual interface with this device is the red knob with a button on my instrument panel. Push the knob to get fuel flowing. Pull the knob to shut down the engine. Don’t mess with the knob in flight.

Simple enough, until it got stiff and then broke. I wrote about it here and here.

Mixture Control ArmTurns out, the reason the mixture cable became fractured is because the mixture control arm (lavender in this image) on the fuel control was too stiff. When I pushed or pulled the mixture control in the cockpit it was buckling and fraying. Pushing it in may not have resulted in full rich fuel, which could result in the engine running hot and lead to even more problems.

Good thing we caught it!

Fuel ControlEd, Wickenburg’s very best airplane mechanic, followed up by pulling the fuel control and fixing it, following instructions of the device’s manufacturer in Wichita, KS. Here’s what it looked like sitting on his workbench with the offending arm removed for repair. This is a lot more of my helicopter’s innards than I usually like to see. But it was interesting to see the piece I’d found an illustration of for this blog (see above) in a place where it was clearly recognizable.

Ed has since put everything back together. I was busy yesterday with the Endurance Ride, so I didn’t fly. And I don’t want to bother Ed on a Sunday. But come tomorrow morning, I’ll be at the airport with the helicopter out on the ramp. I’ll start it up and Ed will likely look at everything from below as its running to make sure the mixture is indeed full rich. I’ll pull the mixture and he’ll watch it work. And then he’ll sign off on it.

And give me a bill. (Ah, the joys of aircraft ownership!)

Of course, if things don’t go as planned, you’ll likely read more about it here.

No Flying this Weekend

It could be worse.

Robinson Mixture ControlThe other day, I reported a mechanical problem with my helicopter. In summary, the mixture control had been kind of stiff and it made a weird noise when I pulled it out. When my mechanic attempted to lubricate it, the mixture cable snapped.

The photo here shows a Robinson Raven II instrument panel very similar to mine. I’ve circled the mixture control. Remember: push in to allow fuel flow, pull out to stop fuel flow. Airplanes have similar controls. Airplane pilots adjust this in flight — that’s called leaning the engine. Helicopter pilots generally do not do this. It’s either in and the engine is running or out and the engine is stopped.

I didn’t make a big deal out of it then because it seemed to be a simple enough fix. We ordered the replacement cable from the factory and I figured that Ed, my local mechanic, would get that sucker installed not long after it arrived.

The more amazing thing to me — at least at the time — is that I’d proactively found and set about resolving a minor mechanical problem before it got me stranded somewhere inconvenient. The timing couldn’t have been better. The day before, I’d written an article for HeliNews about that exact topic. I was pleased that I’d learned a lesson.

Mixture Control SchematicWell, things are never as easy as they should be. Ed got the cable and went to work installing it. He soon ran into problems. The cable wouldn’t move smoothly. It wouldn’t go in all the way. He’s pretty sure we’ll have to order the entire cable assembly today. (This image, taken from Robinson SB-55, shows where the mixture cable attaches to the fuel mixture control. I highlighted the cable and its sheath in red. We ordered just the cable and it is apparently having trouble moving in the original sheath.)

Today is Friday. Although they could overnight the part for Saturday delivery, Ed doesn’t normally work on Saturdays. So I’ll save a few bucks on shipping and get it delivered Monday. With luck, it’ll be just what Ed needs and he can install it then.

Until it’s installed, there’s no flying for me.

But that doesn’t seem to matter much. I have no flights scheduled for this week and I have plenty of writing work to do. (I’m developing my third course for Lynda.com and have an open request for short how-to articles to fill for one of my publishers.) This weekend, I’m volunteering at the annual Land of the Sun Endurance Ride by marking horse butts with numbers, making my famous vegetarian bean soup, and timing in the 50-milers at the 25-mile manditory break. It’s almost a good thing that the helicopter is down for maintenance; less of a distraction for me.

I do want it running soon, though. Murphy’s Law of helicopter charter operations states that the most calls for your service will come in when you’re least able to meet customer needs. It must be a sign of the economy that my phone hasn’t started ringing off the hook yet.