Hmmm

I can only do one successful synchronisation/connection for each session of ActiveSync. If I removed my iPaq from the docking cradle, and plug it back on later, it won't connect to the ActiveSync.


What I need to do is, kill/terminate WCESCOMM.EXE process, and run another copy then later plug my iPaq back on. Only this way, it will get connected and synchronised.


I find this pretty strange, anyone else is experiencing this similar problem? ???

Ronan, I did that both with 38xx on and off.

It is more related to the desktop part, because if I restart the WCESCOMM.EXE process, and plug my iPaq back on, it will reconnect properly again.


I hope this is one of the bug that Compaq/MS found that will be fixed through SP1. The ActiveSync docking/synchronising connection problem. (??) ???

Seems quiet! *Anybody out there?
Yes, I too have had the "weird" ActiveSync problem, much as you've described---no particular improvement after SP1, for me at least. *Very disappointing to have so much difficulty with two Microsoft products communicating. *My desktop OS is Win2Kpro, which I love (for the most part), except when it refuses to sync with the PPC. *At home (WinME on a notebook), I had ONE successful sync back in December. *Good thing I don't need the iPaq for business as most of you likely do.
So much NONSENSE with AS3.5. *I know what connection should work but the clever "Get connected" app tries to point me in directions that are useless, again and again! *I need to use USB, that's what the cradle is plugged into, that's what I use for other gizmos; but, clever "Get connected" has to cycle through all possible routes. *duh...
For me, it is a happy day when, if I am so fortunate to make a connection, that the connection does not drop after some period. *Hours with a connection? *Now, that's something to write home about!
Simply should not be thus. *
*iPaq 3835* *love the machine, not sure yet about the OS! *Any helpful suggestions welcomed!

Pako.. mysteriously, my ActiveSync 3.5 connection with my iPaq 3850 is now working sweet. Occassionally, AS3.5 will quit itself when I put my iPaq back onto the cradle. No biggie, I just undock the iPaq and run AS3.5 again.

What I found out is that, I reinstall the driver for WCEUSB (in device manager) to version 1.0.0.6 (i think, on Windows XP).

I noticed there is a new WCEUSB driver but it crashed on me on the next reboot to Windows XP, so I will give that a skip. WCEUSB version 1.0.0.6 (comes with iPaq CD?) works okay... so try reinstall that.

Make sure you have iPaq docked and Win2k/XP detected it, and the device manager shows up with WCEUSB device. Then perform driver reinstall from there.

Good Luck.

(alternatively, you can use the technique I suggested at the first post)

Kel.

Upgrade to Activesync 3.6 and that should resolve all your problems !