Menneisyys's Tweaks to "Fix" the iPAQ hx4700 WM5 Upgrade

[Janak Parekh]

<div class='os_post_top_link'><a href='http://www.pocketpcmag.com/blogs/index.php?blog=3&title=make_your_ipaq_hx4700_windows_mobile_5_u&more=1&c=1&tb=1&pb=1' target='_blank'>http://www.pocketpcmag.com/blogs/in...1&c=1&tb=1&pb=1</a><br /><br /></div><i>"Thanks to Hal Goldstein at the Smartphone &amp; Pocket PC magazine, I’ve become a proud owner of an HP iPAQ hx4700...Of course, the first thing I’ve done after receiving the device was installing the WM5 upgrade. My first impression of the upgrade was awful. After installing a handful of applications and games, it became really-really slow, irresponsible and consumed a lot of battery power...."</i><br /><br />Many users have complained about extreme slowness after upgrading their hx4700 to WM5. The good news is that PPCT member Menneisyys has just obtained a new hx4700 and set to work on fixing its performance... and that he's found the main causes of the slowness and has simple tips on how to fix it! (The bad news is that most of the slowness seems to stem from at least one extremely simple bug -- in the touchpad driver -- one that you'd expect HP to have found in the first place. :roll:) If you're an hx4700 user poking along with WM5, this article is a <b>must</b>-read.

[sapibobo]

I red the article yesterday and I tried the games-folder trick. It works. Please be notice that I applied another trick also (cache, temp folder in SD, etc) so the increasing speed may not as large as the one who tried this trick first.

I tried the filesys patch and put it in Start Up folder. But somehow the HX is slower. I delete the file and HX is speedy again.

Another masterpiece from him. Congratulations. This is one of the best trick I ever have.

[asims]

Can these hacks work on a WM5-native pda like the hx2495? Or are they just for the hx4700 or other pdas that upgraded to WM5?

[Janak Parekh]

Can these hacks work on a WM5-native pda like the hx2495? Or are they just for the hx4700 or other pdas that upgraded to WM5?
I'm pretty sure WM5 native devices do not need, and cannot benefit from, these hacks. The first one is specific to a hx4700 touchpad driver; the second is the filesys.exe process, which is apparently needed on upgraded units but not units that shipped with WM5 out-of-the-box.

--janak

[hang5lngbd]

So does this hack make WM5 usable on my hx4700 again? I "upgraded" my device back to 2003SE after "downgrading" to WM5. Is it time to try WM5 again?

[ctitanic]

Yes, another good article. I have to point that according to MS, changing or deleting the Compaction registry keys does not do anything or fix anything at all.

[Menneisyys]

I red the article yesterday and I tried the games-folder trick. It works. Please be notice that I applied another trick also (cache, temp folder in SD, etc) so the increasing speed may not as large as the one who tried this trick first.

I tried the filesys patch and put it in Start Up folder. But somehow the HX is slower. I delete the file and HX is speedy again.

Are you sure? In my CPU usage tests, the filesys throttler has not caused any slowdown.

Did anyone else experience slowdowns with the throttler?

Another masterpiece from him. Congratulations. This is one of the best trick I ever have.

Thanks :)

BTW, I've just updated the article with the latest developments (the "Games" hack has been further simplified into an even easier registry hack) and links back to additional user feedback, also here at PPCT.

[Menneisyys]

So does this hack make WM5 usable on my hx4700 again? I "upgraded" my device back to 2003SE after "downgrading" to WM5. Is it time to try WM5 again?

Yes, WM5 is pretty usable. Of course, you'll still have some problems with filesys.exe and the limited compatibility of games (other WM5 devices like the Dell Axim x51v and the HTC Wizard are far more compatible with games - a lot of titles don't even start on the WM5 hx4700). This is topped by the CF bug, which will be a major pain in the back if you permanently have (and use) a CF card in your PDA.

[Sully]

Amazing speed improvement. Thanks so much.

[ctitanic]

Tweaks2K2 v3.22 released including this hack mentioned by Menneisyys that causes slowness in hx4700 machines updated with WM5.

[xdev]

the upgrade kept being postponed due to a "driver issue"

maybe this was the driver that had the issue?

[Janak Parekh]

the upgrade kept being postponed due to a "driver issue"

maybe this was the driver that had the issue?
The thought occurred to me. If it was the case, and HP just ended up shrugging their shoulders and throwing in the broken driver, that just makes it doubly lame.

--janak

