Troubleshooting
Sometimes, things just go wrong. Hard drives die. Floppy drives spin but don't read. Or, most commonly, something just doesn't work right in Windows.  Maybe you're experienced at troubleshooting software problems, device conflicts, and COM port battles -- and maybe you're not -- but either way, you've tried everything and can't get it to work. Doing so is often like my Apollo 13 analogy.

Troubleshooting is my specialty! If something isn't working, let me figure out how to make it work -- or why it won't.  If it isn't your specialty, don't risk making it worse!  Check out my theory on computer skills.

Repair
Is it broken? Is it not working? Did it use to hum and now it screeches? Is something not getting power that needs to get power in order to work? Let me at it.

Debugging
Sometimes is just takes a little tweaking to make things work right. Sometimes Program A might not work hand-in-hand with Program B. It's all a matter of finding out what works which way and how. Refer once again to the Apollo 13 analogy.

Estimated Troubleshooting Time - Click here for fees
Different problems command different procedures. I tackle any troubleshoot by deciding what the most probable causes and their solutions are, and work down to the least probable from there. Still, it's unlikely that even the toughest problem will not be solved, or at least figured out, in more than two hours -- and most are an hour.

 

Home | About David M. Fitzpatrick | Services Available | Past Clients | Contact | Features & Articles

 

Site Copyright © 1998-2005 by David M. Fitzpatrick (indy@fitz42-QQQ.net)
Remove the "-QQQ" part before you send your email! Click here to learn why.