Re: Speeding up wineserver synchronization objects with shared memory

2001-02-24 Thread Robert O'Callahan
I was just reading WWN and saw this discussion. Here's a wacky idea that might or might not work. The basic idea is to grant ownership of each mutex to one Win32 process at a time. Let any thread grab the mutex quickly if it belongs to the process that owns the mutex. If its process does not

SHLocalAlloc

2001-02-24 Thread J.Brown (Ender/Amigo)
I've been trying to get the Windows ME version of internet explorer/explorer to load successfully under Wine.. However, it runs into an unimplemented SHLocalAlloc function in shell32. This appears to be an undocumented function, or I'm looking in the wrong place... has anyone got a patch or API

Re: Speeding up wineserver synchronization objects with shared memory

2001-02-24 Thread Ove Kaaven
On Thu, 22 Feb 2001, Robert O'Callahan wrote: Then on some other thread in the same address space that serves wineserver requests: There's no such thread, and will never be such a thread (having the wineserver calling into client threads is an inherently unstable design).

Re: SHLocalAlloc

2001-02-24 Thread Eric Pouech
"J.Brown (Ender/Amigo)" wrote: I've been trying to get the Windows ME version of internet explorer/explorer to load successfully under Wine.. However, it runs into an unimplemented SHLocalAlloc function in shell32. This appears to be an undocumented function, or I'm looking in the wrong

Re: Speeding up wineserver synchronization objects with shared memory

2001-02-24 Thread Ove Kaaven
On Sat, 24 Feb 2001, Robert O'Callahan wrote: Ove Kaaven wrote: On Thu, 22 Feb 2001, Robert O'Callahan wrote: Then on some other thread in the same address space that serves wineserver requests: There's no such thread, and will never be such a thread (having the wineserver

Re: Speeding up wineserver synchronization objects with shared memory

2001-02-24 Thread Robert O'Callahan
Ove Kaaven wrote: On Thu, 22 Feb 2001, Robert O'Callahan wrote: Then on some other thread in the same address space that serves wineserver requests: There's no such thread, and will never be such a thread (having the wineserver calling into client threads is an inherently unstable

Re: Speeding up wineserver synchronization objects with shared memory

2001-02-24 Thread Robert O'Callahan
Ove Kaaven wrote: On Sat, 24 Feb 2001, Robert O'Callahan wrote: Ove Kaaven wrote: On Thu, 22 Feb 2001, Robert O'Callahan wrote: Then on some other thread in the same address space that serves wineserver requests: There's no such thread, and will never be such a thread (having

Re: Speeding up wineserver synchronization objects with shared memory

2001-02-24 Thread Joerg Mayer
Ove, On Sat, Feb 24, 2001 at 12:06:07PM +0100, Ove Kaaven wrote: There's no such thread, and will never be such a thread (having the wineserver calling into client threads is an inherently unstable design). I think I've read this before, when the topic was FindWindow. IIRC that thread never