<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Misdiagnosing a Computer Problem: How to Deal With It Without Losing The Client</title>
	<atom:link href="http://www.technibble.com/misdiagnosing-computer-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.technibble.com/misdiagnosing-computer-problem/</link>
	<description>A Resource for Computer Repair Technicians &#38; to get PC tech support help.</description>
	<lastBuildDate>Sat, 21 Nov 2009 09:20:45 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: swany971</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3300</link>
		<dc:creator>swany971</dc:creator>
		<pubDate>Mon, 04 Aug 2008 02:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3300</guid>
		<description>A very useful article Bryce. Thanks.</description>
		<content:encoded><![CDATA[<p>A very useful article Bryce. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TimeCode</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3195</link>
		<dc:creator>TimeCode</dc:creator>
		<pubDate>Wed, 30 Jul 2008 17:39:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3195</guid>
		<description>I think we&#039;ve all had times when we&#039;ve misdiagnosed something. I&#039;ve tried a few different tactics and I&#039;ve found that humility is the best thing. After I admit that I was incorrect, I fix the issue and move on. And a follow-up call is mandatory.

There have also been times where I have had “can’t determine the cause” cases but I HATE those. That is where I see people lose confidence. And why is it that if a mechanic tries to fix your car but fails, tries another part, fails and tries again, people accept that. But just one mistake with a computer and you&#039;re an idiot?

Because of these issues, I have purchased testing equipment. It is just easier to spend the cash and make it back than to lose clients and reputation.</description>
		<content:encoded><![CDATA[<p>I think we&#8217;ve all had times when we&#8217;ve misdiagnosed something. I&#8217;ve tried a few different tactics and I&#8217;ve found that humility is the best thing. After I admit that I was incorrect, I fix the issue and move on. And a follow-up call is mandatory.</p>
<p>There have also been times where I have had “can’t determine the cause” cases but I HATE those. That is where I see people lose confidence. And why is it that if a mechanic tries to fix your car but fails, tries another part, fails and tries again, people accept that. But just one mistake with a computer and you&#8217;re an idiot?</p>
<p>Because of these issues, I have purchased testing equipment. It is just easier to spend the cash and make it back than to lose clients and reputation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lonagcio</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3194</link>
		<dc:creator>lonagcio</dc:creator>
		<pubDate>Wed, 30 Jul 2008 13:25:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3194</guid>
		<description>After every job, I find that writing it down into a scenario style format helps me stay on my toes. I can always refer to it and use it for future reference. Just like the book says. Time consuming, but great.</description>
		<content:encoded><![CDATA[<p>After every job, I find that writing it down into a scenario style format helps me stay on my toes. I can always refer to it and use it for future reference. Just like the book says. Time consuming, but great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ZionFrost</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3193</link>
		<dc:creator>ZionFrost</dc:creator>
		<pubDate>Wed, 30 Jul 2008 05:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3193</guid>
		<description>Interesting article.  I&#039;m in my third year of business and I tend to make more &quot;can&#039;t determine cause&quot; than misdiagnosis.  When that happens, I normally explain the difficulty I&#039;m having, do my homework then return (hopefully) to repair the problem and don&#039;t charge for my first visit...I figure I&#039;m still on the learning curve and can&#039;t charge the customer for that.</description>
		<content:encoded><![CDATA[<p>Interesting article.  I&#8217;m in my third year of business and I tend to make more &#8220;can&#8217;t determine cause&#8221; than misdiagnosis.  When that happens, I normally explain the difficulty I&#8217;m having, do my homework then return (hopefully) to repair the problem and don&#8217;t charge for my first visit&#8230;I figure I&#8217;m still on the learning curve and can&#8217;t charge the customer for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryce W</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3191</link>
		<dc:creator>Bryce W</dc:creator>
		<pubDate>Wed, 30 Jul 2008 02:28:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3191</guid>
		<description>Its definitely easy to tell what you have done wrong looking back on it, but when you are doing it on the fly and thinking on your feet its a alot harder and easy to miss things. Im well aware what I should have done. Im sure nearly everyone here has made mistakes that they typically wouldnt make or have the knowlege of how to find/fix it but still managed to do it anyway.

On this website, Im not afraid to post my mistakes as I am not the perfect tech. Im successful, I make a nice amount of money but I too make mistakes, some of them being classed as &quot;rookie mistakes&quot;.

I think something that many people who want to start a business are afraid of is making mistakes and they need to learn that it happens, even to me.</description>
		<content:encoded><![CDATA[<p>Its definitely easy to tell what you have done wrong looking back on it, but when you are doing it on the fly and thinking on your feet its a alot harder and easy to miss things. Im well aware what I should have done. Im sure nearly everyone here has made mistakes that they typically wouldnt make or have the knowlege of how to find/fix it but still managed to do it anyway.</p>
<p>On this website, Im not afraid to post my mistakes as I am not the perfect tech. Im successful, I make a nice amount of money but I too make mistakes, some of them being classed as &#8220;rookie mistakes&#8221;.</p>
<p>I think something that many people who want to start a business are afraid of is making mistakes and they need to learn that it happens, even to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnR</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3190</link>
		<dc:creator>JohnR</dc:creator>
		<pubDate>Wed, 30 Jul 2008 01:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3190</guid>
		<description>Before I ever give a diagnosis of &quot;bad wiring&quot;, I run it through my cable tester.  It&#039;s a $30 piece of equipment and it&#039;s great for confirming problems.  With that and a crimping tool, I can make LANs dance and sing.

Better, you can tell *what wire* has the problem.  99% of the time, it&#039;s a simple break in the jack, and you can pull that apart with a screwdriver and fix it in three minutes flat.

But yeah.  CABLE TESTER.  It&#039;s a necessity if you&#039;re going to be checking anything beyond the output jack.</description>
		<content:encoded><![CDATA[<p>Before I ever give a diagnosis of &#8220;bad wiring&#8221;, I run it through my cable tester.  It&#8217;s a $30 piece of equipment and it&#8217;s great for confirming problems.  With that and a crimping tool, I can make LANs dance and sing.</p>
<p>Better, you can tell *what wire* has the problem.  99% of the time, it&#8217;s a simple break in the jack, and you can pull that apart with a screwdriver and fix it in three minutes flat.</p>
<p>But yeah.  CABLE TESTER.  It&#8217;s a necessity if you&#8217;re going to be checking anything beyond the output jack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Webkinz</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3189</link>
		<dc:creator>Webkinz</dc:creator>
		<pubDate>Wed, 30 Jul 2008 00:45:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3189</guid>
		<description>Going along with a sincere apology, I always find it goes over well with the client if you give them a follow up call in a week or so and see if things are still running smoothly and tell them if they have any other problems to not hesitate to call.  In other words, be as sincere as you possibly can.  It goes a long way.</description>
		<content:encoded><![CDATA[<p>Going along with a sincere apology, I always find it goes over well with the client if you give them a follow up call in a week or so and see if things are still running smoothly and tell them if they have any other problems to not hesitate to call.  In other words, be as sincere as you possibly can.  It goes a long way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3187</link>
		<dc:creator>Ali</dc:creator>
		<pubDate>Tue, 29 Jul 2008 17:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3187</guid>
		<description>worse is when you can&#039;t figure it out at all.
happens to me last Sunday, I got house call that they couldn&#039;t install fresh Xp on almost 2 years old brand name cpu.
after spending more than 7 hours and practically trying every possible solution and scenario, still looking at PC and wondering even after almost 10 years dealing whit this little stupid machine, it can make you look like dump!!</description>
		<content:encoded><![CDATA[<p>worse is when you can&#8217;t figure it out at all.<br />
happens to me last Sunday, I got house call that they couldn&#8217;t install fresh Xp on almost 2 years old brand name cpu.<br />
after spending more than 7 hours and practically trying every possible solution and scenario, still looking at PC and wondering even after almost 10 years dealing whit this little stupid machine, it can make you look like dump!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jm Boyd</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3186</link>
		<dc:creator>Jm Boyd</dc:creator>
		<pubDate>Tue, 29 Jul 2008 17:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3186</guid>
		<description>Better advice...Slow down, take your time, and triple check EVERYTHING before you make diagnosis. 

Misdiagnosis because you failed to properly connect a cable is kind of a rookie mistake.....and had someone else not check behind you, it could have been a costly one for your client.</description>
		<content:encoded><![CDATA[<p>Better advice&#8230;Slow down, take your time, and triple check EVERYTHING before you make diagnosis. </p>
<p>Misdiagnosis because you failed to properly connect a cable is kind of a rookie mistake&#8230;..and had someone else not check behind you, it could have been a costly one for your client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.technibble.com/misdiagnosing-computer-problem/comment-page-1/#comment-3185</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Tue, 29 Jul 2008 16:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.technibble.com/?p=1158#comment-3185</guid>
		<description>Misdiagnosing happens. Most people understand that computers combined with networks are some of the most complex systems devised by homo sapiens and that support technicians will not be right 100% of the time. If this stuff were easy the clients wouldn&#039;t call us!

I often compare what we do with the job of a veterinarian. We handle multiple species of technology—computers, A/V devices, networking devices, cables of all sorts, multiple operating systems, myriad software applications, and assorted other things. Our need for knowledge makes other professionals&#039; jobs seem simple by comparison. It is amazing that we get as much right was we do.

I recently had a client call that they couldn&#039;t get a CD out of the transport. I immediately started trying to diagnose the malfunction. It did not occur to me that he had not turned the computer on.</description>
		<content:encoded><![CDATA[<p>Misdiagnosing happens. Most people understand that computers combined with networks are some of the most complex systems devised by homo sapiens and that support technicians will not be right 100% of the time. If this stuff were easy the clients wouldn&#8217;t call us!</p>
<p>I often compare what we do with the job of a veterinarian. We handle multiple species of technology—computers, A/V devices, networking devices, cables of all sorts, multiple operating systems, myriad software applications, and assorted other things. Our need for knowledge makes other professionals&#8217; jobs seem simple by comparison. It is amazing that we get as much right was we do.</p>
<p>I recently had a client call that they couldn&#8217;t get a CD out of the transport. I immediately started trying to diagnose the malfunction. It did not occur to me that he had not turned the computer on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
