On Mon, 13 Oct 2008 19:13:09 -0400, Bill <> wrote:
>Todd Allcock wrote:
>> At 13 Oct 2008 10:29:48 -0500 Beverly Howard [Ms-MVP/MobileDev] wrote:
>>
>>> >> It takes up very little memory. <<
>>>
>>> But it is also active enough it can hog most of your computers other
>>> resources...
>>
>> To be fair, Ed was referring to the Activesync process on the WinMo device,
>> not the PC. The device's version of Activesync is very unobtrusive
>> comparatively.
>>
>>
>>
>>
>Thanks to all of you for the assistance,
>
>Todd's correct...I have no issue with ActiveSync on my PC...it just
>seems to sit there in my toolbar in gray, waiting until I connect the
>iPaq. But unless the tip from the user below pans out about the Time
>Zones, I'll just bite the bullet and live with it always active on the
>iPaq device.
I don't know any stand-alone program to stop ActiveSync. But I do know
how a program can stop it:
HWND hWnd = ::FindWindow( L"ActiveSync", NULL );
if (hWnd)
::SendMessage( hWnd, WM_CLOSE, 0, 0 );
I feel guilty/silly saying I don't have time to create such a utility.
But maybe someone else will find time or a cooperative programmer.
I think this simple program would solve only part of the problem:
letting a human shut down ActiveSync when that human sees it is
started. One possible way to automate would be a program that wakes up
everyone so often to shut down ActiveSync. This would be only slightly
more complicated to write. It would use very few CPU cycles, but the
memory might be significant. Would it use fewer resources than
ActiveSync?
>Regards,
>Bill
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 400
Boston, MA 02116
www.penfact.com