<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Daniel Walker - Dr. Blip's PC-Doctor Blog</title>
    <link>http://www.pcdoctor-community.com/blog/</link>
    <description>A technical blog for technical people, among other things...</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3 - http://www.s9y.org/</generator>
    <pubDate>Thu, 03 Apr 2008 15:29:01 GMT</pubDate>

    <image>
        <url>http://www.pcdoctor-community.com/blog/templates/competition/img/s9y_banner_small.png</url>
        <title>RSS: Daniel Walker - Dr. Blip's PC-Doctor Blog - A technical blog for technical people, among other things...</title>
        <link>http://www.pcdoctor-community.com/blog/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Five Quick and Dirty Steps to PC Repair</title>
    <link>http://www.pcdoctor-community.com/blog/posts/2008/03/27/Five-Quick-and-Dirty-Steps-to-PC-Repair/</link>
            <category>Hardware</category>
    
    <comments>http://www.pcdoctor-community.com/blog/posts/2008/03/27/Five-Quick-and-Dirty-Steps-to-PC-Repair/#comments</comments>
    <wfw:comment>http://www.pcdoctor-community.com/blog/wfwcomment.php?cid=157</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.pcdoctor-community.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=157</wfw:commentRss>
    

    <author>nospam@example.com (Daniel Walker)</author>
    <content:encoded>
    &lt;br /&gt;
Five steps - that&#039;s all it takes to fix your customers&#039; PCs. As an active PC tech for the last few years, I was regularly asked how I troubleshoot problems. It was a single question with a thousand answers, and one I&#039;m sure most of you field every day.&lt;br /&gt;
&lt;br /&gt;
Narrowed down, here are my Top 5 Quick and Dirty PC Troubleshooting Steps:&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://www.pcdoctor-community.com/blog/posts/2008/03/27/Five-Quick-and-Dirty-Steps-to-PC-Repair/#extended&quot;&gt;Continue reading &quot;Five Quick and Dirty Steps to PC Repair&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 27 Mar 2008 15:35:00 -0400</pubDate>
    <guid isPermaLink="false">http://www.pcdoctor-community.com/blog/posts/2008/03/27/157/</guid>
    
</item>
<item>
    <title>Understand the Problem, Then Fix it</title>
    <link>http://www.pcdoctor-community.com/blog/posts/2008/02/06/Understand-the-Problem,-Then-Fix-it/</link>
            <category>Hardware</category>
    
    <comments>http://www.pcdoctor-community.com/blog/posts/2008/02/06/Understand-the-Problem,-Then-Fix-it/#comments</comments>
    <wfw:comment>http://www.pcdoctor-community.com/blog/wfwcomment.php?cid=136</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.pcdoctor-community.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=136</wfw:commentRss>
    

    <author>nospam@example.com (Daniel Walker)</author>
    <content:encoded>
    I&#039;m from the PC-Doctor QA lab. I won&#039;t mention the name of my former employer here, but I can say that I gathered considerable PC troubleshooting expertise while driving a distinctive black and white vehicle and that I was &lt;em&gt;not&lt;/em&gt; involved in law enforcement.&lt;br /&gt;
&lt;br /&gt;
The biggest challenge to successful troubleshooting is to make very sure that you understand as much as possible about problem. When and under what conditions does the problem occur? What environment causes the problem? Ideally, you will be able to reproduce the problem at will. If you can do that, it&#039;s a simple thing to fix it and then verify that it is fixed.&lt;br /&gt;
&lt;br /&gt;
However, we all get many problems that we can&#039;t reproduce. Sometimes when you are stumped, it&#039;s because the problem is just too simple. Try dumbing it down? looking at it from the simpler perspective of a non-technical user. For example: a customer was not getting any display on the monitor, even though the monitor and system were powered up. The tech checked the video card, changed modes and resolution, but finally found that the monitor was not plugged into the back of the computer. Sometimes the environment is the culprit, as in the classic case of a printer that began spewing paper every afternoon. After many on-site visits and replacement parts, a savvy tech finally discovered that the afternoon sun shined through the window at just the right angle to hit the paper sensor for a few minutes every afternoon.&lt;br /&gt;
&lt;br /&gt;
Tools can help you understand problems. Say, for example, that a client says, &quot;My computer is slow and sometimes I notice data missing.&quot; He could need more RAM (common problem!), or might have a hard drive problem, or it might be something else entirely. Problems like this can become expensive time sinks if you don&#039;t have a good diagnostic tool like &lt;a href=&quot;http://www.pc-doctor.com/pcd_service_center.php&quot;&gt;PC-Doctor Service Center&lt;/a&gt; to quickly confirm suspected hardware problems.&lt;br /&gt;
&lt;br /&gt;
Remember that you can&#039;t know everything. Cultivate every source of information you can find, including colleagues, books, and internet sites. You would be amazed at how often you can Google a problem and find a perfect description of how to reproduce it and/or how to fix it! 
    </content:encoded>

    <pubDate>Wed, 06 Feb 2008 16:04:40 -0500</pubDate>
    <guid isPermaLink="false">http://www.pcdoctor-community.com/blog/posts/2008/02/06/136/</guid>
    
</item>

</channel>
</rss>