[Menneisyys]

the upgrade kept being postponed due to a "driver issue"

maybe this was the driver that had the issue?

It was the ATI video driver that caused the problem and the delay, as far as I know. The e800 ATI driver in the WM2003SE upgrade was really bad and rendered the device almost useless (1-2 FPS) in Landscape mode. The situation may have been the same with the 4700.

[Menneisyys]

The CF fix is available. Please see http://www.pocketpcmag.com/blogs/index.php?blog=3&amp;title=the_hp_ipaq_hx4700_wm5_compact_flash_pat&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1 for mor einfo.

Sorry for not copying the article here - it's full of user comments, which are very important to read so that you can have a background of what this patch is about.

[Tye]

Can anyone tell me if there is any truth to the idea that it is best to install all programs to the SD card instead of the internal store? Supposedly, if I do this the compaction routine won't need to run as often so my system will be faster.
Thanks.

[Menneisyys]

Can anyone tell me if there is any truth to the idea that it is best to install all programs to the SD card instead of the internal store? Supposedly, if I do this the compaction routine won't need to run as often so my system will be faster.
Thanks.

I haven't benchmarked this so there are no objective data to back this up, but I find it pretty logical. That is, try to keep everything on the card.

[tan0139]

Has anyone tried the Filesys patch on any HP PDA other than the Hw4750? Does it work on any WM5.0 PDA or is it specific to the HW4750? Would appreciate some help on this, as I don't want to end up doing a dreaded full reset!

Gerald Tan

[Menneisyys]

Has anyone tried the Filesys patch on any HP PDA other than the Hw4750? Does it work on any WM5.0 PDA or is it specific to the HW4750? Would appreciate some help on this, as I don't want to end up doing a dreaded full reset!

Gerald Tan

1. using Spb or Sprite backup is recommended even with WM5 devices.

2. I have cretaed a version of the throttler for the wm5-upgraded hx2xxx series. I have not announced it though because I, laking any of these devices, couldnt test it. Let me know if you need them - I will post them right away.

3. native wm5 devices dont have any prob with filesys - no throttler is needed for them.

4. welcome to PPCT :)

[tan0139]

Hello Mennisyys,

Many thank for your prompt reply. Yes I have backed up my PDA. Would love to try out your Filesys trottler for the HP hx2750. Please send it to me (via a link?) and I will get back to you with a report on how it went.

Much appreciated.

Gerald Tan
PS My HP Hx 2750 is not a native WM5.0. I had to install the ROM upgrade.

[Menneisyys]

Mike Calligaro addresses the compaction problem in non-native Windows Mobile 5 devices

Everyone that has a device (let it be an iPAQ hx or a Dell Axim x50(v)) upgraded to WM5 knows what problems the compaction service (filesys.exe) causes.

