"filesys.exe" and CompactionPrio256 - Are we close to fixing WM5?

bluevolume · 01-06-06, 05:04 PM

I swear we are going to fix this OS long before Dell does.

I re-re-re-upgraded again today, leaving my friendly WM2003 behind and going back into the lion's den (WM5). I wanted to try the CompactionPrio256 hack since it has showed a little promise and is the only one I haven't tried yet.

Upon starting with the fresh WM5 install, I was already seeing the 'filesys.exe' problem (confirming that this does exist out-of-the-box). I loaded up Resco Explorer (needed the registry editor), TCPMP, and Mapopolis. The Axim worked pretty much like it did before, having glimpses of speed and then bogging down most of the time. So I go into the registry editor and change the CompactionPrio256 from 255 to 128.

Immediately the 'filesys.exe' problem somewhat disappears. The process is still running, but it isn't crippling my Axim. I've been using it for a few hours, and it seems to be OK. The slowdowns haven't vanished completely, but it isn't as bad or as often. Could this be a real solution?

I researched the registry key and class a bit, and it sounds like this process might be trying to compress data in the ROM. The OS is sort of like "Hey, not much going on right now, why don't I read a few files, compress them, then save them back to the ROM?" Sort of like your wife deciding to vacuum the livingroom because she has spare time, not realizing that she's ruining the game you're watching (no offense intended :) ). If this is the case, and the effects for the end user are so negative, then why bother with it at all?

I checked with a co-worker who has a new iPaq (WM5), and his machine does not have the CompactionPrio256 (or the CompactionCritPrio256) key at all. Does this mean that the iPaq just doesn't bother with this? If it was necessary, why would HP remove it?

Lets discuss -- this could be a big step forward.

UnLoGiC · 01-06-06, 05:32 PM

This sounds interesting, any please where we can find more information about CompactionCritPrio256?

SolSie · 01-06-06, 06:34 PM

Originally Posted by bluevolume

I checked with a co-worker who has a new iPaq (WM5), and his machine does not have the CompactionPrio256 (or the CompactionCritPrio256) key at all. Does this mean that the iPaq just doesn't bother with this? If it was necessary, why would HP remove it?
Lets discuss -- this could be a big step forward.

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?

bluevolume · 01-06-06, 06:51 PM

Originally Posted by SolSie

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 upped the ante and deleted them completely. My x50v is FLYING now on WM5. It is at least as fast as it was with WM2003 -- maybe even better. I'm streaming Club 977 through TCPMP, and the CPU is hovering between 104 and 208MHz. This hack could be a sort of fools gold, I won't know till I use it for a while. My memory numbers still look good; not sure what else to look at. I figure the worst that could happen is the ROM will get hosed and I'll have to hard-reset.

If anyone else wants to try this -- do so with caution. But its working great for me so far.

UnLoGiC · 01-06-06, 06:56 PM

Wow, please write a short decription of what needs to be deleted!

SolSie · 01-06-06, 07:27 PM

I just deleted those 2 keys too. So far so good! I can feel my X50v is very snappy...across all applications..

:approve:

01-06-06, 07:40 PM

ok, still no real detailed registry keys... please post.!!!!!!

full registry key

SolSie · 01-06-06, 07:46 PM

Originally Posted by nathanwj

ok, still no real detailed registry keys... please post.!!!!!!

full registry key

I deteled CompactionPrio256 and CompactionCritPrio256 in

HKLM\drivers\Builtin\StrataFMD\CompactionPrio256
HKLM\drivers\Builtin\StrataFMD\CompactionCritPrio2 56

Please handle the registry with care!
:exc:

01-06-06, 07:53 PM

ok, well i gound them by seaching... first changed the value.... nothing happened (actually slower) then deleted........ same as b4

SolSie · 01-06-06, 07:58 PM

Originally Posted by nathanwj

ok, well i gound them by seaching... first changed the value.... nothing happened (actually slower) then deleted........ same as b4

I hope you soft reset each time?

01-06-06, 08:08 PM

ok it is running better now... faster... good job ppls

maddoctor · 01-06-06, 08:19 PM

Wow, impressive speed...Everything seems faster than it was in 2003se, not to mention WM5 before the deletion of the registry keys...Let's just hope this doesn't harm the PDA somehow...Seems too good to be true...

EDIT: or maybe not...It just got stuck at 624 again (maybe it needs a softreset using the button and not a program)...Anyway it seems faster...

Patrick Y. · 01-06-06, 08:22 PM

I'm going to try that too... Thanks a lot guys!!! I guess I won't be selling my x50v after all if this works. Will report back. Thanks again!!

edit: Got CPU load at 100% again, filesys.exe is apparently working fast...

And yes, I reset my Pocket PC after I modify the registry key.

01-06-06, 08:35 PM

So far, so good!! Only time will tell :)

shsmith · 01-06-06, 08:35 PM

Originally Posted by bluevolume

I checked with a co-worker who has a new iPaq (WM5), and his machine does not have the CompactionPrio256 (or the CompactionCritPrio256) key at all. Does this mean that the iPaq just doesn't bother with this? If it was necessary, why would HP remove it?

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.