🚀 go-pugleaf

"Mike Collins" <mikec@kr8.co.uk> wrote in message
news:3f95d1b2@newsgroups.borland.com...

> I don't understand this. The logon dialog is within MSGINA.dll,
> the logon information (username, password, domain etc) all originale
> from MSGINA.dll, however my stub method WlxLoggedOutSAS
> appears to recieve the call and relays it back on to MSGINA.dll.

You altered the Registry to tell the OS that your DLL is the GINA to use, so
it is going to call your GINA for everything, not the original GINA.  What
you do inside your own GINA is your own business, you can do pretty much
whatever you want.  You just happen to have set up your WlxLoggedOutSAS()
function (and I assume the other functions as well) to be a straight
pass-through of data from the OS to the original MSGINA and vice versa,
where the data is passed as-is, unmodified.  As far as either are concerned,
the OS may as well have loaded MSGINA directly instead of your own GINA.
But it didn't, it loaded your GINA instead and as such expects your GINA to
service the OS's requests.

> I just don't understand this - MSGINA.dll has no idea or information
> about myGINA.dll.

Why would you think that it would?


Gambit