on those devices security is a panel not an application. to lock
device correctly, you need to enqueue a specific char, which you can
look up in the docs.

On 9/17/07, Christopher Stamper <[EMAIL PROTECTED]> wrote:
>  I am having some trouble using sysAppLaunch to launch security and lock the
> device. It works just perfect on all devices, until E2, TX and 700p. What is
> wrong? Here is what I am using:
>
> static void LockIt()
> {
>         Err                                  err;
>         UInt16                             cardNo;
>         LocalID                            dbID;
>         UInt32                              resultP;
>         DmSearchStateType         searchState;
>
>          err = DmGetNextDatabaseByTypeCreator (true, &searchState,
> sysFileTApplication, sysFileCSecurity, true, &cardNo, &dbID);
>
>            if (err)
>               FrmAlert(1000);
>            else
>              err = SysAppLaunch (cardNo, dbID, 0, sysAppLaunchCmdSystemLock,
> NULL, &resultP);
>
> }
>
> I think the problem is the &resultP, but why then would it work fine on my
> m515, and TE, z22, Z31, etc sims? I just get some kind of memory errors...
> Sometimes the sim just crashes.
>
> I think it's probably really simple, can anyone please help?
>
> --
> Christopher Stamper
>  [EMAIL PROTECTED] --
> For information on using the ACCESS Developer Forums, or to unsubscribe,
> please see http://www.access-company.com/developers/forums/
>


-- 
Best Regards,
Dmitry Grinberg
(847) 226 9295

-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please 
see http://www.access-company.com/developers/forums/

Reply via email to