🚀 go-pugleaf

Leo,
Thank you for the link to the information.  I'm just wondering how Terminal
Services were enabled on the development workstations.  It sounds like it is
a concerted effort to enable them.  Also, the default of "localizing" kernel
objects is a real concern since it effectively breaks interprocess
synchronization.  A default of "global" kernel objects seems like it would
be safer.

Paul Mac

"Leo Havm�ller" <leh@-nospam-rtx.dk> wrote in message
news:3f3b244f@newsgroups.borland.com...
> "PaulMac" <machiave@i-stat.com> wrote in message
> news:3f3a81c8@newsgroups.borland.com...
> > In using MUTEX objects, I came across something unexpected.  Given a
> Windows
> > GUI app and a Service app, if the same named MUTEX is accessed, both
> > applications can acquire it when the other has already done so.
However,
> if
> > both applications are service apps or both are GUI apps, then the proper
> > synchronization occurs.
> >
> > It has been my understanding that MUTEXes, being kernel objects, are
> > "global" to a system.  So, why am I seeing this behavior?
>
> The GUI app lives in a windows station whereas the service does not.
> You need to add "Global\" to the mutex name. See "terminal services"
under:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/createmutex.asp
>
> Leo Havm�ller.
>
>