Can anyone offer an explanation as to why UPMEULGN seems to halt the system
message queue when called from a PM program?. Called from a VIO program it does
not halt the message queue. I AM callin it from a separate thread, not from my
main WindowProc. The thread that it runs in does not create a message queue
until it is ready to post back to the main thread. The main thread keeps on
going when the logon thread gets blocked on UPMEULGN. It somehow still manages
to halt message passing activity in bursts while it is negotiating with the
remote domain controller. UPMEULGN logging onto a local server does not halt
this way. I have been very careful with my app not to do anything but interface
handling in the main thread and to put ANYTHING that can get blocked into
seperate threads. This problem makes all of that effort for naught during the
logon portion of the program. Note that I am using UPMEULGN and NOT UPM functio

that displays a window. Does this call somehow hook the message queue in a way
that I need to be aware of? If so does it NEED to be in my main thread?

Please forgive my inexperience with PM, but I am faced with learning Lan Server
programming AND PM programming at the same time. I have been programming PM for
4 months now and it feels like a lifetime. My Mountain Dew consumption has
doubled lately... 

___
 * MR/2 1.52 NR * Curiosity didn't kill the cat, I got him with a 12 gauge..

--- WILDMAIL!/WC v4.00h