x50v wm5: filesys.exe uses 95% cpu - Page 5

SolSie · 12-12-05, 08:03 AM

You might want to try FontOnStorage utility. Or check how much RAM your language package is taking. I am sure it is enormous..

TheCooperman · 12-12-05, 10:44 AM

Glad I aint got WM5 yet!

l<rAsl-l · 12-12-05, 01:16 PM

hi all :) i upgraded my x50v to wm5 and had the problem with the procesor being maxed out when i had no other programs installed. i now rolled back to wm2003. Its just a joke that ms and dell would release a o.s that virtually makes the x50v useless. Surely their testing processes included turning the x50v on?

i hope they mangae to fix this soon

12-13-05, 11:16 AM

this is the only problem i have with wm5

but dang, it's annoying

jimhanseng · 12-13-05, 06:27 PM

I installed SuperTasks on my new x51v and it seems to run fine. The graphics are tiny as it appears the program thinks I have a lower resolution screen. How is it working for you?

Jim Hansen

Originally Posted by bluevolume

I loaded up the SuperTask app too -- what a great resource.

OK, my Axim was working fine after a reboot. It was in that "Wow, I think I finally screwed with enough settings to make it work!" state. Ran Supertask and the CPU sat around zero. Ran TCMP, and was watching Napoleon Dynamite with 22% CPU usage, and everything still moving along nicely.

Then I run IE and surf around a bit, and the CPU peaks for a bit but it was expected as IE is a hog when rendering pages. Then it locks up and I reboot.

After the reboot, I'm back to the "I can't stand WM5". Every time I click anything it takes a second or two to respond, everything is crawling. I load up Supertask, and see that filesys.exe is taking up 90-94% of the cpu, and has been sitting there doing that since I started writing this.

What is the frigging deal? Why is that process taking up so much time? Somewhere in this is the root of all the OS problems. Dell, can you hear us????

bluevolume · 12-13-05, 07:25 PM

Originally Posted by jimhanseng

I installed SuperTasks on my new x51v and it seems to run fine. The graphics are tiny as it appears the program thinks I have a lower resolution screen. How is it working for you?

Jim Hansen

It did that for me upon install also. It fixed itself however, I think after a reboot.

shsmith · 01-19-06, 12:57 PM

There have been some new developments in the quest to tame filesys.exe.

Look here for a patch that has helped some.
http://www.aximsite.com/boards/showt...4&page=6&pp=20

shsmith · 01-22-06, 07:54 PM

I posted a new version of the filesys patch today. You can find it here:
http://www.aximsite.com/boards/showp...&postcount=611

02-03-06, 02:45 AM

mods plz sticky this thread

shsmith · 02-07-06, 09:52 PM

Here is a new version of the patch.

2/06/06 v10
Added a second critical section. Not sure if it will make any difference.
Added a configuration dialog that lets you control compaction while on AC power as well as the time
periods between power state checks and compaction checks.
The patch loads without any message, but when you launch it a second time you get the configuration
dialog, with choices to save changed settings, hide (and continue running) or exit the patch.

02-07-06, 10:35 PM

Originally Posted by shsmith

Here is a new version of the patch.

2/06/06 v10
Added a second critical section. Not sure if it will make any difference.
Added a configuration dialog that lets you control compaction while on AC power as well as the time
periods between power state checks and compaction checks.
The patch loads without any message, but when you launch it a second time you get the configuration
dialog, with choices to save changed settings, hide (and continue running) or exit the patch.

THANKS for all your hard work!!

Patrick Y. · 02-08-06, 06:45 PM

THANKS!!! :love: :)

shsmith · 02-08-06, 07:54 PM

Originally Posted by grmiller

For the V10 what is the best setting that you have used. I have a Dell X50v WM5.

Please.

Hi grmiller. If you find your axim very stable, you can turn the settings down as low as 1 second and the patch will then respond very quickly. If you are having troubles with locking up or slow power-up, you can set the patch to much higher numbers (such as 60 seconds per compaction check) in order to stabilize things. That's why I made it configurable in v10--because a lot of different versions I made in the past were little more than adjustments of these settings.

I have been running v10 with "always allow compaction on AC" checked,
60 seconds delay between power state checks, and
20 seconds delay between compaction checks.
It has been real stable for me with those settings.

sgtsampay · 02-08-06, 08:16 PM

Hey shsmith did you read my latest idea on the other thread? The one about making a program that will wake up the axim...Plz tell me if it isn't possible. Cause if it isn't, then I will have to think of some more. Also can you tell me how you are making these programs? I mean what are the C++ codes? Thanks

shsmith · 02-08-06, 08:26 PM

Originally Posted by sgtsampay

Hey shsmith did you read my latest idea on the other thread? The one about making a program that will wake up the axim...Plz tell me if it isn't possible. Cause if it isn't, then I will have to think of some more. Also can you tell me how you are making these programs? I mean what are the C++ codes? Thanks

Hi sgtsampay. It is possible to make something wake up by adding an entry to the notification queue--like how pop up reminders can wake up the axim, or how activesync wakes it up before you put in the fake-server fix. I always thought one of the big problems was keeping the axim asleep, not waking it up.

Did you try v10? If you did, I suggest you turn up the delay settings to higher settings (maybe 2-4 times the defaults) and see if that helps any with the problem you are having.