The problem has been addressed by Pocket PC gurus/hackers (including me) several times, with varying success. (See for example this article (http://www.pocketpcmag.com/blogs/index.php?blog=3&amp;p=861&amp;more=1&amp;c=1&amp;tb=1&amp;pb=1).)

Now, well-known Windows Mobile Team blogger Mike Calligaro addressed this problem in his blog (http://blogs.msdn.com/windowsmobile/archive/2006/06/07/621132.aspx), with particular attention to the WM5-upgraded HP iPAQ hx4700.

The article is a nice read to anyone that wants to know more about the compaction process. Also, it points the reader to the new, free, much more WM5-friendly (it doesn't writ temporary files back to the main storage) DockWare version (http://www.iliumsoft.com/download.php?prodcode=20120), which is highly recommended for all hx4700 users (go and get it!).

Unfortunately, there are no solutions/hacks provided in the article. However, it still contains some good news: they've sent device manufacturer OEM's the way of speeding up the process. Now, we're in the hand of the manufacturers: hope they do issue some kind of an update. Unfortunately, these hacks can not be implemented by hand (on, for example, the Registry level). With some laborous ROM reverse engineering, recompiling/hexediting and re-flashing the entire device, it can be done, even if HP/Dell don't bother releasing a new ROM version, though. Any Pocket PC guru having the necessary time to do it? ;)

[Menneisyys]

Hello Mennisyys,

Many thank for your prompt reply. Yes I have backed up my PDA. Would love to try out your Filesys trottler for the HP hx2750. Please send it to me (via a link?) and I will get back to you with a report on how it went.

Much appreciated.

Gerald Tan
PS My HP Hx 2750 is not a native WM5.0. I had to install the ROM upgrade.

http://www.winmobiletech.com/052006iPAQhx4700WM5/hx2xxx

[tan0139]

Hello Menneisyys,

Many thanks for the link. Will try out the patch for the HP hx2750 and let you know what effect it has had on my PDA.

Much appreciated.

Gerald Tan

[tan0139]

Dear Menneisyys,

I tried out the Filesys patches you kindly sent me and got the "Cannot find MSthread" error message, so I am attaching my out.txt file. Hope you can help.

Regards,

Gerald Tan

Copying C:\New Downloads\FileSysPatch\isutils-pps\itsutils.dll to WCE:\windows\itsutils.dll
06be6492 035f96ec fb fb 0.0 0.0 redir.dll a7be4d3e: device.exe 20
06c36f92 00013684 fb fb 0.4 0.0 0768461a: repllog.exe AppRunAfterRndisFnDetected
06f3efd2 00ec3c5c fb fb 0.0 0.0 plusactions.dll 479ec68a: shell32.exe 50
0707afca 00e23508 fb fb 0.0 0.0 spbweatherservice.dll 676fdece: services.exe 60
071ff58a 034b2d44 fb fb 0.0 0.0 cspnet.dll 6724cb56: connmgr.exe 70
072d4176 02de68e4 fb fb 0.0 0.0 ossvcs.dll 479ec68a: shell32.exe 50
075c42ea 000145b4 fb fb 0.0 0.0 676fdece: services.exe 60
075dee2a 00041fb8 fb fb 0.0 0.0 479ec68a: shell32.exe 50
0772c83a 00071e3c fb fb 0.0 0.0 07be4eee: gwes.exe 30
078f2f8a 00016e6c fb fb 0.0 0.0 07be4eee: gwes.exe 30
0793b3b6 02fe216c fb fb 0.0 0.0 dhcpv6l.dll a7be4d3e: device.exe 20
079a3ad6 02fb1b60 fb fb 0.0 0.0 afd.dll a7be4d3e: device.exe 20
079a8caa 02ea5638 fb fb 0.0 0.0 wapdrv.dll a7be4d3e: device.exe 20
079b3c5a 0366b75c fb fb 0.0 0.0 tcpip6.dll a7be4d3e: device.exe 20
079f8f32 01065ffc 65 65 0.0 0.0 sdbus.dll a7be4d3e: device.exe 20
07a61f82 019b5b3c fb fb 0.0 0.0 btceif.dll a7be4d3e: device.exe 20
07b51402 01132550 62 62 0.0 0.0 pxa27x_dma.dll a7be4d3e: device.exe 20
07ed7fc2 00041080 fb fb 0.0 0.0 87ff0752: filesys.exe
07ffcfde 9ac5737c 01 01 0.0 0.0 07fff002: NK.EXE
07fff266 9ac595a4 ff ff 0.0 0.0 07fff002: NK.EXE
26acd57e 00015bb0 fb fb 0.0 0.0 66ad0ee6: tmail.exe -RunInBKG
26ad0d2a 000127d4 fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
26c831a6 02df1e54 fb fb 0.0 0.0 ossvcs.dll 46d8fd16: Vidya Task Manager.exe
27215f72 00011068 fb fb 0.0 0.0 2724cfae: srvtrust.exe 80
2724abde 0001416c c8 c8 0.0 0.0 272b8f4e: BioDetect.exe
27265fc2 00016a70 fb fb 0.0 0.0 479ec68a: shell32.exe 50
273bb6ea 01211868 6e 6e 0.0 0.0 irsir.dll a7be4d3e: device.exe 20
273c19ee 00011ccc fb fb 45.6 0.0 86be6426: rapiclnt -drndis_peer
273cc8e2 030f127c fb fb 0.0 0.0 dtpt_srv.dll 676fdece: services.exe 60
27409f62 02e83970 fb fb 0.0 0.0 softkb.dll a7be4d3e: device.exe 20
27474a4e 037d1bc8 fb fb 0.0 0.0 ipv6hlp.dll a7be4d3e: device.exe 20
2791bb4e 01151a54 6d 6d 1.3 0.0 rndisfn.dll a7be4d3e: device.exe 20
279a87ca 03191bbc fb fb 0.0 0.0 ethman.dll a7be4d3e: device.exe 20
27a39ec6 010a20b4 fb fb 0.0 0.0 pwrbutton.dll a7be4d3e: device.exe 20
27a39fd6 010a1988 fb fb 0.0 0.0 pwrbutton.dll a7be4d3e: device.exe 20
27a68f9e 019b7888 fb fb 0.0 0.0 btceif.dll a7be4d3e: device.exe 20
27acffbe 0336321c fb fb 0.0 0.0 audevman.dll a7be4d3e: device.exe 20
27b6ffbe 03ef2a80 fb fb 0.0 0.0 pm.dll a7be4d3e: device.exe 20
27b72f0e 03ef6458 f8 f8 0.0 0.0 pm.dll a7be4d3e: device.exe 20
27b76fc2 03ef68dc f9 f9 0.0 0.0 pm.dll a7be4d3e: device.exe 20
27bf7b8e 03f53020 fb fb 3.6 0.0 certmod.dll 87ff0752: filesys.exe
46a7cc3e 00011ccc fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
46b6c266 030f127c fb fb 0.0 0.0 dtpt_srv.dll 676fdece: services.exe 60
46df584e 0001b9bc fb fb 0.0 0.0 46d8fd16: Vidya Task Manager.exe
46ffef7a 00046e78 fb fb 0.0 0.0 479ec68a: shell32.exe 50
471a3042 00035e38 fb fb 0.0 0.0 471a6cce: BTTrayCE.exe
471bf0aa 0229de40 fb fb 0.0 0.0 wsp.dll 2724cfae: srvtrust.exe 80
47215392 03326864 fb fb 0.0 0.0 connplan.dll 6724cb56: connmgr.exe 70
473b3b1e 02274ad8 fb fb 0.0 0.0 obexsrvr.dll 676fdece: services.exe 60
47710ec2 0003f8ec f9 f9 0.0 0.0 07be4eee: gwes.exe 30
478f3f1e 000448a0 f9 f9 0.0 0.0 07be4eee: gwes.exe 30
478fefc6 00017584 fb fb 10.8 0.0 479ec68a: shell32.exe 50
47995d0e 03c41ee8 fb fb 0.0 0.0 dhcp.dll a7be4d3e: device.exe 20
479faa3e 0302a2f8 fb fb 0.0 0.0 pptp.dll a7be4d3e: device.exe 20
47a170aa 01065ffc 64 64 0.0 0.0 sdbus.dll a7be4d3e: device.exe 20
47a74242 01246580 0a 0a 0.0 0.0 wavedev.dll a7be4d3e: device.exe 20
47a748a6 012465a0 d2 d2 0.0 0.0 wavedev.dll a7be4d3e: device.exe 20
47a82bc6 01246560 0a 0a 0.0 0.0 wavedev.dll a7be4d3e: device.exe 20
47ad4366 03371a38 fb fb 0.0 0.0 tapi.dll a7be4d3e: device.exe 20
47b268e2 0123a028 68 68 0.0 0.0 pcmcia.dll a7be4d3e: device.exe 20
47b26f46 01237218 69 69 0.0 0.0 pcmcia.dll a7be4d3e: device.exe 20
47b26fba 01237800 67 67 0.0 0.0 pcmcia.dll a7be4d3e: device.exe 20
66a1cd02 00011ccc fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
66a63e02 0002a1d0 fb fb 0.0 0.0 0768461a: repllog.exe AppRunAfterRndisFnDetected
66a89fa6 00011ccc fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
66acebae 02df1e54 fb fb 0.0 0.0 ossvcs.dll 66ad0ee6: tmail.exe -RunInBKG
66ad0f0a 00013fa8 fb fb 0.0 0.0 66ad0ee6: tmail.exe -RunInBKG
66ee3fb6 02df1e54 fb fb 0.0 0.0 ossvcs.dll 0768461a: repllog.exe AppRunAfterRndisFnDetected
671fff1e 034b5d64 fb fb 0.0 0.0 cspnet.dll 6724cb56: connmgr.exe 70
672b8df2 000480c8 ff ff 0.0 0.0 479ec68a: shell32.exe 50
672d4272 02ba7060 fb fb 0.0 0.0 sqlcese30.sys.dll 87ff0752: filesys.exe
673bbfca 01211a88 70 70 0.0 0.0 irsir.dll a7be4d3e: device.exe 20
676845f6 00011aa8 fb fb 0.0 0.0 6724cb56: connmgr.exe 70
6770d95e 00011814 fb fb 0.0 0.0 676fdece: services.exe 60
67713b52 0002b5f8 f9 f9 0.0 0.0 07be4eee: gwes.exe 30
678f2d86 010b901c fb fb 0.0 0.0 pxa27x_lcd.dll 07be4eee: gwes.exe 30
6793bb3e 01291a3c 64 64 8.7 0.0 ms2_usbfn.dll a7be4d3e: device.exe 20
679e9642 011227dc 23 23 0.0 0.0 sdhc_mainstoneii_b2.dll a7be4d3e: device.exe 20
679ecd36 01123424 24 24 0.0 0.0 sdhc_mainstoneii_b2.dll a7be4d3e: device.exe 20
679fac7e 02cf67c8 fb fb 0.0 0.0 ndis.dll a7be4d3e: device.exe 20
67a5d99e 039b6ad4 fb fb 0.0 0.0 wzcsvc.dll a7be4d3e: device.exe 20
67a6e7b6 011677c4 fb fb 0.0 0.0 ms2_serial.dll a7be4d3e: device.exe 20
67a71926 011677c4 9f 9f 0.0 0.0 ms2_serial.dll a7be4d3e: device.exe 20
67af3482 03fb1548 fb fb 0.0 0.0 coredll.dll a7be4d3e: device.exe 20
67af80e6 02d0bc4c 76 76 0.0 0.0 ndis.dll a7be4d3e: device.exe 20
67af8fca 02d0b458 78 78 0.0 0.0 ndis.dll a7be4d3e: device.exe 20
86a509e6 000119e8 fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
8707fa86 00e6b450 fb fb 0.0 0.0 mfcce300.dll 676fdece: services.exe 60
871bb822 022a0124 fb fb 0.0 0.0 wsp.dll 2724cfae: srvtrust.exe 80
8724c002 00016bc8 fb fb 0.0 0.0 479ec68a: shell32.exe 50
875f170e 0307662c fb fb 0.0 0.0 notify.dll 676fdece: services.exe 60
879a384e 037f6068 fb fb 0.0 0.0 netbios.dll a7be4d3e: device.exe 20
87ac7612 00022c14 fb fb 0.0 0.0 86f3e512: PimHelper.exe
87af5eee 02cf96e8 7e 7e 0.0 0.0 ndis.dll a7be4d3e: device.exe 20
87b03f86 03b51b8c 84 84 0.0 0.0 cxport.dll a7be4d3e: device.exe 20
87b7670e 03ef6d24 f9 f9 0.0 0.0 pm.dll a7be4d3e: device.exe 20
87fc7fce 03dea218 fb fb 0.0 0.0 stratad_intel_l.dll 87ff0752: filesys.exe
87ff072e 0001359c fb fb 0.0 0.0 87ff0752: filesys.exe
a6ba5182 0002e200 fb fb 0.0 0.0 0768461a: repllog.exe AppRunAfterRndisFnDetected
a6ee3a12 0001482c fb fb 0.3 0.0 46d8fd16: Vidya Task Manager.exe
a6ffe8a2 02ea5638 fb fb 0.0 0.0 wapdrv.dll a7be4d3e: device.exe 20
a71a6d32 00014078 fb fb 0.0 0.0 a71a6872: swb.exe
a71fbfd2 03392e3c fb fb 0.0 0.0 cspwwan.dll 6724cb56: connmgr.exe 70
a7219f1a 033274c8 fb fb 0.0 0.0 connplan.dll 6724cb56: connmgr.exe 70
a72b8fba 000261a8 fb fb 0.0 0.0 a7225faa: buttons.exe
a740e06e 00011ccc fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
a77134ca 01273d94 6d 6d 0.0 0.0 touch.dll 07be4eee: gwes.exe 30
a7718432 01274c9c fb fb 0.0 0.0 touch.dll 07be4eee: gwes.exe 30
a7718fb2 012739d0 fb fb 0.0 0.0 touch.dll 07be4eee: gwes.exe 30
a79d69da 036a31fc fb fb 0.0 0.0 tcpstk.dll a7be4d3e: device.exe 20
a7a3cc82 011148f0 fb fb 0.0 0.0 battdrvr.dll a7be4d3e: device.exe 20
a7a3ff06 01112de4 fb fb 0.0 0.0 battdrvr.dll a7be4d3e: device.exe 20
a7a44dc6 01112d80 fb fb 0.0 0.0 battdrvr.dll a7be4d3e: device.exe 20
a7a44fc6 01114610 fb fb 0.0 0.0 battdrvr.dll a7be4d3e: device.exe 20
a7a6b416 011677c4 9f 9f 0.0 0.0 ms2_serial.dll a7be4d3e: device.exe 20
a7b3a94e 011677c4 fb fb 0.0 0.0 ms2_serial.dll a7be4d3e: device.exe 20
a7b4fb0a 011677c4 9f 9f 0.0 0.0 ms2_serial.dll a7be4d3e: device.exe 20
a7b76d72 03ef4564 63 63 0.0 0.0 pm.dll a7be4d3e: device.exe 20
a7b80d4e 03e061cc fb fb 0.0 0.0 devmgr.dll a7be4d3e: device.exe 20
a7be4d1a 00011048 fb fb 0.0 0.0 a7be4d3e: device.exe 20
a7fc78ca 03f38a30 fb fb 0.0 0.0 fsdmgr.dll 87ff0752: filesys.exe
c6ee39ee 011c2784 fb fb 0.0 0.0 sdmemory.dll a7be4d3e: device.exe 20
c71c6d8e 032e1644 f8 f8 0.0 0.0 mmtimer.dll 2724cfae: srvtrust.exe 80
c75f1d72 03075e18 fb fb 0.0 0.0 notify.dll 676fdece: services.exe 60
c7908472 030c3330 f9 f9 0.0 0.0 dwxfer.dll a7be4d3e: device.exe 20
c79b383a 02fe2cb0 84 84 0.0 0.0 dhcpv6l.dll a7be4d3e: device.exe 20
c7a3cfde 01115ae0 f9 f9 0.0 0.0 battdrvr.dll a7be4d3e: device.exe 20
c7a556ea 03364414 0b 0b 0.0 0.0 audevman.dll a7be4d3e: device.exe 20
c7a6bfba 011677c4 fb fb 0.0 0.0 ms2_serial.dll a7be4d3e: device.exe 20
c7acab22 034c70ec 0c 0c 0.0 0.0 waveapi.dll a7be4d3e: device.exe 20
c7afafde 03b51918 84 84 0.0 0.0 cxport.dll a7be4d3e: device.exe 20
c7bf0dfe 02fa94ac fb fb 0.0 0.0 afd.dll a7be4d3e: device.exe 20
c7d4f412 00011ccc fb fb 0.0 0.0 86be6426: rapiclnt -drndis_peer
c7fd51fa 00041080 fb fb 0.0 0.0 87ff0752: filesys.exe
e6f20ece 02ea5638 fb fb 0.0 0.0 wapdrv.dll a7be4d3e: device.exe 20
e707a252 000111ec fb fb 0.0 0.0 a71a6872: swb.exe
e707fd02 00e23624 fb fb 0.0 0.0 spbweatherservice.dll 676fdece: services.exe 60
e70895ba 0001899c fb fb 0.0 0.0 471a6cce: BTTrayCE.exe
e7207d16 02df1e54 fb fb 0.0 0.0 ossvcs.dll 6724cb56: connmgr.exe 70
e724a25e 00020d0c fb fb 0.0 0.0 e7225fde: TapText.exe
e73c7642 000156f8 fb fb 0.0 0.0 676fdece: services.exe 60
e7684886 02df1e54 fb fb 0.0 0.0 ossvcs.dll 479ec68a: shell32.exe 50
e7736f6a 01072548 fb fb 0.0 0.0 keypad.dll 07be4eee: gwes.exe 30
e78f3f42 01072478 f9 f9 0.0 0.0 keypad.dll 07be4eee: gwes.exe 30
e790b242 011540e8 8b 8b 0.9 0.0 rndisfn.dll a7be4d3e: device.exe 20
e7912a32 011534b4 fb fb 0.3 0.0 rndisfn.dll a7be4d3e: device.exe 20
e792ff8e 01291588 fb fb 0.0 0.0 ms2_usbfn.dll a7be4d3e: device.exe 20
e7964f4a 0001b99c fb fb 0.0 0.0 471a6cce: BTTrayCE.exe
e79fa242 03029fe0 fb fb 0.0 0.0 pptp.dll a7be4d3e: device.exe 20
e7a74fda 01246740 d2 d2 0.0 0.0 wavedev.dll a7be4d3e: device.exe 20

[Menneisyys]

patch_filesys-x7fc78ca.exe uploaded to the same directory. Hope it'll work.

[tan0139]

Hi Menneisyys,

The Filesys patch works beautifully now. Thank you very much for your kindness and generosity in sharing your expertise knowledge.

Much appreciated.

Gerald Tan