<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" 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/"><channel><title>HoppeRx - the cure for your ailing device</title><link>http://blogs.msdn.com/hopperx/default.aspx</link><description>A community site dedicated to the support of device problems found by Hopper</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Big Iron</title><link>http://blogs.msdn.com/hopperx/archive/2009/04/24/big-iron.aspx</link><pubDate>Fri, 24 Apr 2009 16:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9566921</guid><dc:creator>shende</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/9566921.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=9566921</wfw:commentRss><description>The ability to try out bug fixes is a valuable part of the Hopper process and re-building images quickly is one of the easiest ways to improve your Hopper numbers. We recently went about trying to find the combination of build server parts that makes...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2009/04/24/big-iron.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9566921" width="1" height="1"&gt;</description></item><item><title>Troubleshooting guide - part 2</title><link>http://blogs.msdn.com/hopperx/archive/2009/04/21/troubleshooting-guide-part-2.aspx</link><pubDate>Tue, 21 Apr 2009 14:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9559271</guid><dc:creator>shende</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/9559271.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=9559271</wfw:commentRss><description>Below is the second half of a well executed document from guestRx: Bulent Elmaci. Bulent has worked with Windows Mobile debugging for a long time and backs up his writing with a lot of experience. It is the first of a series of articles he has written...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2009/04/21/troubleshooting-guide-part-2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9559271" width="1" height="1"&gt;</description></item><item><title>Troubleshooting guide - part 1</title><link>http://blogs.msdn.com/hopperx/archive/2009/03/05/troubleshooting-guide-part-1.aspx</link><pubDate>Thu, 05 Mar 2009 14:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9459895</guid><dc:creator>shende</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/9459895.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=9459895</wfw:commentRss><description>Below is a well executed document from guestRx: Bulent Elmaci. Bulent has worked with Windows Mobile debugging for a long time and backs up his writing with a lot of experience. It is the first of a series of articles he has written to help our OEM's...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2009/03/05/troubleshooting-guide-part-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9459895" width="1" height="1"&gt;</description></item><item><title>A Windows CE 6.0 Book that I keep paging back to...</title><link>http://blogs.msdn.com/hopperx/archive/2008/12/19/a-windows-ce-6-0-book-that-i-keep-paging-back-to.aspx</link><pubDate>Fri, 19 Dec 2008 14:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9242169</guid><dc:creator>shende</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/9242169.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=9242169</wfw:commentRss><description>I am not much of a programming book person, I am much more likely to select code and press "F1". However, I find myself reaching for a CE 6.0 book and have been finding it quite useful. "Windows Embedded CE 6.0 Fundamentals" [Pavlov, Belevsky][ISBN 0735626251...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2008/12/19/a-windows-ce-6-0-book-that-i-keep-paging-back-to.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9242169" width="1" height="1"&gt;</description></item><item><title>Writeable code sections got you down? Fear no more!</title><link>http://blogs.msdn.com/hopperx/archive/2008/09/19/writeable-code-sections-got-you-down-fear-no-more.aspx</link><pubDate>Fri, 19 Sep 2008 17:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8959183</guid><dc:creator>shende</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/8959183.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=8959183</wfw:commentRss><description>Virtual Memory changes included in Windows Mobile 6.1 can relocate read- only code sections out of Slot 0 and into a higher address range. This change was taken to relieve pressure from our coveted, read- write Slot 0. This change will be transparent...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2008/09/19/writeable-code-sections-got-you-down-fear-no-more.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8959183" width="1" height="1"&gt;</description></item><item><title>Hopper: Start Menu Dead!</title><link>http://blogs.msdn.com/hopperx/archive/2008/03/08/hopper-start-menu-dead.aspx</link><pubDate>Sat, 08 Mar 2008 00:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8107873</guid><dc:creator>shende</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/8107873.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=8107873</wfw:commentRss><description>Interesting post over at "Reed &amp;amp; Steve" regarding Hopper and full screen apps and the Start Menu Dead message. Check it out here . Kudos to them for making this available....(&lt;a href="http://blogs.msdn.com/hopperx/archive/2008/03/08/hopper-start-menu-dead.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8107873" width="1" height="1"&gt;</description></item><item><title>Use CallWindowProc when using WNDPROC pointers directly</title><link>http://blogs.msdn.com/hopperx/archive/2008/02/07/use-callwindowproc-when-using-wndproc-pointers-directly.aspx</link><pubDate>Thu, 07 Feb 2008 17:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7521064</guid><dc:creator>shende</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/7521064.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=7521064</wfw:commentRss><description>A recurring theme I see while debugging application compatibility issues has to do with the direct use of the window proc pointer. If the intended WNDPROC exists in a DLL that is located in Slot 0, the pointer “looks right” and is often mistakenly used...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2008/02/07/use-callwindowproc-when-using-wndproc-pointers-directly.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7521064" width="1" height="1"&gt;</description></item><item><title>Are you passionate about Windows Mobile Devices?</title><link>http://blogs.msdn.com/hopperx/archive/2008/01/18/you-passionate-about-windows-mobile-devices.aspx</link><pubDate>Fri, 18 Jan 2008 22:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7153842</guid><dc:creator>shende</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/7153842.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=7153842</wfw:commentRss><description>Do you want to work on next generation Windows Mobile devices long before they become commercially available? Want to be the first one to work with and influence next year’s Windows Mobile devices? Then you’re in luck! The Windows Mobile team is looking...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2008/01/18/you-passionate-about-windows-mobile-devices.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7153842" width="1" height="1"&gt;</description></item><item><title>MemoRx incorrectly displaying VM overlap in pre-release Windows Mobile versions</title><link>http://blogs.msdn.com/hopperx/archive/2008/01/11/memorx-incorrectly-displaying-vm-overlap-in-wm6-1.aspx</link><pubDate>Fri, 11 Jan 2008 00:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7064430</guid><dc:creator>shende</dc:creator><slash:comments>11</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/7064430.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=7064430</wfw:commentRss><description>Many OEM’s have already noticed that Memory Doctor doesn’t correctly represent VM overlap in some pre-release versions of Windows Mobile. There have been some changes in WM VM architecture that contradict an assumption made by MemoRx which results in...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2008/01/11/memorx-incorrectly-displaying-vm-overlap-in-wm6-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7064430" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hopperx/archive/tags/Virtual+Memory/default.aspx">Virtual Memory</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/KITL/default.aspx">KITL</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/VM/default.aspx">VM</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/WM6/default.aspx">WM6</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/hoppeRx/default.aspx">hoppeRx</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/memoRx/default.aspx">memoRx</category></item><item><title>Understanding Output From “meminfo kernel”</title><link>http://blogs.msdn.com/hopperx/archive/2007/11/15/understanding-output-from-meminfo-kernel.aspx</link><pubDate>Thu, 15 Nov 2007 23:52:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6280110</guid><dc:creator>JeCahill</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/6280110.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=6280110</wfw:commentRss><description>I was debugging a weird hang at device boot and I used the command “meminfo kernel” in CeDebugX to get more info, but I realized right away that I didn’t know what this command was showing me. So, I did a bit of investigation into what the output meant...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2007/11/15/understanding-output-from-meminfo-kernel.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=6280110" width="1" height="1"&gt;</description><enclosure url="http://blogs.msdn.com/hopperx/attachment/6280110.ashx" length="41129" type="image/jpeg" /><category domain="http://blogs.msdn.com/hopperx/archive/tags/Platform+Builder/default.aspx">Platform Builder</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/training/default.aspx">training</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/meminfo/default.aspx">meminfo</category></item><item><title>Passive KITL to the rescue</title><link>http://blogs.msdn.com/hopperx/archive/2007/11/02/passive-kitl-to-the-rescue.aspx</link><pubDate>Fri, 02 Nov 2007 15:59:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5838922</guid><dc:creator>deanmel</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/5838922.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=5838922</wfw:commentRss><description>I'm sure many of you have been in a situation where your device hangs during field testing. Or sometimes you are trying to track down a problem which only repros at a certain location. The best thing you can have in these situations is, of course, a live...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2007/11/02/passive-kitl-to-the-rescue.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5838922" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hopperx/archive/tags/KITL/default.aspx">KITL</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/DeanMel/default.aspx">DeanMel</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/WM6/default.aspx">WM6</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/jetstream/default.aspx">jetstream</category></item><item><title>Running Platform Builder 6 on Vista</title><link>http://blogs.msdn.com/hopperx/archive/2007/10/25/running-platform-builder-6-on-vista.aspx</link><pubDate>Thu, 25 Oct 2007 17:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5674024</guid><dc:creator>deanmel</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/5674024.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=5674024</wfw:commentRss><description>There are a lot of people that afraid to switch of Vista because they are afraid that their stuff will not work. Well truth be told, I've been running Vista+VS2005_SP1+PB6 since March of this year and haven't had any major problems. The only two problems...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2007/10/25/running-platform-builder-6-on-vista.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5674024" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hopperx/archive/tags/DeanMel/default.aspx">DeanMel</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/WM6/default.aspx">WM6</category></item><item><title>Improving the Cat Parade (Part 3)</title><link>http://blogs.msdn.com/hopperx/archive/2007/10/05/improving-the-cat-parade-part-3.aspx</link><pubDate>Fri, 05 Oct 2007 18:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5299833</guid><dc:creator>JeCahill</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/5299833.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=5299833</wfw:commentRss><description>I was recently running hopper on a device that supported screen rotation and I realized that my test coverage was completely missing the rotation scenario. The device would switch between portrait and landscape mode if the user took a specific action,...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2007/10/05/improving-the-cat-parade-part-3.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5299833" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hopperx/archive/tags/hopper/default.aspx">hopper</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/cat+parade/default.aspx">cat parade</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/ISV/default.aspx">ISV</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/focusApp/default.aspx">focusApp</category></item><item><title>Where did Callstacks go from the Hopper logs?</title><link>http://blogs.msdn.com/hopperx/archive/2007/10/04/where-did-callstacks-go-from-the-hopper-logs.aspx</link><pubDate>Thu, 04 Oct 2007 20:03:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5278282</guid><dc:creator>deanmel</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/5278282.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=5278282</wfw:commentRss><description>If you upgraded from an older version of Hopper to a more recent one, you probably noticed that the callstacks are gone from the Hopper logs. We made them optional for two reasons: 1. Printing out callstacks slowed down the run significantly 2. They did...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2007/10/04/where-did-callstacks-go-from-the-hopper-logs.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5278282" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hopperx/archive/tags/DeanMel/default.aspx">DeanMel</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/WM6/default.aspx">WM6</category></item><item><title>Why my private binaries do not show up in the image?</title><link>http://blogs.msdn.com/hopperx/archive/2007/09/28/why-my-private-binaries-do-not-show-up-in-the-image.aspx</link><pubDate>Fri, 28 Sep 2007 18:34:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5191132</guid><dc:creator>deanmel</dc:creator><slash:comments>4</slash:comments><comments>http://blogs.msdn.com/hopperx/comments/5191132.aspx</comments><wfw:commentRss>http://blogs.msdn.com/hopperx/commentrss.aspx?PostID=5191132</wfw:commentRss><description>Why my private binaries do not show up in the image? I've been asked this question too many times by now. Many partners when testing their private changes have to figure it out the hard way. The reason why your updated binary doesn't show up in the image...(&lt;a href="http://blogs.msdn.com/hopperx/archive/2007/09/28/why-my-private-binaries-do-not-show-up-in-the-image.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5191132" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/hopperx/archive/tags/DeanMel/default.aspx">DeanMel</category><category domain="http://blogs.msdn.com/hopperx/archive/tags/WM6/default.aspx">WM6</category></item></channel></rss>