<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Blog:: Craig Pringle - Troubleshooting</title>
    <link>http://www.pringle.net.nz/blog/</link>
    <description>A collection of my thoughts about TabletPCs, mobility and, well other stuff...</description>
    <image>
      <url>http://www.pringle.net.nz/blog/images/pringle.gif</url>
      <title>Blog:: Craig Pringle - Troubleshooting</title>
      <link>http://www.pringle.net.nz/blog/</link>
    </image>
    <language>en-us</language>
    <copyright>Craig Pringle</copyright>
    <lastBuildDate>Thu, 16 Apr 2009 10:29:42 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.0.7226.0</generator>
    <managingEditor>craig@pringle.net.nz</managingEditor>
    <webMaster>craig@pringle.net.nz</webMaster>
    <item>
      <trackback:ping>http://www.pringle.net.nz/blog/Trackback.aspx?guid=1946b842-7f1a-4f4d-9ad8-362076b9da34</trackback:ping>
      <pingback:server>http://www.pringle.net.nz/blog/pingback.aspx</pingback:server>
      <pingback:target>http://www.pringle.net.nz/blog/PermaLink,guid,1946b842-7f1a-4f4d-9ad8-362076b9da34.aspx</pingback:target>
      <dc:creator>Craig Pringle</dc:creator>
      <wfw:comment>http://www.pringle.net.nz/blog/CommentView,guid,1946b842-7f1a-4f4d-9ad8-362076b9da34.aspx</wfw:comment>
      <wfw:commentRss>http://www.pringle.net.nz/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=1946b842-7f1a-4f4d-9ad8-362076b9da34</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Previously I blogged about an issue I was having on one of my PCs with Live Mesh. 
The problem was that Moe.exe (the process behind Live Mesh) was <a href="http://www.pringle.net.nz/blog/PermaLink,guid,c0cea460-9352-4ac1-9331-7c23cb5de287.aspx">consuming
excessive CPU when ever it was running</a>.  This has obvious ill effects on
the battery life and overall system performance.
</p>
        <p>
I was hoping that the recent update to Live Mesh would of fixed it.  Unfortunately
this was not the case.  However since I was only experiencing this issue on one
of my machines I decided to see if I could find a fix.  I did.
</p>
        <p>
What I did was remove my problematic machine from my Mesh.  I then copied the
contents of the synchronised folder to another location on my hard drive (as a precaution)
and deleted everything in the target folder.  I then re-added my machine to my
Mesh and set up synchronisation for that folder again.  
</p>
        <p>
In the Before shot below the yellow line shows the percentage of the CPU that Moe.exe
was using.
</p>
        <p>
          <img src="http://www.pringle.net.nz/blog/ct.ashx?id=c0cea460-9352-4ac1-9331-7c23cb5de287&amp;url=http%3a%2f%2fwww.pringle.net.nz%2fblog%2fcontent%2fbinary%2fWindowsLiveWriter%2fWhyisLiveMeshkillingmyProcessor_13434%2fimage_2.png" />
        </p>
        <p>
After the fix it consistently looks more like this:
</p>
        <p>
          <a href="http://www.pringle.net.nz/blog/content/binary/WindowsLiveWriter/WorkaroundtostopLiveMesheatingyourCPU_12025/image_2.png">
            <img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://www.pringle.net.nz/blog/content/binary/WindowsLiveWriter/WorkaroundtostopLiveMesheatingyourCPU_12025/image_thumb.png" width="643" height="196" />
          </a>
        </p>
        <p>
        </p>
        <p>
A vast improvement and suddenly Live Mesh is useful to me again.
</p>
        <img width="0" height="0" src="http://www.pringle.net.nz/blog/aggbug.ashx?id=1946b842-7f1a-4f4d-9ad8-362076b9da34" />
      </body>
      <title>Work around to stop Live Mesh eating your CPU</title>
      <guid isPermaLink="false">http://www.pringle.net.nz/blog/PermaLink,guid,1946b842-7f1a-4f4d-9ad8-362076b9da34.aspx</guid>
      <link>http://www.pringle.net.nz/blog/PermaLink,guid,1946b842-7f1a-4f4d-9ad8-362076b9da34.aspx</link>
      <pubDate>Thu, 16 Apr 2009 10:29:42 GMT</pubDate>
      <description>&lt;p&gt;
