Thursday, August 17, 2006, 8:46:12 AM, Vitaliy Margolen wrote:
> ChangeLog:
> user: Pass hook handle to the destination thread. Call server to get hook
> information for inter-thread hooks.
> Currently Wine has a major problem with LL hooks (low level hooks) when
> second hook is installed in a se
On 8/22/06, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
Tuesday, August 22, 2006, 7:56:00 PM, James Hawkins wrote:
> Hi,
> More and more installers are expecting the MSI service to exist, or at
> least be installable using msiexec /regserver. This patch is the
> first step in fixing bug 5540.
Tuesday, August 22, 2006, 7:56:00 PM, James Hawkins wrote:
> Hi,
> More and more installers are expecting the MSI service to exist, or at
> least be installable using msiexec /regserver. This patch is the
> first step in fixing bug 5540.
> +if (!scm)
> +{
> +fprintf(stderr, "Fail
On 8/7/06, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
"Elijah Newren" <[EMAIL PROTECTED]> wrote:
> Anyway, the returning from fullscreen mode bug makes perfect sense,
> and I'm pretty sure I know the cause: metacity tries to return the
> window to the size it was before it was fullscreened, and
Hi,
> You are right - with native dmusic,dmloader,dmime,dmsynth the game runs.
> I also had some dmusic/dmime output with the heap error, but that
> looked quite normal.
>
> Strange though that my regression testing had a different result.
> I did it just like the GitWine entry in the wiki suggests
I think the DEVELOPERS-HINTS contents should really be moved to the
Wiki, it would be a lot easier to keep up to date there. Does anybody
feel like doing that?
--
Alexandre Julliard
[EMAIL PROTECTED]
That would be a good place for it. It would be easier to locate. The
developer's guide, resou
Am Tue, 22 Aug 2006 08:56:05 +0200
schrieb Stefan Dösinger <[EMAIL PROTECTED]>:
> This is odd, I did a regression testing and it came up with Jason
> Greens dynamic shader constant patch as the first bad commit. While
> this sounds odd for a d3d7 game it could happen because of broken
> stateblock
"Matt Finnicum" <[EMAIL PROTECTED]> writes:
> Hi,
> Is there something wrong with this patch / a reason it's not being accepted?
>
> Sorry if this might have been answered this on IRC last night - X died
> while I was away, so I'd have missed it.
When resending a patch, especially a patch by some
> All you need to do is to change this:
> http://source.winehq.org/source/dlls/ntdll/thread.c#L218
> to look like:
>
> NtAllocateVirtualMemory( NtCurrentProcess(), &addr, 0, &size,
> MEM_RESERVE | MEM_COMMIT, PAGE_READONLY );
Ah, indeed. Thank you, that solves it for me.
--Juan
Hi,
Is there something wrong with this patch / a reason it's not being accepted?
Sorry if this might have been answered this on IRC last night - X died
while I was away, so I'd have missed it.
Thanks,
--Matt Finnicum
On 8/19/06, Matt Finnicum <[EMAIL PROTECTED]> wrote:
Hi,
I've cleaned up / re
"Tom Wickline" <[EMAIL PROTECTED]> writes:
> Changelog: add newly implemented dlls and update http links
I think the DEVELOPERS-HINTS contents should really be moved to the
Wiki, it would be a lot easier to keep up to date there. Does anybody
feel like doing that?
--
Alexandre Julliard
[EMAIL P
> > I did that, I created a new field in the PDEVICE structure and used two
> > new ExtEscape codes (SET_FLAGS/GET_FLAGS), but Alexandre doesn't want to
> > add new ExtEscape codes..
> > That's why I hacked even more on wine and moved the wgl implementation
> > to x11drv... and there they are, my o
Vitaliy Margolen wrote:
Tuesday, August 22, 2006, 1:56:20 AM, Juan Lang wrote:
--- Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
0x7ffe is KSHARED_USER_DATA and 0x2c0 is (not even sure how to get
what is at this offset). You can see it's declaration in
include/ddk/wdm.h
Tuesday, August 22, 2006, 1:56:20 AM, Juan Lang wrote:
> --- Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
>> 0x7ffe is KSHARED_USER_DATA and 0x2c0 is (not even sure how to get
>> what is at this offset). You can see it's declaration in
>> include/ddk/wdm.h
> Thanks Vitaliy. So this is supposed
> I did that, I created a new field in the PDEVICE structure and used two
> new ExtEscape codes (SET_FLAGS/GET_FLAGS), but Alexandre doesn't want to
> add new ExtEscape codes..
> That's why I hacked even more on wine and moved the wgl implementation
> to x11drv... and there they are, my old patches
James Liggett <[EMAIL PROTECTED]> writes:
> +/* fall back to he KDE hints if the WM doesn't support XEMBED'ed
> + * systrays */
> +
> +/* Put the window back within the screen so it will be mapped */
> +SetWindowPos( data->hwnd, NULL, 0, 0, 0, 0, SWP_NOZORDE
Roderick Colenbrander wrote:
> If we could set a pbuffer flag in there and retrieve it in wglMakeCurrent it
> would work. I fear that this can only be done in a clean way if it code would
> be in x11drv :(
>
I did that, I created a new field in the PDEVICE structure and used two
new ExtEscape
Stefan Dösinger <[EMAIL PROTECTED]> writes:
> @@ -245,11 +252,12 @@ void
> IDirectDrawImpl_Destroy(IDirectDrawImpl *This)
> {
> IDirectDrawImpl *prev;
> +DDOBJ_LOCK(This);
You shouldn't need locking in Destroy, if the refcount is zero no one
else can be using the object.
> fo
> Hello
> > Your pixel format patches caused a regression in half-life 1 for me with
> > the fglrx drivers.
>
> The same happend to me with opensource Intel drivers on a:
> $ lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM
> Integrated
> Graphics Device (rev 0
--- Robert Shearman <[EMAIL PROTECTED]> wrote:
> It might be easier to implement the necessary functions in userenv,
> depending on which ones it uses.
Thanks for the suggestion. I think not in this case; it's calling unnamed
ordinal 149.
--Jua
Juan Lang wrote:
Hi folks, I'm trying to debug an access (by native userenv.dll in my case,
but also by MS Money 2006) to address 0x7ffe02c0.
It might be easier to implement the necessary functions in userenv,
depending on which ones it uses.
--
Rob Shearman
--- Vitaliy Margolen <[EMAIL PROTECTED]> wrote:
> 0x7ffe is KSHARED_USER_DATA and 0x2c0 is (not even sure how to get
> what is at this offset). You can see it's declaration in
> include/ddk/wdm.h
Thanks Vitaliy. So this is supposed to be a boolean for some processor
feature? I guess it doesn
Hello
> Your pixel format patches caused a regression in half-life 1 for me with
> the fglrx drivers.
The same happend to me with opensource Intel drivers on a:
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)
> It refuses t
23 matches
Mail list logo
