LAP on device

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi everyone,

I'm porting an authentication application from 4.2 to 5.0 and thanks to Marcus Perryman's weblog, it is just simple.
I managed to have it run on an emulator quickly, but, when I tried it
on a real CE 5.0 device (both a qtek 9000 and a qtek 9100) I had some troubles :
- I flashed my dll and a small application in charge of doing the LassReloadConfig(), and called it : the reload succeeded
- the enrollement part was fine
- I did a soft-reset and expected to see the verifyUser screen. Instead, when waking up, the Pocket PC screen flashes, ... but seems to work. I can authenticate myself, and get to the today screen, while the screen continues to flash.
When I get there, there is no way the screen stops flashing, I just have to make a hard-reset.

I signed my dll and application using a developpment certificate (TEST USE ONLY - Sample Privileged Root for Windows Mobile SDK) and I got no popup (saying the solution comes from an untrusted provider) when registering my LAP to the system.

I tried with the one provided by Marcus Perryman, but the Pocket PC reacts the same.

The fact that the test on emulator is good makes my think of a certificate problem, but I thought with the privileged key, there won't be problem, am I right ?

As anyone ever seen this ?
.

Relevant Pages