Previously I blogged about an issue I was having on one of my PCs with Live Mesh.&amp;#160;
The problem was that Moe.exe (the process behind Live Mesh) was &lt;a href="http://www.pringle.net.nz/blog/PermaLink,guid,c0cea460-9352-4ac1-9331-7c23cb5de287.aspx"&gt;consuming
excessive CPU when ever it was running&lt;/a&gt;.&amp;#160; This has obvious ill effects on
the battery life and overall system performance.
&lt;/p&gt;
&lt;p&gt;
I was hoping that the recent update to Live Mesh would of fixed it.&amp;#160; Unfortunately
this was not the case.&amp;#160; However since I was only experiencing this issue on one
of my machines I decided to see if I could find a fix.&amp;#160; I did.
&lt;/p&gt;
&lt;p&gt;
What I did was remove my problematic machine from my Mesh.&amp;#160; I then copied the
contents of the synchronised folder to another location on my hard drive (as a precaution)
and deleted everything in the target folder.&amp;#160; I then re-added my machine to my
Mesh and set up synchronisation for that folder again.&amp;#160; 
&lt;/p&gt;
&lt;p&gt;
In the Before shot below the yellow line shows the percentage of the CPU that Moe.exe
was using.
&lt;/p&gt;
&lt;p&gt;
&lt;img src="http://www.pringle.net.nz/blog/ct.ashx?id=c0cea460-9352-4ac1-9331-7c23cb5de287&amp;amp;url=http%3a%2f%2fwww.pringle.net.nz%2fblog%2fcontent%2fbinary%2fWindowsLiveWriter%2fWhyisLiveMeshkillingmyProcessor_13434%2fimage_2.png" /&gt;
&lt;/p&gt;
&lt;p&gt;
After the fix it consistently looks more like this:
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.pringle.net.nz/blog/content/binary/WindowsLiveWriter/WorkaroundtostopLiveMesheatingyourCPU_12025/image_2.png"&gt;&lt;img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://www.pringle.net.nz/blog/content/binary/WindowsLiveWriter/WorkaroundtostopLiveMesheatingyourCPU_12025/image_thumb.png" width="643" height="196" /&gt;&lt;/a&gt; 
&lt;/p&gt;
&lt;p&gt;
&lt;/p&gt;
&lt;p&gt;
A vast improvement and suddenly Live Mesh is useful to me again.
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.pringle.net.nz/blog/aggbug.ashx?id=1946b842-7f1a-4f4d-9ad8-362076b9da34" /&gt;</description>
      <comments>http://www.pringle.net.nz/blog/CommentView,guid,1946b842-7f1a-4f4d-9ad8-362076b9da34.aspx</comments>
      <category>General</category>
      <category>Troubleshooting</category>
    </item>
    <item>
      <trackback:ping>http://www.pringle.net.nz/blog/Trackback.aspx?guid=11668756-4d03-485e-a256-b8af004247f1</trackback:ping>
      <pingback:server>http://www.pringle.net.nz/blog/pingback.aspx</pingback:server>
      <pingback:target>http://www.pringle.net.nz/blog/PermaLink,guid,11668756-4d03-485e-a256-b8af004247f1.aspx</pingback:target>
      <dc:creator>Craig Pringle</dc:creator>
      <wfw:comment>http://www.pringle.net.nz/blog/CommentView,guid,11668756-4d03-485e-a256-b8af004247f1.aspx</wfw:comment>
      <wfw:commentRss>http://www.pringle.net.nz/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=11668756-4d03-485e-a256-b8af004247f1</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
I have been living with the fact that SD Card reader on the LS800 does not work under
Vista since I installed Vista last year.  However I recently had a conversation
with a Motion Computing employee in which he indicated that he thought that issue
had been solved.
</p>
        <p>
Full of hope I rushed off to check <a href="http://www.motioncomputing.com/kb/article.aspx?id=10132">the
knowledge base article on the Motion site</a> that documented the issue to see if
it had been updated...
</p>
        <blockquote>
          <p>
There is no SD card reader driver available for Windows Vista on the LS800/LE1600
at the time of this writing (1/29/2007).  Motion is working to provide this driver
as soon as possible.  This knowledge base article will be updated at the time
of the driver update.
</p>
        </blockquote>
        <p>
Hmmm, still no joy.  However - while I was on the site I thought that I might
as well see if there were any driver updates available.  Why OEMs don't put an
RSS feed on their drivers page is beyond me.
</p>
        <p>
While poking around I realise that there have been two BIOS revisions released since
my version.  I'm was running A09 and A14 and A15 are on the site.  What
happened to A10-A13 I wonder?
</p>
        <p>
Nevermind.  I check the release notes for the two new BIOS releases.  Low
an behold the <a href="http://www.motioncomputing.com/drivers/LS800/LS800_BIOS_A14_RN.htm">Release
Notes for A14</a> state:
</p>
        <blockquote>
          <p>
            <b>What's New In This Release</b>
          </p>
          <p>
· Support for Intel 1.1GHz processor
</p>
          <p>
· Support for SD card reader in Vista
</p>
        </blockquote>
        <p>
I check the <a href="http://www.motioncomputing.com/drivers/LS800/LS800_BIOS_A15_RN.htm">release
notes for A15</a> as well, nothing major in that one except one fix.  However
BIOSes are cumulative, so A15 includes everything A14 had.  To avoid having to
do two upgrades I flash the BIOS with the A15 version.
</p>
        <p>
After a reboot I can see that the SDA Host Controller is listed in Device Manager
without the little yellow exclaimation point it had before!
</p>
        <p>
Full of anticipation I break out a SD card and slot it in.  **Poof**  Bluescreen
of death.  Interesting.  I reboot and try it again.  **Poof** again. 
Well at least the fault is repeatable...
</p>
        <p>
