GetQueueStatus: unknown flag 0x4000

[Cihan Altinay]

Hi,

When running G-Ware[1] I get a lot of these:
   fixme:key:GetQueueStatus QS_xxxx flags (4000) are not handled

Interestingly I couldn't find any information about what the
flag 0x4000 is meant to be. Could that be another undocumented
flag like QS_SMRESULT? The program works so it can't be that
important :-) but I thought it's worth mentioning...

Cheers,
Cihan

[1] http://www.clearone.com/docs/downloads/G-Ware5.0.6.zip (20MB)

[Uwe Bonnes]

> > > > > "Cihan" == Cihan Altinay  writes:

Cihan> Hi, When running G-Ware[1] I get a lot of these:
    Cihan> fixme:key:GetQueueStatus QS_xxxx flags (4000) are not handled

Cihan> Interestingly I couldn't find any information about what the flag
    Cihan> 0x4000 is meant to be. Could that be another undocumented flag
    Cihan> like QS_SMRESULT? The program works so it can't be that important
    Cihan> :-) but I thought it's worth mentioning...

I get this only when running with native ole32/oleaut32/rpcrt4 (XP )

On Mon, 14 Nov 2005 09:48:50 +0100, Uwe Bonnes  
 wrote:
> > > > > > "Cihan" == Cihan Altinay  writes:
> Cihan> Hi, When running G-Ware[1] I get a lot of these:
> Cihan> fixme:key:GetQueueStatus QS_xxxx flags (4000) are not handled
>
> Cihan> Interestingly I couldn't find any information about what the  
>
> flag
>     Cihan> 0x4000 is meant to be. Could that be another undocumented flag
>     Cihan> like QS_SMRESULT? The program works so it can't be that  
> important
>     Cihan> :-) but I thought it's worth mentioning...
>
> I get this only when running with native ole32/oleaut32/rpcrt4 (XP )

I get ,literally, hundreds using builtin ole of 0.9.1

[Cihan Altinay]

[e-mail] wrote:
> On Mon, 14 Nov 2005 09:48:50 +0100, Uwe Bonnes  
>  wrote:
> > > > > > > "Cihan" == Cihan Altinay  writes:
> > Cihan> Hi, When running G-Ware[1] I get a lot of these:
> > Cihan> fixme:key:GetQueueStatus QS_xxxx flags (4000) are not handled
> >
> > Cihan> Interestingly I couldn't find any information about what 
> >
> > the  flag
> >     Cihan> 0x4000 is meant to be. Could that be another undocumented flag
> >     Cihan> like QS_SMRESULT? The program works so it can't be that  
> > important
> >     Cihan> :-) but I thought it's worth mentioning...
> >
> > I get this only when running with native ole32/oleaut32/rpcrt4 (XP )
>
> I get ,literally, hundreds using builtin ole of 0.9.1

The program doesn't work with native ole so I can't confirm but after
some debugging it is clear now that ole32.dll is using flags like 0x4000
and 0x4400. I guess they are 'magic' flags for ole.

[Andreas Mohr]

Hi,

On Tue, Nov 15, 2005 at 09:39:48AM +1000, Cihan Altinay wrote:
> The program doesn't work with native ole so I can't confirm but after
> some debugging it is clear now that ole32.dll is using flags like 0x4000
> and 0x4400. I guess they are 'magic' flags for ole.

So they're probably trying to check for OLE related messages there.
You could try to run a message spy app on Windows around the time that it
does the GetQueueStatus() call with the 0x4000 flag.
Maybe you manage to discover which kinds of OLE related messages
GetQueueStatus() probably checks for...
(then send suspected message types to a window and then run GetQueueStatus()
0x4000 to see whether it triggers)

Andreas