During the upgrade of my ipaq hx2410 with (WM2003se-> WM5 1.00.00L -> WM5 1.00.00H -> WM5 1.00.02H ->WM 6) procedure my device has lost some asset info. To be more precise, Serial #: and Model ID: fields in HP Asset viewer are blank. It has happend probably somewhere between WM5 1.00.00H and WM5 1.00.02H. Now my ipaq is not able to comunicate with Activesync (4.5) or HP flasher. Although it is properly recognisable by system drivers, every attend to connect ends with endless loop of Activesync or freeze of HP flasher. Even in pre bl. mode i get an invalid SKU message or freeze.
I’m able to cheat the HP flasher by hotswapping the ipaq with an identical (WM6) unit and upload whatever rom I want. Only downgrade to 2003SE results with proper communication with Activesync (4.5). .... but it doesn’t help with asset info recovery.
Can anybody help?
Related
I've got a Qtek 2020 with TomTom 5.21.
I also have a Dell Axim X51 with the same problem.
After installing TomTom via the .cab files the created Today-plugin doesn't work. Installing on this WM5 devices wasn't easy.
After tapping the today-plugin I get a beep from the device but TomTom doesn't start. It will only start via Program Files.
Anyone any idea?
Greetz from Holland
BB
The TomTom Today-Plugin just links to a startmenu-entry of TomTom. Make shure you have a "TomTom.lnk" in "\windows\Startmenu" and/or in "\windows\Startmenu\Programs". (If not - copy it to there)
It also maybe that the Plugin links to the "TomTom.exe " -> check the installation-path. Possibly you have it in "\Programs" and the Today-Plugins expects it in "\Programme"
Greetz from Berlin
I have an HP iPaq rx3715 (WM2003), which I used to sync with ActiveSync 3.8. Never any problems.
Nowadays I also have a MDA Vario (WM5), which can only be synced with ActiveSync 4.1, so I installed 4.1. Synching the Vario is no problem.
Now... The problem... I can no longer sync my iPaq.
The iPaq needs ActiveSync 3.8, the MDA Vario needs ActiveSync 4.1.
There is no way to have both versions installed on the same PC. I tried.
I even tried to install the different versions on seperate XP accounts. Didn't work either.
In theory I could install 3.8 on PC1, and install 4.1 on PC2.
The problem with that is that the PST-file is located on PC1, and not on PC2. For security-reasons it is not possible to run a copy of the PST on PC2. (Besides... It wouldn't not be a very handy workaround.)
Now... How can I sync the above two devices on the same PC, with the same PST-file?
Anyone???
AS 4.1 includes 3.8 in it.
When you sync 2003, all icons etc become old type - I do it everyday - sync my universal and sync my Benq p50
No issues.
Well.... My rx3715 won't sync on AS4... But AS4 is needed for the MDA Vario... :|
Anyone else any ideas?
Why do the iPAQ need AS 3.8? Alls WM2003 Devices are working with AS 4 too.
Hello Sjaakman!
Unfortunately, i don't know an alternative way to sync a PPC with a PC, but I can tell you that I've successfully synchronized a rx3715 with a PC running XP SP2 and AS 4.1 many times, infect I even managed to sync a Dell with WM 2002 with the same PC no problem.
I suggest you make sure you have the latest version of AS and that the installation is clean. It is possible that while trying to install the previous version you somehow damaged the current installation which is why it wont sync.
Good luck!
I tried and I tried and I tried.... And I could never get it to work...
I just now tried a clean install of AS... And what do you know... It works :shock: :roll:
Thanks.
lutzs said:
Why do the iPAQ need AS 3.8? Alls WM2003 Devices are working with AS 4 too.
Click to expand...
Click to collapse
Not sure how you got it to work.
I was never able to get my iPAQ h6315 to sync with AS 4.1. After struggling with it a while, I noticed that in fact, Microsoft states the following on the AS 4.1 download page:
- ActiveSync 4.1 is the latest sync software release for Windows Mobile 5.0 devices.
- For customers using Windows Mobile 2003 or 2002 powered devices, please continue using ActiveSync 3.8.
For customers using Windows Mobile 2003 or 2002 powered devices please continue using ActiveSync 3.8
Click to expand...
Click to collapse
I just wanted to add that I believe this statement means you don't need to upgrade unless you have a WM5 device.
If any one is interested I can tell you from experience that I've successfully synchronized devices with OSs WM2002, WM2003 / SE (including iPaq 6315), WM5 and CE 4.2 (not PPC) with a clean install of AS 4.1 and no tweaking done. So far it appears to be completely backward compatible.
Just for the record: I am not trying to defend MS. But if you have a similar problem to the one mentioned in this thread, you should check the AS installation before breaking your head trying to find another solution. The problem could also be on the device side, and may be solved by hard reset (not pleasant but effective).
I have been living with Windows Vista Beta 2 Build 5384 since June. This is an "evoluting version" that is upgraded/improved/corrected from time to time. All in all I should not have done that and stay with XP Pro but I was not sure how to unistall it. However, the Windows Mobile Sync function works well with my HTC prophet (Qtek S200) which is equipped with ROM 2.15.23.27 WME, 3/9/06, Radio version 02.19.21, Protocol version 4.1.13.09, ExtROM version 2.15.13.121. Last week, after a little research, I decide to upgrade with RUU_Prophet_2151327_22113102_022021_Dopod_PDAMobizEdition_v101 though I was not that sure that it was really an upgrade (I was looking for the Push-Email feature). In any event, the upgrade program did not work. I am stuck. It stopped regularly with a code error [202]: Th update utility (V2.5.2) could not connect to the PDA Phone. All comments are welcome
I can only speak for the Blue Angel on this - but I couldn't upgrade it using Vista because Activesync is used for the connection. However, in Vista, Activesync has been replaced and it cannot be installed on Vista. In the end, I got out a spare HDD, dropped it into my pc, installed XP FLP and upgraded using that instead.
RC1 of Vista (Build 5600) is now out to certain testers and I can confirm that Mobile Center is no longer present/doesn't work properly. This is also true of 5536 and 5552. The PDA will show up in Computer and you can browse it - but there was no utility to sync. Activesync can again, not be installed either.
Windows Mobile Device Center
With respect to the Sync function, I recall that the "Windows Mobile Device Center" that has replaced in Windows Vista the ActiveSync 4.1 of the past did not work until I triggered the firewall options. After it worked well though the Notes included in the Contacts (MC Outlook) are not synchronised correctly. Hence, my surprise for the impossibility to upgrade s explained above.
Hi Guys,
I know that the i320 isn't an HTC device, but I have sucessfully managed to get blackberry connect up and running on my Wizard and my work is hopefully about to supply me with an i320.
I realise that it's a smartphone and not a PPC, but I believe that there is some interoperablity between the two in WM5.
So my question is, will I be able to use the BB Connect that I use on my Wizard (downloaded from the ftp site) on the i320 or does anyone know of any varients for the smartphone platform?
Cheers!
anyone?
Even a little guidancee would be good! Thanks!
If you find a solution, let us all know
We are talking about this on the S620 aka Dash SP forum as well. We know that a SP client came out for WM 2003 in South Africa on the Vodacom network, but we haven't see one since. Where oh where, if at all, is the WM5 for Smartphone BB Connect client?
Here is the original BB Connect cab file for WM 2003
It would only install on a Moto MPx220 device running WM 2003 and gave a uncertified device error when I tried it on any other device. Any programmers out there want to give it a shot and change the cab file so it does not require a particular device to install on?
This one installs. I couldn't get it to work on my MPx200 w/ 2003.
http://forum.xda-developers.com/showthread.php?p=961343#post961343
Hi,
I have imate jamin. I have installed ms reader on my device (on the main memory) but on activation I get the message from the ms site that the software is workable only on wm3 to 5, whereas my device is wm5.
Can anyone help fix the problem please?