Time to break out the Windows Debugging Tools to analyse the crash dump.  Not
for the faint of heart.
</p>
        <p>
After repeating this a few times and analysing three dumps I see the debugger pointing
to three different drivers. None of which are the SD Card driver.  Given the
highly repeatable nature of the fault I think it is clear that it is related to the
SD Card Driver, so my guess is that the SD Card driver is corrupting bits of memory,
which causes an exception when some innocent driver wanders along and falls into the
whole.  Believe it or not - this is progress.
</p>
        <img width="0" height="0" src="http://www.pringle.net.nz/blog/aggbug.ashx?id=11668756-4d03-485e-a256-b8af004247f1" />
      </body>
      <title>Trying to get the SD Card Reader on the LS800 working with Vista</title>
      <guid isPermaLink="false">http://www.pringle.net.nz/blog/PermaLink,guid,11668756-4d03-485e-a256-b8af004247f1.aspx</guid>
      <link>http://www.pringle.net.nz/blog/PermaLink,guid,11668756-4d03-485e-a256-b8af004247f1.aspx</link>
      <pubDate>Wed, 23 Apr 2008 11:17:52 GMT</pubDate>
      <description>&lt;p&gt;
I have been living with the fact that SD Card reader on the LS800 does not work under
Vista since I installed Vista last year.&amp;#160; However I recently had a conversation
with a Motion Computing employee in which he indicated that he thought that issue
had been solved.
&lt;/p&gt;
&lt;p&gt;
Full of hope I rushed off to check &lt;a href="http://www.motioncomputing.com/kb/article.aspx?id=10132"&gt;the
knowledge base article on the Motion site&lt;/a&gt; that documented the issue to see if
it had been updated...
&lt;/p&gt;
&lt;blockquote&gt; 
&lt;p&gt;
There is no SD card reader driver available for Windows Vista on the LS800/LE1600
at the time of this writing (1/29/2007).&amp;#160; Motion is working to provide this driver
as soon as possible.&amp;#160; This knowledge base article will be updated at the time
of the driver update.
&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;
Hmmm, still no joy.&amp;#160; However - while I was on the site I thought that I might
as well see if there were any driver updates available.&amp;#160; Why OEMs don't put an
RSS feed on their drivers page is beyond me.
&lt;/p&gt;
&lt;p&gt;
While poking around I realise that there have been two BIOS revisions released since
my version.&amp;#160; I'm was running A09 and A14 and A15 are on the site.&amp;#160; What
happened to A10-A13 I wonder?
&lt;/p&gt;
&lt;p&gt;
Nevermind.&amp;#160; I check the release notes for the two new BIOS releases.&amp;#160; Low
an behold the &lt;a href="http://www.motioncomputing.com/drivers/LS800/LS800_BIOS_A14_RN.htm"&gt;Release
Notes for A14&lt;/a&gt; state:
&lt;/p&gt;
&lt;blockquote&gt; 
&lt;p&gt;
&lt;b&gt;What's New In This Release&lt;/b&gt;
&lt;/p&gt;
&lt;p&gt;
&amp;#183; Support for Intel 1.1GHz processor
&lt;/p&gt;
&lt;p&gt;
&amp;#183; Support for SD card reader in Vista
&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;
I check the &lt;a href="http://www.motioncomputing.com/drivers/LS800/LS800_BIOS_A15_RN.htm"&gt;release
notes for A15&lt;/a&gt; as well, nothing major in that one except one fix.&amp;#160; However
BIOSes are cumulative, so A15 includes everything A14 had.&amp;#160; To avoid having to
do two upgrades I flash the BIOS with the A15 version.
&lt;/p&gt;
&lt;p&gt;
After a reboot I can see that the SDA Host Controller is listed in Device Manager
without the little yellow exclaimation point it had before!
&lt;/p&gt;
&lt;p&gt;
Full of anticipation I break out a SD card and slot it in.&amp;#160; **Poof**&amp;#160; Bluescreen
of death.&amp;#160; Interesting.&amp;#160; I reboot and try it again.&amp;#160; **Poof** again.&amp;#160;
Well at least the fault is repeatable...
&lt;/p&gt;
&lt;p&gt;
Time to break out the Windows Debugging Tools to analyse the crash dump.&amp;#160; Not
for the faint of heart.
&lt;/p&gt;
&lt;p&gt;
After repeating this a few times and analysing three dumps I see the debugger pointing
to three different drivers. None of which are the SD Card driver.&amp;#160; Given the
highly repeatable nature of the fault I think it is clear that it is related to the
SD Card Driver, so my guess is that the SD Card driver is corrupting bits of memory,
which causes an exception when some innocent driver wanders along and falls into the
whole.&amp;#160; Believe it or not - this is progress.
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.pringle.net.nz/blog/aggbug.ashx?id=11668756-4d03-485e-a256-b8af004247f1" /&gt;</description>
      <comments>http://www.pringle.net.nz/blog/CommentView,guid,11668756-4d03-485e-a256-b8af004247f1.aspx</comments>
      <category>LS800</category>
      <category>Troubleshooting</category>
      <category>Vista</category>
    </item>
  </channel>
</rss>