🚀 go-pugleaf

"JF Jolin" <jfj@nospam.com> wrote in message
news:op.t0ikcozljr09w3@localhost...

> call WlxLoggedOnSAS() from msgina.dll

Do not call GINA's functions directly.  WinLogon calls GINA's functions
internally when needed.  There is no point in calling GINA's functions
directly, because there is no way to manually pass the return values to
WinLogon to perform the requested actions.  Instead, you should be calling
WlxSasNotify(), which is exposed by WinLogon and is the same call that GINA
makes when it wants to notify WinLogon of something happening, ie:

    WlxSasNotify(hWlx, WLX_SAS_TYPE_CTRL_ALT_DEL);

Unfortunately, you run into the same problem that Emmanuel has already
discovered - obtaining the correct hWlx value to use.  There is no direct
way to do that because it is a value that only WinLogon knows when it loads
GINA at system startup.  You can't fake it, since GINA will use that value
to call back into WinLogon when needed.  You would have to write your own
GINA DLL to replace (or at least be a proxy stub for) the default GINA DLL.
Then WinLogon will load your DLL and pass the correct hWlx value to it at
startup, and you can store it away for later use.


Gambit