Re: Can't call WlxSASNotify in a separate thread! Alternative ways?
From: Mauro Iorio (dodomio_at_tiscalinet.it)
Date: 12/18/04
- Next message: Colin Grant: "AcquireCredentialsHandle failing with SEC_E_INTERNAL_ERROR for domain logon"
- Previous message: David Cross [MS]: "Re: Security Error"
- In reply to: Mzito: "Re: Can't call WlxSASNotify in a separate thread! Alternative ways?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 18 Dec 2004 21:50:36 +0100
The message window works fine.
Thank you all, Mauro.
"Mzito" <nosend@nohost.nodomain> ha scritto nel messaggio
news:eyMD03R4EHA.3840@tk2msftngp13.phx.gbl...
> Or maybe try using a synchronization event
>
> <Sektor> wrote in message news:ONfaxaO4EHA.3236@TK2MSFTNGP15.phx.gbl...
>>
>> "Mauro Iorio" <dodomio@tiscalinet.it> wrote in message
>> news:e6v9IuD4EHA.3120@TK2MSFTNGP12.phx.gbl...
>> > Thanks for the reply.
>> > I think it's a good idea, but I can't figure out what will happen when
> the
>> > winlogon desktop is hidden. I mean: the dialog windows stays on the
>> > winlogon destkop, which is hidden in loggedon state. Will the thread be
>> > able to post messages to this window when the user's desktop is active?
> I
>> > have no idea of it.
>>
>> Yes the thread will be able to to post messages always, also when the
> user's
>> desktop is active.
>>
>> > Anyway I'm going to try it immediatly.
>> >
>> > Thanks again, Mauro.
>>
>> Bye Sektor.
>> >
- Next message: Colin Grant: "AcquireCredentialsHandle failing with SEC_E_INTERNAL_ERROR for domain logon"
- Previous message: David Cross [MS]: "Re: Security Error"
- In reply to: Mzito: "Re: Can't call WlxSASNotify in a separate thread! Alternative ways?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]