> If you are up for it, you can also try the steps at
> http://BevHoward.com/ASync.htm#RAPI but they are far from perfect.
>
> fwiw, I gave up and went back to 2003se
I was basically doing that manually already (don't have to end
wcescomm.exe because that doesn't spike CPU usage) :)
As a FYI I don't even notice the performance decrease with the AMD X2,
I'm really liking this system. I've had several things that started
looping, and I've never felt the slowdown (just upgraded from a P4
1.6GHz and there's a BIG difference :) The processor seems to have so
much raw power with it's multi-processing that anything that starts to
have problems just happens on the one core and the other core keeps the
system peppy.
> Among other things, windows media player on the desktop relaunches
> activesync and rapimger and I found that since I used wmp, I was
> contstantly having to execute my killwcescomm batch file to regain
> reasonable use of my computer... got to the point where when it dawned
> that things were slow, I would run it without even looking to see if
> async had restarted.
I forgot about that, I do have Media player 11 Beta for XP, I wonder if
it's the problem. I wonder if anyone is having the problem with Media
player 10.
I think I'll probably just downgrade to AS 3.8 and go from there. Less
headache :) Thanks Beverly
David Troesch
Stiffler - 13 Aug 2006 18:35 GMT
> I forgot about that, I do have Media player 11 Beta for XP, I wonder if
> it's the problem. I wonder if anyone is having the problem with Media
> player 10.
Hmm. I am having the same problem with rapimgr.exe using 100% CPU. I have a
2.6Ghz single core laptop w/ 1.5 GB RAM WinXP Home SP2 and ActivSync 4.2.0
(Build 4876).
rapimgr.exe runs on startup whether I have any USB plugged in or not. I
haven't sync'd for about a dozen reboots either (nobody probably cares about
that one). But I DO have WMP11 Beta! It sounds like this isn't the culprit
however because I'd guess that Noni isn't running WMP11 Beta given that
he/she has an apparently stock Dell Inspiron.
Each time I reboot, I stop the rapimgr.exe process with the Windows Task
Manager and haven't had any problems yet. In fact, just in the process of
getting my ActivSync version for this post, I had to start ActivSync... and I
look in Windows Task Manager now only to find rapimgr.exe using 0% CPU and
5,788 K Mem Usage! so you're on good behavior now, are ya?
So the temporary fix seems to be to kill the process but surely there must
be something better.
-Stiffler