http://blogs.msdn.com/hopperx/archive/tags/Virtual+Memory/default.aspxTags: Virtual Memoryen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/hopperx/archive/2008/01/11/memorx-incorrectly-displaying-vm-overlap-in-wm6-1.aspxFri, 11 Jan 2008 03:07:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:7064430shende11http://blogs.msdn.com/hopperx/comments/7064430.aspxhttp://blogs.msdn.com/hopperx/commentrss.aspx?PostID=7064430Many 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...(<a href="http://blogs.msdn.com/hopperx/archive/2008/01/11/memorx-incorrectly-displaying-vm-overlap-in-wm6-1.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=7064430" width="1" height="1">Virtual MemoryKITLVMWM6hoppeRxmemoRxhttp://blogs.msdn.com/hopperx/archive/2007/07/02/saving-vm-by-using-oemdrivershigh-package.aspxTue, 03 Jul 2007 01:42:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:3665074wesbarc15http://blogs.msdn.com/hopperx/comments/3665074.aspxhttp://blogs.msdn.com/hopperx/commentrss.aspx?PostID=3665074The release of Windows Mobile 6 (WM6) gave us a few more tools for dealing with Virtual Memory (VM) issues. Compaction of slot 1 is new for WM6, in previous releases all slot 1 modules were aligned on 64k boundaries, causing VM address space to be wasted...(<a href="http://blogs.msdn.com/hopperx/archive/2007/07/02/saving-vm-by-using-oemdrivershigh-package.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=3665074" width="1" height="1">Virtual MemoryVM