Re: Why does this help my Titan Memory?
 

I found some new information on MSDN:
http://msdn.microsoft.com/en-us/library/aa914334.aspx
It says that the "Dword:Cachesize" is obsolete for Windows Mobile 6.x and/or Windows CE 6.0.
Although it was having an affect on my memory management, I have now removed the values and now have this working well.

edit: It seems that the "EnableCache" entry just assumes that the cache is automatic when no "CacheSize" value is found. In other words, This is just not as helpful as I expected. Testing on these settings are done. Autosizing of the cache is not helpful in my experience.

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"FatCacheSize"=dword:2048
"DataCacheSize"=dword:8192
"EnableFatCacheWarm"=dword:1
"EnableWriteBack"=dword:1
"Flags"=dword:65606
"EnableDataCacheWarm"=dword:1
"EnableCache"=dword:1
"FriendlyName"="FAT FileSystem"
"Dll"="fatfsd.dll"
"Paging"=dword:00000001
"Util"="fatutil.dll"
"CacheDll"="diskcache.dll"

Plus my filter cache is down to 8196 and my glyph cache is down to 32K.
At this moment I have text messaging and IE open and I still have 20MB free. Enjoy!

Re: Why does this help my Titan Memory?
 

so does this mean we should reenable the cachesize key? or delete the enablecache key? kinda confused...

I will say that overall I dont notice a speed increase but I do notice my RAM holding out much better and that when I use Quickmenu or Oxios t reclaim ram I usually get most of it back. Third party apps usually recover all of it, MS apps usually keep a little.

Re: Why does this help my Titan Memory?
 

I would say re-enable the cache size.
I've moved on to the 20270 Kitchen w/ a 5MB PagePool and did not add all of the FATFS entries that I OP'd. Just the CacheSize(8096),DataCacheSize(2048),EnableCacheWar m(1), and EnableDataCacheWarm(1).
It is interesting to see that the builder(s) have added paging for a few of the StoreManager sections. I thought it would slow my Titan down but it seems to help.
Anyway, cheers to happy hacking.