I tinkered with this key a while ago and finally came to the conclusion the thread was already running at the lowest priority. It is in a critical section, so no matter how low the priority it slows anything needing to read/write the ROM. Also the "auto" speed mode doesn't seem to care about priority and will give even a low priority thread the full CPU speed as long as it doesn't go idle much.
BTW, I decompiled filesys.exe and found a patch that I hope will help. I posted the details over in the "SD flash" tutorial thread.
Can you explain how to apply the patch again? I read your post at the SD flash tutorial but I don't really understand it. Thanks.
__________________
Got my first PPC when I was 12:approve:
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Acer n10 > x50v > x51v :approve:
2200mah secondary To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
3 year warranty
Dopod Bluetooth Keyboard- NOW WORKS WITH WM5 THANKS TO WIDCOMM PROJECT!! To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Big thanks to Solsie, Shsmith, Beemer, Menneisyys, and many others who provided various tweaks/fixes :approve:
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Can you explain how to apply the patch again? I read your post at the SD flash tutorial but I don't really understand it. Thanks.
I know how to find the patch location, and which bytes to patch. What I don't know is how to flash the patched version back to the Axim. Once we know how to make new CRC files, I should be able to try different pathes fairly easily. There is a good chance this first one won't help at all, but I am hopeful I am on the right track.
__________________ Freedom is a heavy load, a great and strange burden for the spirit to undertake. It is not easy. It is not a gift given, but a choice made, and the choice may be a hard one. -- Ursula K. LeGuin
I know how to find the patch location, and which bytes to patch. What I don't know is how to flash the patched version back to the Axim. Once we know how to make new CRC files, I should be able to try different pathes fairly easily. There is a good chance this first one won't help at all, but I am hopeful I am on the right track.
Thanks you clearing things up a bit. Also, I really appreciate you guys' hardwork. I wish I can do something useful to help...
__________________
Got my first PPC when I was 12:approve:
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Acer n10 > x50v > x51v :approve:
2200mah secondary To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
3 year warranty
Dopod Bluetooth Keyboard- NOW WORKS WITH WM5 THANKS TO WIDCOMM PROJECT!! To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Big thanks to Solsie, Shsmith, Beemer, Menneisyys, and many others who provided various tweaks/fixes :approve:
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
I tinkered with this key a while ago and finally came to the conclusion the thread was already running at the lowest priority. It is in a critical section, so no matter how low the priority it slows anything needing to read/write the ROM. Also the "auto" speed mode doesn't seem to care about priority and will give even a low priority thread the full CPU speed as long as it doesn't go idle much.
BTW, I decompiled filesys.exe and found a patch that I hope will help. I posted the details over in the "SD flash" tutorial thread.
What about deleting the keys entirely? That is what is claimed to speed things up...
Its going on about 3 hours now and my Axim is still working great. It still has a few slowdowns, but they are brief and don't seem to be as painful as before.
I've read through the posts and it sounds like others have already tried this and haven't had good luck. Maybe the good performance I'm seeing is because of something else. The only other changes I've made was to turn off the error reporting and running 'security turn off' utility (from tweaks2k2 I think). I'm almost afraid to install anything else on my Axim because I don't want to screw this up! This Axim was miserable before, but the same device running the same OS is now much improved.
If I find anything else out, or if it goes sour, I'll be sure to post.
i can't erase the registry keys ...when i do a soft reset after erase them form the registry with resco explorer i check the registry ... they are there again .... why?
i can't erase the registry keys ...when i do a soft reset after erase them form the registry with resco explorer i check the registry ... they are there again .... why?
The mystery continues. I deleted mine, but never looked after a soft-reset. Mine are back as well, but the CompactionPrio256 is still set to 128.
So the system restored the keys, but it put the second one back to my modified value? Bizarre.
HKLM\drivers\Builtin\StrataFMD\CompactionPrio256 (i set this one to 128) but filesys.exe still raise ti 95%)
HKLM\drivers\Builtin\StrataFMD\CompactionCritPrio2 56 (this one was i n a number like 4234234234234 or so ... then i set it to 255)
in some part of the windows mobile 5 Microsoft Registry tutorial said that the value 255 means IDLE ... weird...so set to 128 mean high level of priority to a process
after set up to 255 both registry values ... it seems that the compactation last less than before and the x50v get more responsive when compactation take place ...
i check filesys in wm2003 and it's the same thing ...it happens only when you write in the built in store ... but of course we don't notice because the priority it set to low ... if i have to guess ... maybe this regsitry hack it a 99% solution for this mather...
This is my conclusion of the reading and testing that I've done so far:
HKLM\drivers\Builtin\StrataFMD\CompactionPrio256 has a default value of 0xFF which is 255 in decimal and seen in my previous post 255 stands for THREAD_PRIORITY_IDLE which is the lowest availible priotity setting so I dont think we should bother changing the value of this setting at all.
HKLM\drivers\Builtin\StrataFMD\CompactionCritPrio2 56 on the other hands has a default prio of 0xFFFFFFFF which is 4294967295 in decimal seems more interesting although changing it 0xFF (255) doesnt make any noticable diffrence on my X50v.
I think the biggest problem lies within the filesys.exe file itself!
__________________
Palm IIIc -> Palm T3 -> X50v
UnLoGiC Movie Converter
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
What about deleting the keys entirely? That is what is claimed to speed things up...
That is something I did not try. I suspect it uses the default (lowest) priority when the key is missing, but there is a possibility it doesn't even start the thread.
Meanwhile, I flashed a rom with filesys patched to stay asleep, and so far I think it has made a difference. Time will tell. It is easy to jump to the conclusion that the problem is solved, only to see it return in day or two.
That is something I did not try. I suspect it uses the default (lowest) priority when the key is missing, but there is a possibility it doesn't even start the thread.
Meanwhile, I flashed a rom with filesys patched to stay asleep, and so far I think it has made a difference. Time will tell. It is easy to jump to the conclusion that the problem is solved, only to see it return in day or two.
Is there any way to replace filesys.exe without flashing the rom?
__________________
Palm IIIc -> Palm T3 -> X50v
UnLoGiC Movie Converter
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
The X51 does not have those keys neither. Can sombody display the key HKLM\drivers\Builtin\StrataFMD\CompactionCritPrio2 56...CompactionPrio256
on the X51..Or something similar, I know the X51 does not have strataFMD..I am tempted to take them out completely?
I'm guessing that there is something about the X50v ROM being different that makes the compaction/filesys.exe necessary. That is why the X51 and Ipaq don't have it. I don't think that HP has come out with a WM5 upgrade for their 2003 models have they?. Isn't there some way to find out what problem this thing is trying to solve. I think most of us would trade speed for more ROM space if all it is doing is compressing files but I'm a bit concerned it could be doing something more vital. Someone has to know right Well speak up :approve:
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
Well speak up :approve:
