Re: WLX_DLG_SAS (101)

From: Eric Perlin [MS] (ericperl_at_online.microsoft.com)
Date: 10/30/04

  • Next message: Dave: "Re: Question about SID" 
    Date: Fri, 29 Oct 2004 15:56:08 -0700

    WLX_DLG_SAS is used in the call to EndDialog when the DialogProc of the top
    dialog box doesn't handle a SAS message. 

    -- 
Eric Perlin [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.
---
"philippe broccard" <pbroccar@yahoo.com> wrote in message
news:O2C4q4bvEHA.3200@TK2MSFTNGP14.phx.gbl...
> During the GINA hook operation in the WlxLoggedOutSAS function as a
> response to the insertion of a smartcard token, a call is made to the
passed
> function WlxDialogBox to place a custom PIN dialog on screen. The screen
> momentarily goes to blue and then back to the CTRL-ALT-DEL dialog and the
> return code is WLX_DLG_SAS (101). This code does not match any action that
> would normally be returned and I can not find any information on what to
do
> with the code. The expected action would be similar to
WLX_SAS_ACTION_LOGON,
> which would cause the gathering of the information for logon from the
token.
> When the token is removed and then reinserted, normal operation results.
> This inconsistent operation happens on the second time the token is
inserted
> after a successful logon attempt. The third, fourth... attempts result in
> success.
>
> Also, occassionally after a successful logon attempt, the desktop is void
of
> icons and the start bar. Sometimes this can be cleared by displaying the
> task manager, others, logout and relogon corrects the problem. This
happens
> inconsistently, but the traces through the GINA hook show normal
operation.
>
> Any help on either of these conditions would be appreciated.
>
> Phil.
>
>
  • Next message: Dave: "Re: Question about SID"