This week we ran into a real puzzler of a technical problem for my father-in-law, Ken. I had to enlist the help of not just the NosillaCastaways through our Facebook and Google Plus groups, but also the Mac Geek Gab community. In the end, it was Bart who cracked the code on the solution.
I thought it might be interesting to walk through the different diagnostic steps people suggested and then wait till the end of the story to tell you the solution. While you most likely will never run into the exact same problem Ken had, the diagnostic process is always valuable to discuss.
One of the most important concepts in the diagnostic process is to try to change one variable at a time, test the change, and document the result. Ok, with all of that setup let’s talk about Ken’s problem.