Hi
I have found a regression in wine. a strange one. What is a policy
about posting such regressions, here on malling list?
(Or is regression is worth enough to post it here?)
I don't play that particular game on wine and it's "minor" bug - but i
have found (via bitsect) that
"user32: Cache the
James Hawkins wrote:
>
> On Nov 17, 2007, at 6:24 AM, Paul Vriens <[EMAIL PROTECTED]>
> wrote:
>
>> Hi,
>>
>> I've opened a bug (which if fixed now btw) and the regression
>> testing page at
>> http://wiki.winehq.org/RegressionTesting said "Also be sure to add
>> the author of
>> the patch
I compiled wine on Solaris using a .spec provided by the people of
http://pkgbuild.sourceforge.net/spec-files-extra/
Maybe contact them ?
My version runs quite nice as far as i can see.
Cheers
I am trying to read the memory of another process with ReadProcessMemory but I
can only get it to work when I use VirtualAllocEx to commit the region of
memory - problem is (as you very well know) that VirtualAllocEx initializes the
region with 0s. So my question is how do I get ReadProcessMemo
On Nov 17, 2007 11:45 AM, James Hawkins <[EMAIL PROTECTED]> wrote:
>
>
> On Nov 17, 2007, at 9:34 AM, "Vijay Kiran Kamuju"
> <[EMAIL PROTECTED]> wrote:
>
> > There is a test in derive_key function that fails.
> > If I put a if condition to make it a todo_wine, it looks loke a hack
> > and its ugly
On Nov 17, 2007, at 9:34 AM, "Vijay Kiran Kamuju"
<[EMAIL PROTECTED]> wrote:
> There is a test in derive_key function that fails.
> If I put a if condition to make it a todo_wine, it looks loke a hack
> and its ugly
> As that function is used alot.
>
> ---
> VJ
>
> On Nov 16, 2007 5:45 PM, Ree
On Nov 17, 2007, at 6:24 AM, Paul Vriens <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I've opened a bug (which if fixed now btw) and the regression
> testing page at
> http://wiki.winehq.org/RegressionTesting said "Also be sure to add
> the author of
> the patch to the CC".
>
> So this is what I d
There is a test in derive_key function that fails.
If I put a if condition to make it a todo_wine, it looks loke a hack
and its ugly
As that function is used alot.
---
VJ
On Nov 16, 2007 5:45 PM, Reece Dunn <[EMAIL PROTECTED]> wrote:
>
> On 16/11/2007, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote
Dave Cartright wrote:
> I am trying to read the memory of another process with
> ReadProcessmemory and I can only get it to work when I commit the
> entire region I want to read with VirtualAllocEx - but as you probably
> know when I do this it initializes the entire memory region to 0s.
> So my
Dave wrote:
> I am trying to read the memory of another process with
> ReadProcessmemory and I can only get it to work when
> I commit the entire region I want to read with VirtualAllocEx -
> but as you probably know when I do this it
> initializes the entire memory region to 0s.
> So my question i
On Nov 17, 2007 3:44 PM, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
>
> "Paul Vriens" <[EMAIL PROTECTED]> wrote:
>
> > I've opened a bug (which if fixed now btw) and the regression testing page
> > at
> > http://wiki.winehq.org/RegressionTesting said "Also be sure to add the
> > author of
> > th
"Paul Vriens" <[EMAIL PROTECTED]> wrote:
> I've opened a bug (which if fixed now btw) and the regression testing page at
> http://wiki.winehq.org/RegressionTesting said "Also be sure to add the author
> of
> the patch to the CC".
>
> So this is what I did.
>
> Should that line be removed from
Hi,
I've opened a bug (which if fixed now btw) and the regression testing page at
http://wiki.winehq.org/RegressionTesting said "Also be sure to add the author
of
the patch to the CC".
So this is what I did.
Should that line be removed from the wiki or do we generally want the author to
be C
On Sat, Nov 17, 2007 at 01:58:31PM +0100, Stefan Dösinger wrote:
> Hello,
> Did anyone change #winehackers to require an invite? What was the reason for
> this?
Sorry, we had a kiddie problem.
It is back to normal now.
Ciao, Marcus
Am Samstag, 17. November 2007 13:58:31 schrieb Stefan Dösinger:
> Hello,
> Did anyone change #winehackers to require an invite? What was the reason
> for this?
It's sorted out already
signature.asc
Description: This is a digitally signed message part.
On 16/11/2007, Vijay Kiran Kamuju <[EMAIL PROTECTED]> wrote:
> ChangeLog
> --
> Add tests for RSA_AES provider in rsaenh
>
> Note:
> ---
> Some tests might fail as there is no RSA_AES provider in wine.
> These will be fixed once the implementation is in place, which will be
> sent n
Hello,
Did anyone change #winehackers to require an invite? What was the reason for
this?
Thanks,
Stefan
signature.asc
Description: This is a digitally signed message part.
Hi,
Roderick Colenbrander schreef:
> They should get updated. In case of Solaris there are some bugs which prevent
> it from running I think. In case of Windows someone needs to update the
> package. It is very useful to use some of the wine dlls (wined3d for
> instance) or tests on Windows.
>
> It appears that the links for the Windows and Solaris versions on the
> winehq downloads page are very, very old. Since they're no longer
> maintained, we should just remove them, yes?
>
> Thanks,
> Scott Ritchie
>
They should get updated. In case of Solaris there are some bugs which prevent
19 matches
Mail list logo
