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
[EMAIL PROTECTED] wrote:
On Mon, 14 Nov 2005 09:48:50 +0100, Uwe Bonnes
<[EMAIL PROTECTED]> wrote:
"Cihan" == Cihan Altinay <[EMAIL PROTECTED]> writes:
Cihan> Hi, When running G-Ware[1] I get a lot of these:
Cihan> fixme:key:GetQueueStatus QS_ flags (4000) are not handled
On Mon, 14 Nov 2005 09:48:50 +0100, Uwe Bonnes
<[EMAIL PROTECTED]> wrote:
"Cihan" == Cihan Altinay <[EMAIL PROTECTED]> writes:
Cihan> Hi, When running G-Ware[1] I get a lot of these:
Cihan> fixme:key:GetQueueStatus QS_ flags (4000) are not handled
Cihan> Interestingly I coul
> "Cihan" == Cihan Altinay <[EMAIL PROTECTED]> writes:
Cihan> Hi, When running G-Ware[1] I get a lot of these:
Cihan> fixme:key:GetQueueStatus QS_ flags (4000) are not handled
Cihan> Interestingly I couldn't find any information about what the flag
Cihan> 0x4000 is meant t
Hi,
When running G-Ware[1] I get a lot of these:
fixme:key:GetQueueStatus QS_ 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 tha
