Quote:
Originally Posted by jucytec
Ok, I reflashed last night using 21015 SYS with 21018 XIP by Former and cooked it with SSK Kitchen C2. I had to set PP to 9.5 megs rather than 6-8 (which is what I normally use). It was locking up on me at < 9 Megs... but since I've changed the PP to 9.5 Meg the ROM has been solid. I did lose the 1 Meg worth of free RAM but I'm going to tone down the file system cache down to 1MB from 2MB to gain the lost memory.
So far i had no issues, stable, I've got a lot of stuff running, and they all seem to play nicely.
I also installed TouchResponse for heptic feed back on screen touch, and it's working very nicely.. Also seem to have pretty good battery life... I'm down 10% since 7, and I've been Bluetooth Tethering...
I know the GPS works because i've done this combo before... but I'll try again during lunch... Keep ya'll posted.  |
I'm running 10MB and it seems good. BTW - don't bother messing with the filesystem cache sizes. Changes there only affect the SD Card - the cache sizes for the on-board flash are set in the XIP and can only be changed there. In other words, if you have cache size tweaks you are applying, don't apply them. You will likely have more memory, and it will be better used. Here's what I use for the SD card cache and it works just fine:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ SDMemory\FATFS]
"DataCacheSize"=dword:00000000
"EnableFatCacheWarm"=dword:00000001
"EnableWriteBack"=dword:00000001
"FatCacheSize"=dword:00000000
Note - Data/FatCacheSize=0 means system-managed, not disabled. That means WinCE looks at the FAT size and Meta Data directory size and determines how much to cache (which is usually the entire thing) based on how much stuff you have on your SD card. If you set an actual number here without knowing what you are doing, you will end up just allocating memory for a cache that is never used.