LMWin Software & Cradle Driver (32/64bit Version) Which Files are available for LMWin (FLink) and Microsoft ActiveSync?ĬASIO USB Cradle Driver (32bit) for Microsoft ActiveSync Start > Communication > For LMWin (FLink) and Microsoft ActiveSync / WMDC Q: Software Development Windows CE & Windows Mobile

The LAP has WS_EX_ABOVESTARTUP as exstyle set and DS_SETFOREGROUND | WS_VISIBLE as style.For LMWin (FLink) and Microsoft ActiveSync / WMDC It flickers through my LAP and all tap events don't go to my LAP. I made sure this is the case (actually i didn't have to change anything since that policy was set already) and still face the problem.Īnother mysterious behaviour i see when the user craddles his device is that my LAP gets displayed but tapping on the screen brings the today screen (or any other active application) for some milliseconds to the foreground and back. Checking the SDK documentation revealed that the policy SECPOLICY_LASS_DESKTOP_QUICK_CONNECT (0x1032) has to be set to POLICYVAL_LASS_DESKTOP_QUICK_CONNECT_ALLOWED (0x1). Those devices still expect the user to authenticate themselves on the device. Unfortunately this doesn't work as expected on WindowsMobile 6.x devices. Instead he can enter his password in a small popup window displayed by ActiveSync which works fine for WindowsMobile 5.0. The next time the user craddles his device he doesn't have to authenticate on the device. In order to achieve this i just set the password with ::SetPassword(LPWSTR lpszOldpassword, LPWSTR lspzNewPassword). I would like to offer users the option to authenticate themselfs with an ActiveSync password if on craddling their devices.

I'm working on a LAP that replaces the default password application for WindowsMobile 5.0, 6.0 and 6.1.

Microsoft activesync windows mobile 6.1