The new HP iPAQ hx4700 WM5 upgrade: Questions & Answers
UPDATE (07/14/2007): this article is no longer up-to-date. Check out THIS instead.
(end of update.)
Due to popular demand (particularly here in the blog, at Pocket PC Thoughts, MobilitySite and BrightHand), I summarize what needs to be known about the new upgrade.
Note that by "new" and "2.01" I refer to the new patch available here; by "old" and "2.0" I refer to the upgrade CD orderable here.
- Q: Do I need to install the "old", non-free, 2.0 upgrade? Or, can I install 2.01 right on my WM2003SE device?
A: Unfortunately, you must install 2.0 first (and purchase it if you still don't have it). The new, 2.01 upgrade must be installed on top of 2.0. I don't think HP will ever release a stand-alone 2.01 upgrade CD meant for WM2003SE devices. However, don't be afraid of the two upgrades: it has gone with all the hx4700 users flawlessly, as opposed with, say, the A12 upgrade for the Dell Axim x51v (see this for more info if interested). All you need to do is making sure you don't use any USB cable extender or hub (the main causes for upgrade-time Blue Screen of Death (BSOD) screens.)
UPDATE (09/09/2006): according to Brighthand forum member duc748bip, now, the purchasable upgrade is already 2.01. That is, you won't need to do double updates. I still keep the original version of the answer in cases you want to use the original version of the 2.0 update.
- Q: Is 2.01 worth installing at all? The old, 2.0 upgrade really sucked, even with your hacks and patches.
A: It depends on your usage patterns and the need for running "legacy", pre-WM5 applications incompatible with WM5. The new version is about 60% better when it comes to compaction (see the reports here and here on this), the biggest enemy of WM5-upgraded hx4700 (and, for that matter, Dell Axim x50(v)) users. This means the dreaded filesys.exe compaction "kicks in" 60% less times than with 2.0. Also, it contains the CF patch built-in. I'd say it's pretty usable, particularly if you follow my advice on not putting anything in the built-in storage and try to relocate everything from there to storage cards.
- Q: Has the incompatibility problem (they just wouldn’t start, unlike on other WM5 devices) with many games and some utilities been fixed?
A: Nope (see this for more). A lot of games (still) don't run, while they did under WM2003SE. This is one of the biggest problem with the hx4700 WM5 upgrade(s). If you want all your games run on your hx4700, do not upgrade to WM5 at all.
- Q: Is the NavPointService bug fixed?
A: Now, it behaves considerably better, as opposed to version 2.0. However, particularly if you keep many games on your PDA, you may still want to disable it as described in here.
- Q: Do I need to apply your cache tweaks?
A: Nope, not any more. The I/O system seems to be well-optimized now.
- Q: Do I need to use your filesys.exe throttler?
A: I'd say no. It caused lockups with several users with the 2.0 and, therefore, its usability was pretty limited. Now that filesys.exe is far friendlier in the new version, I'd say the filesys throttler need not be used.
- Q: Do I need to apply your Compact Flash patch?
A: Not any more - now, CF works just great.
- Q: Do I need to apply the "fake server hack" (see bullet 5 in this article)?
A: Absolutely! It's a must in the new version too if you don't have any Exchange servers to be accessed.
- Q: All in all, which hacks must be applied?
A: Disabling NavPointService is recommended; the fake server hack is a must (if you don't access Exchange servers from your handheld).
- Q: Is there any way I could make filesys.exe only run when I don't actively use the Pocket PC / it's on AC power / I explicitly let it run?
A: There isn't. Unfortunately, attempts at this (with the Dell Axim x50 series) have been unsuccessful too. You have to live with the filesys.exe compactions whenever filesys sees it right to "kick in". Right now, there is no way of fine-controlling it.
- Q: Will Dell Axim x50(v) users also receive a similar upgrade?
A: I don't think so. Dell seems to have completely abandoned the Dell Axim x50(v) WM5 upgrade. Hope I turn to be wrong though.
- Q: You've mentioned in your previous articles (for example this one) the old, 2.0 upgrade had the (errorenous) sector size of 4096 bytes, instead of the recommended 512 bytes. Has this been fixed?
A: Yes, it has been fixed, as can also be seen in this screenshot.
- Q: You've also mentioned in your previous articles on the 2.0 version (for example here) that the built-in DockWare application is buggy and must be updated to avoid compaction. Does the new, 2.01 version of ROM contain the new latest DockWare, or, should I, as before, install the freely downloadable update?
A: This issue has also been fixed - 2.01, unlike 2.0, contains the latest DockWare version. That is, you don't need to upgrade DockWare. However, as before, I really recommend entirely getting rid of the (built-in storage-based and, therefore, deletable) factory-default DockWare input files in \My Documents\My Pictures\ to reduce the load on the built-in flash ROM (and, consequently, the time spent at compactions / the frequency of them). Also, if you don't use it, consider removing (or relocating to a storage card) \Program Files\Dockware\DockWare.exe too for exactly the same reasons.
- Q: Earlier, the homepage of all the available hx4700 upgrades mentioned we need to install an earlier, WM2003SE-related extended battery patch. How come it isn't incorporated in this ROM upgrade?
A: The Extended Battery upgrade is very old and only applies to the old, 1.10 upgrade, NOT the 2.01 one. Listing this old upgrade as an additional, recommended upgrade for 2.01 users was HP's mistake. Now, HP has fixed the mistake. That is, you don't need to install the upgrade at all.
- Q: What sources of WM5 & hx4700-related information are there?
A: I recommend the following three threads on the 2.01 upgrade: Pocket PC Thoughts, MobilitySite and BrightHand.
General hx4700- (or, with PPCT, HP-) related information (some of it being related to WM5) can be found in the following forums: BightHand, MobilitySite, PPCT.
- Q: What about WM5 hx4700-specific compatibility information? Where do I find additional information on the WM5 compliance of current (and past) releases?
A: In all my software reviews, roundups and comparisons, I (along with my other Pocket PC’s) also test the given title on my WM5-upgraded hx4700. That is, make sure you follow my (new) reviews and roundups for hx4700 compatibility information.
- Q: I'm not sure I should switch from WM2003SE to WM5 at all. I'm still afraid of the reduced effectiveness of the device, the spontaneous hard resets and battery depletion.
A: Battery depletion can be easily fought by just applying the fake server trick (see bullet 8). As far as your other questions are concerned: it all depends on how you use your device. If you follow my tutorials and do what's listed in the list that follows, you can effectively reduce the time filesys.exe spends at compaction, which means a dependable and reliable hx4700. Then, I'd certainly recommend the upgrade (if other problems - for example, the somewhat limited compatibility with pre-WM5, "legacy" applications and games - aren't a showstopper). The list:
- do NOT install any application in the main storage or put any file in there
- relocate everything possible from there (for example, the ActiveSync-synchronized Outlook mail - tutorial here)
- use RAM disks whenever possible (please do read this article for more information), particularly for desktop-based program installation, quick tests and browser caches
- Login or Register to post comments
Printer-friendly version
You can use any WM5-compliant (!) backup program (I recommend either Spb Backup 1.5 or Sprite Backup 5.1) to clone the device. In no way should you use the trial version of Spb Clone because, after restoration, the restored system bug you with registration messages every 15 minutes.
It's, however, very important that the ROM version of the two devices must be the same. (Both 2.0, OR 2.01.)
Cloning devices this way is absolutely safe even if some people say the opposite.
Dunno about the AOL client - is it using the built-in Messaging client? if yes, then, it can be relocated.
Throttling-wise: it may be beneficial and may work. However, as I've received mixed reports on it, I don't, generally, recommend it any more to avoid future/possible lock-ups.
Yes, it has the new version; no need for upgrading.
You'll need to use for example chrismalone's HX4700 BootLoader Tool to re-flash your device. See http://www.mobilitysite.com/forums/showthread.php?t=30741 for more info.
Go to Settings/ System / HP Asset Viewer / Version. Does your ROM version read "
2.01.05 ENG" as can also be seen in this screenshot?It seems none of these hacks help (not even the fake server hack). The same happens to me too from time to time when there are memory cards inserted in the device. Therefore, I tend to pop up my SD card before suspending the device.
Have you applied the fake server hack? (bullet 8)
1. did you suspend your device (in order for the changes to be flushged to the flash ROM) and, then, reset it?
2. It's doing the same on my PPC - it's suspending pretty slowly.
Yes, apply the hack, and just turn it off before you ever reset it. This makes sure the (internally) modified WinCE system database is flushed back to the flash ROM.
Nope, don't really have.
BTW, don't you have a Today plug-in (for example, weather / news / RSS services) that regularly wakes up the device? Did you try disabling all custom Today plug-ins (if any)?
The latter, I'm pretty sure. Disable all Today plug-ins and check it again.
HP ProtectTool: I'm absolutely sure it doesn't cause the problem.
I don't think IrDA would have to do anything with this problem.
What Today plug-ins / other services do you have? Could you list them?
Also, could you list your notification queue? The best way to do this is with SKTools. Just export the list to a file and dump the contents here so that I can tell if it contains some info on a rogue 3rd party app.
Nope. With 2.01, you don't need to use any of them. Just make sure you remove the Navi registry key and apply the fake server hack.
Brad, please see THIS for the new links.
Joseph,
I DO think the problems would be alleviated and the compaction time / frequency (greatly) reduced (but not entirely fixed - with the slow-to-write flash ROM, it's plain impossible with the hx4700) if you moved all the possible stuff out of the main storage.
Just delete the link from \Windows\Start Menu\Programs