🚀 go-pugleaf

Ok guys, not a virus - would like to think that i've asked enough stupid 
questions here that people would know i'm not a virus writter.

I just didn't want to distract from the problem by going into a long 
explaination of the exact problem.  Basically I'm bug fixing a GinaStub 
system that we have had in place for the last 9 months.  I've just recently 
started to recieve some errors.  On careful examination and scowering MSDN, 
I have found that the winlogon exported funtions are not thread safe.  In my 
main dll / thread I had a procedure that called a specific winlogon exported 
function.  My polling thread would call this procedure.  However, this would 
seem to be in the context of the polling thread, not the main thread.

So this is the reason for the message window.  The polling thread would 
SendMessage to the hidden window which would call the procedure in the 
context of the main thread.

I've got a basic implimentation working now except it causes some strange 
problems in Windows 2k3 i.e. seems to cause certain services not to start.

If i simply wanted to hide a window i would do it with ShowWindow....

Mike


"JD" <nospam@nospam.com> wrote in message 
news:448c53ad$1@newsgroups.borland.com...
>
> Bob Gonder <notbg@notmindspring.invalid> wrote:
>>
>> [...] Best way to prevent that is to not do it this way.
>
> Sounds like a damn virus to me.
>
> ~ JD
>